¿ªÔÆÌåÓý

Date

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

 

Scott,

What do you mean virtual sensors? Normally Internal sensors are used when there is no related hardware.

I only see LocoNet sensors. The list in the xml matches Tools >> Sensors. The xml sensor list is not sorted so comparisons are more difficult. The content of the user name has no impact.

The xml and Logix table match, with one Logix with 25 conditionals.

If you set zoom to 1 and scroll to x: 1168, y: 4980 you will see a turnout. The toolbar shows the current zoom and mouse location.

Dave Sand

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

When I open up the "Tables->Sensors" I see many sensors (i have quite a few real sensors), but the ones that I added (virtual sensors) that are placed on the Panel (to form buttons) are missing. I see that they are in the XML though. Switching over to the Logix table, it's just an empty gray page (it might even be trying to show something but failing. And the panels seem to be incomplete -- the one panel is missing the virtual sensors I added. I sorted the list several times and they are clearly not in the displayed list. All the ones I added had Usernames and many, but not all, of the real sensors had Usernames.
I first added virtual sensors as a range (16 of them) and it pyut a colon (":") in the username. I didn't remove that from all of them Could that be part of the issue?

Scott


Locked Re: Layout Editor, too much for RPi3?

 

¿ªÔÆÌåÓý

Did you also post this on the Anyrail Forum?

?

What version on Anyrail do you have?? V 6.14.0 is the latest.

?

Dennis Cherry

?

Created on my Desktop PC.

?


Locked Re: Adding new "info" field to the Cars and Loco tab in Oospore

 

Paul D,

Since this is a user group discussion, I was focusing on the concepts. So
yes to your first part. The developer group is where the discussion of the
second part takes place. While I know the form of the roster data and how
that worked (I've used it). I don't know the form of the data in the
Operations data tables. So I don't know either how simple or not the same
idea would be to implement.

But discussions like this spot the 'givens and druthers' of the ideas. From
that developers get the guidance of which solutions might be worth the
effort to implement.

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


Locked Re: Layout Editor, too much for RPi3?

 

*default options in jmri.conf


Locked Re: Layout Editor, too much for RPi3?

 

Tried increasing memory in jmri.com,?default_options="-J-Xmx768m", but that didn't help. Then noticed I was getting a stack trace in system console whenever I clicked. Does that shed any light? I also get a stack of bad blockname errors when I open the panel in case that's related. I've pasted that at the bottom. The block table does get populated with these blocks though.

2018-11-08 18:13:46,463 ptionhandler.UncaughtExceptionHandler ERROR - Uncaught Exception caught by jmri.util.exceptionhandler.UncaughtExceptionHandler [AWT-EventQueue-0]
java.lang.NullPointerException
?at jmri.jmrit.display.layoutEditor.LayoutTurnout.showPopup(LayoutTurnout.java:2501)
?at jmri.jmrit.display.layoutEditor.LayoutEditor.showEditPopUps(LayoutEditor.java:5586)
?at jmri.jmrit.display.layoutEditor.LayoutEditor.mouseReleased(LayoutEditor.java:5423)
?at java.awt.Component.processMouseEvent(Component.java:6535)
?at javax.swing.JComponent.processMouseEvent(JComponent.java:3324)
?at java.awt.Component.processEvent(Component.java:6300)
?at java.awt.Container.processEvent(Container.java:2236)
?at java.awt.Component.dispatchEventImpl(Component.java:4891)
?at java.awt.Container.dispatchEventImpl(Container.java:2294)
?at java.awt.Component.dispatchEvent(Component.java:4713)
?at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4888)
?at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4525)
?at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4466)
?at java.awt.Container.dispatchEventImpl(Container.java:2280)
?at java.awt.Window.dispatchEventImpl(Window.java:2750)
?at java.awt.Component.dispatchEvent(Component.java:4713)
?at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:758)
?at java.awt.EventQueue.access$500(EventQueue.java:97)
?at java.awt.EventQueue$3.run(EventQueue.java:709)
?at java.awt.EventQueue$3.run(EventQueue.java:703)
?at java.security.AccessController.doPrivileged(Native Method)
?at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
?at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86)
?at java.awt.EventQueue$4.run(EventQueue.java:731)
?at java.awt.EventQueue$4.run(EventQueue.java:729)
?at java.security.AccessController.doPrivileged(Native Method)
?at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
?at java.awt.EventQueue.dispatchEvent(EventQueue.java:728)
?at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
?at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
?at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
?at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
?at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
?at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)

2018-11-08 18:15:52,925 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'South Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:52,927 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'South Main' in tracksegment TS824 [AWT-EventQueue-0]
2018-11-08 18:15:52,930 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'Uphill' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:52,932 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'Uphill' in tracksegment TS706 [AWT-EventQueue-0]
2018-11-08 18:15:52,935 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'Upper West Side' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:52,937 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'Upper West Side' in tracksegment TC843 [AWT-EventQueue-0]
2018-11-08 18:15:52,940 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'Western Pass' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:52,941 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'Western Pass' in tracksegment TC165 [AWT-EventQueue-0]
2018-11-08 18:15:52,945 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'South Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:52,946 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'South Main' in tracksegment TS857 [AWT-EventQueue-0]
2018-11-08 18:15:52,949 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'North Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:52,951 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'North Main' in tracksegment TS797 [AWT-EventQueue-0]
2018-11-08 18:15:52,955 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'North Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:52,957 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'North Main' in tracksegment TS854 [AWT-EventQueue-0]
2018-11-08 18:15:52,961 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'Upper West Side' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:52,963 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'Upper West Side' in tracksegment TC296 [AWT-EventQueue-0]
2018-11-08 18:15:52,966 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'South Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:52,967 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'South Main' in tracksegment TC779 [AWT-EventQueue-0]
2018-11-08 18:15:52,970 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'North Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:52,971 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'North Main' in tracksegment TS858 [AWT-EventQueue-0]
2018-11-08 18:15:52,973 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'South Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:52,974 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'South Main' in tracksegment TC852 [AWT-EventQueue-0]
2018-11-08 18:15:52,976 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'South Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:52,977 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'South Main' in tracksegment TS853 [AWT-EventQueue-0]
2018-11-08 18:15:52,979 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'Western Pass' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:52,980 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'Western Pass' in tracksegment TC846 [AWT-EventQueue-0]
2018-11-08 18:15:52,981 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'North Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:52,982 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'North Main' in tracksegment TC855 [AWT-EventQueue-0]
2018-11-08 18:15:52,984 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'Western Pass' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:52,985 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'Western Pass' in tracksegment TC121 [AWT-EventQueue-0]
2018-11-08 18:15:52,986 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'Western Pass' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:52,987 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'Western Pass' in tracksegment TC12 [AWT-EventQueue-0]
2018-11-08 18:15:52,989 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'Uphill' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:52,990 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'Uphill' in tracksegment TS836 [AWT-EventQueue-0]
2018-11-08 18:15:52,992 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'North Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:52,993 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'North Main' in tracksegment TS798 [AWT-EventQueue-0]
2018-11-08 18:15:52,994 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'South Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:52,995 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'South Main' in tracksegment TS801 [AWT-EventQueue-0]
2018-11-08 18:15:52,998 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'Uphill' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:52,999 layoutEditor.LayoutTurnout??????????? ERROR - bad blockname 'Uphill' in layoutturnout TOL714 [AWT-EventQueue-0]
2018-11-08 18:15:53,000 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'Uphill' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,001 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'Uphill' in tracksegment T-I-TOL714 [AWT-EventQueue-0]
2018-11-08 18:15:53,003 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'Uphill' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,004 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'Uphill' in tracksegment T-ER-TOL714 [AWT-EventQueue-0]
2018-11-08 18:15:53,005 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'Uphill' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,006 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'Uphill' in tracksegment T-EL-TOL714 [AWT-EventQueue-0]
2018-11-08 18:15:53,008 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'Uphill' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,009 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'Uphill' in tracksegment TS365 [AWT-EventQueue-0]
2018-11-08 18:15:53,011 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'North Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,012 layoutEditor.LayoutTurnout??????????? ERROR - bad blockname 'North Main' in layoutturnout TOL840 [AWT-EventQueue-0]
2018-11-08 18:15:53,013 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'North Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,014 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'North Main' in tracksegment T-I-TOL840 [AWT-EventQueue-0]
2018-11-08 18:15:53,015 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'North Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,016 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'North Main' in tracksegment T-ER-TOL840 [AWT-EventQueue-0]
2018-11-08 18:15:53,017 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'North Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,018 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'North Main' in tracksegment T-EL-TOL840 [AWT-EventQueue-0]
2018-11-08 18:15:53,020 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'South Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,021 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'South Main' in tracksegment TC777 [AWT-EventQueue-0]
2018-11-08 18:15:53,022 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'Upper West Side' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,023 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'Upper West Side' in tracksegment TC101 [AWT-EventQueue-0]
2018-11-08 18:15:53,025 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'Upper West Side' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,026 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'Upper West Side' in tracksegment TC107 [AWT-EventQueue-0]
2018-11-08 18:15:53,027 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'South Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,028 layoutEditor.LayoutTurnout??????????? ERROR - bad blockname 'South Main' in layoutturnout TOR710 [AWT-EventQueue-0]
2018-11-08 18:15:53,029 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'South Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,030 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'South Main' in tracksegment T-I-TOR710 [AWT-EventQueue-0]
2018-11-08 18:15:53,031 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'South Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,032 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'South Main' in tracksegment T-EL-TOR710 [AWT-EventQueue-0]
2018-11-08 18:15:53,033 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'South Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,034 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'South Main' in tracksegment T-ER-TOR710 [AWT-EventQueue-0]
2018-11-08 18:15:53,035 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'South Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,036 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'South Main' in tracksegment TS806 [AWT-EventQueue-0]
2018-11-08 18:15:53,037 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'Western Pass' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,038 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'Western Pass' in tracksegment TC284 [AWT-EventQueue-0]
2018-11-08 18:15:53,041 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'North Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,042 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'North Main' in tracksegment TC781 [AWT-EventQueue-0]
2018-11-08 18:15:53,044 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'North Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,045 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'North Main' in tracksegment TC780 [AWT-EventQueue-0]
2018-11-08 18:15:53,047 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'North Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,048 layoutEditor.LayoutTurnout??????????? ERROR - bad blockname 'North Main' in layoutturnout TOL708 [AWT-EventQueue-0]
2018-11-08 18:15:53,049 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'North Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,050 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'North Main' in tracksegment T-I-TOL708 [AWT-EventQueue-0]
2018-11-08 18:15:53,052 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'North Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,053 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'North Main' in tracksegment T-ER-TOL708 [AWT-EventQueue-0]
2018-11-08 18:15:53,055 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'North Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,056 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'North Main' in tracksegment T-EL-TOL708 [AWT-EventQueue-0]
2018-11-08 18:15:53,058 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'South Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,059 layoutEditor.LayoutTurnout??????????? ERROR - bad blockname 'South Main' in layoutturnout TOR709 [AWT-EventQueue-0]
2018-11-08 18:15:53,060 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'South Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,061 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'South Main' in tracksegment T-I-TOR709 [AWT-EventQueue-0]
2018-11-08 18:15:53,062 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'South Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,063 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'South Main' in tracksegment T-EL-TOR709 [AWT-EventQueue-0]
2018-11-08 18:15:53,064 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'South Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,065 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'South Main' in tracksegment T-ER-TOR709 [AWT-EventQueue-0]
2018-11-08 18:15:53,074 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'North Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,076 layoutEditor.LayoutTurnout??????????? ERROR - bad blockname 'North Main' in layoutturnout TOR707 [AWT-EventQueue-0]
2018-11-08 18:15:53,077 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'North Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,077 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'North Main' in tracksegment T-I-TOR707 [AWT-EventQueue-0]
2018-11-08 18:15:53,078 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'North Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,079 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'North Main' in tracksegment T-EL-TOR707 [AWT-EventQueue-0]
2018-11-08 18:15:53,080 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'North Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,081 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'North Main' in tracksegment T-ER-TOR707 [AWT-EventQueue-0]
2018-11-08 18:15:53,082 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'Uphill' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,083 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'Uphill' in tracksegment TS368 [AWT-EventQueue-0]
2018-11-08 18:15:53,084 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'Western Pass' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,085 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'Western Pass' in tracksegment TC389 [AWT-EventQueue-0]
2018-11-08 18:15:53,086 layoutEditor.LayoutEditor???????????? ERROR - LayoutBlock 'South Main' not found when panel loaded [AWT-EventQueue-0]
2018-11-08 18:15:53,088 layoutEditor.TrackSegment???????????? ERROR - bad blockname 'South Main' in tracksegment TC778 [AWT-EventQueue-0]


Locked Re: Mentor for JMRI DecoderPro in Central MA?

 

Doug,
A lot of the information out there can be misleading. This appears to be the first time you have requested help.

Below is a correct set of instructions.
--
Dave Heap
(a member of the JMRI development team and an NCE hardware technical expert)

NCE USB on Windows
================

- The NCE USB uses the SiLabs CP2102 chipset. Download and install SiLabs CP210x drivers from
<>
- There is a Universal driver for Windows 10.
- The downloaded file will be a ".zip"
- You open that file and then open the file called:
"CP210xVCPInstaller_x86.exe" or "CP210xVCPInstaller_x64.exe" depending on whether your Windows is 32 bit or 64 bit.
- After doing this you should get the SiLabs device appearing as a new COM port in Windows Device Manager when you plug it in.
- Sometimes you may need to install the driver again after plugging in the NCE USB to get rid of the error symbol in Windows Device Manager.
- If you still have questions marks, try removing driver in Device Manager and try again as above
- When you have it working properly, the COM port should appear/disappear as you plug/unplug the NCE USB.
- Do not try to set the baud rate in Windows Device Manager.
- Ignore all other documentation to the contrary (there is some incorrect information in places) and set up as below:
- 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).

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).
- There is a potential hardware issue with the NCE USB/Power Cab combination.
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.

On 9 Nov 2018, at 8:44 AM, Doug Lowing <delowing1903@...> wrote:

I finally give up trying to get JMRI Decoder Pro to work on Win 10, communicating with either NCE PowerCab or DCC++ base station


Locked Re: Adding new "info" field to the Cars and Loco tab in Oospore

 

Ken...not sure I understand your statement. If you are asking if the extension method used for the loco roster would be workable if that same method was applied to the cars file, I would find that very workable.? If I could add columns to the cars file, I would be happy.
However, if you are asking if the loco roster method could be applied (technically) to the cars file, I don't have a clue. I am not a programmer nor am I savvy on the JMRI coding.
Paul D


Locked Ops: Order within a spur

 

In operations, the option is available for both yard and C/I tracks to select Normal, First In First Out, or Last In First Out. I see that the status of spurs is always displayed as Normal. Is there a way to have the FIFO and LIFO options for spurs as well? I use custom loads and schedules for all my spurs, and I have a reverse loop at a power plant for coal unloading. I'd like the program to apply the custom schedule and unload coal hoppers on this spur?in the order they are received.

Micheal Farley
Bismarck, ND
www.facebook.com/yellowstonedivision


Locked Re: panel xml file corrupted

 

Jim,

JmriFunctions.py is the source for the invalid properties that have been added to the sensors.

The property is a listener that has been created to provide notifications of changes within JMRI. When JmriFunctions needs to update the listeners, it uses the property content to identify old ones to be deleted before adding a new one. If the panel xml file is saved before JMRI is shutdown, the property changes are retained. This causes XML validation errors on startup. If validation is disabled, each property generates a Java error since the listener reference is unknown to JMRI.

There are a couple of alternate methods that might work to address this requirement. Did you create this or did it come from someone else? If someone else, they might be aware of the issue and have made the necessary changes. Or they are not aware of it but should be and can develop a change.

I could try making a change but there is no way that I can test it.


Dave Sand

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

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

Sent from Mail for Windows 10

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




Locked Re: Mentor for JMRI DecoderPro in Central MA?

 

¿ªÔÆÌåÓý

Doug?
Are using updated drivers for windows 10. I been using win 10 with nice power cab and pro. Had problems with the pro system until I got a newer updated usb to serial adapter.?
Bob C



On Nov 8, 2018, at 4:44 PM, Doug Lowing <delowing1903@...> wrote:

Hi all -

Anyone around the Amherst-Northampton MA area willing to help with JMRI Decoder Pro, in person?
I could drive an hour or more if we set a time.

I finally give up trying to get JMRI Decoder Pro to work on Win 10, communicating with either NCE PowerCab or DCC++ base station

I have done the due diligence. I have read many messages, pages, and tried many configurations. I do not give up easily. And I have some knowledge of coding and communications. I even got it to work several years ago in earlier versions of JMRI and Win.

Thanks much


Locked Re: Mentor for JMRI DecoderPro in Central MA?

 

Well, I know Sudro is in the area. He's been a long time part of the Amherst
Railway group that does the Springfield show at the end of January. I think
he watches this list and may chime in. If not before the end of January, if
you come to the show, I'll be there doing my clinics and help desk.

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


Locked Re: NCE not reading AIU

 

Thanks guys. I will check when I get home and let you know. I do know that the leds on the AIU do light up as the locomotive moves across the layout. But wasn¡¯t able to get anything to read on layout editor.

On Nov 8, 2018, at 1:33 PM, Dave Heap <dgheap@...> wrote:

In the NCE Command Monitor:
- If all AIU lights are off the return value should be 3f ff
- If AIU light 1 is on and all others are off the return value should be 3f fe
- If all AIU lights are on the return value should be 00 00
- If an AIU is not present at the specified address, the return value will be 00 00
--
Dave in Australia


On 9 Nov 2018, at 5:00 AM, Michael Murphy <smurfmm@...> wrote:

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.


Locked Re: BD20 block detection

 

Thank you Dave.

Derek.


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

 

When I open up the "Tables->Sensors" I see many sensors (i have quite a few real sensors), but the ones that I added (virtual sensors) that are placed on the Panel (to form buttons) are missing. I see that they are in the XML though. Switching over to the Logix table, it's just an empty gray page (it might even be trying to show something but failing. And the panels seem to be incomplete -- the one panel is missing the virtual sensors I added. I sorted the list several times and they are clearly not in the displayed list. All the ones I added had Usernames and many, but not all, of the real sensors had Usernames.
I first added virtual sensors as a range (16 of them) and it pyut a colon (":") in the username. I didn't remove that from all of them Could that be part of the issue?

Scott


Locked Re: Mentor for JMRI DecoderPro in Central MA?

 

¿ªÔÆÌåÓý

Do you have a raspberry pi around? There¡¯s an image you can download with auto detection. Connection for NCE Powercab and DCC++ Arduino both worked at boot with 0 tinkering.


On Nov 8, 2018, at 2:44 PM, Doug Lowing <delowing1903@...> wrote:

Hi all -

Anyone around the Amherst-Northampton MA area willing to help with JMRI Decoder Pro, in person?
I could drive an hour or more if we set a time.

I finally give up trying to get JMRI Decoder Pro to work on Win 10, communicating with either NCE PowerCab or DCC++ base station

I have done the due diligence. I have read many messages, pages, and tried many configurations. I do not give up easily. And I have some knowledge of coding and communications. I even got it to work several years ago in earlier versions of JMRI and Win.

Thanks much


Locked Mentor for JMRI DecoderPro in Central MA?

Doug Lowing
 

Hi all -

Anyone around the Amherst-Northampton MA area willing to help with JMRI Decoder Pro, in person?
I could drive an hour or more if we set a time.

I finally give up trying to get JMRI Decoder Pro to work on Win 10, communicating with either NCE PowerCab or DCC++ base station

I have done the due diligence. I have read many messages, pages, and tried many configurations. I do not give up easily. And I have some knowledge of coding and communications. I even got it to work several years ago in earlier versions of JMRI and Win.

Thanks much


Locked Re: Layout Editor, too much for RPi3?

 

Thanks but that doesn't work either. And I don't have this issue on an earlier layout with less sections so it just feels like the RPi is hitting an element limit for it's memory. Here's a picture of the same turnout working on the Pi on the simpler layout. My connection is over VNC which may also contribute. I'll have to test directly.

I noticed another oddity. If you turn off the grid in edit mode a lot of the "construction lines" get cut off on the right side. Happens on windows too. What are all those lines and what is there purpose. And regarding the?track segment control circles, their size gets adjusted when you adjust the turnout circle size option which doesn't seem like they should.


Locked Re: NCE not reading AIU

 

In the NCE Command Monitor:
- If all AIU lights are off the return value should be 3f ff
- If AIU light 1 is on and all others are off the return value should be 3f fe
- If all AIU lights are on the return value should be 00 00
- If an AIU is not present at the specified address, the return value will be 00 00
--
Dave in Australia

On 9 Nov 2018, at 5:00 AM, Michael Murphy <smurfmm@...> wrote:

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.


Locked Re: Layout Editor, too much for RPi3?

 

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

Dave Sand

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.


Locked Re: BD20 block detection

 

¿ªÔÆÌåÓý

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


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.