Skip to content

Commit 29f6748

Browse files
committed
example of echoes
1 parent 4899e96 commit 29f6748

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

README.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -172,6 +172,14 @@ The app give you the information by listening `rx_log` from the device, when obt
172172

173173
In meshcore-cli I went lower-level by implementing channel echoes. When activated (with `/set channel_echoes on`), all the channel messages will be printed on the terminal along with the SNR and path taken. When sending a message, you'll have all the repeats from 0-hop repeaters as echoes, and when a message is received, you should see information about the received message, but also all the instances of the same message that might have reached you from another path.
174174

175+
In the example below, a msg has been sent between two repeaters, 21 and 25. 25 repeated the message and 21 the repeat and both echoes came back to the node with different SNRs.
176+
177+
```
178+
f1down/#fdl|*> 8
179+
#fdl f1down: 8 [25] -4.75-112
180+
#fdl f1down: 8 [2521] 1.00-109
181+
```
182+
175183
### Issuing batch commands to contacts with apply to
176184

177185
`apply_to <f> <cmd>` : applies cmd to contacts matching filter `<f>` it can be used to apply the same command to a pool of repeaters, or remove some contacts matching a condition.

0 commit comments

Comments
 (0)