Thank you for the quick response.
So the following caveat applies equally to the CAB-1L as it did to the original CAB-1:
Two operators, one with a CAB-2 and one with a CAB-1, should not operate the same Engine or Train simultaneously. It is not recommended to “go between” CAB-2 and CAB-1 while operating the same Engine or Train. Doing this will make the graph on the CAB-2 incorrect.
page 8 of the 1.5 manual, paragraph on Sharing Control.
Are the address range issues with the TR's fixed? aka greater than 9?
I'm curious as to how Lionel intended to implement the absolute speed steps that were first documented when the original Command Base was released. There was never mention of the need for a graphic feed back/display and there definitely wasn't one on the original controller. My understanding was the yard boss ZW was going to have an LCD but these never made it out of development/prototype.
I'm curious as to how Lionel intended to implement the absolute speed steps that were first documented when the original Command Base was released.
The Cab-2 can issue 32 absolute speed steps, that is how it was used. Cab1 or Cab1-L will not use absolute, but the command were documented for computer control and now the Legacy system.
On the latest Legacy Locos, (all since the Vision Hudson); I keep a translation between absolute 32, absolute 200, and relative, internally in the loco. Switching between modes does not appreciably change the loco speed. Prior to my Engine Operating System code I wrote for the RCMC (O gauge) and BEMC(S gauge) electronics, that was not true.
It is still not possible to track throttle changes on the Cab-2 from Cab-1 speed changes without a change to the Legacy Base - which may be possible. Theoretically, we could keep Cab1-L changes updating on the Cab-2; as now the Cab1-L communicates to the Legacy Base. Maybe we can look at this next Legacy update; but it really is icing on the cake and of limited return.
We do sync the iPad and iPhone apps throttle and the Cab-2 display, bi-directionally.
