开云体育

OK. Thanks Peter G

----- Forwarded Message ----- To: "JMRIusers@..." <JMRIusers@...> Sent: Wednesday, March 7, 2018 10:21 PM Subject: Subject: Issues with latest version 4.10 Hello, I'm having

OK, since we are talking sensor tables again, I have a few questions for those with knowledge of Team Digital BlocD8 sensors, although these questions might refer to any sensor. In Panel Pro, on the

That was it. The default preferences were not all set to Loconet. Changed them, restarted and now all the turnouts work.? Thanks for the help Sent via the Samsung Galaxy S7 edge, an AT&T 4G LTE

At a guess you initially bound the socket before you opened it. You closed the socket but never unbound it so it is still "attached" to the original instance when you try to open it again. Try an

Hi Folks Thanks for the info on the latest test version Will make the change to this version and try it; will let the group know what occurs John Stewart www. bhamrails.info

Hi Dave, thanks for the explanation, and thanks again for fixing my xml file. Now back to playing trains. Cheers, Darren

Peter G, Yes the sensor button in the table is a known issue with 4.11.3. It is fixed in 4.11.4 which will be released sometime soon. I think the cycle has another week to go. -Ken Cameron, Member

Hi All I recently succeeded in getting a number of computers running JMRI to share sensor information with each other using sockets. The only problem is that I cannot work out how two close the

Hi, I just upgraded from test release 4.11.2 to 4.11.3 and I find I cannot now change the state of any sensors from inside the sensor table. Clicking on the button has no effect. I have reverted to

It much depends on the deadlines. Im currently unemployed so now i can dedicate time to this, but I cannot guarantee the same dedication in case i get a job, sooner or later. Which is the tipical time

Mike and John, JMRI 4.10 has known problems in acquiring and releasing LocoNet throttles. This includes acquisition via WiThrottleServer. JMRI version 4.11.3 included some SIGNIFICANT improvements to

Harold, The only thing is you will have to create the sensors first for the AIU's to be seen. -Ken Cameron, Member JMRI Dev Team www.jmri.org www.fingerlakeslivesteamers.org www.cnymod.com

We've now come to the conclusion that you will be fine. -- Dave in Australia The New England Convention 2018 http://www.newenglandmodelrailwayclub.com/content/convention.shtml

Dave, My understand of the command station cycle is it polls all cab addresses either fast (ones it has got responses before) and those that didn't respond (infrequent to see something get added). So

It much depends on the deadlines. Im currently unemployed so now i can dedicate time to this, but I cannot guarantee the same dedication in case i get a job, sooner or later. Which is the tipical time

Dave/Ken, I'm sure you understand your exchanges but, for me, they may as well be in Chinese!.? The bottom line for me is, once I have v1.65b software in my SB3a, will JMRI receive the signals from

My guess is that the 0x8A command uses the CS Memory Block to compare/store the last polled state for the AIU, hence populating the last two bytes. It's possible the Power CS does actually poll all

Well I figured it out. I had defined the cars as 'passenger' in the drop down menu under the cars menu but I had not checked the box underneath the drop down which has a list of passenger, caboose,

Tried the Power Pro and the only difference was that it used the 0x8A command instead of the 0x9B command and got a 4 byte reply instead of a 2 byte reply. There were no memory read commands from