Re: Panel Block Occupancy

#154195

Perhaps you could associate that siding block with an internal sensor (taking the place of a hardware detector’s sensor) that your scripts could set active/inactive as they follow the train.

Bob

Show quoted text

On Dec 6, 2018, at 8:55 AM, David Smith via Groups.Io <daversmth@...> wrote:

I use a PanelPro panel to display block occupancy, with the name of the loco occupying the block added.
Each block has a hardware sensor and that all works fine.

My layout is operated using my own Jython script to dispatch and route the trains.

For sidings, I am considering not having an occupancy detector in the siding, but using the fact that the script knows where it has routed the train to  ( ie which siding ) . so when the previous block sensor goes inactive, I know that the train has then entered the siding. So I can detect its presence in the siding by inference, without the need for a block occupancy hardware detector. But if I do this, is there anyway to show the block as occupied, with the loco name, in the panel. The main application is for a turntable where I do not want to add a hardware detector on each radial track, but just have one for the turntable track.

Panel Block Occupancy

#154194

Hi All,

I use a PanelPro panel to display block occupancy, with the name of the loco occupying the block added.
Each block has a hardware sensor and that all works fine.

My layout is operated using my own Jython script to dispatch and route the trains.

For sidings, I am considering not having an occupancy detector in the siding, but using the fact that the script knows where it has routed the train to? ( ie which siding ) . so when the previous block sensor goes inactive, I know that the train has then entered the siding. So I can detect its presence in the siding by inference, without the need for a block occupancy hardware detector. But if I do this, is there anyway to show the block as occupied, with the loco name, in the panel. The main application is for a turntable where I do not want to add a hardware detector on each radial track, but just have one for the turntable track.

Re: Blocks next to Crossovers are inaccessible as transit destinations

#154193

Jack,

Was there a specific reason for changing from automatic SML to manual SML?  Since you had created sections from the SML, changing the SML resulted in errors during JMRI startup for the sections since they were based on the automatic SML.

I would not include six of the signal masts since they don’t appear to provide any value.  They are 15 East, 8 East, 2 West, 4 East, 10 West and 17 West.  2 West and 4 East would be OK if the Block 3 is long enough to hold a complete train.

As a rookie with using Dispatcher, I don’t use SML based sections.  I create a section for each block.  This provides me with maximum flexibility in creating transits.

Based on the above, I had no problems creating a transit from 20 to 24 and running a train using simulated block occupancy.

Dave

Show quoted text

On Dec 5, 2018, at 7:12 PM, Jack Basiago <jbasiago@...> wrote:

JMRI version: 4.13.4
Java version: 1.8.0_191
MacOS: Version 10.13

I've been working on a layout that includes 6 crossovers, 3 left hand and 3 right hand.  I've uploaded my layout to Full Yard with Signals.  I've been able to create and place signal masts at end blocks, and turnouts on the layout.  I've used the auto-generate signal pairs tool to create signal mast logic, which I ultimately had to convert to not use Layout Paths.  I also created Sections from the Signal Mast pairs.  The signal mast logic looks good to me.  I have created auto trains that traverse the layout and return successfully.

However, when creating transits for automatic trains, I ran into one issue that I can't figure out.  Because the crossovers only allow you to assign signal masts that face outside looking in, I can't create a transit that includes the block next to a crossover as a destination.  For instance, if I create a transit to go from the end of 20 to the end of 24, the last block at 24 is inaccessible because there is no signal mast for 24 East, only 23 West at the open end of block 24.  I could create the signal mast, but I have nowhere to attach it because the crossover prevents the mast from being assigned to position C.  Only 23 West can be assigned to C of that crossover.  As a result, the last block for the transit would then be 23.  How do I create a section / transit that allows me to park a train in a block after the crossover; block 24?

Of course, I could create another block beyond 24, but that would require an additional block detection circuit for each end track in the layout.

What am I missing?

Thanks,
Jack Basiago

Re: Blocks next to Crossovers are inaccessible as transit destinations

#154192

Have you set Buffer Stops at the end and added Buffer Stop masts?

Re: MQTT Connection in JMRI

#154191

Note: I didn’t write the MQTT code in JMRI, so might not know what I’m talking about there.

I think it would be good to add JMRI Sensor code to go alongside the JMRI Turnout code.  Some parts of it seem to be there, but large parts are missing. In particular, there’s nothing about mapping MQTT traffic to particular sensors:  How to figure out names, states, etc.

Is there somebody with MQTT knowledge interested in working with me on that? I can do the JMRI part, but don’t know enough about how people would want it to work.

Bob

Show quoted text

On Dec 5, 2018, at 5:53 AM, Nathan Tableman <nathan@...> wrote:

Now what I really need is for mqtt to be supported for sensors/block detection. Anyone got this to work using python, seems like some people have come close when I hunt around. My goal is to use all these adafruit feathers I have sitting around to send mqtt messages about block detection with a goal being a track powered wireless block detection system. Look, mom, no wires!

Re: No NCE connection

#154190

A timely warning, which Marcus does mention at:
<>

Removal of the posts for testing needs to be done with command station cover removed to ensure no loose hardware and the posts must be replaced after testing/modification in order to avoid stress failure of solder connections etc. on the top board. Leaving them off permanently is not a viable option.
-- 
Dave in Australia

Show quoted text

On 6 Dec 2018, at 11:42 PM, Ken Cameron <kcameron@...> wrote:

A caution about removing the mounting studs is to not leave loose hardware
inside the command station box. If you do decide to remove the external
parts, remove the internal too.

Re: No NCE connection

#154189

A caution about removing the mounting studs is to not leave loose hardware
inside the command station box. If you do decide to remove the external
parts, remove the internal too.

-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.com
www.syracusemodelrr.org

Re: Signalling issue with my panel

#154188

Hi Dave,

Will have a look at SML and see if I can make it work for the main signals but the ground signals or shunt signals need to be turned on and off despite the setting of the points. ?Well those that could route in more than one direction. ?So all I need to do is set them at the start and run them manually.

regards

Doug

Re: Packet Delays and Timeout - SPROG3 and JMRI 4.12

#154187

Hi, maybe i am not understanding this but? I am using command station and turn on a throttle and almost immediately get

2018-12-06 09:21:52,183 PanelPro.PanelPro???????????????????? INFO? - Main initialization done [main]
2018-12-06 09:22:49,352 sprog.SprogCommandStation???????????? WARN? - Packet delay was 180 ms [SPROG slot thread]
2018-12-06 09:22:53,782 sprog.SprogCommandStation???????????? WARN? - Packet delay was 83 ms [SPROG slot thread]
2018-12-06 09:22:58,736 sprog.SprogCommandStation???????????? WARN? - Packet delay was 79 ms [SPROG slot thread]

Is this OK?

Re: Missing turnouts in turnout tables

#154186

Don,

In what follows, some information requests from you and maybe a few of your questions can be addressed. Our club and several of my friends use Digitrax DS100/200 Command Stations, but I have no DS240 experience. Our club uses DS44 stationary decoders, not DS64, so there is a second hole in what help I can provide.

Starting with some of the simple features first:
- What computer and operating system are you using?
- What version of JMRI and what version of Java are you using?
- What LocoNet connection are you using?
- What ERROR or WARN messages do you see on the JMRI System console window or in the log\session.log file?

开云体育

I agree, higher level protocols in a real network are (hopefully) the future of layout control. And I think the communication to the network should come directly from the layout control bus. That’s why I did the LocoNet to MQTT gateway () and programs like JMRI should get the information from there, not from a slow point to point interface. In my opinion this is also the correct layer for multi system integration. Why develop just another hardware and network layer like OpenLCB (with all the difficulties to get manufacturers to accept and support it) ?when integration simply can be done on the presentation and application layer level?

Hans

?

Re: No NCE connection

#154182

Dave wasn't meaning the USB A-B cable. He was saying from the 9 pin on the
Keyspan, you normally need a short 'straight' 9 pin cable to connect to the
front of the PowerPro.

-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.com
www.syracusemodelrr.org

Re: No NCE connection

#154181

The "Keyspan serial to USB connector" must have a 9-pin serial connector, otherwise it wouldn't be "USB to Serial" . In the case of the Keyspan, (at least the previous models) won't plug directly into the Power Pro's serial port because of fouling issues and need a 9-pin M-F straight-through cable between the Keyspan and Power Pro.

As far as alternatives are concerned:, see the document lower down in this post.

Dave

On 6 Dec 2018, at 1:18 PM, stanbmattingly@... wrote:

Thanks again for the incredibly prompt response Dave. Items #1 and # 3 in your above 5 item checklist have indeed been checked and confirmed.  Regarding Item #2, my Keyspan cable is a USB A to USB B.  I do not know if I have a "straight through" as you are asking and ask that you advise me how to tell.  Could you provide a weblink to purchase the ESU or RRCirKits cable? I will in the meantime check the helpful link in checklist Item #5.Do not try to use an NCE USB with JMRI Decoder Pro and a PH Pro system. The PH Pro firmware does not support decoder programming with the NCE USB.

<>

You need a third-party USB-Serial adaptor.

Ignore the el-cheapo RS232 to USB connectors you see at office supplies and computer stores and buy a reliable genuine FTDI chipset-based one such as these two ~$30 solutions:
<>
<> The UN8-BE is the item you want.
<>
<>
(Also ESU dealers in the UK and Australia can supply.)

Both these adaptors have the correct screw terminals rather than binding
posts and the USB cables are 1.8m long, so you do not need an extension cable. I use my ESU one regularly on a 10m Active USB extender as well.

Both work well with JMRI and have unique IDs so will not change COM ports capriciously.

Drivers download from:
<>
There are Windows 10 drivers on this site.

I have found them very stable with JMRI on Windows, Mac and Linux.

There are problems with many USB-Serial adaptors readily available in retail outlets:
1) The older PL2303 chipset version does not work with Windows 7 or 8.
2) Both thePL2303 and FTDI chipsets have been counterfeited and there are numerous non-genuine devices out there in the market place.
3) Many of the cheaper devices do not incorporate a unique serial number on-board so are likely to capriciously appear at different COM port numbers when plugged in to Windows or Mac computers.

Another problem with the USB-Serial adaptors is that many units readily available have binding posts attached to the male RS-232 plug rather than lock-down screws. This requires either physical modification of the adaptor (sometimes impossible) or the purchase of an RS-232 straight-through extension cable. However many RS-232 male-female extension cables come with null modem or crossover wiring rather than straight through.

The often-recommended Keyspan adaptor does have a genuine chipset, but it does need the extension cable in order to be able to be connected. It ends up costing considerably more than the FTDI-based cables I recommend above.

Re: No NCE connection

[email protected]

#154180

Thanks again for the incredibly prompt response Dave. Items #1 and # 3 in your above 5 item checklist have indeed been checked and confirmed.? Regarding Item #2, my Keyspan cable is a USB A to USB B.? I do not know if I have a "straight through" as you are asking and ask that you advise me how to tell.? Could you provide a weblink to purchase the ESU or RRCirKits cable? I will in the meantime check the helpful link in checklist Item #5.

Re: No NCE connection

#154179

开云体育

See my other post for further information.

In response to your specific questions:

Thanks John and Dave for your prompt responses.? John, I presume 9600 is the baud rate to be checked?? If that is your intent, as stated before, my baud rate is confirmed at 9600.

You can't change baud rate in JMRI for the Power Pro. The only place you can change it is in the Power Pro itself. See my other post.

? I have read Dave's earlier posts about baud rate and I do not intend to change it through his firm guidance.? I have checked "N" for my connection prefix and that is confirmed.? John - how do I check for "8" and "1"?

You don't need to worry about them either. JMRI sets them correctly when it opens the port.

? Am I correct that the system console echo should state something about the EPROM? in response to the the?nce.NceConnectionStatus statement after the statement containing NCE USB COM3 port opened at 9600 baud [main]?

Yes, it should, and that's not what it is doing at present. Timeout indicates no connection. Flushing unexpected response indicates mismatched baud rate, unless you are doing a loopback test (in which case flushing "AA" indicates a successful loopback - "AA" is the Get EPROM Version command JMRI sends out.

Dave in Australia

Re: No NCE connection

#154178

Dave knows more about this than I, just thought you should check those is all,
best do as Dave says after all, he works with this stuff.

Over to you Dave.

John

Show quoted text

---------- Original Message ----------
From: stanbmattingly@...
Date: December 5, 2018 at 8:03 PM

Thanks John and Dave for your prompt responses.? John, I presume 9600 is the
baud rate to be checked?? If that is your intent, as stated before, my baud
rate is confirmed at 9600.? I have read Dave's earlier posts about baud rate
and I do not intend to change it through his firm guidance.? I have checked
"N" for my connection prefix and that is confirmed.? John - how do I check for
"8" and "1"?? Am I correct that the system console echo should state something
about the EPROM?in response to the the?nce.NceConnectionStatus statement after
the statement containing NCE USB COM3 port opened at 9600 baud [main] ?

Thanks for any and all help,

Stan Mattingly
ProPanel 4.12+Rb6a9bb1
Java Version 1.8.0_101

Re: No NCE connection

#154177

Well, Dave, you know more about this stuff than I.

John

Show quoted text

---------- Original Message ----------
From: Dave Heap <dgheap@...>
Date: December 5, 2018 at 7:49 PM

Changing the device baud rate etc. settings in Windows Device Manager has
absolutely no effect and is a waste of time. JMRI overrides those settings
when it opens the port.

The log reveals that the Baud Rate in JMRI is correct.
-- 
Dave in Australia

On 6 Dec 2018, at 12:23 PM, John <jonie41@...> wrote:

Check...9600, 8, N, 1

Re: No NCE connection

#154176

Thanks for the console log. Here is a checklist.

1) Make sure the port that appears/disappears in Windows Device Manager when you plug/unplug the Keyspan cable is actually COM3. If not, change the JMRI setting to match the actual port appearing/disappearing.
2) Since you have a Keyspan cable, you need an adaptor lead due the binding post issue. Did you get a straight-through one? If you got a crossover one (usually called a Null Modem cable) it won't work. I prefer the FTDI cables from ESU or RRCirKits as they don't need an adaptor, are cheaper and have other advantages.
 3) On the Power Pro under Setup Command Station, make sure AIU broadcasts are disabled and baud rate is set to 9600.
4) You quite possibly have the connection post issue documented at the link below.
5) The link below also explains how to do a loopback test. The loopback test eliminates JMRI, Windows and Keyspan issues. If the loopback test returns the expected result (as documented), your problem is probably either (2) or (4) (there are other less likely possibilities, such as a Power Pro fault - mine had one).
<>
-- 
Dave in Australia

Show quoted text

On 6 Dec 2018, at 11:31 AM, stanbmattingly@... wrote:

I copied the following thread from my system console while in Panel Pro.  I have a Keyspan serial to USB connector and when I go to Device Manager on my laptop it says device is working properly. I have NCE power pro command station and pro cab throttle.  When I start up Panel Pro the NCE on COM3 goes red and the data light on the keyspan serial adapter goes solid green.  I see in below thread that the EPROM is not being echoed back.  In Panel Pro preferences I have tried both serial and NCE to USB option on connections screen.  My baud rate is 9600.  I have my pro cab turned off.What is wrong with my configuration?