开云体育

Sounds like an interesting project. Although I've not looked at it in any detail, I think most of the communications stuff should go over pretty cleanly. So you'll be able to talk to the various DCC

The LocoBuffer will almost certainly work. It uses standard serial speeds. I've never heard of somebody having trouble with those. The MS100 needs a non-standard speed, or a specific alternate. On

Greg, You need to check the settings for the port. It is probably defaulting to 9600 speed, and just needs to be reset to a higher maximum setting. Assuming you have Windoze installed, look at the

My hunch is that this is an operating system rather than a hardware issue. PC serial ports have been doing 56K for man years. I assume you're using Windows. I know nothing about Windows so I can't

Bob: Would "Typical" work for "General"? Jim Hanna

widget. Maybe a scrollable list of decoder names, with up to 10 showing? That would make it clear that there are multiple choices, because you could see the alternatives. The scroll bars would make it

I think there are several causes of confusion that are really different. Maybe it would help to think about them seperately? a) "The Ident button picked the wrong decoder!" Some of these are problems

Well, I installed JMRI on my 1 year old laptop and it says that my COM port can only be set to 9600. I don't understand the reasons why. Anyway, if this is true for JMRI, what about other loconet

I've already ordered my Zephyr with the guy who did the obsolete Digitrax list. He doesn't take CC's you need to send a check. I think this is probably the best deal out there. Paste from his site

I've heard that it has a Chief-style programming track which can both read and write. That would be a really good alternative to the PR1, esp. if they can hit their price point. I'll be interesting in

same micro-code for his line of "Silent Running" decoders. They all contain the same program, hence the same version number. The only thing that changes is the PC card, which can vary in shape/size,

Thanks for catching that! I've fixed the originals. That's an example of a "family" of decoders. Jim Scorse uses the same micro-code for his line of "Silent Running" decoders. They all contain the

the above needed category? Unfortunantly, I'm not a Java Developer. Actually, I don't get to develop code much at all these days - I've evolved into more of a "Professional Meeting Attendee" and

CV8 seems to be the most reliable data but I'm not sure what they do when a decoder is subcontracted like say Digitrax makes a decoder for Atlas or similar. One of the very large problems I see with

Bob, What about by Manufacturer, Scale, Model Example: Digitrax, N, DN142 or North Coast Engineering, HO, D13SR Al Silverstein

'Family' seems like a rather confusing category. Dividing the list by manufacturer is a good idea. In other words, I agree with Robin. Mike

I'm still getting my DCC system up and running; so, I'm not (yet) a JMRI user; but, I work in the software development industry, so I'll jump in and offer up my $0.02. Perhaps what is needed is a

Bob, I think I suggested a similar approach that was simpler. The dropdown decoder list just shows manufacturers, but then there are flyout menus for each manufacturer that list the models. If you

I don't have any real ideas about how to better identify decoders. I agree it's a mess, and will be happy to implement whatever you guys think is best. Mark Gurries made a suggestion a while back that

Because with some manufactures CV7 isn't going to always tell much maybe the DN14(x) concept would be good. The tabs (panes) for that group could then be asterisked with the comment, "not all of this