Welcome to EnviroDIY, a community for do-it-yourself environmental science and monitoring. EnviroDIY is part of 
@neilh20
Active 1 days, 6 hours agoForum Replies Created
-
AuthorPosts
-
OK I think I’ve figured out something. I can only get the last variable at the moment (432) .. which is what I need for my real analysis of looking at the last value of the voltage returned andOK I think I’ve figured out something. I can only get the last variable at the moment (432) .. which is what I need for my real analysis of looking at the last value of the voltage returned and and checking it it has dropped below a threshold.
http://data.envirodiy.org/sites/TU-RC-01/ visually its 16.0V the first Battery Voltage “All_ExternalVoltage_Battery” and I can also see with a download of series=1906
So then using
http://data.wikiwatershed.org/wofpy/rest/1_1/GetValues?location=envirodiy:TU-RC-01&variable=envirodiy:All_ExternalVoltage_Battery
comes back with something that includes<values>
<value methodCode=”2″ qualityControlLevelCode=”1″ censorCode=”nc” dateTime=”2019-11-18T19:27:02″ dateTimeUTC=”2019-11-19T03:27:02″ sourceCode=”611″ timeOffset=”-08:00″>16.0</value>which seems like I read as
<values>
<value …>16.0</value>and its the 16.0 Volts that I’m after. So I need to parse to find that and compare it to my threshold.
Gosh @srgdamiano wonderful!. ..As every another question … (thankyou thankyou in advance)
So following the examples and trying for some GetValues on EnviroDIY_Mayfly_Temp from
https://dataGosh @srgdamiano wonderful!. ..As every another question … (thankyou thankyou in advance)
So following the examples and trying for some GetValues on EnviroDIY_Mayfly_Temp from
https://data.envirodiy.org/sites/LCC45a3/
with this
http://data.wikiwatershed.org/wofpy/rest/1_1/GetValues?location=envirodiy:LCC45a3&variable=envirodiy:EnviroDIY_Mayfly_Temp&startDate=2019-09-01T00:00:00&endDate=2019-11-01T02:30:00I get a response but no <values> that I would think I should get.
Any pointers – many thanks.To piggy back on this discussion – I’m wondering if anybody (@srgdamiano?) knows if there is a way of doing a POST/GET to request data from the ODM database for the latest row, or be ableTo piggy back on this discussion – I’m wondering if anybody (@srgdamiano?) knows if there is a way of doing a POST/GET to request data from the ODM database for the latest row, or be able to access latest readings via WaterML.
The readings POST structure is described here
https://github.com/ODM2/ODM2DataSharingPortal/blob/master/doc/example_rest_requests.mdhttps://www.envirodiy.org/midstream-making-real-time-data-publicly-available/ from early architecture suggest access through WOFpy
What I’m looking for is to be able setup elsewhere a periodic request on the latest reading to be able to do a threshold check.
I know I can request data from ThingSpeak in this fashion, just wondering if there is a spec for it for data.enviroDIY.org
many thanksI had a similar problem – see my comment in https://www.envirodiy.org/topic/trouble-registering-with-lte-m-network-on-hologram/
The fix that seemed to work was if it didn’t connect afterI had a similar problem – see my comment in https://www.envirodiy.org/topic/trouble-registering-with-lte-m-network-on-hologram/
The fix that seemed to work was if it didn’t connect after a 100 AI status polls it issues
gsmModem.sendAT(GF(“+CREG”));
Search for +CREG in
https://github.com/neilh10/ModularSensors/blob/rel1_dvlp1m/src/modems/DigiXBeeCellularTransparent.cppMy Hologram with data connection every 4hrs looks like this – pink is no session , blue is with data
Attachments:
Yup – the network is challenging when making it work, and adding to the biggest and most diverse machine in the world.
I’ve been more the old wireline, POTS to ISDN (now ADSL) – mYup – the network is challenging when making it work, and adding to the biggest and most diverse machine in the world.
I’ve been more the old wireline, POTS to ISDN (now ADSL) – moving the analog to the CircuitSwitched Digital, and now its packet switched.Though when I was working with one customer, when our product wasn’t connecting to the bigger machines, he referred to us being on the “Bleeding Edge” (the other side of cutting edge).
It actually turned out our product was working, but we interworking with a German device that wasn’t coping with US standards.
That’s why its nice to know about the 7Layer OSI model to have some common language about what the scope of the discussion is.
A lot of the 2G v 3G v 4G is industry fashion, bands of specifications, the reality is related to very specific specifications which evolve slower than 2G->3G->4G. The cellular industry is coping with high bandwidth expectations (5G), as well as low bandwidth IoT.
Whatever the technology, what does it take for my packets to be delivered successfully at what cost of power and devices.
I have heard of new silicon that can have problems with memory deep inside the chip – debugging that is hard.
For manuals I’ve been using mostly the
“Digi XBee3® Cellular LTE-M_NB-IoT 90002258revLsept2019.pdf”
https://www.digi.com/resources/documentation/digidocs/PDFs/90002258.pdf
though I’ve seen the questions and advice in various support forums about the Sara-R4.
Again thanks for the details on CREG – I’m mostly a niche usage for some environmental monitoring I’m supporting.
When my bit is stable I’ll put it in a wiki.No problem – I appreciate the earlier tip.
What I haven’t figure out is there another manual that specifies +CREG cmd – it isn’t in the user manual I’m using.
I havNo problem – I appreciate the earlier tip.
What I haven’t figure out is there another manual that specifies +CREG cmd – it isn’t in the user manual I’m using.
I have seen it before where latest manual “inherits” a context of another set of cmds specified in an common manual.Thanks for the tips here.
I’ve also had trouble with a new Hologram SIM registering to the cell network with a Digi XB3M1.
I had a working hologram SIM that connected straight away, and then wThanks for the tips here.
I’ve also had trouble with a new Hologram SIM registering to the cell network with a Digi XB3M1.
I had a working hologram SIM that connected straight away, and then would power off and swop in the new Hologram enabled SIM, and it would poll the cell tower and not work.
I started trying about 2weeks ago, had to move on to a few other items, came back to it.
Tried a few more times yesterday, added the tip above, and it worked, and ran overnight OK.
I’m based 0.23.15 (but latest github.com/EnviroDIY/TinyGSM) and using DigiXBeeCellularTransparent.cpp
I included and monitored the AT responses
bool DigiXBeeCellularTransparent::extraModemSetup(void)
added at the end
gsmModem.sendAT(GF(“+CREG”));
and it sent back an ERROR
but then the XB3M1 registered.
Seems like its a magic recipe workaround of some sort, but no idea if this really works till I try registering my next sim.The code is here – search “+CREG”
The first commented out “+CREG” is how I had it.
Then I introduced an algorithm to only issue “+CREG” it if has been monitoring for 100 times for the next time I register a sim.
https://github.com/neilh10/ModularSensors/blob/rel1_dvlp1m/src/modems/DigiXBeeCellularTransparent.cppThe output is
Version 11413 <–DigiXBeeCellularTransparent
Loop=Sec] rx db : Status ‘ Operator ‘ #Polled Cell Status every 1sec
0=5.28] 0:0x22 ‘OK’
1=6.30] 0:0x22 ‘OK’
2=7.32] 0:0x22 ‘OK’
3=8.34] 0:0x22 ‘OK’
4=9.35] 0:0xff ‘OK’
5=10.37] 0:0xff ‘OK’
6=11.39] 0:0xff ‘OK’
7=12.41] 0:0xff ‘OK’
8=13.43] 0:0xff ‘OK’
9=14.44] 0:0x22 ‘OK’
10=15.46] 0:0x22 ‘OK’
11=16.48] 0:0x22 ‘OK’
12=17.50] 0:0x22 ‘OK’
13=18.52] 0:0x22 ‘OK’
14=19.53] 0:0x22 ‘OK’
15=20.55] 0:0x22 ‘OK’
16=21.57] 0:0x23 ‘OK’ Cnt=1
17=22.59] 0:0x0 ‘AT&T Hologram’ Cnt=2
Cell scan ‘ S MCC:310 MNC:410 Area:35651 CID:169103376 Signal:-98 ‘
… Setup successful! <–DigiXBeeCellularTransparentThanks.
The cct V0.5b shows an option of connecting the Xbee to the LiIon V_bat – which can get to 4.2V – and a very nice low impedance for the Cellular Tx power requirements.
So if thThanks.
The cct V0.5b shows an option of connecting the Xbee to the LiIon V_bat – which can get to 4.2V – and a very nice low impedance for the Cellular Tx power requirements.
So if the Xbee-V1-UT/XB3-C-A2 Cellular @ 4.2V was pulling up, that would over drive the mega1284 pins above their Vcc (3.3V).
At some point the megas1284 protection diodes start to conduct. The issue not stated in the Xbee docs is if there is a -RESET pullup. If there is no pull-up, or its week (greater than 100K) its probably workable.Oh good to hear it works.
What pin are you using on the Mayfly.? I could see the references in the code on modemConnect() but couldn’t find any designation.One of the problems is that the ATm
Oh good to hear it works.
What pin are you using on the Mayfly.? I could see the references in the code on modemConnect() but couldn’t find any designation.One of the problems is that the ATmega1284 doesn’t have any 5V compatible pins, so it may cause some unpredictable behaviour if it pulls the mega1284 pin up too hard – which depends on the Xbee.
One way would be to decouple with a NMOSFET with low drive voltage – eg with legs/TO92-3 TN0702N3-G – it turns on between 0.5-1V
https://www.digikey.com/products/en?keywords=TN0702N3http://ww1.microchip.com/downloads/en/DeviceDoc/TN0702%20C080813.pdf
It doesn’t need an R on the Gate where it interfaces to the micro, and probably doesn’t needs a pullup on the Drain, as there may be enough pull up in the Xbee – otherwise I would recommend a 10K-1M R. Its only activated for short period of time so the R doesn’t really matter – except it must be low enough to guarentee that the MOSFET turns OFF.I’ve also had this problem with the Xbee S6 WiFi. However I’ve lowered the polling rate and a few other tweaks of the TinyGSM and its been better https://github.com/neilh10/TinyGSM.
@calI’ve also had this problem with the Xbee S6 WiFi. However I’ve lowered the polling rate and a few other tweaks of the TinyGSM and its been better https://github.com/neilh10/TinyGSM.
@cal the Mayfly 0.5b schematic diagram of the U6/XBEE-1XBEE-1_LOCK shows the RESET pin5 – the schematic symbol of circle on the mainbody is typically a way of indicating the RESET is pulled low to activate it, also sometimes indicated as -RESET.I’d be interested in the solution for where to connect the Xbee reset line to the Mega1284 – but haven’t tried any options yet.
-
AuthorPosts
