search for: baudrat

Hello If I try to open COM in a app. I got: BaudRate 9600 fixme:comm:SetupComm insize 1024 outsize 1024 unimplemented stub BaudRate 5760 fixme:comm:SetupComm insize 131072 outsize 8192 unimplemented stub err:comm:SetCommState baudrate 5760 BaudRate 5726 fixme:comm:SetupComm insize 1024 outsize 1024 unimplemented stub err:comm:SetCommState baudrate...

...umm wrote: >>>> >>>> 115200 = 0x1C200 so "SERIAL 1 115200" should be setting the bit rate >>>> to 9600 and the flow control to 0x200. >>>> >>> >>> I really hope that is not true. >> >> Should "SERIAL port [[baudrate] flowcontrol]" actually be "SERIAL port >> [baudrate [flowcontrol]]"? >> > > Yes. Was there ever a time that the behavior was "SERIAL port [[baudrate] flowcontrol]" or has it been misdocumented for years? -- -Gene

...ki:/usr/libexec/nut# ./bcmxcp -DDDDD -a DSAups Network UPS Tools - BCMXCP UPS driver 0.23 (2.4.3) RS-232 communication subdriver 0.17 0.000000 send_to_all: SETINFO driver.parameter.port "/dev/ttyUSB0" 0.000035 debug level is '5' 0.008369 Attempting to autodect baudrate 1.603672 Receive error (PW_COMMAND_START_BYTE): 0!!! 2.604114 Receive error (PW_COMMAND_START_BYTE): 0!!! 3.604528 Receive error (PW_COMMAND_START_BYTE): 0!!! 3.604547 No response from UPS on /dev/ttyUSB0 with baudrate 1200 5.199170 Receive error (PW_COMMAND_S...

...t;hpa at zytor.com> wrote: > On 05/27/2013 04:49 AM, Gene Cumm wrote: >> >> 115200 = 0x1C200 so "SERIAL 1 115200" should be setting the bit rate >> to 9600 and the flow control to 0x200. >> > > I really hope that is not true. Should "SERIAL port [[baudrate] flowcontrol]" actually be "SERIAL port [baudrate [flowcontrol]]"? -- -Gene

...:file:CreateFileA Couldn't open device 'com4'! fixme:dosfs:DOSFS_OpenDevice device open COM3 not supported (yet) err:file:CreateFileA Couldn't open device 'com3'! trace:comm:GetCommState handle 132, ptr 0x40596080 trace:comm:GetCommState OK trace:comm:GetCommState bytesize 8 baudrate 110 fParity 0 Parity 0 stopbits 1 trace:comm:GetCommState ~IXON ~IXOFF trace:comm:GetCommState CRTSCTS trace:comm:BuildCommDCBAndTimeoutsA (com2:115200,n,8,1,0x40596080,(nil)) trace:comm:BuildCommDCB16 (com2:115200,n,8,1), ptr 0x40596004 trace:comm:BuildCommDCB16 baudrate (110) trace:comm:BuildCom...

Hello, GNU Emacs suffers from poor performance because the baud rate in HP-UX 11.00 is set to 300 baud when connecting via OpenSSH 2.1.1p1. Can anybody tell why? Maybe ssh should modify some termio bits when logging in? Regards, Ulrich

Hello All ! i'm purchased sangoma card A-101. i connect to E1 with MF/R2 signalling. but card don't work. negotiation with E1 fail. please help me to correct it. i dont' know some parameters such as: MTU, BAUDRATE Thanks Tin Trung -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20050509/e0753093/attachment.htm

...2 to it with a shutdown time of 2 minutes. This is my nut configuration in /etc/nut/ups.conf : [aasgaard] driver = bcmxcp port = /dev/ttyS0 This is what happens when i try to start the driver: -----------START----------- robert at tor:~$ sudo upsdrvctl start Attempting to autodect baudrate Communications with UPS lost: Receive error (Requested only mode command): e7!!! Communications with UPS lost: Receive error (Requested only mode command): e2!!! Can't connect to the UPS on port /dev/ttyS0! Driver failed to start (exit status=1) -----------STOP----------- I'v...

Hi Matthijs, > Arnaud. >After some trial and error, i found out that the HP R3000 XR ups's we have >can be used with Network Ups Tools. >This using the bcmxcp driver. > >Note that in the code of this driver (line 1420) , the Baudrate is fixed to >9600 baud. >to connect to a serial HP R3000 XR ups one needs to change this to 19200 >baud. > >ideally, this should be an config option/autodetect. As i have not the >time/knowledge to make it so, >and as we only have the HP R3000 XR ups's here, i will leave i...

...to communicate at 9600, and "autodetects" a rate of 19200: babylon4:root:/opt/nut/etc:9 # ../bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - BCMXCP UPS driver 0.21 (2.4.1) RS-232 communication subdriver 0.17 No response from UPS on /dev/tty00 with baudrate 9600 Attempting to autodect baudrate Connected to UPS on /dev/tty00 with baudrate 19200 If I set baud_rate=19200 in ups.conf, that starts right up: babylon4:root:/opt/nut/etc:11 # ../bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - BCMXCP UPS driver 0.21 (2...

...ontroller 2.0.5 Network UPS Tools - BCMXCP UPS driver 0.11 (2.0.5) Communications with UPS lost: Error executing command Communications with UPS lost: Error executing command Communications with UPS lost: Error executing command Communications with UPS re-established Connected to UPS on /dev/ttyS0 baudrate: 9600 Model = HP R3000 XR 3000VA Firmware = Inve:01.09 Netw:03.60 Shutdown delay = 120 seconds # It all seems to work but the initial errors or warnings concern me. I'm running stable 2.05 built from source. Thanks, Greg.

...>>>>> 115200 = 0x1C200 so "SERIAL 1 115200" should be setting the bit rate >>>>> to 9600 and the flow control to 0x200. >>>>> >>>> >>>> I really hope that is not true. >>> >>> Should "SERIAL port [[baudrate] flowcontrol]" actually be "SERIAL port >>> [baudrate [flowcontrol]]"? >>> >> >> Yes. > > Was there ever a time that the behavior was "SERIAL port [[baudrate] > flowcontrol]" or has it been misdocumented for years? > It's ju...

...nil)) trace:file:get_dos_device L"COM1" -> "/home/met/.wine/dosdevices/com1" trace:file:CreateFileW returning 0x9c fixme:comm:GetCommProperties (0x9c 0x4132b414 ) trace:comm:GetCommState handle 0x9c, ptr 0x4132b454 trace:comm:GetCommState OK trace:comm:GetCommState bytesize 8 baudrate 38400 fParity 0 Parity 2 stopbits 1 trace:comm:GetCommState ~IXON ~IXOFF trace:comm:GetCommState fOutxCtsFlow 1 fRtsControl 2 trace:comm:GetCommState fOutxDsrFlow 0 fDtrControl1 trace:comm:GetCommState CRTSCTS trace:comm:GetCommTimeouts (0x9c,0x4132b470) trace:comm:BuildCommDCBAndTimeoutsA (38400,...

.../class/input/input4 (input) UDEV [1215983089.770017] add /class/input/input4/event2 (input) This is what can be found in dmesg: usb 1-1: new low speed USB device using ohci_hcd and address 4 usb 1-1: configuration #1 chosen from 1 choice input: Ver 1.0 USB To RS232 Interface (V1.0) BaudRate 2400bps as /class/input/input4 input,hidraw0: USB HID v1.00 Gamepad [Ver 1.0 USB To RS232 Interface (V1.0) BaudRate 2400bps] on usb-0000:00:0f.2-1 Gamepad...? Sounds like fun. I tried these drivers: megatec - no success, I couldn not find any virtual serial ports being created (like with usbse...

...at was a fluke. If I restart the driver, the communication is regained for a few minutes but then drops again. Below are excerpts from running '/lib/nut/bcmxcp -DDD -a pw9120'. Any ideas? Many thanks, Chris 0.000000 debug level is '3' 0.000659 Attempting to autodect baudrate 1.591977 Receive error (PW_COMMAND_START_BYTE): 0!!! 2.592977 Receive error (PW_COMMAND_START_BYTE): 0!!! 3.593976 Receive error (PW_COMMAND_START_BYTE): 0!!! 3.593992 No response from UPS on /dev/ttyS0 with baudrate 1200 5.184976 Receive error (PW_COMMAND_STA...

...ote the different thread-ids). In the wine trace (done with +comm +file) you see the following ------------------------------------- trace:file:CreateFileA opening device 'COM1' trace:comm:GetCommState handle 268, ptr 0x421666f8 trace:comm:GetCommState OK trace:comm:GetCommState bytesize 8 baudrate 9600 fParity 1 Parity 0 stopbits 2 trace:comm:GetCommState ~IXON ~IXOFF trace:comm:GetCommState ~CRTSCTS trace:comm:BuildCommDCBAndTimeoutsA (baud=9600 parity=o data=8 stop=2,0x421666f8,(nil)) trace:comm:SetCommState handle 268, ptr 0x421666f8 trace:comm:SetCommState bytesize 8 baudrate 9600 fPari...

....11 (2.0.5) Communications with UPS lost: Error executing command Communications with UPS lost: Error executing command Communications with UPS lost: Error executing command Communications with UPS lost: Error executing command Communications with UPS re-established Connected to UPS on /dev/ttyS0 baudrate: 19200 Communications with UPS lost: Receive error (Request command): 9!!! Communications with UPS lost: Receive error (Request command): 9!!! Communications with UPS lost: Receive error (Request command): 9!!! Communications with UPS lost: Error executing command Could not communicate with...

.../dev/ttyS0 desc = "Powerware Prestige 9 EXT" baud_rate = 2400 And when I start the driver I get root% upsdrvctl -v start Network UPS Tools - UPS driver controller 2.0.4 exec: /lib/nut/bcmxcp -a powerware Network UPS Tools - BCMXCP UPS driver 0.10 (2.0.4) Connected to UPS on /dev/ttyS0 baudrate: 2400 Model = Powerware Prestige 1000VA Firmware = 01.06 Shutdown delay = 120 seconds Communications with UPS lost: Receive error (Request command): 9!!! Communications with UPS lost: Receive error (Request command): 9!!! Communications with UPS lost: Receive error (Request command): 9!!! Comm...

...behavior might be evident to developers, but not to users. _ Line 406: Suggestion: Similarly to the suggestion for 'Line 135' above, explicitly mentioning the particular case of 'ONTIMEOUT label' might be helpful for newcomers. _ Line 429: Suggestion: Correct "SERIAL port [[baudrate] flowcontrol]" to "SERIAL port [baudrate [flowcontrol]]" _ Line 598: This comment is not about documentation (so it's off-topic here), but about a request / reminder to fix the 'ASCII24+LSS16+newline' issue still present in Syslinux 5.10 (since 5.00). _ Line 825: Sug...

...und] section of your config file. fixme:opengl:wglSwapIntervalEXT (0),stub! fixme:comm:SetupComm insize 1024 outsize 1024 unimplemented stub trace:comm:SetCommTimeouts (0xc8,0x4069f964) trace:comm:GetCommState handle 0xc8, ptr 0x4069f978 trace:comm:GetCommState OK trace:comm:GetCommState bytesize 8 baudrate 38400 fParity 0 Parity 0 st opbits 1 trace:comm:GetCommState IXON ~IXOFF trace:comm:GetCommState fOutxCtsFlow 0 fRtsControl 1 trace:comm:GetCommState fOutxDsrFlow 0 fDtrControl1 trace:comm:GetCommState ~CRTSCTS trace:comm:SetCommState handle 0xc8, ptr 0x4069f978 trace:comm:SetCommState bytesize 8...