Welcome to EnviroDIY, a community for do-it-yourself environmental science and monitoring. EnviroDIY is part of WikiWatershed, an initiative of Stroud Water Research Center designed to help people advance knowledge and stewardship of fresh water.
New to EnviroDIY? Start here

neilh20

Forum Replies Created

Viewing 10 posts - 181 through 190 (of 376 total)
  • Author
    Posts
  • in reply to: Using the Teensy 3.5 #15791
    neilh20
    Participant

      Thanks, good for reference – the critical aspect of any plastic outdoor box is I understand polycarbonate and those IP65 seals 🙂 Keep out the falling rain. Those ants like to get in if they can, so it is a challenge. I really appreciate the detailed guide of what to think about with https://www.envirodiy.org/mayfly-sensor-station-manual/ though I choose my polycarbonate box based on the project.

      When building a system, I do try and document it for myself so that I can easily repeat it, and also share it. The Mayfly can fit in a small space ~ NBB-15240 with the uSD facing outwards for easy offloading.
      Sometimes though its the instrument wires and dessicant that need routing space, so I’ve also been using the Bud PTQ-11050 and for testing PTQ-11050-C.

      Still it would be soo nice to have a processor with at least 4 UARTs, an embedded USB host, and a 1M flash, enough ram and timers for totalizing/counting … with a little screen for site provisioning. I’m playing around with the Wio Terminal – https://wiki.seeedstudio.com/Wio-Terminal-Getting-Started/ but how to get the sleep power usage down, and have it take an Xbee format socket with Digi LTE powering, with all the software open source license…. as ever a variety of engineering challenges. 🙂

      in reply to: Using the Teensy 3.5 #15789
      neilh20
      Participant

        Ahh very nice.  I’m sure its worth it to get a standard design for all climates, and able to cope with keeping some sensors warm.   Seems like the cost is going to go up dramatically though. Powering is a lot of cost and of course IP65 space is costly (for those batteries!!).  I wonder if it is open sourced, or a private contract design.  I use a 4.4AH LiIon, which is quite large for the Mayfly, and of course it can only charge at a max of 0.5A/hr – which means the solar panel is only about 3Watts (though easy to oversize to cope with shading) . Thanks for sharing and the references.

        in reply to: Publish to AWS? #15784
        neilh20
        Participant

          I wonder if the AWS interface can be done through some form of @vogelrnws  python that runs on the Xbee LTE? JMight be worth looking for something that runs on the raspberryPi in Python for AWS, and then seeing if they could be adapted to Xbee LTE python.  (so easy to throw out an idea – but I have no experience with AWS)

          in reply to: Using the Teensy 3.5 #15783
          neilh20
          Participant

            @vogelrnws thanks.  Would you have an overall schematic of it. Sounds like Solar to +12V.  Then guessing +12V battery that is the main power source. Then  Teensy3.5 supply 3.5to5.5V, possibly also Xbee LTE boards

            https://www.pjrc.com/store/teensy35.html

            Probably a carrier board for the Teensy3.4 and LTE board?

             

            in reply to: Using Xbee Cellular Modem with ThingSpeak #15776
            neilh20
            Participant

              @vogelrnws  sounds great .. the Teensy 3.5 is a great board and amazing support. If you’ve figured out remote upgrade as well, very noce.  I wonder if you would create a separate thread for it ~ perhaps “using the Teensy 3.5”. One of the biggest issues for me is always how to make a system, low power and solar powered.

              in reply to: Using Xbee Cellular Modem with ThingSpeak #15771
              neilh20
              Participant

                @zeke-holloman do you want to send me the thingspeak details on my email neilh20@wLLw.net and I’ll try them in my setting.  I have a historical thingspeak account which has exceeded its free quota, so I can’t create more devices.

                The hologram account should work with the Xbee LTE ( I have an XB3-CA2-UT-001) if setup, and I started with hologram.  If it works for getting time, should work for any other connection.  If you post the trace can see if its getting good response .

                @vogelrnws  gosh sounds interesting, especially as you are logging the readings. I couldn’t see the python files – could you provide a link.

                 

                in reply to: Using Xbee Cellular Modem with ThingSpeak #15767
                neilh20
                Participant

                  https://thingspeak.com/channels/5940 shows a data point at Aug 02 2021 15:17 GMT-0700  Yeah!!

                  in reply to: Using Xbee Cellular Modem with ThingSpeak #15766
                  neilh20
                  Participant

                    @zeke-holloman,  I figured out that the other day I hadn’t changed the apn to the source I was using.

                    So with your code, my apn and thingspeak API, using tera-term 4.105 with TimeStamp and the following changes I got a good response from  thingspeak

                    #include <ModularSensors.h> //pre 0.30.0 was <LoggerBase.h></div>

                    The core thingspeak looks like this

                    I have a lot more debug, and better scale-ability built into my fork https://github.com/neilh10/ModularSensors but the above worked for me.

                    in reply to: Using Xbee Cellular Modem with ThingSpeak #15765
                    neilh20
                    Participant

                      Hello @rick-vogel – sounds fascinating & fun to use python in the Xbee.  Though for ModularSensors there are layers of software that allow the physical modem to be abstracted so it could be possible to use another LTE when it becomes available (0.30.0 seems to have hooks for a new LTE modem SIM7080G) – through TinyGSM. As a Class package that @srgdamiano has put together its quite comprehensive – though as with all abstractions it has upsides and downsides.   I think this is working through what it takes to figure out the control flow, which would be needed whatever route is taken. In my fork (with some LTE interface changes) it has worked.


                      @zeke-holloman
                      , I’d got pulled off onto something else, now I’ve added the STREAMDEBUGGER_DBG to your “Logging_to_Thingskeak5.ino”and removed my extra code that I had and about to test it – but I have to get another dataplan going to test it – I use https://dataplans.digikey.com/ that has a 50Mbytes/month plans,

                      in reply to: Using Xbee Cellular Modem with ThingSpeak #15762
                      neilh20
                      Participant

                        hello @zeke-holloman. Just looking through it, and yes thats my assumption at the moment is that its the cellular side that is not connecting.
                        There are 2 parts 1) getting internet & time 2) thingspeak.
                        1) If the cell phone connects for NIST time, then it can connect with the internet, and the cell modem account setting is good.

                        2) if thingspeak then doesn’t connect its something to do with the account ino.

                        I’m just looking at your posted new file

                        The STREAMDEBUGGER_DBG is a bit strange, it should really be this

                        The log you posted with some basic cell phone interface is looking very minimal. Possibly also compile it with

                        -DMS_DATAPUBLISHERBASE_DEBUG
                        -DMS_THINGSPEAKPUBLISHER_DEBUG

                        -DSTREAMDEBUGGER_DBG

                        .
                        I was thinking of creating a branch off envirodiy (master) – and seeing if it can be referenced for an update to the cell phone interface so it can show more detail. Gotta try it out.

                      Viewing 10 posts - 181 through 190 (of 376 total)