Constantly wait for receive instead of looping send. #796
Unanswered
fanzypantz
asked this question in
Q&A
Replies: 2 comments 1 reply
-
hi with this code can i make a class C device ? |
Beta Was this translation helpful? Give feedback.
1 reply
-
Hi,
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm not a massive C++ coder and I'm trying to get my head around how this work. I'd like for my application to sit idle for the majority of the time, waiting for a message from TTN or some other broker. Then start sending metering data until a stop message is received. However, the examples and what I can read in the doc makes me unsure where to go.
From my testing, I only receive after sending data, which makes sense according to the doc. We'll be using privately owned gateways, so sending all the time instead wouldn't be a big deal. But it should be doable to just listen? From what I gather, I'm looking at creating a Class C device.
My slightly changed OTAA TTN code:
I did remove the os timer from the picture and call the send function manually after reading some modbus values:
Main loop
Beta Was this translation helpful? Give feedback.
All reactions