> When you changed the ID on the ISS did you also change the ID on the console?
Oh yes, as I said earlier, I did it and re-did it several times from both the console and from WL. All the other IDs are properly disabled except 3 (ISS) and 6 (WIND).
> power outages
My console has both AC and batteries and I did try to unplug it from the power socket and it did not trigger the problem. Besides, there has not been a power outage here for months.
> walk around the neighborhood with the console and measure the signal strength
Good technique, that would work. Even if it does not help with the problem, I am dying to know who the other weather geeks are
I just hope that if I walk around the neighborhood with a device with an antenna and peek into peoples' backyards I don't end up at the local precinct or worse
In any case, no matter what these stations send, my console should NOT switch to ID 1 by itself. Davis support confirmed that (quote from their e-mail):
Engineering informs me and I have verified here that the wind TX column is determined by the setup only. If for instance, I have wind on ID 8, Iss on address 7 and another station running but not on is on address # 1 Then when download occurs
Wind TX is 8.
If I turn the wind # 8 off then the Wind TX column when downloaded shows the ISS Address # 7.
If that is turned off it goes to default ISS address # 1.
I tested this throughout our e-mailings and have found that this is true and happens all the time here consistently.
> Finally, you did say USB connection and that always throws a red flag.
Yep, I agree. It has been my prime suspect all along since the problem seems to be triggered by shutting down WL. I would not be surprised if the serial/USB bridge that WL uses sent some garbage data to the console upon shutdown, which could sometimes accidentaly reset the address assignments.
Yesterday I have upgraded WL to 5.8.0 and switched the communication to pure USB that is now available in the program. So far so good, the transfers seem faster. I'll see if this fixes it, it has not happened since, but it is too early for any conclusion. I'll refrain from making any more modifications or experiments until it happens again so that I know in case the upgrade fixed it.
Regards,
Alex Khain
Portland, Oregon, USA