it seems just pure LoRa, no receive windows. However, I do not know whether opening and closing communication is lasting nothing.
Can you explain it some more? I dont know what you trying to say here.
Where did you calculate this? I used a excel sheet available here in the forum for the 17ms.
You are right, I wanted to start with the point to point. If this is running (and I get the power consuption and number of transmissions down ) I will do the next step and try to unse TTN
The Semtech LoRaCalculator Tool.
For LoRaWan Class A, downlinks are only sent after uplinks. After sending, a node need to listen to see if there is a downlink packet sent. This happens during the RX1 or RX2 window (depending on the frequency plan / channel).
So it would make sense to me to wait for the receive window is over before going to sleep…
Oh – wrong forum then…
Ah - thank you. I forgot about this. How can I calculate the time of this window or is it not possible?
I just want to start with pure LoRa. I thought it would be easier to begin with.
With OTAA, RX1 is 1 sec, and RX2 one second later, the choice of the window is based on the frequency plan.
But again this is LoRaWan specific.
Okay, got it. Thank you.
Is it possible, that the LoRa module is by standard in the LoRaWAN Class A? So the chip is thinking, that its sending to a network? Cant figure it out why these times are not the same or even in the same area… but the 700ms is to huge!
I dont have access to the Semtech LoRa Forum and to the tools. I calculted with some more free calculators for LoRa and returning me the ~17ms is correct…
You can download the LoRaCalculator from the Semtech Website.
No, your missunderstanding the difference between what your trying to configure, point to point LoRa, and LoRaWAN.
Tell a LoRa device to send a packet and it does just that, and that only, it sends a packet. When its finished sending the packet it turns the transmitter off. It does not attempt any clever stuff like listening for replies. If you want to listen for a reply (like you might in LoRaWAN) you have to specifically configure the LoRa device to flip to being a receiver.
If you think the LoRa device is transmitting longer than you think it should be, you might want to raise the issue with the author of the library you are using.
As an aside, i notice you are using pins 34 and 35 as RX and TX. Note that those pins are input only. While it works now for an RX only operation, the TX on Pin 35 will never work should you try to transmit out of Serial2.
Thank you again for your explanation. I was just looking for a reason of the behavoir of the board - thats why i made the “default mode suggestion”.
I will try to contact the author of the library I am using with this issue, thats a good idea.
Thank you for that hint! This connection is only to get the data from the electrical meter to the board, there is no communication from the board to the electrical meter.
Use ESP32 ULP - with one analog measurement every 200msec will last 10 years on a battery
here is for arduino UI/comparability mode:
Thank you for that hint, its looking very complicated tbh but I will try to implement it! If I have success I will let you know about the effects
I tried to print the millis and thats what its printing:
Serial.println(millis()); LoRa.begin(BAND, PABOOST); // Sending via Lora start Serial.println(millis()); LoRa.beginPacket(); Serial.println(millis()); LoRa.print(trans); Serial.println(millis()); LoRa.print(trans) Serial.println(millis()); LoRa.endPacket(); Serial.println(millis());
So I would say, that the LoRa.begin and LoRa.endPacket is the problem --> libary probelm
Am I right with this?
hmmm I watched about this in “The guy with the swiss accent” video and give it a try and it worked for me - I’m using Heltec LoRa32 Arduino IDE 1.8.8
Have you tried any other SF values to see whether the duration increases even further?
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.