I am also guessing that the supplied driver does not retrieve that data if it is not requested by an application. I thought the 1ms interrupt happened on NT as well, but I’m a Unix guy Apr 17, 4. USB on Windows is still not quite solid. Other possibilities would be RS and RS Apr 16, 2. Are you thinking of RS?
|Date Added:||26 March 2015|
|File Size:||61.16 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
PIC gear from Dontronics. Paul Reply Start a New Thread.
Recommended USB/Serial Adapters
Apr 16, 2. Whilst being a fairly good device, I still have found a few problems which others may have experienced.
Sign in Sign in Remember me Forgot username or password? Eontronics about using Can? The other problem is that if I restart the PC, and leave the serial device connected, WinXP thinks it has found a new serial mouse. Other possibilities would be RS and RS Apr 17, 6.
Has anyone seen this before?
When “0” Space is transmitted, the RS transmitter is also enabled driving the line actively to the “0” “dominant” state. Sure, it sucks, but that’s how you have to do it donhronics you’ve got a crippled UART. If drivers don’t work on certain Windows versions and the manufacturer doesn’t have new drivers, you have to find a different USB-RS adapter. Apr 17, 7. Usb to driver problem. Arduino Robotics Lonnie Honeycutt.
Is there a recommended USB to serial (DB9) converter lead for C-Bus?
On 12 Feb You must log in or sign up to reply here. The Embedded Systems Experts http: Apr 17, 4. Apr 20, The main problem is that I am dealing with serial devices that continuously transmit data. Apr 17, 5. That’s what the Windows driver guys I know told me. What I have found is that if I try re-opening the com port straight away then the second time is successful. There are various ways it could be implemented, such as waiting a character time after the final interrupt to give the last character a chance to get out, or sending an extra dummy character into the queue and switching off RTS before it gets sent.
Its always a potential problem.
When a “1” Mark bit is transmitted, the transmitter is switched off and the termination resistors pull the line to the “1” “recessive” state. You’ll need to choose a username for the site, which only take a couple of moments here.
It checks the shfit-register empty status bit every millisecond until true, then drops RTS. My guess is without checking with an oscilloscope that the Windows driver simply drops the DTR when the last character has been transferred from the Tx register to the Tx shift register, which on style chips can generate an interrupt. If so is there an easy work around?
Apr 16, 3. This works quite well for short lines a few meters at moderate speeds. On Wed, 11 Feb I thought the 1ms interrupt happened on NT as well, but I’m a Unix guy