[Matt Barney]

Will do – thank you.

Matt

[Matt Barney]

OK, that makes sense. Thank you!
Matt

[Matt Barney]

Sweet – I’ve got it now. Thanks Sara!

[Matt Barney]

I’m unclear on what changing the units of a temperature variable on MMW does for me; it seems to label the data as degrees F, but the values are still in deg C, as it appears that the Decagon CTD-10 (in this case) can only report in deg C. Assuming that is the case, could we get a calculated variable set up on MMW for temperature in deg F? Our users are also wanting to see depth in inches, so I’d like to have a calculated variable set up for that as well, if possible.

Thanks,
Matt

[Matt Barney]

Thanks Sara. I was plotting air temperature from the Maxim DS3231 and wanted to display it in F, but that option is not available that I can see. I hope I didn’t make it sound like I thought anything about the portal was hacky; my use of calculated variables to do a unit conversion was. 🙂

[Matt Barney]

Thank you Sara. I see that the list of calculated variables is curated, so this avenue may not be the best fit for my use case. In particular, what is a non-hacky way for me to display a sensor’s measurements in different units? I’m using the ModularSensors library. Would I need to customize the code for that sensor to do the units conversion?

This is not a critical need for us, so I don’t want to ask you to spend any substantial time on it. I am curious whether there is an existing hook somewhere in the code for doing units conversion, or, if not, whether there is enough interest in creating one in the future.

Best,
Matt

[Matt Barney]

Neil and Sara, thank you both! Last night, before seeing your posts, I began testing again while in a different location (happens to be much more remote). I switched to Bypass mode last night, and it appears to be working! Now back in my office in the city, it works as well. I’ll attach my logfile as an fyi.

The above sketch displays firmware version 11051. I should probably buy the XBee3 TH development board.

Attachments:

1. logFileNov11.txt

[Matt Barney]

I modified line endings and changed the wait time to 30 minutes: modem.connectInternet(1800000L). I then had to leave and left the Mayfly running overnight. Still no data at MMW, but I now see connections being logged on my Hologram dashboard, and a single message that shows data usage: https://drive.google.com/file/d/15FjVP3x_ySw_IEkIQVZ0OvbIB9x8UpQ1/view?usp=sharing . With the exception of that one, 1.88KB, all other data sessions show 0 bytes: https://drive.google.com/open?id=1YXvI1Kv9nn6ZgoKBINbav9SArQEFB-3b”

Also, here is my terminal log file (~2MB): https://drive.google.com/open?id=13_cvDM8-UMZ5dJueux9vZjbe9g5GmIcW

[Matt Barney]

Hi Sara,

Initially I was testing on USB power only, but will now keep the LiPo plugged in as well, though no success so far with that. (I’m guessing the LiPo is needed to provide adequate current for signal transmission?) I’m testing in my office in an urban area where we have good Verizon and AT&T signals. I did carefully press the antenna’s u.Fl connection together a couple of times just in case it wasn’t fully engaged.

I have never gotten the XBee3 to connect. I will try changing the timeout from 2 min to something longer and report back. Would this only be needed the first time you bring a new XBee3 online, and then could change it back to to minutes before deploying into the field?

I have tried Bypass mode previously, but changed back to Transparent after not having luck.

Yeah, I was wondering whether I needed to check firmware versions, and was just beginning to read about that in Digi’s docs. Do I need additional hardware to connect the XBee to the PC in order to use XCTU?

I’ll try modifying the line endings and post the logs.

Thanks!

[Matt Barney]

Great – Thanks Shannon!

Matt

[Author]

Posts