Re: [Jmri-developers] Digitrax board programming (was Re: First 4.9.6 files available

[B. M. <dcc...@sb...>]

Bob J.

There was (and perhaps still is) a problem with using JMRI's "decoder" programming mechanisms for programming things like "Digitrax hardware which can be programmed via DS64-like OpSw programming" and things like LocoNet "SV2-programmable" devices.  That shortcoming is that an "identify device" can return more than one device, and those devices are not necessarily of the same device type.  When the "identify device" response is a "list of unique devices which really exist", there would need to be some way to choose one to work with, and then select the correct "decoder" .XML file, and then open a programmer which uses that "decoder" .XML file.

When the "LocoNet/SV2" functionality was added (two or three years ago?), this problem was known and was going to get some attention, but the key player who would look into the problem was seriously distracted by real-life problems.  

I do not know if there has been any progress on that basic problem since that time.

I have a vague recollection that there are secondary and perhaps tertiary problems that come along with implementations for JRMI decoder-like programmation of LocoNet "SV2" devices, and, by similarity, for JMRI decoder-like programmation of LocoNet "DS64-like OpSw-programmable".  

When I get a chance, I'll try to dig thru some old e-mails and distill and report to the list.

Regards,
Bob M.

> -----Original Message-----
> From: Bob Jacobsen [mailto:jac...@ma...]
> Sent: Saturday, November 25, 2017 5:06 PM
> To: Discussions between JMRI developers <jmri-
> dev...@li...>
> Subject: [Jmri-developers] Digitrax board programming (was Re: First 4.9.6 files
> available
> 
> 
> 
> > On Nov 23, 2017, at 1:45 PM, railrodder railrodder <rai...@sy...>
> wrote:
> >
> > For 4.11.1 I'd like to
> ...
> >  save the configurations for digitrax DS64's, command
> > station etc. in such a way that you can pull up different configs and not tied
> > to a layout or connection.
> 
> I think the best way to do that is to
> 
> 1) Create a programming facade that’ll allow DecoderPro to read and write
> configuration info to those boards
> 
> 2) and then create DecoderPro decoder definitions that use that facade to read
> and write the boards.
> 
> By doing it that way, you get a _lot_ of useful functionality for free.
> 
> I think the facade would be pretty straightforward, happy to help.  But I don’t
> have convenient hardware to develop/test with.
> 
> Bob
> --
> Bob Jacobsen
> jac...@ma... +1-510-708-5988 AIM, Skype JacobsenRG
> 
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Jmri-developers mailing list
> Jmr...@li...
> https://lists.sourceforge.net/lists/listinfo/jmri-developers