restart when "lost touch" with devices

Brian, the previous thread was locked so I have created a new one to resurface it. I don’t know if others are having problems with this or not. Here’s my original posting…

"Brian, can you tell me why, when I have a problem with my sensors flatlining, if I shutdown WD and restart it, that they come back online?

Is there some way that WD can tell that it’s got a problem with the sensors and “recapture” them?"

Rocketman had suggested that I test to see if the ‘save and exit’ does what I want…but my system is remote so I haven’t been able to test this. I also searched the BB to revisit your response, but couldn’t locate it. (maybe it got lost in the archiving).

So, the question on my mind remains…is there a way that WD can detect when it has lost contact with the sensors and attempt to reconnect with them? I find that when my system loses contact that it eventually causes my system to hang. When it’s an unattended system - this is a real problem for me!

Any ideas?

Thanks

i forgot about adding this
i will add the option, to do it daily say, and test on my system first

Thanks Brian,

Here’s a couple of observations on my system:

  1. it tends to lose contact late in the afternoon
  2. if it goes through 'til midnight (rollover) it tends to have problems
  3. if I close/restart WD it rediscovers the sensors

Can WD “sense” that it has lost contact with the sensors?

Ideally, I would see the functionality to include:

  • if it has lost contact, restart WD
  • option of select this or not (assuming others wouldn’t want)
  • select frequency of testing whether it has lost contact (I would like it to do it more than once per day)

Thanks!

Hi Jeff,

Can you post a schematic diagram of your setup please ?
Also include lenght of cable between sensors and type of cable used .

what sort of connectors are you using ?

I don’t have a schematic, but here’s the net of my setup.

  • all CAT5
  • use RJ12 connectors
  • my weather system is currently disconnected and in for warranty repair so it’s not connected (problems still exist)
  • 3 temp sensors connected, lengths are 6 feet, 10 feet, 30 feet.

ILink adapter. (I had a DS9097U - but replaced with ILink hoping for better reliability)

I have had additional sensors connected and no noticeable impact (positive or negative) on reliability.

  • AAG weather station (60 feet)
  • temp sensor (60 feet)
  • rain gauge (15 feet)

my suggestion:
throw away all your rj12 connectors and instead directly solder all connections, as corrosion can occur in the connectors and that will cause problems. A good 1 wire circuit, and you should have no problems with WD and 1 wire devices.

all of my RJ connections are indoors. My outdoor connections are in a Bell Demarc box with screw attachments. Shouldn’t this be ok?

What’s the best way to consolidate connections? Right now I have a splitter box connection just prior to the ILink. Is there a better connection method that allows for easy add/change?

I’m using RJ12’s on my network . Check all connectors for corrosion ( especially inside the socket ends ) I’ve have had this trouble before .

Since your setup is so far away , I would consider replacing all connections . I found a couple on my network that looked fine ( the corrosion was inside the socket )
small cost considering your so far away .

you could also solder the connections ( but RJ12’s are easier to break up your mircoLAN when finding faults )

good luck ( whatever you chose to do )
rocketman

and i will add the reset option, tomorrow…

Rocketman, thanks for the suggestion on the RJ replacements. I actually have replaced some with connectors. The ones that remain allow me to change the setup. I guess I will do some more work on it where practical!

Brian, thanks for the reset. Can you detect when it’s lost contact with the sensors?

this option is in the latest version now
just tick it then click on save /reset in the dallas 1 wire setup
good luck

thanks once again Brian. I have my fingers crossed that this will help me out!

I have upgraded and “ticked” the option in the Dallas 1 setup. It seems that every hour it switched from reporting accurate readings to indicating very high temps. (our normal temp here right now is around 0C). The only change I made was to install the new version and “tick” the new option in the Dallas setup. (I am currently running “stationless” since my unit is in for repair)

I would really appreciate your help on this one. Any ideas?

I have dumped a screen print into an email to you.

Sorry to be such trouble!..Jeff

i will make it so it only does whats needed to just re look for the sensors, and nothing else
but i am surprised its done that jump
anyway, keep an eye on it, and first thing is to see if it maintain reading the sensors over time…

I guess I’ll leave it go and see if it settles in. It has been stable for about 4 hours now. I’ll watch it over the next day or so…Thanks

Brian, I continue to have the same problem. I think I’ll have to roll back a version. It seems to run fine for a few hours (maybe 8-10) and then it suffers from spikes that look like they’re exactly an hour apart. When it starts to happen it seems that the interval is fixed…incorrect high temperature for an hour, then normal for an hour, high again for an hour…etc. It will go like this for 4-6 hours…then back to ok again for a period. Then the cycle starts all over again.

Any ideas?

i am uploading 9.97e now, keep an eye out for it
i have made some improvements to this reset system that should help
please try
at least though its stopped the flat lining, yes?

Update - I have not updated the version yet since it’s at my remote location, but I am not sure that the flatlining is fixed. It has encountered flatlines over the last 24 hours. It seems to flatline and then “jump” to the incorrect higher temp for an hour, then back to normal (or flatline).

QUESTION: at what times does the program do the reset? Is it on the hour?

Thanks Brian, the flatlining seems to be gone - although it’s hard to confirm due to the frequency of the spiking. I’ll download the new version and give it a try.

Thanks

Brian, I continue to have problems with the 9.97b and 9.97e. The “b” version gives me extended spikes almost every hour (for an hour) and the “e” version gives me flatlines and spikes. I have backed out to version 9.96e for now and am running 9.97e on my test machine to continue to monitor.

Do you have any idea what would be causing these problems?

Thanks again for your help on trying to work through these…am I the only one seeing these issues?

Thanks again for your help on trying to work through these…am I the only one seeing these issues?

YES, which is why I say to redo all your connections with solder conndection s(and then seal), as re are running after a hardware issue