DCC++ over WiFi issues

miniThrottle: A model railroad WiFi throttle.


↓↓ Dig deeper ↓↓


An issue using the WiFi interface of DCC++

When using the WiFi interface of DCC++ and using DCC++ protocol, it appeared some packets were either being dropping or scrambled. The JMRI protocol over this interface appeared more reliable, but less feature rich than miniThrottle to DCC++. The examples below were a result of sending a status command to DCC++ over WiFi from miniThrottle console a few seconds apart. A further issue was found when DCC++ rebooted unexpectedly when using DCC++ over WiFi.

In the illustrations below the commands run at the console have no prefix, while outgoing packets are prefixed with "-->" and incoming packets are prefixed with "<--". In the unexpected interaction it looks like the data is all there but out of sequence, as if there are 2 separate streams of data being returned to miniThrottle.

Expected interaction

showpackets
sendcmd <s>
--> <s>
<-- <p1>
<-- <iDCC-EX V-4.0.1 / MEGA / STANDARD_MOTOR_SHIELD G-a26d988>
<-- <H 20 0>
<-- <H 21 0>
<-- <H 22 0>
<-- <H 23 0>
<-- <H 24 0>
<-- <H 25 0>

Unexpected interaction

showpackets
sendcmd <s>
--> <s>
<-- <p1>
<-- <iDCC-EX V-4.0.1 / MEGA / STANDTRSIL -2d8>
<-- ARD_MOO_HEDGa698
<-- <H 20 0>
<-- <  >
<-- H210
<-- <H 22 0
<-- <H 2 >
<-- 30
<-- <  >
<-- H240
<-- <H2 >
<--  50

A few options are worth trying:




Thank you for visiting this websiteHome