开云体育

Sorry, I didn't mean to ruffle feathers here. As to which "thread", I thought by replying to the immeadiate email it was obvious..thay's what I dislike about Yahoo..it disconnects story lines tandomly.
All that aside, yes,I am a long time DCC user now having moved to NEC for our layout. Sorry about the confusion of my statement about not using a "system" to program. I guess I have always thought of my SPROG3 as a computer interface and not an actual system as in NCE, MRC, DIGITRAX,etc. Okay, wrong choice of words.
What I wS hoping to do was maybe clarify that the club was using an interface like a SPROG and not actually hooked up to a "system", thus no connection to the layout.
For those of us who do not disect JMRI but simply use the fine programs, we may not be versed in all the syntax and code writing that so many here take for granted. Whrn we post a problem we do so in the o ly wst we know how to explain what "we" see on our system. I have learned a lot at this and the Facebook JMRI sites. Until I encountered my first problem with DecoderPro at update 4.6, I had no idea there were logs and such to look at or submit for people to troubleshhot with. I don't know how old or what year DecoderPro was first introduced, but I began using it many years ago when I met a guy at a On30 meet in New York state who had it on a laptop and kindly showed me the advantages of programming decoders in whole pages instead of one CV at a time.
I'm a big fan of DecoderPro and couldn't tell you what the other programs are for. I'm simply a happy user and I appreciate whoever is responsible for inventing the program in the first place.
Thanks again for making our model railroading more fun!!



Sent from my Verizon, Samsung Galaxy smartphone