Re-establishing Sensor Contact

[sanramonrover]

So I have searched all the pages on the forum that mentions lost sensor contact, but can't find a solution.

I have reunited my receiver/console with the sensor/transmitter back in Costa Rica, but cannot get the two of them to talk to each other. It worked fine before taking the console to Canada, due to the broken touch screen. I even bought a new console in Canada.

I followed the usual routine - insert batteries in TX, then into RX, wait for connection before touching the screen - but no connection. Waited 12 hours, waited half an hour...nothing.

I tried the new console, but it does not connect either. I have tried them separately, together, one at a time, both together, but no luck. Tried them at 10 feet (minimum) with no walls between, tried them at 50 feet - no connection.

Checked batteries in TX and RX - OK. I see the little radiating arcs just above the outdoor %RH symbol flashing every 48 seconds.

Any other suggestions?

[Super-T]

Are they operating on the same frequency?

[sanramonrover]

Because one RX/console is the original for that TX, and it worked until I disconnected it in March, it must be on the same frequency as the RX. The new unit was bought in Canada from the original supplier so I assume it should be the same freq. There is no marking on the back of the case, and I haven't opened it to check the PCB.

But as an aside, the website http://site.ambientweatherstore.com/Manuals/ws1080.pdf states that they sell extra receiver/displays so you can use the two of them on the one TX. Therefore I assume two RXs should not cause conflict.

I did notice in the above website instructions a warning not to insert the batteries in backwards or else the unit can be damaged. I did briefly, but also assume all such electronics usually have a diode to prevent such damage. Anyway, after putting them in right, (after only a few seconds backwards), the red LED comes on just like it should, so assumed no harm done.

Next step is to tear down the outdoor sensor/TX and see what's up.

[Ned]

I too would expect a diode guarding against reverse polarity to be fitted, but in that case I would also expect no damage was possible by reversing the batteries - no current should flow. If the diode was omitted to maximise battery voltage available to the circuitry , permanent damage due to reversed batteries could be pretty well instantaneous.
But then, I'm no expert
These days I always mark the polarity in battery compartments with a bold marker, as the factory markings are usually inadequate. It's too easy to make mistakes.

Hope it comes right for you...

[sanramonrover]

Took the TX unit apart again, but could see nothing that obviously failed. I'm beginning to suspect that the TX unit is history, though.

What are others experiences with this scene: took the TX/sensor unit off its pole and stored it indoors for 3 months. Took out the batteries.

Took the receiver/console to Canada and used it as an indoor temp/humidity/pressure unit for the three months. At times I would see the little "receive icon" come up on the screen, and even the "TX battery low" icon. Of course there was nothing for it to receive.

When I re-setup the unit this week I get no sensor connection. Could it have something to do with using the RX unit alone? Could it be having installed the TX batteries in backwards for a few seconds?

While I had the TX unit apart, I noted that there does NOT seem to be a protection diode in the 3V track. I can see a marking where one should be, but the pads are blobbed across with solder, so there is no need for the diode.

Anyone else find these experiences?

[Super-T]

As Ned said....no reverse diode and reversed batteries and the damage, if it was to happen, would be instantaneous. 3 seconds is a long time in electronics

[apenwith]

Hi
I don't think it is relevant here but I seem to get data dropouts when the memory is getting full - maybe just coincidence.
Regards
Alan

[steve]

I don't think it is relevant here but I seem to get data dropouts when the memory is getting full - maybe just coincidence.

Like a lot of people, I run with my memory permanently "full" - clearing it only gives scope for problems - and I never get any dropouts since I found a good position for the console.

Not that I know anything about this but maybe you have a dodgy area of memory, and when the station tries to write to it, it causes it to lose the signal?