I’m wondering if anyone else has noticed an uptick in errors when using the
RECEIVE BUFFER command to read from a serial port? Our application does a lot
of serial port communication. We also log all errors. There has been a
_significant_ uptick in errors that occur on the following line of code since
we moved to v17:
RECEIVE BUFFER($tBuffer)
The error number reported is always -1. But if I look in the extra information
the error is always one of these:
Error #: 995
Resource: WI32
Message: The I/O operation has been aborted because of either a thread exit or
an application request.
Error #: 22
Resource: WI32
Message: The device does not recognize the command.
Users simply reconnect to the port and all is fine for awhile
Anyone know what might be going on?
Thanks.
--
Cannon.Smith
Synergy Farm Solutions Inc.
Aetna, AB Canada
<can...@synergyfarmsolutions.com>
<www.synergyfarmsolutions.com>
**********************************************************************
4D Internet Users Group (4D iNUG)
Archive: http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:4d_tech-unsubscr...@lists.4d.com
**********************************************************************
