¿ªÔÆÌåÓý

Locked Re: USING JMRI WITH MULTIPLE SYSTEMS


 

Stephen,

Since the system name format is specific to a particular connection type, it is not feasible to change just the connection type.

For example, ¡°LS101" on LocoNet might be "MS1.2.3.4.5.6.7.8;1.2.3.4.5.6.7.9¡± on LCC or CS1001 on CMRI.

If you look at the panel xml file, you will see a class specification for each connection type and object type. For example: class="jmri.jmrix.loconet.configurexml.LnSensorManagerXml¡± for saving and loading LocoNet sensors.

Some objects have type specific features such as available feedback options for turnouts. Trying to load such an item in a class that does not support the option will result in an error.

The bottom line is that the system name is a LOT more than just the connection character. It is a lot of work to move hundreds of user names from one system name to another, but for most people it is a one time project. They are not going to replace all of their hardware frequently.


Dave Sand

On Jun 10, 2019, at 5:59 PM, Stephen Grant Brown <steve.brown_nbn@...> wrote:

Hi All.

Dave says
------------------------------------------------------------------
why is there a need to ¡®associate¡¯ each line entry when there could be hundreds of line entries to go through? I understand the need to tie the System Name to the User Name of the actual component on the layout but having to do this one-by-one! Surely if the records are stored within a Table why can¡¯t we use something like ¡®Find and Replace¡¯ within the System Name Field to change the Code Letter from using the original ¡®I¡¯ Internal to using the ¡®M¡¯ MERG code or whatever system code is appropriate when we actually change the Configuration Profile from Internal to our chosen system type? The same could also apply to when we are changing DCC Systems, say from ZTC to Lenz?

Dave
-----------------------------------------------------
Is it possible to have JMRI change the system name depending on the dcc system in use?
ie when changing from a simulated DCC++ system to real DCC++ hardware that the appropiate internal name is used?

Or have I completely misunderstood what the quoted paragraph is saying?

Stephen






Join [email protected] to automatically receive all group messages.