I was just about answering your and Ken's questions when I saw your good news that seems to make my answers untimely. (A minor point: I don't mind creating reporters manually, but I guess your prospective change of the software will make it automatically automatic.)
I¡¯ve made a few corrections to the reporter code that should help the situation. ?These are available in the current daily build ( package build 2685 as I type this ):
The basic problem was that the Z21ReporterManager was not being registered correctly. ?
I have made some improvements to the reporter table. ?I also added translations for the railcom related messages in the Z21 monitor ( some of the non-address data values are clearly not correct, but that is not critical and will be corrected later).
Hopefully the reporters ( both LocoNet and the one for the built in reader on the Z21 ) are now created automatically for you.
One interesting thing about the built in reader on the Z21, It continues to report addresses even after they should no longer be seen ( in my case, this was physically removing the locomotive from the track). ?This makes it look like the reporter has a current report, even if the block is not occupied. ?I need to try this with more than one railcom equipped locomotive to see how the behavior changes.
A number of people have already spent considerable time on my problem and I was serious in saying that, in order to express my gratitude, I would be glad to "make life easier" for you, e.g by sending you a Roco 10808. (I am expecting a concrete answer.)
At this point, assuming the current code is functioning as expected, I really do think It would be helpful to have the hardware to do anything else with the functionality the Roco 10808 provides. ?Contact me off list so we can work out details.
Paul
