[Letsid]

Hello all. I have recently been delivered two of the newest versions of the Hydros 21 CTD sensors. They are replacing two that were destroyed after a year in the field. Anyway, with these new sensors, I am  having issues with the SDI12 address. I have run the SDI12 check code (posted earlier) and have used that to try and program the sensor so that the SDI12 address is 1 and not 0. That works great. However, each time I restart the Mayfly or try and upload the logging sketch, the sensors revert back to address 0. As such they fail to transmit the data and I get -9999 results. Thoughts?

[Letsid]

It worked! Thank you, thank you!  I very much appreciate all the help.

[Letsid]

Wanted to send an update: the XBee is now connecting to the internet in a timely manner!  I saved the testing code for my future units.  Thanks again!

[Letsid]

Got it!  So this time I left it long enough to connect (or I think it is connecting).  Attached are snips of the monitor.  It repeats for quite a while and then right at the end it changes.  So, pictures 3 & 4 are almost consecutive.

 

I commented back after fixing my ini file and did not reload the page and didn’t see your other comments!  I will try the network scan tomorrow!

Attachments:

1. 

   XBee-connect_1-1.png
   

2. 

   XBee-connect_2-1.png
   

3. 

   XBee-connect_3-1.png
   

4. 

   XBee-connect_4-1.png
   

[Letsid]

The battery I am using is basically straight from the box so I was under the assumption that it was about 50% charged.  I have not had the opportunity to complete the solder on the Voltaic solar panel.  The antenna has been gently wiggled!  I should also note that I did not remove the antenna when testing the second Digi XBee (to avoid unnecessary damage).  So, I have gotten the same result with two different antenna, both with a seemingly secure connection.  I am not certain that there AT&T is available but when it did connect, and came up on my Hologram account, I assumed there was.  Also, I tried connecting to Verizon and had no luck connecting.

Attached are snapshots of the serial monitor as it moves through trying to connect.  I cut it up because it was pretty long.  I see no 22s, 23s or 25s.  But I do see many zeros.  These changed into -93 for a while and then to -45 and then back to zeros (as you can see in the pictures).  Is this what you were looking for?

 

Attachments:

1. 

   XBee-connect_1.png
   

2. 

   XBee-connect_2.png
   

3. 

   XBee-connect_3.png
   

4. 

   XBee-connect_4.png
   

[Letsid]

Thank you for taking the time to put that together!  It worked… sort of.  My SIM successfully connected to the internet!  It took maybe 30 minutes.  My signal quality is listed as -45.

After successfully connecting, I restart the Mayfly and build in the MMW example.  This code fails to connect and I get the same result as before ( “could not connect to internet for clock sync” and is “putting modem to sleep”).  I then re-try the code you provided above and it takes another 30 minutes or so to connect. And repeat.

Is there a way to do the ‘wait forever to connect’ strategy within the MMW example?  Is this not an ideal solution?

P.S. I originally bought three of the Digi XBees.  I have tried two of them, repeating all the steps above.  They are acting the same.

 

[Letsid]

The pio lib install worked!  Thank you so, so, so much.

[Author]

Posts