Does using the Detection Sensor module prevent the node’s telemetry from being updated? #10942
Unanswered
profetolocka
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi!
I have 3 nodes that I’m using to test the operation of the Detection Sensor module. I was able to make it work correctly by configuring, on the node that has the sensor (Node A), a channel 0 with a key, called Sensor, and creating the same channel 0 with the same key and the same name on the receiving node (Node B).
On this second receiving node (B), I moved the LongFast channel with the “AQ==” key to position 1, as a secondary channel, and adjusted its frequency slot so that it matches the other two nodes, slot 20.
With these settings, all three nodes can participate in LongFast conversations. However, using MeshSense connected to Node C, I see that Node B shows an incorrect position on the map. Also, I changed its name and I don’t see it updated in MeshSense.
Is this behavior due to Node C being unable to receive telemetry from Node B because Node B uses the primary channel to receive Detection Sensor activation messages from Node A?
Thankfully,
Ernesto (Profe Tolocka)
Beta Was this translation helpful? Give feedback.
All reactions