Yeah...
I figured I needed to retrieve as much debug information as possible. It is a bit bothersome gathering that sort of data as we run trains for the public.? I will be on site Thursday and will gather as much data as possible.? Let me add to the list of glitches that we have seen.? They do not seem to be fatal because we can get everything up and running and it runs quite nicely.? I fear what we are seeing is left over schmutz for the way the panels were developed (kind of like microwave radiation left over from the big bang?)..? Let me repeat and add to what we are seeing:
1. When we load panels? as part of the configuration booting we never get to the console screen.? We have to kill java, remove the panel load from the config, start JMRI and load the panels from the Panel menu. Everything is then cool...
2. When we realized we had made errors in developing the panels and associated tool tables, we moved all data entry to the JMRI computer (Windows 10) running the layout.? The turnout tables and sensor tables were built using the OpenLCB menu selection Configure Nodes. We used the Make Turnouts and Make sensors tool in the LCC CDI..? The block tables were built using the add button associated with the Block Table tool.? The original panels were stripped of any connections that had been preconfigured.? The panels were graphics only.? The panels were reconnected to the various tool tables within JMRI on the computer running the layout.? When all that stew got simmered we noticed that there were turnouts and sensors added to their respective? tables.? If we deleted?? them when we restarted? PanelPro, they came back.? One frustrating aspect of how the various tables are built is the under the hood connections between objects is somewhat opaque.? The is noticeable when, for example, you delete a turnout...? You get a message something like "this object is used by the table manager and? 4 other objects".? How do you find out what those other objects are?? (I know those objects related to NCE because they have the "N" prefix).? My guess our clumsy development process has left some things hanging and JMRI is being polite and reconnects them.
3. One last oddity...? Our DCC command station is an NCE PH-PRO 5 amp system..? We know the command station is the latest and greatest.? It came back from the shop in October? and we run the part of the layout that is operational just fine.? We have not been able to get that command station to talk to our JMRI computer..The Serial set up is correct.? The cable is correct. When i fire up the system console I see stuffing going down the line to the NCE DCC command station but never get anything back..? I have not had the opportunity to check the set up with a PROCAB .? I called NCE tech support and all they would suggest is double check the serial parameters. Any ideas?? System console log to follow...
But in closing, let me say we are more than comfortable with the design decisions we made.? LCC is all that and a box of chocolate and DCC is a fine way to power an engine...?
Dan Kubarych
ARHS
