We have an application that listens on a com port for data, but in certain
scenarios, which we cannot yet reproduce, after a couple of hours the
serialEvent() is simply no longer called when data is sent to the com port.
We have connected another third-party software AccessPort to the same device
using a serial cable splitter, and it receives the data without problem.
This is not a problem however at any of our other installations, only this one.
We are using a RS232 to USB converter.
Using:
JSSC 2.6.0
Windows 8 Pro (64)
What are the scenarios that could cause this to happen? Do we need to send some
kind of heart-beat to keep the com connection active? What is the best practice
for long term com connections?
Thanks for any help!
Original issue reported on code.google.com by rudi.mi...@gmail.com on 15 Dec 2013 at 9:53
Original issue reported on code.google.com by
rudi.mi...@gmail.com
on 15 Dec 2013 at 9:53