|
kristen
|
 |
« on: August 19, 2009, 06:35:41 PM » |
|
A while ago my 1-wire network stopped working, I've only just got around to trying to fix it.
I had turned off some Java caching (something from Control Panel, forgotten exactly what)
Didn't reboot ...
... some time later we had a thunder storm and a power cut, and when the PC came back up 1-wire easn't working.
I've uninstalled / re-installed Java
Reinstalled the 1-wire DLL driver
OneWireViewer now believes that there is a USB dongle present ...
... but can't see any sensors.
Its message log says:
VERBOSE: TemperatureViewer (null) No Device
VERBOSE: HumidityViewer (null) No Device
VERBOSE: PotentiometerViewer (null) No Device
VERBOSE: ADViewer (null) No Device
VERBOSE: ClockViewer (null) No Device
VERBOSE: ThermochronViewer (null) No Device
VERBOSE: MissionViewer (null) No Device
ERROR: OneWireViewer (null) 1-Wire error: com.dalsemi.onewire.adapter.OneWireIOException: native TMEX error -12
ERROR: OneWireViewer (null) 1-Wire exception: com.dalsemi.onewire.adapter.OneWireIOException: native TMEX error -12
ERROR: OneWireViewer (null) 1-Wire exception: java.lang.NullPointerException
ERROR: OneWireViewer (null) 1-Wire exception: com.dalsemi.onewire.adapter.OneWireIOException: native TMEX error -12
then repeats of the last two messages in various combinations.
The Device List is empty.
OnwWireViewer then won't close. (I can kill it, but I have a feeling that leaves the driver unable to talk to anything until I reboot)
LogTemp shows nothing, and the Messages tab says "1-wire network does not exist"
Any thoughts / suggestions please?
|
|
|
|
|
Logged
|
|
|
|
|
sleepybubble
|
|
« Reply #1 on: August 19, 2009, 06:43:40 PM » |
|
try it with just one 'test' sensor and not connected to the full network. I have a test sensor that is very useful for diagnostics. My one wire network is not radial, its a large star pattern and I do occasionally suffer problems. On our web interface it causes major headaches, but that is down to the way my code is written. At console level it is usually easy to figure out which sensor has dropped out and why.
So yeah, wire up one sensor and start from basics.
|
|
|
|
|
Logged
|
;-)
|
|
|
|
kristen
|
|
« Reply #2 on: August 19, 2009, 08:07:40 PM » |
|
Did that before. Honest. ... ... must have traced the wrong cable and unplugged the wrong one  ... OneWireViewer can now see one sensor. LogTemp ain't having it though ... but I'll try a few reboots and things. Thanks! |
|
|
|
|
Logged
|
|
|
|
|
kristen
|
|
« Reply #3 on: August 19, 2009, 10:03:44 PM » |
|
Can't get LogTemp working I've tried adjusting the Setup. It seems to be happy with USB Port 1 or 2, but doesn't find the sensor. Any other USB Port that I try gives "1-Wire network does not exist" I expect there is some happy combination I need to find, any ideas? |
|
|
|
|
Logged
|
|
|
|
|
wookey
|
|
« Reply #4 on: August 20, 2009, 02:11:55 AM » |
|
I expect there is some happy combination I need to find, any ideas? Linux+OWFS :-) Sorry, I have nothing useful to contribute, knowing nowt about winders. |
|
|
|
|
Logged
|
Wookey
|
|
|
|
sleepybubble
|
|
« Reply #5 on: August 20, 2009, 08:58:56 AM » |
|
Well the only thing I can think is that the one-wire viewer is not closing the port properly on exit, hence log temp cannot see the dongle.
I know its pedantic but have you tried rebooting and then running logtemp first. Other things to check is that you dont have log temp in your start up folder or if it has a setting to run on start up, and the same with the one wire viewer.
I'd also try a clean install of the one-wire drivers and logtemp on a seperate control machine to see if the problem is unique to the one machine, ie. a driver corruption or if the dongle has suffered some sort of damage. Again just using the single sensor to start with.
Sometimes windows uninstallers are not actually very effective at cleaning up drivers and .dll's
I know these are only common sense answers and not a magical solution.
|
|
|
|
|
Logged
|
;-)
|
|
|
|
kristen
|
|
« Reply #6 on: August 20, 2009, 11:27:01 AM » |
|
I had made the assumption that One Wire Viewer was not clearing out properly, so have already been rebooting before testing LogTemp. Reboot is a good 5 minutes on this machine I had also already starting thinking that it was going to come to a clean-install on something else, but was hoping I wouldn't have to pollute another machine with all the Java bits and bobs Although, I think there may be an unused legacy machine lying around - prime for a sacrifice! LogTemp is only happy with USB1 or USB2 - anything else gives me some sort of "1Wire Network not found message". So I reckon it is seeing something, just not the single sensor I have hooked up. I thought I had a stand alone temperature graphing tool (from memory it came with OneWireView, or from Dallas), but I can't find it. That would be handy in proving things a bit more. |
|
|
|
|
Logged
|
|
|
|
|
kristen
|
|
« Reply #7 on: August 20, 2009, 05:30:24 PM » |
|
" ... OneWireViewer can now see one sensor." No it can't It can see the USB dongle. That's it ... WhatAPratAmI So either the cable to the first sensor is damaged, or the USB dongle is. I've tried plugging the far end of the first leg of network cable into a couple of different sensors, no change. Given that it was working OK up until a reboot (inflicted by a power cut due to a lightening strike nearby), it seems unlikely to be cable damage. Should I just order another USB Dongle? Strikes me it would be sensible to have one in reserve. What's a good (cheap!) source pls? |
|
|
|
|
Logged
|
|
|
|
|
|
|
sleepybubble
|
|
« Reply #9 on: August 20, 2009, 06:03:08 PM » |
|
Don't you have one spare sensor you can wire up as opposed to trying it out on your shonky network? If you haven't I'd just order one sensor for now and test the dongle properly first before buying a dongle (but then I'm really tight!). I got my USB dongle from Homechip they're in Milton Keynes and delivery was only two days to up here so it must be good, it cost about £12 IIRC I know I ordered it with a bunch of temp sensors and the total was about £24 including postage. If you do order a dongle I really reccomend getting yourself some spare sensors, one screwed sensor can pull a whole network down. My sensors are just soldered direct to cable and dont have the fancy individual plugs that others do, I have one on the return from my panels outside which died a month or so ago, I think the cable got fried by steam when the pipe burst ( again!) took me hours to find which one had gone offline. During that whole time the rest of my network failed to report in properly. Sounds to me like your having the same sort of problems, youve probable got a short on one sensor which is taking the whole network off line. My network is powered, and I guess if the network is on parasitic mode then this wouldn't happen. <edit> ah if homechip are out of stock then your bumblebeed, I'd borrow seans, see if he has any spare sensors too...  |
|
|
|
|
Logged
|
;-)
|
|
|
|
dhaslam
|
|
« Reply #10 on: August 20, 2009, 06:18:37 PM » |
|
It is quite common for attached components to be damaged by electrical surges that computers can survive themselves. It is quite likely this has happened. The big advantage of USB is that they become active immediately and when you plug them in they usually get some kind of reaction from the computer. If there isn't a response it is likely the device has had it. USB devices don't like extension cables so it is best to plug them directly into the computer.
|
|
|
|
|
Logged
|
|
|
|
|
kristen
|
|
« Reply #11 on: August 20, 2009, 06:35:18 PM » |
|
" Don't you have one spare sensor you can wire up as opposed to trying it out on your shonky network? " I've got about 30 sensors. I've tried several. Just the cable from the USB plugged into various of my sensors on the pipes. No shoddy soldered-to-wire here, everything pluggable  The cable from USB to Device has special ends, and I'm sure I had a spare, but I'm blowed if I can find it, and I'm not good at crimping, so that will be my last port ... " It is quite common for attached components to be damaged by electrical surges that computers can survive themselves." How would they get "surged"? (Not my skill-set!) The 1-Wire is running on a network cable from a USB dongle plugged into a powered hub (external "brick" power supply / transformer) to the devices. All indoors. No other connections or direct-power connections. Thunderstorm wasn't overheat that I remember, I guess it was just nearby and that tripped the local substation. |
|
|
|
|
Logged
|
|
|
|
|
sleepybubble
|
|
« Reply #12 on: August 20, 2009, 07:02:42 PM » |
|
USB devices don't like extension cables so it is best to plug them directly into the computer.
nah... its not extension leads they dislike its lack of power, USB ports provide 5v on one of the pins for parasitic USB devices e.g. pensticks, if you have too many parasitic devices or devices beyond 5m away then you need to provide external power. Either through a powered USB hub or using a special booster extension cable. I have a 10m USB cable which comprises of a 5m booster and a 5m standard and stuff works fine at the end of it. |
|
|
|
|
Logged
|
;-)
|
|
|
|
sleepybubble
|
|
« Reply #13 on: August 20, 2009, 07:18:19 PM » |
|
" Don't you have one spare sensor you can wire up as opposed to trying it out on your shonky network? " I've got about 30 sensors. I've tried several. Just the cable from the USB plugged into various of my sensors on the pipes. No shoddy soldered-to-wire here, everything pluggable The cable from USB to Device has special ends, and I'm sure I had a spare, but I'm blowed if I can find it, and I'm not good at crimping, so that will be my last port ... " It is quite common for attached components to be damaged by electrical surges that computers can survive themselves." How would they get "surged"? (Not my skill-set!) The 1-Wire is running on a network cable from a USB dongle plugged into a powered hub (external "brick" power supply / transformer) to the devices. All indoors. No other connections or direct-power connections. Thunderstorm wasn't overheat that I remember, I guess it was just nearby and that tripped the local substation. OK my last suggestion (other than trying on a different machine) when you plug a USB device into a port on a windows machine the driver install request dialog comes up and you go through driver install all fine. The driver has been asscociated with that port. If you unplug and then plug into a differnt port then sometimes you get the driver install dialog again, this is because PC's and lappy's often have more than one USB hub built in, so you need to associate a driver for the hub/port that the device is now plugged into. So are you sure you have the dongle plugged into the correct USB port on the particular machine, and have you tried it in other ports. This may lead to a solution or it may lead to a driver corruption on the orginal port, cant be sure which depends on how well written the one wire drivers are. If you do change physical port/hub then stuff like one wire viewer and presumable logtemp need reconfiguring for the correct port. If you then plug it into a different port then you'd have to reconfigure. It may just be you've got into a mess when playing around with things trying to get it working again. If you want you can post me up all your nice molded pluggable sensors to test and I'll swap them for my perfectly working solder and sellotape cables  Ultimately I have to agree with Wookey, I only use one-wire viewer on a lappy when doing diagnostics to see which bit of selloptape insulation has melted. The rest of the time my USB dongle is plugged into my Slug running linux, logging to MySQL. It was a bit of a pain to set up initially but (apart from the occasional bit of melted sellotape and solder) has never stopped working since november of last year. You should really come over to the dark side!  |
|
|
|
|
Logged
|
;-)
|
|
|
|
kristen
|
|
« Reply #14 on: August 21, 2009, 07:23:12 AM » |
|
"when you plug a USB device into a port on a windows machine the driver install request dialog comes up and you go through driver install all fine."
I like that idea. The dongle is obviously working enough to be detectable by OneWireViewer ... but if it fails the "New hardware detected ... installed" test I can just bin it.
"If you unplug and then plug into a differnt port then sometimes you get the driver install dialog again, this is because PC's and lappy's often have more than one USB hub built in, so you need to associate a driver for the hub/port that the device is now plugged into. So are you sure you have the dongle plugged into the correct USB port on the particular machine, and have you tried it in other ports."
I've seen that happen, so I know what you mean.
My dongle is plugged into an external, powered, hub - which in turn is plugged into a single USB port on the PC. Just out of curiosity does the above apply, or is plugging into any of the ports [on the hub] seen as "the same" from the PC's perspective?
"It may just be you've got into a mess when playing around with things trying to get it working again."
I've plugged the thing into this-and-that USB port on the hub, so you are absolutely right in that assumption. The other thing that I have not been careful to do is to power-cycle the hub whenever I rebooted the PC - I don;t know if the hub remaining "up" during a PC reboot might perpetuate an issue?
"If you want you can post me up all your nice molded pluggable sensors to test and I'll swap them for my perfectly working solder and sellotape cables"
No Deal!
"It was a bit of a pain to set up initially but (apart from the occasional bit of melted sellotape and solder) has never stopped working since november of last year"
Mine was a pain to set up initially but has worked flawlessly ... until now. I'm staying in the light, for now!
Thanks for your help, very useful to have an opportunity to bounce ideas in order to locate the solution.
I reckon wannabe 1-wire-ers should have a spare Dongle and a spare first-cable (mine goes from the US-telephone type connector to CAT5 type (sorry, forgotten the relevant RJ numbers), and as a non-hardware-bod I'm not accurate with crimping those little wires ...
|
|
|
|
|
Logged
|
|
|
|
|
