开云体育

Bosse, Please confirm that JMRI is having problems with the L2T112 item? That would make sense to me, as JMRI sees L2T112 as a LocoNet "turnout" item (as specified by the "T" in the system name).

Hi Billybob You can call me Bosse. My setting is Roco, Roco Z21 in Preferences now I have added Digitrax, BT Locobridge and goes towards the bluetooth interface to MGP servers and sensors on the

Dave, Thanks, I will verify this tonight, and see how it goes. Hopefully all will be resolved once I am in Direct Mode. Regards James

OK, so JMRI accepts the track occupancy feedback when it comes through a plain LocoNet interface, but not when it goes though the Z21 and then over to JMRI. Something strange either in Z21 or the

I might be overlooking something but I can't find a setting to create a dcc4pc connection using simulated hardware. I haven't yet purchased any dcc4pc hardware and was wanting to create a version of

Hello Anders. I wrote the wrong address on "SW_REP: address 201 state: closed" should be 112. My setting was Roco, Roco Z21 in Preferences now I added Digitrax, BT Locobridge. I got another tab in

Hej Bo and others I have no answer to what is wrong but some more info to those that know JMRI and perhaps Z21: You have Z21 as an interface between JMRI and the LocoNet. On the LocoNet you have a

James, Almost (if not) all modern decoders support Direct mode programming (read/write). Direct mode is very much faster and (for many DCC systems and decoders) gives more reliable results. JMRI is

Dave, I will test Monday night when I get back to the system, using Direct Mode and making the preference changes as well. Can CV's be read in Direct Mode, and is this true for all decoder brands,

bossevest, (Is that a "friendly name"? If not, please provide us something to call you.) Below is information about LocoNet messaging and JMRI. I have _zero_ experience and knowledge about Z21, so

Dave, Thank you for the response, I’ll try this out and report back. Thank you, Jasen Jasen

David, In most cases, good advice. Any "decoders" folder and the "decoderIndex.xml" found in User Files Location are best quarantined, they often indicate installation of between-releases updates,

James, It sounds like a DCC system-specific issue, or a loco-specific issue. Try turning off the caching options in Preferences->Roster->Programmer. (Enable Show CV numbers in tooltips but turn the

Another member was at the club today and found something while googling the issue and here is what I got from him. The local decoder file and decoder index.xml cause the bug. I pulled them into a

Dave/Ken; My hunch last night was confirmed today. I started up DP and after a bit I attempted to go to get the log file and still got an error. I uploaded a screen shot of the error in the folder

Hello, This email message is a notification to let you know that a file has been uploaded to the Files area of the [email protected] group. *File:* Java Error.pdf *Uploaded By:* David Klemm

I have never heard of this particular sensor. Can you point to any documentation on it? I am having some trouble deciphering this statement. There are three different monitors involved here: The raw

Hi All, I forgot to add to my original post, that i am using Java 1.8.0_211 and that reading Soundtraxx Decoders works just fine on the same programming track, in this case an Athearn Genesis SD70ACe

Hi All, I had one thought, could this be related to the firmware version contained in the LokSound Select decoders themselves, not being at a level high enough, or the reverse, that the firmware level

Hi All, I am having some issues with JMRI for the first time while I have been programming a Loksound Select decoder as part of using the Read type from decoder function. I am trying to standardize a