[UKBloke.. this is an integral part of the MultiBooster development)
if we want super efficiency, it would be best if CS automatically sent the currents every x seconds then we dont have to deal with the extra command parsing and input comms. But I would still insist on sending the conversion factors at startup and just the raw values while running.
I would have no problems adding a command to set the frequency.
e.g. (using $ as a placeholder for a mores suitable char) JMRI sends <$ 5> meaning give me currents every 5 seconds... CS Replies <$ 5 2.99 1.68> meaning ok 5 seconds and these are the conversion factors for main and prog.
then every 5 seconds CS sends <$ 123 456> being the averaged raw main and averaged raw prog over the previous 5 seconds.
[UKBloke.. this is an integral part of the MultiBooster development) if we want super efficiency, it would be best if CS automatically sent the currents every x seconds then we dont have to deal with the extra command parsing and input comms. But I would still insist on sending the conversion factors at startup and just the raw values while running. I would have no problems adding a command to set the frequency. e.g. (using $ as a placeholder for a mores suitable char) JMRI sends <$ 5> meaning give me currents every 5 seconds... CS Replies <$ 5 2.99 1.68> meaning ok 5 seconds and these are the conversion factors for main and prog.
then every 5 seconds CS sends <$ 123 456> being the averaged raw main and averaged raw prog over the previous 5 seconds.