Closed klues closed 6 years ago
https://github.com/asterics/AsTeRICS/pull/221/files
changes in functionality:
CIM.mode.raw
, default false
, if set to true
only raw connections can be used, but CIM scanning is used in order to get mapping cimID -> comPortName
other changes regarding performance and stability:
CIMPortManager.rescan()
is started in own thread, and therfore does not block starting of AsTeRICS. If a model wants to use a CIMPort, methods retrieving the ports are blocking until rescan has finished.sendPacket
) is started in own threads and has a default timeout of 2 seconds -> prevents freezing of AsTeRICS if sendPacket
failsCIMIdentifyPortController
IOException
occurs and therefore do not produce endless exceptionsDid tests with the following CIM devices:
Testing steps I did:
Acceleration_test.acs
as autostartAcceleration_test.acs
starts and works without errorsAcceleration_test.acs
works without problemsDigitalIn_test.acs
with digital in moduleRemoteMouse_test.acs
with HID actuator module (bluetooth)Acceleration_test.acs
works againSo all looks good, except of (10). The reason for not finding a re-connected device again is probably that the close()
method of the RXTX-library does not correclty close the device in every case and therefore rescan() fails because of an "already in use" error. After restarting ARE, the devices are found again, normally.
merged https://github.com/asterics/AsTeRICS/pull/221 -> closing issue
We encountered some strange situations, where CIM Port scanning or usage of CIM Ports caused AsTeRICS to crash. Unfortunately we could not reproduce all errors or causes of errors. These errors occur:
These issues should be resolved or at least improved.