¿ªÔÆÌåÓý

Date

Locked Win10 ITO

 

Has anyone ever tried JMRI on a RasPi running Win 10?????

Talmadge C 'TC' Carr
Sn42 and Hn42 somewhere in the wilds of the Pacific Northwest
group_list@...


Locked Re: Tortoise wiring

 

Ya, but if they accidentally let it go while moving over the switch it's
going to return to whatever position the DS had it set to originally... Can
you say "break out the Dixie cups!"????

JD

-----Original Message-----
From: jmriusers@... [mailto:jmriusers@...]
Sent: Wednesday, August 16, 2017 11:25 AM
To: jmriusers@...
Subject: Re: [jmriusers] Tortoise wiring

I would add if you can locate spring loaded dpdt switch, the local crew can
hold the switch in the "Hand" position while they operate the toggle for the
switch motor. When they are done, releasing the spring loaded switch will
return the control to JMRI automatically. Dispatcher then has control again
without relying on the crew to return control. Cheers!



Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: "'Jim Duncan' jdbandman@... [jmriusers]"
<jmriusers@...>
Date: 8/16/17 10:05 AM (GMT-07:00)
To: jmriusers@...
Subject: RE: [jmriusers] Tortoise wiring



Put a second DPDT toggle in. The 2 center pins to the switch motor. Top pair
to JMRI connection. Bottom pair to local control toggle. Label above
selector as follows: Above "HAND" Below "POWER".

Now the DS can give your crews permission to take switch on hand! Just
remember to remind them that they need to tell the DS when they are
returning control of the switch back to him!!! It DOES tend to annoy
dispatchers when they can't throw a controlled switch and the local crew is
now several miles on down the line and there's mobody around to restore the
switch to the power position! <G>

Jim Duncan

-----Original Message-----
From: jmriusers@... [mailto:jmriusers@...]
Sent: Wednesday, August 16, 2017 10:31 AM
To: jmriusers@...
Subject: [jmriusers] Tortoise wiring

I have my tortoise machines wired to dpdt switches on the facia. a common
installation.
I now want to wire the to RR-Cirkits Signalman boards for use through JMRI
panel pro.
Can anyone tell me how I would wire the so as to still retain control on the
facia when I am not using JMRI.
Thank you
JZ



------------------------------------
Posted by: mt813@...
------------------------------------

------------------------------------

Yahoo Groups Links









------------------------------------

------------------------------------


------------------------------------

Yahoo Groups Links


Locked Re: Tortoise wiring

 

Another option: (expensive, but cool!)

A key operated switch that holds the key when it's turned from it's normal position. The local crew is issued a switch key and has to keep it with them. Now, when they forget their switch lock key, the have to sit without moving the train for the amount of time it would take for the brakeman to walk to the last place he used it and back to the head end of the train... 5 miles out and back, easily a two to 2.5 hour delay! <evil laughter ensues>

Jim Duncan

-----Original Message-----
From: jmriusers@... [mailto:jmriusers@...]
Sent: Wednesday, August 16, 2017 11:42 AM
To: jmriusers@...
Subject: [jmriusers] Re: Tortoise wiring

What he said¡­ ;-)



(I was typing up a rather verbose answer when his posted¡­ and said pretty much exactly what I was typing... just somewhat more succinctly... ;-)





Basically the MotorMan (and WatchMan) inputs can be configured to output a SSB(/LocoNet) command to close/throw a turnout. If a MotorMan on that same SSB(/LocoNet) is configured to respond to that command then it will close/throw the turnout associated with that command. (The WatchMan sending the command and the WatchMan that responds to that command can be the same WatchMan.)













------------------------------------
Posted by: geowar1@...
------------------------------------


------------------------------------

Yahoo Groups Links


Locked Tortoise wiring

Model Railroad Builder
 

For local control of switches I have installed panels locally with a toggle switch, a key switch that captures the key until returned to normal and an LED for indication that it is in hand not machine.

If the crew leaves without the key and it is on hand they likely will recognize that and retrieve the key thereby returning to machine control. As Mr. Duncan knows you don't want to upset the DS.

Mouser sells several key switches. Www.mouser.com you may want to consider this option.

I'm using with C/MRI but can be adapted to JMRI.

Mark Juett
Ace Services LLC
Your First Choice
www.modelrailroadbuilder.com
Begin forwarded message:

From: "Richard Bell katmedia@... [jmriusers]" <jmriusers@...>
Date: August 16, 2017 at 11:24:36 AM CDT
To: "jmriusers@..." <jmriusers@...>
Subject: Re: [jmriusers] Tortoise wiring
Reply-To: jmriusers@...

I would add if you can locate spring loaded dpdt switch, the local crew can hold the switch in the "Hand" position while they operate the toggle for the switch motor. When they are done, releasing the spring loaded switch will return the control to JMRI automatically. Dispatcher then has control again without relying on the crew to return control. Cheers!



Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: "'Jim Duncan' jdbandman@... [jmriusers]" <jmriusers@...>
Date: 8/16/17 10:05 AM (GMT-07:00)
To: jmriusers@...
Subject: RE: [jmriusers] Tortoise wiring



Put a second DPDT toggle in. The 2 center pins to the switch motor. Top pair
to JMRI connection. Bottom pair to local control toggle. Label above
selector as follows: Above "HAND" Below "POWER".

Now the DS can give your crews permission to take switch on hand! Just
remember to remind them that they need to tell the DS when they are
returning control of the switch back to him!!! It DOES tend to annoy
dispatchers when they can't throw a controlled switch and the local crew is
now several miles on down the line and there's mobody around to restore the
switch to the power position! <G>

Jim Duncan

-----Original Message-----
From: jmriusers@... [mailto:jmriusers@...]
Sent: Wednesday, August 16, 2017 10:31 AM
To: jmriusers@...
Subject: [jmriusers] Tortoise wiring

I have my tortoise machines wired to dpdt switches on the facia. a common
installation.
I now want to wire the to RR-Cirkits Signalman boards for use through JMRI
panel pro.
Can anyone tell me how I would wire the so as to still retain control on
the facia when I am not using JMRI.
Thank you
JZ



------------------------------------
Posted by: mt813@...
------------------------------------

------------------------------------

Yahoo Groups Links









------------------------------------

------------------------------------


------------------------------------

Yahoo Groups Links



Locked Re: Test version 4.9.2 of JMRI/DecoderPro is available for download

 

The error is caused by opening my panel file with JMRI version 4.9.2. The panel file is loaded without error in versions 4.9.1 and prior. I have uploaded a copy of the panel file to the following Yahoo group folder:

ProblemsBeingWorkedOn/Craig G

Could someone please take a look at the panel file? Thanks in advance for your help.

Craig

On 08/15/2017 02:53 PM, Craig Goodyear cjhs22a@... [jmriusers] wrote:
On 08/13/2017 09:06 PM, Bob Jacobsen jacobsen@... [jmriusers] wrote:
Test version 4.9.2 of JMRI/DecoderPro is available for download.
I am seeing an error in the system console log that was not there with
JMRI 4.8.
2017-08-15 14:32:48,351 automat.Siglet ERROR -
Siglet start invoked, but defined no inputs [AWT-EventQueue-0]
Does this indicate a possible error in my panel file, or is it a bug?
I'm running Fedora 26 operating system with Java 1.8.0_141. Below is the
complete output from the system console.
Craig
2017-08-15 14:32:42,391 util.Log4JUtil INFO -
* JMRI log ** [main]
2017-08-15 14:32:42,542 util.Log4JUtil INFO -
This log is appended to file: /home/craig/.jmri/log/messages.log [main]
2017-08-15 14:32:42,545 util.Log4JUtil INFO -
This log is stored in file: /home/craig/.jmri/log/session.log [main]
2017-08-15 14:32:42,617 apps.Apps INFO -
PanelPro version 4.9.2+Rff24066 starts under Java 1.8.0_141 on Linux
amd64 v4.12.5-300.fc26.x86_64 at Tue Aug 15 14:32:42 CDT 2017 [main]
2017-08-15 14:32:43,396 apps.Apps INFO -
Starting with profile Dover_Oakland.3f4c226b [main]
2017-08-15 14:32:43,658 node.NodeIdentity INFO -
Using jmri-52540095A9D2-3f4c226b as the JMRI Node identity [main]
2017-08-15 14:32:44,427 locobuffer.LocoBufferAdapter INFO -
/dev/ttyUSB0 port opened at 57600 baud with DTR: true RTS: true DSR:
true CTS: true CD: false [main]
2017-08-15 14:32:45,271 apps.PerformFileModel INFO -
Loading file /home/craig/.jmri/Dover_Oakland/Dover_Oakland_SH_2.xml [main]
2017-08-15 14:32:48,351 automat.Siglet ERROR -
Siglet start invoked, but defined no inputs [AWT-EventQueue-0]
2017-08-15 14:32:52,239 apps.PerformScriptModel INFO -
Running script /home/craig/.jmri/Dover_Oakland/Initilize_Turnouts.py [main]
2017-08-15 14:32:52,254 script.JmriScriptEngineManager INFO -
python 2.7 is provided by jython 2.7.0 [main]
2017-08-15 14:32:52,293 script.JmriScriptEngineManager INFO -
ECMAScript ECMA - 262 Edition 5.1 is provided by Oracle Nashorn
1.8.0_141 [main]
2017-08-15 14:33:02,428 util.FileUtilSupport INFO -
File path program: is /home/craig/JMRI/ [main]
2017-08-15 14:33:02,453 util.FileUtilSupport INFO -
File path preference: is /home/craig/.jmri/Dover_Oakland/ [main]
2017-08-15 14:33:02,454 util.FileUtilSupport INFO -
File path profile: is /home/craig/.jmri/Dover_Oakland/ [main]
2017-08-15 14:33:02,454 util.FileUtilSupport INFO -
File path settings: is /home/craig/.jmri/ [main]
2017-08-15 14:33:02,454 util.FileUtilSupport INFO -
File path home: is /home/craig/ [main]
2017-08-15 14:33:02,454 util.FileUtilSupport INFO -
File path scripts: is /home/craig/JMRI/jython/ [main]


Locked Re: Test version 4.9.2 of JMRI/DecoderPro is available for download

 

FYI Nelson, when writing to an ESU decoder, there are over 1500 CVs to write,
that does take some time. I also use the SPROG, when writing or reading with the
SPROG, I just go do something else, like get supper ready or cut the lawn.

John

---------- Original Message ----------
From: "nelson.allison@... [jmriusers]" <jmriusers@...>
Date: August 16, 2017 at 10:02 AM


tested on a Windows 7 system (mainly Panel Pro) all functioning as normal,
converted CMR/I hardware to cpNode hardware (which it is), some tweaking
required but hardware functioning as expected. Documentation on setting up the
cpNode software would be an asset.


tested decoderpro on a pi-sprog and all functions are working as
expected.....still way slow to read ESU decoders.





Locked Re: Tortoise wiring

 

What he said¡­ ;-)

(I was typing up a rather verbose answer when his posted¡­ and said pretty much exactly what I was typing... just somewhat more succinctly... ;-)


Basically the MotorMan (and WatchMan) inputs can be configured to output a SSB(/LocoNet) command to close/throw a turnout. If a MotorMan on that same SSB(/LocoNet) is configured to respond to that command then it will close/throw the turnout associated with that command. (The WatchMan sending the command and the WatchMan that responds to that command can be the same WatchMan.)


Locked Re: Tortoise wiring

 

JZ,

I think you mean MotorMan, not SignalMan.

Untested theory follows:
1) The MotorMan has an eight port Input/Output socket. Essentially half of a TowerMan.
2) The DPDT is replaced by a SPST (or wired to behave as one).
3) The I/O socket is configured as Input and to send a switch request.
4) A motor output entry is configured to listen for that switch request.
5) When it the SPST is changed, the switch request drives the Tortoise.

Notes:
1) Once a xxxxMan board is configured, it listens for and responds to events on the SSB bus and the LocoNet by way of the SSB-Gateway.
2) When JMRI is running, JMRI might not know the turnout position if someone uses the toggle switch.


Dave Sand


Locked Re: Tortoise wiring

 

I would add if you can locate spring loaded dpdt switch, the local crew can hold the switch in the "Hand" position while they operate the toggle for the switch motor. When they are done, releasing the spring loaded switch will return the control to JMRI automatically. Dispatcher then has control again without relying on the crew to return control. Cheers!



Sent from my Verizon, Samsung Galaxy smartphone

-------- Original message --------
From: "'Jim Duncan' jdbandman@... [jmriusers]" <jmriusers@...>
Date: 8/16/17 10:05 AM (GMT-07:00)
To: jmriusers@...
Subject: RE: [jmriusers] Tortoise wiring



Put a second DPDT toggle in. The 2 center pins to the switch motor. Top pair
to JMRI connection. Bottom pair to local control toggle. Label above
selector as follows: Above "HAND" Below "POWER".

Now the DS can give your crews permission to take switch on hand! Just
remember to remind them that they need to tell the DS when they are
returning control of the switch back to him!!! It DOES tend to annoy
dispatchers when they can't throw a controlled switch and the local crew is
now several miles on down the line and there's mobody around to restore the
switch to the power position! <G>

Jim Duncan

-----Original Message-----
From: jmriusers@... [mailto:jmriusers@...]
Sent: Wednesday, August 16, 2017 10:31 AM
To: jmriusers@...
Subject: [jmriusers] Tortoise wiring

I have my tortoise machines wired to dpdt switches on the facia. a common
installation.
I now want to wire the to RR-Cirkits Signalman boards for use through JMRI
panel pro.
Can anyone tell me how I would wire the so as to still retain control on
the facia when I am not using JMRI.
Thank you
JZ



------------------------------------
Posted by: mt813@...
------------------------------------

------------------------------------

Yahoo Groups Links


Locked Re: Tortoise wiring

 

Put a second DPDT toggle in. The 2 center pins to the switch motor. Top pair
to JMRI connection. Bottom pair to local control toggle. Label above
selector as follows: Above "HAND" Below "POWER".

Now the DS can give your crews permission to take switch on hand! Just
remember to remind them that they need to tell the DS when they are
returning control of the switch back to him!!! It DOES tend to annoy
dispatchers when they can't throw a controlled switch and the local crew is
now several miles on down the line and there's mobody around to restore the
switch to the power position! <G>

Jim Duncan

-----Original Message-----
From: jmriusers@... [mailto:jmriusers@...]
Sent: Wednesday, August 16, 2017 10:31 AM
To: jmriusers@...
Subject: [jmriusers] Tortoise wiring

I have my tortoise machines wired to dpdt switches on the facia. a common
installation.
I now want to wire the to RR-Cirkits Signalman boards for use through JMRI
panel pro.
Can anyone tell me how I would wire the so as to still retain control on
the facia when I am not using JMRI.
Thank you
JZ






------------------------------------
Posted by: mt813@...
------------------------------------


------------------------------------

Yahoo Groups Links


Locked Tortoise wiring

 

I have my tortoise machines wired to dpdt switches on the facia. a common installation.
I now want to wire the to RR-Cirkits Signalman boards for use through JMRI panel pro.
Can anyone tell me how I would wire the so as to still retain control on the facia when I am not using JMRI.
Thank you
JZ


Locked Re: Test version 4.9.2 of JMRI/DecoderPro is available for download

 

Nelson,
Regarding reading of ESU decoders being way too slow, that is a result of their complexity. When writing a sound file to an ESU with their own LokProgrammer hardware, it takes 30 minutes or so. Just a lot there to deal with.
Tom Wilson


Locked Re: Roco Zimo decoder question

 

Dear All,

I just checked the updates for all sound decoders on the ZIMO page and all versions up to 37.0 are documented :-



You have to click on the + sign which is an expand button next to the "f¨¹r ALLE Sound-Decoder MX640-MX658, MX690-MX699" line to see all the updates. The description of the update is in German and English. It includes definitions of new CVs added to expand the functionality.

Regards
John Russell

---In jmriusers@..., <acarasso_fr@...> wrote :

Hi Thomas

If identifying the decoder model doesn't give you anything, it could be that your new BR85 has got an MX645P22 with the latest SW release 37 (version number is stored in CV7). This new release is not detected by current version 4.8 (July release) or 4.9.1 (July test release).


Thus:
>>> Either just add you lok using the MX645P22 from the Version 32 Plus family
>>> Or wait for test version 4.9.2 which will detect SW release from 36 to 40


Using MX645P22 from either Version 32 Plus Family or from the future Version 36 Plus Family will have the same features as Zimo has not published any information about updates made with SW release higher than
35.


Alain


Locked Re: Test version 4.9.2 of JMRI/DecoderPro is available for download

 

tested on a Windows 7 system (mainly Panel Pro) all functioning as normal, converted CMR/I hardware to cpNode hardware (which it is), some tweaking required but hardware functioning as expected. Documentation on setting up the cpNode software would be an asset.


tested decoderpro on a pi-sprog and all functions are working as expected.....still way slow to read ESU decoders.


Locked Re: Slot monitor is blank

 

Something to add to your Trouble shooting list

CHECK THE LOCO BUFFER FOR A LOOSE CONNECTION ~!

All is working now
Thanks for your help





Terry
Visit My Web site@

-----Original Message-----
From: 'Ken Cameron' kcameron@... [jmriusers] <jmriusers@...>
To: jmriusers <jmriusers@...>
Sent: Wed, Aug 16, 2017 7:37 am
Subject: RE: [jmriusers] Slot monitor is blank






Terry,

One of the reasons that the uninstall and clear out the program directory
may be needed now and then is that the many upgrades may miss deleting some
of the old parts for one reason or another. So the software will work with
'add on' packages like CATS, when it runs it loads what it finds. If
something had been left around over time, it could get loaded and interfere
with the newer correct parts.

At this point your descriptions and logs show the LocoBuffer is our major
suspect. Here is a clip from the manual about testing the LocoBuffer. Give
it a try and see if that helps to confirm it working or not.

6.1 Sanity Test

To perform a very basic LocoBuffer-USB sanity test perform the following

steps:

1. Unplug the LocoNetR cable. Disable the internal LocoNet terminator if

enabled. (remove any internal jumper at "Term")

2. Power up the LocoBuffer-USB by plugging it into the computer.

3. The lower green power LED should come on.

4. Plug in the LocoNetR cable. The upper green power LED should light.

5. Unplug the LocoNetR cable. The red activity light should blink briefly as

the cable is removed.

6. Restore the termination jumper to its original position if used.

If the lower green power LED does not light, be sure that the USB drivers

have been properly installed. The LocoBuffer-USB does not power up

until the drivers have properly enumerated. (installed and started up)

If the Rail Sync upper power LED does not light, or if the activity LED

does not blink when you unplug the LocoNetR cable, be sure that your

DCC command station is powered up, then check your LocoNetR wiring.

To further test the LocoBuffer-USB you may also perform the following

Loop Back test.

6.2 Loop Back Test

The LocoBuffer-USB input circuit and code actually reads from the unit's

LocoNetR output jack, so if you send a character it should be seen on the

input This test uses the free software available from the JMRI project to

watch the test commands. (www.jmri.org)

Steps:

1. Open the JMRI LocoNetR Monitor window.

2. Using a throttle send a speed change to a locomotive.

3. The set speed commands should appear in the LocoNetR monitor

window and the LocoBuffer-II activity LED should blink

4. Using JMRI send some commands (e.g. switch commands)

5. The commands should appear in the LocoNetR monitor window and the

LocoBuffer-II activity LED should blink

If there is no activity light when throttle commands are sent, check the

LocoNetR wiring. If there is no activity shown in the LocoNetR monitor

window, check that you have LocoBuffer-USB selected in the JMRI

preferences, or that you have LocoBuffer selected and are running at

57.6Kb. Check that you have the correct COM port selected.

Emailing RR-CirKits may be helpful and Dick and Karen are good with
responding to email.

-Ken Cameron, Member JMRI Dev Team

www.jmri.org

www.fingerlakeslivesteamers.org

www.cnymod.com

www.syracusemodelrr.org

[Non-text portions of this message have been removed]










[Non-text portions of this message have been removed]


Locked Re: Digiblast

 

Hi Michael,

Where are you seeing that EngineDriver is limited to 3 engines on a single train? That needs to be corrected. EngineDriver can have up to three separate throttles, each of which can have any number of engines assigned.
As for the steal, if you request an address via EngineDriver that is already in use, the user is prompted to Steal? that address. This works fine for individual addresses between phones. I do not have any Digitrax throttles, so I can't test your scenario.
Do you know if your procedure with the Digitrax throttle is creating what Digitrax calls a "Universal" (command-station-stored) consist or an "Advanced" (decoder-stored) consist?


Regards,
SteveT


Locked Re: Slot monitor is blank

 

On Aug 16, 2017, at 8:23 AM, terryintexas7@... [jmriusers] <jmriusers@...> wrote:

Its a Loco Buffer USB and it has 2 green lights and both are working
Have you tried a different Loconet port and/or a different Loconet cable?

I ask because last night I went through the process of installing a new LocoBuffer USB at my train club to replace one that was destroyed. I had two Loconet ports available near the computer. Plugging in to either of the ports caused all the LEDs to turn on, but only one of the two ports was giving me a Loconet signal.

The cables can certainly wear out over time. ( Movement can cause an open circuit in one or more of the signal wires. The plugs can also wear out from repeated use.)


Paul


Locked Re: Slot monitor is blank

 

Terry,



One of the reasons that the uninstall and clear out the program directory
may be needed now and then is that the many upgrades may miss deleting some
of the old parts for one reason or another. So the software will work with
'add on' packages like CATS, when it runs it loads what it finds. If
something had been left around over time, it could get loaded and interfere
with the newer correct parts.



At this point your descriptions and logs show the LocoBuffer is our major
suspect. Here is a clip from the manual about testing the LocoBuffer. Give
it a try and see if that helps to confirm it working or not.



6.1 Sanity Test

To perform a very basic LocoBuffer-USB sanity test perform the following

steps:



1. Unplug the LocoNetR cable. Disable the internal LocoNet terminator if

enabled. (remove any internal jumper at "Term")

2. Power up the LocoBuffer-USB by plugging it into the computer.

3. The lower green power LED should come on.

4. Plug in the LocoNetR cable. The upper green power LED should light.

5. Unplug the LocoNetR cable. The red activity light should blink briefly as

the cable is removed.

6. Restore the termination jumper to its original position if used.



If the lower green power LED does not light, be sure that the USB drivers

have been properly installed. The LocoBuffer-USB does not power up

until the drivers have properly enumerated. (installed and started up)

If the Rail Sync upper power LED does not light, or if the activity LED

does not blink when you unplug the LocoNetR cable, be sure that your

DCC command station is powered up, then check your LocoNetR wiring.

To further test the LocoBuffer-USB you may also perform the following

Loop Back test.



6.2 Loop Back Test

The LocoBuffer-USB input circuit and code actually reads from the unit's

LocoNetR output jack, so if you send a character it should be seen on the

input This test uses the free software available from the JMRI project to

watch the test commands. (www.jmri.org)

Steps:



1. Open the JMRI LocoNetR Monitor window.

2. Using a throttle send a speed change to a locomotive.

3. The set speed commands should appear in the LocoNetR monitor

window and the LocoBuffer-II activity LED should blink

4. Using JMRI send some commands (e.g. switch commands)

5. The commands should appear in the LocoNetR monitor window and the

LocoBuffer-II activity LED should blink



If there is no activity light when throttle commands are sent, check the

LocoNetR wiring. If there is no activity shown in the LocoNetR monitor

window, check that you have LocoBuffer-USB selected in the JMRI

preferences, or that you have LocoBuffer selected and are running at

57.6Kb. Check that you have the correct COM port selected.



Emailing RR-CirKits may be helpful and Dick and Karen are good with
responding to email.



-Ken Cameron, Member JMRI Dev Team

www.jmri.org

www.fingerlakeslivesteamers.org

www.cnymod.com

www.syracusemodelrr.org


Locked Re: Loconet throttles with SPROG command station

 

On Aug 16, 2017, at 2:15 AM, torgrimg@... [jmriusers] <jmriusers@...> wrote:
A question from a newbie:
Is it possible to have LocoNet throttles on a standalone LocoNet connected to jmri via a Locobuffer,
and have the throttles control an SPROG running as command station?
Not with a standalone Loconet.

While it is possible for JMRI to bridge throttles from one system to another, to make this work on a Loconet system, you have to be able to read the slot associated with the throttle. No command station means there are no slots to read.


Paul


Locked Re: Slot monitor is blank

 

Its a Loco Buffer USB and it has 2 green lights and both are working

I can't call because i am mute due to throat cancer
so i'm stuck with email or texting

Its way out of warranty and It will be awhile before i could buy a new one if it is needed





Terry
Visit My Web site@

-----Original Message-----
From: 'Ken Cameron' kcameron@... [jmriusers] <jmriusers@...>
To: jmriusers <jmriusers@...>
Sent: Wed, Aug 16, 2017 7:17 am
Subject: RE: [jmriusers] Slot monitor is blank






Terry,

My idea was finding anything in JMRI that talks to the layout that worked.
So far it is sounding like the real issue may be a problem in the
LocoBuffer. One thing about the LocoNet Stats, if the wrong flavor of
LocoBuffer is picked in the config, it won't display right.

Asking about the JMRI throttle was an example of something that would talk
to the LocoBuffer as more proof the layout connection is working or not. It
sounds like the programming mode isn't working, or do you have some
locos/decoders that you can read and write from JMRI??

I'd ask about the lights on the LB, but that would require knowing exactly
which LB you have and there are enough slightly different ones, I'd not be
the right person for that. If you feel you have reason to suspect the
LocoBuffer, and it came from RR-CirKits, call them and they can step you
through a couple of tests to know if it working or not.

[Non-text portions of this message have been removed]