开云体育

Sorry Seth, I got my groups mixed up, my bad!! -ken c

That’s the LDSIG motto: make only new mistakes

Hi there I would like to add a power on power off button to my panels I have found the icons to add to the internal sensors but no script Many thanks in advance for any assistance Peter

We are very pleased to announce that the 4.13 series of JMRI test releases has resulted in a version that's good enough to be recommended for general use, including by new users. We're therefore

/On 12/23/2018 7:50 AM, Dale Gloer wrote:// / ??? Stupid question but does the DCS240 also do this or did they change the software? -- Jon Miller For me time stopped in 1941 Digitrax Chief/Zephyr

Reading CVs is not a simple case of asking for the value in a CV and reading the answer.? To read a CV the command station sends a packet to that CV with a value - usually starting a x'00' - and

Thank you for replying.? I do direct byte programming wherever I go, thank you for that confirmation.? It just perplexes me that the speed of communication between the controller and locomotive in a

Really simple, and for everyone:?? "'The download links below are for all installs - new and update.? If you are updating from a version prior to x.xx.x, see the data migration steps that may be

Yes.? What Jan and Tom said (in his second thoughts) would be solve this problem 100%.

I merged something similar to the suggestion below while doing the JMRI 4.14 update. I dialed it back a little bit, as it ended up being somewhat repetitive. Repetition can help understanding, but it

Let's start at the beginning. Defined the JMRI connection to the SUSIC which is built with the RS232 parts to match the match the Keyspan. Baud rate and card configured to address 0?? Or is there an

Dave, If you made a mistake you think anybody else might make, let us know. It might serve to help others avoid the same hang up. It is like the OpSig rule: Only make new mistakes. -Ken Cameron,

Hello Tim, Creating a clean loop sound could be challenge. I also have the experience that taking a zero crossing point may be insufficient. Another cause for a "bad click" could be a bug in a JMRI

Hey Sorry Guys, found my mistake. Got it working now. Dave, Brisbane Australia

Hello All, I wanted to have a go at configuring MQTT in JMRi 13.7. I have been able to connect to broker.hivemq.com and I have MQTT Dashboard on my phone. I tried to add a turnout to the turnout table

Hi Timothy, While my experience with jmri is very limited (so far), my professional expertise is in the audio realm. It is probably something like the decoder creating an endpoint in the waveform that

123 is the key to the question. 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%

My version is 4.11.4+R4534304. I checked defaults, and yes it had changed to internal.? I reset to NCE as you suggested.? Now working perfectly.? THANKS to Peter and Tom.? I will get the upcoming

Hey Timothy, It may indeed be something else, something like you hypothesized... but, it might be the nature of the waveform on either side of the zero crossing. ?For example, if the signal is

I'd say start by confirming the node configuration is showing the right type and bits of the I/O cards on the SUSIC. Next confirm you have the right turnout names for those cards. So the turnouts