Open FritzOS opened 5 months ago
Hi @FritzOS , thank you very much for this code! I tested it with some static data, and also displayed the data on ThingSpeak – it works like a charm! As soon as I have access to my sensors, I will test it with them and let you know how that went. Thank you again so much for taking your time and commenting your solution here!
I'm using a Wireless Stick Lite V3. I'm confident this will work so long as I can modify my pinmap. Do you have any suggestions for the best way I can do this with what you've created?
NVM I think these are correct:
@xuuxij While I have personally not yet worked with the Wireless Stick Lite V3, I think modifying the code according to your pinmap should work – on the Heltec forum, I received a reply from another user that this code (with some adjustments) also works for Chirpstack LNS. Other than that, I'd say just try and go for it.
The difference between Wireless Stick and Wireless Stick Lite is just the display. The code should work when you simply deleted all code related to the display. Would be great to here from you if that works.Cheers Fritz.--Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.Am 11.01.24, 17:21 schrieb xuuxij @.***>:
Hey @FritzOS, thank you so much for this. Do these pins match the Wireless Stick Lite V3 or should I modify them to match? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
As soon as I have access to my sensors, I will test it with them and let you know how that went.
Okay, I tested the code with my sensors today, everything is working like a charm! I "only" have to figure out the issue with the electrical conductivity sensor, then all is well.
Update: The issue with the EC sensor could be resolved. I just realized that I didn't use your code to its full potential because I had been unaware that Vext concerns the Ve pins on the board. Tomorrow, I will check if there's still a transistor at home I could use or if I have to order another step-up converter to get the 3.3V from the Ve pin to the necessary 5V supply voltage for my sensors.
@FritzOS Okay, so I have the following setup now (for testing purposes): The Heltec board is powered via USB-C cable from the Laptop (-> I face the same issue when powering with a battery), and the outputs of the sensors are connected to the pins on the Heltec board. The GND and Ve pin of the Heltec board are connected to a step-up converter that increases the 3.3V input of the board to an output of 5V to supply the sensors. The GND and 5V output connections of the step-up are connected to a breadboard where the GND and 5V pins of the sensors are plugged into.
Now, if I use your code to power off the sensors during deep sleep, the following happens:
Previously, when I did not power the sensors via Ve, they also did not go into deep sleep, but at least the transmission of data was only according to the duty cycle (here: 30 minutes). Now neither works. Could you take a look at my code workingCode.ino and check if there's anything that could lead to these issues? Thank you so much in advance!
please find below an example which sends something to TTN. Power consumption is 19uA.