Skip to content
Questions and answers
Q: My node does not display the time immediately after a reboot, when is it created?
A: The node receives the time from the MeshCom server via a gateway. This message is sent every 5 minutes. If you have an RTC (Real Time Clock), this time is adopted immediately but still synchronized with the server time every 5 minutes. This time is also displayed immediately if the GPS is connected and receives a SAT-FIX. The GPS time is not overwritten with the server time.
Q: Why does the clock show the wrong time?
A: The time that comes from the MeshCom server via a gateway and also the time that comes from the GPS is in UTC. it is therefore necessary to set the time offset to the local time. Either via APP (Node UTC Time Offset), via WEBService or serial command (- - utcoffset 2.0)
Q: What do I have to do when using an APP via Bluetooth if I equip my MeshCom node with new firmware and also use ERASE?
A: The "old" existing peering information must be deleted in the system settings under Bluetooth.
Q: What are TEST MESSAGES ?
A: These are messages that have the word "Test" at the beginning of the text. The spelling "Test", "TEST" or "test" does not matter. DM messages that begin with "Test" in the text are also not forwarded. No response ("ACK") is sent and therefore no cloud with a hook is reported. However, if two nodes hear each other directly on the RF frequency, the messages are displayed but not acknowledged in any way.
Q: What does the green tick mean?
A: If a message from the APP has arrived in the MeshCom node via Bluetooth, this is reported back to the APP and displayed with a green check mark.
Q: What does the green cloud mean?
A: After the message has been sent out by the own MeshCom node and at least one other MeashCom node has heard this message and sends it out again (mesh network). The own NODE receives this message and passes on this information to the SmartPhone APP. In short: at least one other MeshCom node has heard us.
Q: What does the green cloud with a small check mark mean?
A:
1) The cloud with a small check mark gives us the information that our message was received by a MeshCom gateway node and passed on to the server.
For this a special ACK message goes from the gateway node via mesh network back to its own node.
2) If we have sent a direct message (DM), this cloud informs us with Hakerl that the destination callsign of the DM message has been received.
For this purpose, an ACK message goes directly from the receiver node back to the sender node via the mesh network (including MeshCom server).
Q: The Hop number, in the DashBoard, what does it say ?
A: The hop count always counts down from 5 by 1 when a message has passed over a node, i.e. has been sent out again. 4 means that the message has just made a hop. If the counter is 0, it will not be sent out again, because it has made the maximum allowed hops. This prevents that messages are sent out again and again forever.
Additional note: ah thanks for the clarification! I previously thought it was the number of hops the message had taken to get to a GW. Was wondering why it was such a high number. So it is the other way around - it shows the hops remaining. "Hops remaining"
We use cookies to ensure that we give you the best experience on our website. If you continue to use this website, we will assume that you are happy with it.
OK
