Re: Layout Editor, too much for RPi3?

#153364

On Linux and macOS, a control click will normally be more consistent in displaying the context menu.

Dave Sand

Show quoted text

On Nov 8, 2018, at 2:39 PM, j_bernardini@... wrote:

Thanks Dave. Meant to say above that if I open the panel on my windows laptop the actual turnout context menus open just fine. Here's a picture showing what it looks like in the editor including the context menu that won't open on the RPi.

Re: BD20 block detection

#153363

开云体育

Address Range

If your Power Cab firmware (second screen at startup of your Power Cab, after the "Pro Cab V1.3" message) is:

- "V1.28C" the only valid addresses for extra cabs are 3 & (unofficially) 4.

- "V1.65" the only valid addresses for extra throttles ?are 3, 4 and 5. Non-throttle devices such as the NCE USB, Mini Panel or AIU can also use addresses 8, 9 & 10. However if you have ever done a System Reset, you will have lost all the extra addresses and be back to the V1.28C restrictions.

- "V1.65B" the only valid addresses for extra throttles ?are 3, 4 and 5. Non-throttle devices such as the NCE USB, Mini Panel or AIU can also use addresses 8, 9 & 10.

Similar ?comments apply to the SB3/5 with the range 2-5 for V1.28 and 2-7 for V1.65B.

Configuration Instructions

Here are the best settings for JMRI and jumpers for Power Cab (and also SB5).

Make sure you always unplug/replug both cables on the NCE USB after changing jumpers.?

It also explains how to read the version of your NCE USB (only the first digit counts, the last three report how your jumpers 2-4 are set and jumper 1 is ignored on all systems).

Power Cab Instructions

The correct settings for a Power Cab V1.65 or V1.28 (as shown when the Power Cab starts up) and an NCE USB V6 (or you are not sure of the USB version) ?are:

- All USB Jumpers off (or at least 2, 3 & 4. Jumper 1 is ignored).

- JMRI preferences are:

-- System manufacturer: NCE

-- System connection: ?NCE USB

-- Serial port: <whatever is appropriate for your system>

-- USB version: V6.x.x

-- System: PowerCab

-- Additional Connection Settings checkbox ON

--- Baud rate: 9600.

The JMRI console log should then report V6.3.0. If it reports V7.3.0 and your Power Cab is V1.65, use the settings below instead.

If you don't get a version number or the system does not work, Use Help->System Console...->Copy to clipboard and paste into a post for us to see.

The correct settings for a Power Cab V1.65 or V1.65b and an NCE USB V7 ?are:

- All USB Jumpers on (or at least 2, 3 & 4. Jumper 1 is ignored).

- JMRI preferences are:

-- System manufacturer: NCE

-- System connection: ?NCE USB

-- Serial port: <whatever is appropriate for your system>

-- USB version: V7.x.x

-- System: PowerCab

-- Additional Connection Settings checkbox ON

--- Baud rate: 19200.

The JMRI console log should then report V7.3.7.

SB5 Instructions

The correct settings for an SB5 and an NCE USB V7 ?are:

- USB Jumper 4 on. All others off (or at least 2 & 3. Jumper 1 is ignored).

- JMRI preferences are:

-- System manufacturer: NCE

-- System connection: ?NCE USB

-- Serial port: <whatever is appropriate for your system>

-- USB version: V7.x.x

-- System: SB5

-- Additional Connection Settings checkbox ON

--- Baud rate: 19200.

The JMRI console log should then report V7.3.1.

General Troubleshooting

If the system does not work after this:

- If your SB5/Power Cab is V1.65 rather than V1.65B, you may have been affected by a firmware issue (triggered by a System Reset).

- Your NCE USB may be set to a bad cab address (V7 only).

?In either case, go through the following :

- Quit JMRI.

- Ensure neither LED on the NCE USB is stuck ON. If so, power cycle the USB by unplugging it from the cab bus cable.

- Ensure you have no other throttles connected.

- Restart JMRI and immediately go to Configure USB Interface under the NCE menu.

- Set the Cab ID to 3.

- Attempt a JMRI operation (use a throttle, Identify a decoder).

- The status line should stay green and it should work?

-If this does not work, do not fiddle with any other settings but instead:

-- Observe whether the Cab Bus LED on the NCE USB is stuck on and report back.

-- Use Help->System Console...->Copy to clipboard and paste into a post for us to see.

--?

Dave in Australia

Show quoted text

On 9 Nov 2018, at 7:15 AM, Derekr <m1arfm0dfx@...> wrote:

Dave do all these settings for the PowerCab and AIU,s hold good for an SB5 i.e. USB jumpers and cab IDs.

Re: Dispatcher - SML - auto-allocation problem

#153362

Hi steve,

I think I have witnessed this once before. I have IR relays for stop sensors. Whenever this odd re-allocate thing happens I hear the relay fire but it doesn’t stop the loco because it has a yellow. By the time it reaches?the crossover the turnout has changed back to closed to allow it through, even though 37254 was already allocated across the crossover and through that turnout.

my email Mitchell.scott93@...

I might try and make a video of the situation occurring from both a panel perspective and a layout perspective.

i still dont know how to get a detailed log of how dispatcher is allocating, what’s the best way to log that?
ive heard of adding a debug line into a default file of some kind..
--
Thanks
Mitch

Re: NCE not reading AIU

#153361

Michael,

Key things to keep in mind:

1. Set the right address on the AIU.
1.1. CS02/PowerHouse command stations, that usually means starting at 50 and
working up from there.
1.2. USB based command stations, it depends on the firmware in the command
station and in the USB interface. Is always 10 or less.
1.3. Older USB and related command stations, use 3 for the Interface and 4
for the AIU.
2. The sensors must be created in JMRI before it will check for the
hardware.
3. Entering the system value like 50:1, it is much simpler than figuring the
NS### value.
4. If the LEDs on the input bits are not changing, JMRI won't see anything
change either.

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

Re: panel xml file corrupted

#153360

开云体育

Both there now one called jmriTCPDeviceMgr.py and one called jmrFunctions.py

?

Sent from for Windows 10

?

Show quoted text

From: [email protected] <[email protected]> on behalf of Dave Sand <ds@...>
Sent: Thursday, November 8, 2018 8:22:56 PM
To: [email protected]
Subject: Re: [jmriusers] panel xml file corrupted

?

Jim,

Can you also upload the script?? If so, then we can verify that it is the source of the sensor changes and possibly how to avoid the problem.

Dave Sand

> On Nov 8, 2018, at 2:12 PM, James Anderson <james_anderson_999@...> wrote:
>
> Hi, yes there is a main script running that waits on TCP/IP connections from a remote raspberry Pi that is controlling the physical devices. When I save the panel there are no active communication? happenig but there is a thread on the JMRI instance sitting and waiting for incomming messages.
>
> Thanks Jim
>

Re: Layout Editor, too much for RPi3?

#153359

Thanks Dave. Meant to say above that if I open the panel on my windows laptop the actual turnout context menus open just fine.?Here's a picture?showing what it looks like in the editor including the context menu that won't open on the RPi.

Re: panel xml file corrupted

#153358

Hi , uploaded. Have not seen it arive yet though

Re: Layout Editor, too much for RPi3?

#153357

Jb,

All of those “turnout circles” are track segment control circles.  AnyRail represents curved track as MANY small track segments.   I believe there is an AnyRail option to use a flex track feature which addresses this issue.  If you zoom in and right click on the anchor points, you can join track segments together into a more manageable piece of track.

Dave Sand

Show quoted text

On Nov 8, 2018, at 2:23 PM, j_bernardini@... wrote:

Hi, I exported my layout from AnyRail and opened it as a panel. After enabling editing mode it seems like there's a lot of stuff that maybe isn't needed coming with the import? For instance there's a lot of "turnout circles" that aren't turnouts. Most of the actual turnouts do not open the context menu to edit them though they will animate. If I open the same panel in jmri on m windows laptop. While the RPi3 appears to have available memory and cpu I'm wondering if this is too many elements to work on the layout directly on the RPi? If so, what's the recommended workflow to build stuff up on my PC and then move it over to the RPi for layout control?

If you want to try yourself download the xml and image below. The image need to be named bachman4_6.jpg and the file path to the image may need to be edited in the xml for your system but if it's an RPi with default paths it should work as is.

/g/jmriusers/files/ProblemsBeingWorkedOn/bernardini/bachman4_6.xml
/g/jmriusers/photo/77943/0?p=Name,,,20,1,0,0

Thanks!
jb

Re: Added sensors and logix to panels. The sensors and logix have disappeared

#153356

Scott,

It is quite possible that the sensor and Logix windows are very tiny.  Look at the Windows list in the main PanelPro menu.  You may need to expand them.

Dave Sand

Show quoted text

On Nov 8, 2018, at 12:49 PM, Scott Walton <jscottwalton@...> wrote:

After extensive work (and frequent saves), all the sensors and logix have disappeared no that I have quit JMRI and restarted it. I can see (by looking at the raw XML) that those elements are still present but JMRI is ignoring them. I have edited the files only with the Layout Editor (though I have looked at them several times with a text editor, but never saved from that). The environment is:
Windows 8.1 Pro
JMRI 4.13.3
Java 1.8.0_181
Digitrax (DCS 240 with LocoBuffer USB connection)

The only error messages in the log are about "No assigned Turnout" for several blocks (log will be uploaded to folder "Scott_Walton_Panels). An addition (though minor) problem is that one panel (Pennsy_West_Main) when "Zoom to fit" becomes very small -- there must be some element way outside the boundaries but I can't seem to find it.

I hope someone can help find the problem. If you do find it, I would like to know what the issue is, so I don't feel quite so helpless in the future.

Scott Walton

Layout Editor, too much for RPi3?

#153355

Hi, I exported my layout from AnyRail and opened it as a panel. After enabling editing mode it seems like there's a lot of stuff that maybe isn't needed coming with the import? For instance there's a lot of "turnout circles" that aren't turnouts. Most of the actual turnouts do not open the context menu to edit them though they will animate. If I open the same panel in jmri on m windows laptop. While the RPi3 appears to have available memory and cpu I'm wondering if this is too many elements to work on the layout directly on the RPi? If so, what's the recommended workflow to build stuff up on my PC and then move it over to the RPi for layout control?

If you want to try yourself download the xml and image below. The image need to be named bachman4_6.jpg and the file path to the image may need to be edited in the xml for your system but if it's an RPi with default paths it should work as is.

/g/jmriusers/files/ProblemsBeingWorkedOn/bernardini/bachman4_6.xml
/g/jmriusers/photo/77943/0?p=Name,,,20,1,0,0

Thanks!
jb

Re: panel xml file corrupted

#153354

Jim,

Can you also upload the script?  If so, then we can verify that it is the source of the sensor changes and possibly how to avoid the problem.

Dave Sand

Show quoted text

On Nov 8, 2018, at 2:12 PM, James Anderson <james_anderson_999@...> wrote:

Hi, yes there is a main script running that waits on TCP/IP connections from a remote raspberry Pi that is controlling the physical devices. When I save the panel there are no active communication  happenig but there is a thread on the JMRI instance sitting and waiting for incomming messages.

Thanks Jim

NCE not reading AIU

#153353

Hello,  I’m just getting into this myself. I have a Power Pro with version 2007c software. I have 2 AIU’s wired up to 17 BD-20’s, and a switch-it 8 for turnouts. 

I’m able to add turnouts and make them work in layout editor just fine. My problem is, is that I can’t seem to get my system to detect an occupied block. I’ve made the sensor table with the sensors/pins (like NS784, etc). But to no avail. In the NCE monitoring on the startup menu, it seems to be reading the AIU’s. It show it switching back and forth between #50 and #51. 

Yes I’m working on this for myself to learn to do it, but I also work at a train store and am learning it to be more helpful to the customers asking about it. Any information you could suggest would be appreciated 

Michael

Re: BD20 block detection

#153352

Hope I am not hijacking the thread.

Dave do all these settings for the PowerCab and AIU,s hold good for an SB5 i.e. USB jumpers and cab IDs.

Thanks for any help.

Derek.

Re: panel xml file corrupted

#153351

Hi, yes there is a main script running that waits on TCP/IP connections from a remote raspberry Pi that is controlling the physical devices. When I save the panel there are no active communication? happenig but there is a thread on the JMRI instance sitting and waiting for incomming messages.

Thanks Jim

Re: panel xml file corrupted

#153350

James,

Each of your internal sensors has the property attached.  It appears to be a reference to a Python based listener.

Are you running any scripts while JMRI is running?  Any other software that might communicate with JMRI?

Dave Sand

Show quoted text

On Nov 8, 2018, at 12:58 PM, James Anderson <james_anderson_999@...> wrote:

sorry - worked it out I have put it there.

Re: BD20 block detection

#153349

Very funny Dave, laugh out loud. Thanks very, very much for all your help. Tonight I will connect some new BD,s to the new AIU and I don’t expect to have any problems. I am learning a lot.
Cheers.

Re: Injecting a delay between turnout operations

#153348

BTW I use feedback on my module and so far one other module in our group has it. It is really cool to watch the signals dropping back to red as a train passes. The feedback is on the mainline turnouts and block detection, which also stops routes being set into occupied blocks or oncoming traffic.
?
See here for them operating, a bit long but shows the signals changing.

Mike

Re: panel xml file corrupted

#153347

sorry - worked it out I have put it there.

Re: Injecting a delay between turnout operations

#153346

Several ways I can think of to cut down on interference.
1. Can the decoder and motor supplies be separated? If not use the decoder to switch a relay that then uses a different supply to operate the motors. I've done this for other reasons, using latching relays, they then remember the last position and can be used by pulse output decoders.
2. Fit VDRs (voltage dependant resistors) across the motor connections, these will cut off any high voltage spikes, I had to use them on some Fulgurex motors which messed up a hardwired signal system.
3. If voltage is dropping when motors operate fit a larger capacity supply if the voltage drops at the power supply. If the power supply end is ok run larger cables to the decoder / motors. We had this on a modular layout where the wire runs were long or used small wire.

Mike

Added sensors and logix to panels. The sensors and logix have disappeared

#153345

After extensive work (and frequent saves), all the sensors and logix have disappeared no that I have quit JMRI and restarted it. I can see (by looking at the raw XML) that those elements are still present but JMRI is ignoring them. I have edited the files only with the Layout Editor (though I have looked at them several times with a text editor, but never saved from that). The environment is:
Windows 8.1 Pro
JMRI 4.13.3
Java 1.8.0_181
Digitrax (DCS 240 with LocoBuffer USB connection)

The only error messages in the log are about "No assigned Turnout" for several blocks (log will be uploaded to folder "Scott_Walton_Panels). An addition (though minor) problem is that one panel (Pennsy_West_Main) when "Zoom to fit" becomes very small -- there must be some element way outside the boundaries but I can't seem to find it.

I hope someone can help find the problem. If you do find it, I would like to know what the issue is, so I don't feel quite so helpless in the future.

Scott Walton