I thought I would return to this thread to see if there is anyone who has built this monitor and uses an Elink. I have an Elite controller. I have noticed that, when Railmaster starts up, it displays on the "Splash" screen "Initialising DCC Controller". During this time, the green status box, to the right of the RM Programs Combo dropdown list, flashes a number of times. When I first noticed this, I counted the number of flashes, and there were around 27. It occurred to me that this was roughly the number of locos I have defined in my loco database. With the DCC monitor running, from this point onwards, 6 DCC commands were appearing for each loco on the DCC bus, and these were being repeated continually. Now, repeating the information for each loco, in my opinion, isn't a bad thing. It means that if a new command from the controller doesn't get through for any reason, then it is repeated very soon afterwards. However, doing this for ALL locomotives in a user's database, even though many of them might not be used in a RM session, seems to me a bit over the top. I decided to try to reduce this DCC bus traffic. I introduced a new group to the loco database called "Operational", and I assigned to this group only those locos which are used in my current program schedule. The number of these locos is 15, and, sure enough, when RM starts up, with "Operational" having been the selected group when RM last closed down, the number of flashes seen when the "Initialising DCC Controller" message is displayed, reduces to 15, and the DCC monitor only displays traffic for these locos.
These 6 DCC commands are as follows...
Loc xx Forw128 Stop
Loc xx L F4-F1 0
Loc xx F8-F5 0
Loc xx F12-F9 0
Loc xx F20-F13 0
Loc xx F28-F21 0
... and these are sent to every loco in the group, irresepective of whether the loco has all of these functions or not.
My questions arising from these observations are as follows...
1. Does Elink repeat these 6 DCC commands for each loco, as well as the Elite?
2. Why does RM send out this information to the controller during initialisation?
3. Is there a case for having a new system setting/INI file entry to make this initialisation optional? Maybe a new "Desirable Feature".
4. If the controller is busy sending out all of these commands to the DCC bus, does that increase the risk of missing an incoming command from the RM pc?
5. If the answer to (4) is yes, then is there a case for having another optional system setting/INI file entry which is similar to the Double Pulse command for points, which will instruct RM to send Function commands to the Elite twice, to reduce the risk of them being lost and for the controller to get out-of-sync with RM?