A couple of things you could try:
C:> mode com1 Status for device COM1: ----------------------- Baud: 1200 Parity: None Data Bits: 7 Stop Bits: 1 Timeout: OFF XON/XOFF: OFF CTS handshaking: OFF DSR handshaking: OFF DSR sensitivity: OFF DTR circuit: ON RTS circuit: ON c:> help mode Configures system devices. Serial port: MODE COMm[:] [BAUD=b] [PARITY=p] [DATA=d] [STOP=s] [to=on|off] [xon=on|off] [odsr=on|off] [octs=on|off] [dtr=on|off|hs] [rts=on|off|hs|tg] [idsr=on|off] Device Status: MODE [device] [/STATUS] ...
Write the command sequence into a file using a (binary capable) editor. Then send that sequence to the device: copy file.bin /b comN: /b
Then retrieve the response using the same technique: copy comN/b response.bin /b. Then you can check the file to see what you get.
By configuring the port using mode, you can start with a slow transmission rate (say 1200), and whatever handshaking (rts=on or xon=on) until you get reliable transmission. Then slowly ramp the baud rate until it starts to fail or you reach the maximum.
Once you've figured out what the device is capable of, you can automate the process using the module .
In reply to Re^3: Win32:SerialPort not reading all characters
by BrowserUk
in thread Win32:SerialPort not reading all characters
by sxmwb
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |