开云体育

Have you checked that the tabs from the motor are making contact with the pads on the bottom of the decoder?? I've had them become misaligned so the motor was no longer connected to decoder. Michael

Bob, Oh no :( Our hardware can not properly control this signal using aspect messages because we do not have any internal control on flash rate options. This is the first time that I have heard of a

Bob, My gut reaction is that arbitrarily adding 'aspects' to cover the lit and not lit cases is probably not a good idea. My feeling is that we should always move closer to the prototype, not away

Hi I've noticed a problem for a while (I cannot remember exactly when it started) when trying to add multiple internal sensors. The situation can be created as follows: * Open PanelPro (no panel

Hey all, Just providing an update on this issue. I think this message might not have attached to this topic originally, so just doing so now. I received the Digitrax decoder and got it installed. I

Dick wrote "I would like to hear about the rule set that requires more than 32 aspects." FIY - The following existing JMRI mast definitions implement more than 30 aspects: - CROR-2008 - 3A-Hi : 31

Ken, The original USB V7 documentation showed 7.3.7 for ALLSYS. The revised USB V7 documentation shows 7.3.7 for PowerCab. The revised USB V7 documentation shows 7.3.1 for SB5 (19,200). The revised

I've found better results with the 7.3.7 (all jumpers on) setting. Effectively it says the USB will attempt to pass all commands to the command station. All the other settings have combinations of

Dan, Correct, but there's further qualification needed regarding firmware versions: If your Power Cab firmware (second screen at startup of your Power Cab, after the "Pro Cab V1.3" message) is: -

Dan, You are quite correct, as I had posted in an earlier message on this thread, which shows exactly what jumper and JMRI settings to use. It appears Russ may not have seen

Here's a link to a table that shows how to properly configure the jumpers for the USB.? I believe you should set up your jumpers so you get a 7.3.1 response, not a 7.3.7 that's showing in your

Found this on the NCE site with regards to AIUs: Valid cab addresses (for cabs in) a Powercab system are 2,3,4, or 5. Total of 4 actual cabs. 6 and 7 are unused. 8,9 and 10 can be used for other cab

In your system console text, it shows that there is a response to the command to poll the AIU, a "30" which means command not supported.? I believe you need to have your AIUs in a lower address range

Bob, As I remember it, the issue with the SE8c, LDT, etc. devices was that they use turnout commands in a way that requires remembering the last sent message information rather than the last state of

Russel, Since the log shows the line: 2019-11-24 17:07:42,699 nce.NceConnectionStatus INFO - NCE EPROM revision = 7.3.7 [AWT-EventQueue-0] We know you are talking to the USB ok. Now

See PR #7663 ( https://github.com/JMRI/JMRI/pull/7663 ).

Ken, Spoke to soon - I am not getting the following System Console readout: 2019-11-24 17:07:38,280 util.Log4JUtil INFO - * JMRI log ** [main] 2019-11-24

Paul, If you get "Found mfg 123 (Masoth Electronic, GMBH) version 123; no such decoder defined.", and/or all CVs return a value of 123 and long address 15,227 it is 100% certain that the

What am I doing wrong? In an attempt to build my Roster, when I “create new loco” and select ?“Read type from decoder” all I get on multiple locos is “Found mfg 123 (Massoth Elektronik,

At least in some systems, “dark” is a valid appearance, at least for parts of a mast.