开云体育

Ken, The problem occurs when attempting to create a sensor or turnout in the node configuration window - not the table view for sensors or turnouts. The two connections are for geographic separation

Steve, If it is going to be a problem defining the Loconet commands for each aspect using existing JMRI signal heads, you can define them in CATS designer and CATS will create JMRI signal heads when

Hi Michael, If every read returns 123, you will find you are not using the hardware. Instead, you're accessing the simulator. You need to check your defaults! (Please don't ask me how I know) Wouter

I'm sorry if my latest question wasn't clear. I appreciate the advice regarding layout panels and the like, but my question is about Signal Heads and having icons and Simple Signal Logic stay with the

I have been noticing the following entry in the console log. timestamp audio.JoalAudio Factory INFO Initialised JOAL using OpenAL: vendor – OpenAL Community Version – 1.1 ALSOFT 1.15.1 [Listed

Hi, I gave up on 4.6. I uninstalled it and reinstalled the old 3.x I had on a thumb drive. It still gave me issues, but it did recognize the Atlas Dual Mode decoder in the test engine, but when I went

Hi, I gave up on 4.6. I uninstalled it and reinstalled the old 3.x I had on a thumb drive. It still gave me issues, but it did recognize the Atlas Dual Mode decoder in the test engine, but when I went

I wish you could edit a post. My heading should have stated as above.

Do modern decoders use Paged Mode Addressing (described in NMRA 9.2.3 line 202)? Or is this only in older decoders? If it is in older decoders, what decoders and what year roughly are we talking? Is

This could be on earlier version of JMRI also, but having issues reading Indexed CV's on a Wow-121 Steam Ver 3. On a DCC++ Command station I can 100% read all regular CV's and the CVT3 Cv's but noe

Installed 4.8 - problem no longer exists. Never mind.

Bob J's idea seems like a good alternative to (waiting for) new JMRI source code features... Regards, Billybob

thanks Bob I'll wait for the update to arrive. Brian

The fix for this is in current development builds (see http://jmri.tagadab.com/jenkins/job/Development/job/Packages/ ) and will be in JMRI 4.9.2 in a couple weeks. Keep those reports coming, please!

The 8th line in my System Console Message is a warning "2017-07-28 11:01:15,484 lenz.XNetInitializationManager WARN - Command Station disconnected, or powered down assuming LZ100/LZV100 V3.x [main]"

HI More thoughts on this problem. Two years back, when I started to define my own signal masts, I needed to have my own version of the signals in my user files folder to work from. I think now I must

Nom, Did you pick from the pull down for 'System Name' the 2nd connection?? It is correctly creating table entries for the two systems. What reason do you have for using 2 connections rather than

Just for completeness, one more possibility is to use an _internal_ SignalHead driven by the layout status, and then write a script that watches that SignalHead and sends the right commands to the

Steve, I don't think that it will be easy with existing JMRI signal head "type" definitions. The SE8c uses an odd encoding of two turnout addresses and both states of each turnout. It uses a "last

Ken thanks. I tried to create Sensors and Turnouts in both OpenLCB connections. Selecting "Make Sensor" or "Make Turnout" creates sensors or turnouts in the first connection only. Manually entering an