Hi everybody.
Ok, here's the situation:
I recently bought the following equipment:
- 1 x RJ-45 Coupler
- 1 x Adaptor Cable RJ45 to RJ11 3ft (1m)
- 2 x Humidity/Temp Case
- 2 x Humidity/Temp
- 1 x 1-Wire USB Adaptor
They've been sitting on the shelf for a week before I installed them on site.
The configuration is as follows:
[Computer] --> [1-wire USB Adaptor] --> [RJ11 to RJ45 cable] --> [RJ45 coupler] --> Cat5e RJ45 cable, 5 m (~16 ft) --> [Humidity/Temp Sensor] --> Cat5e RJ45 cable, 10 m (~ 33 ft) --> [Humidity/Temp Sensor]
As you now might expect, both sensor boxes are jumpered so they are using parasitic power.
Everything was going according to my plan: I installed the drivers (version 4.03 beta) with the USB Adaptor disconnected. Once successfully installed, I plugged the Adaptor in and ran the "Default 1-wire Net" program and pressed auto-detect. The Adaptor was detected successfully in USB1.
Obviously the next step was to check whether I get any readings out from the sensors, so I ran the "OneWireViewer" program. All the sensors were detected as they should.
I selected the first DS2438 device on the list and clicked on the "Real-Time Temperature" tab. It successfully polled the temperature once and then threw the following exception:
ERROR: TemperatureViewer (D9000000F1D81C26) Error reading device! com.dalsemi.onewire.OneWireException: 1-Wire Adapter communication exception
ERROR: OneWireViewer (null) 1-Wire exception: com.dalsemi.onewire.adapter.OneWireIOException: native TMEX error -12
After throwing those exceptions, it suddenly read the temperature once again, this time successfully three times in a row and then it started throwing the same exceptions again and never recovered from it afterwards. Restarting the program revealed 0 devices. Only way to recover from this situation is either disconnecting the USB Adaptor, disabling and then enabling it from the Device Manager or by machine reboot. Doing so brings the sensors back but only until they're polled for readings again.
I'm using a program called "LogTemp", but it suffers the same symptoms as seen in the OWV.
The computer specs are as follows:
- ASUS CUSL2 rev. 1.02
- Pentium III 866MHz
- 512MB RAM
- 40GB HDD
Believe it or not, this ancient machine is running Windows Server 2003 R2, with Service Pack 2.
I'm not sure if this is of any importance, but USB ports in this machine are all 1.1's. According to the Device Manager, the USB Adaptor is taking about 100mA current so it's not a case of port overload.
At present, it's running Java 1.5.0 Update 22, the last of the 1.5.0 series.
I'm running to a brick wall with this problem.
Any thoughts, comments or ideas are very welcome.
Thanks in advance and Best Regards,
Juha
Ok, here's the situation:
I recently bought the following equipment:
- 1 x RJ-45 Coupler
- 1 x Adaptor Cable RJ45 to RJ11 3ft (1m)
- 2 x Humidity/Temp Case
- 2 x Humidity/Temp
- 1 x 1-Wire USB Adaptor
They've been sitting on the shelf for a week before I installed them on site.
The configuration is as follows:
[Computer] --> [1-wire USB Adaptor] --> [RJ11 to RJ45 cable] --> [RJ45 coupler] --> Cat5e RJ45 cable, 5 m (~16 ft) --> [Humidity/Temp Sensor] --> Cat5e RJ45 cable, 10 m (~ 33 ft) --> [Humidity/Temp Sensor]
As you now might expect, both sensor boxes are jumpered so they are using parasitic power.
Everything was going according to my plan: I installed the drivers (version 4.03 beta) with the USB Adaptor disconnected. Once successfully installed, I plugged the Adaptor in and ran the "Default 1-wire Net" program and pressed auto-detect. The Adaptor was detected successfully in USB1.
Obviously the next step was to check whether I get any readings out from the sensors, so I ran the "OneWireViewer" program. All the sensors were detected as they should.
I selected the first DS2438 device on the list and clicked on the "Real-Time Temperature" tab. It successfully polled the temperature once and then threw the following exception:
ERROR: TemperatureViewer (D9000000F1D81C26) Error reading device! com.dalsemi.onewire.OneWireException: 1-Wire Adapter communication exception
ERROR: OneWireViewer (null) 1-Wire exception: com.dalsemi.onewire.adapter.OneWireIOException: native TMEX error -12
After throwing those exceptions, it suddenly read the temperature once again, this time successfully three times in a row and then it started throwing the same exceptions again and never recovered from it afterwards. Restarting the program revealed 0 devices. Only way to recover from this situation is either disconnecting the USB Adaptor, disabling and then enabling it from the Device Manager or by machine reboot. Doing so brings the sensors back but only until they're polled for readings again.
I'm using a program called "LogTemp", but it suffers the same symptoms as seen in the OWV.
The computer specs are as follows:
- ASUS CUSL2 rev. 1.02
- Pentium III 866MHz
- 512MB RAM
- 40GB HDD
Believe it or not, this ancient machine is running Windows Server 2003 R2, with Service Pack 2.
I'm not sure if this is of any importance, but USB ports in this machine are all 1.1's. According to the Device Manager, the USB Adaptor is taking about 100mA current so it's not a case of port overload.
At present, it's running Java 1.5.0 Update 22, the last of the 1.5.0 series.
I'm running to a brick wall with this problem.
Any thoughts, comments or ideas are very welcome.
Thanks in advance and Best Regards,
Juha