Hi,
I have a problem on openhab2 with a busware CUL to read and write to FS20 devices on a raspberry 2.
Sometimes once or twice a day the busware device (to start with connected as ttyACM0) seem to discconnect from the USB interface and reappears again and comes up as ttyACM1. So I set a udev rule so that the device would be
accessable via ttyUSB-01 pointing to ttyACM0 or ttyACM1…
Starting openhab2 with the link to ttyUSB-01 works, but once the device disconnects, it seems like openhab cannot find the new device, though using the link.
2017-02-09 19:34:07.479 [ERROR] [port.cul.internal.AbstractCULHandler] - Can't write report command to CUL
java.io.IOException: Input/output error in writeArray
at gnu.io.RXTXPort.writeArray(Native Method)
at gnu.io.RXTXPort$SerialOutputStream.write(RXTXPort.java:1211)[181:com.neuronrobotics.nrjavaserial:3.12.0.OH]
at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)[:1.8.0_121]
at sun.nio.cs.StreamEncoder.implWrite(StreamEncoder.java:282)[:1.8.0_121]
at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:125)[:1.8.0_121]
at java.io.OutputStreamWriter.write(OutputStreamWriter.java:207)[:1.8.0_121]
at java.io.BufferedWriter.flushBuffer(BufferedWriter.java:129)[:1.8.0_121]
at java.io.BufferedWriter.flush(BufferedWriter.java:253)[:1.8.0_121]
at org.openhab.io.transport.cul.internal.AbstractCULHandler.requestCreditReport(AbstractCULHandler.java:285)[204:org.openhab.io.transport.cul:1.9.0]
at org.openhab.io.transport.cul.internal.AbstractCULHandler.writeMessage(AbstractCULHandler.java:311)[204:org.openhab.io.transport.cul:1.9.0]
at org.openhab.io.transport.cul.internal.AbstractCULHandler.access$0(AbstractCULHandler.java:297)[204:org.openhab.io.transport.cul:1.9.0]
at org.openhab.io.transport.cul.internal.AbstractCULHandler$SendThread.run(AbstractCULHandler.java:59)[204:org.openhab.io.transport.cul:1.9.0]
This is the udev rule I am using:
SUBSYSTEM=="tty", ATTRS{idVendor}=="03eb", ATTRS{idProduct}=="204b", SYMLINK+="ttyUSB-01"
Any suggestion?