¿ªÔÆÌåÓý

  1. Jmriusers
  2. Messages
Expanded Topics Messages Polls
Date
Locked HELP! Signals not working

 

I have had APB signals set up for several years and now they won't work.?

When I load my panel I get the following error:? Could not create sensor System name "LS10" User name "Lowelville in adaptor of type jmri.jmrix.loconet.configurexml.LnSensorManger.Xml.? It goes through all the signals to tell me it isn't working for ANY of them.

I am using Digitrax SE8c boards and I checked that I could manually change signal color, so at least I know the SE8c board addresses are still what they should be.

The signals HAD BEEN working fine, and I have NOT changed anything with the panel so I have no clue what is wrong.
?
I'm guessing that something changed in the latest version of PanelPro and now I need to 'fix' my panel.

Please let me know what I should do.
Thanks
Kerry
Locked Re: Parse error with a very old file

 

On Mon, Nov 25, 2019 at 10:42 AM, leo pesce wrote:

Ok, I guess I need to find an early version of JMRI so I can load the file.

Once you get the proper version number or approximate date, examine the list at

Some clues to your puzzles can be found by reading the warnings and suggestions for the sequence of changes found on each of the links.

Cliff in Baja SoCal
Locked Re: Parse error with a very old file

 

Leo,

According to the release notes, 4.12 is supposed to handle the migration from older releases.

Dave Sand



----- Original message -----
From: leo pesce <lpescester@...>
Subject: Re: [jmriusers] Parse error with a very old file
Date: Monday, November 25, 2019 12:42 PM

Ok, I guess I need to find an early version of JMRI so I can load the file.?

The next parse error is

? ? <sensor systemName="CS1" inverted="true" userName="TOFB City Lead">
? ? ? <systemName>CS1</systemName>
? ? ? <userName>TOFB City Lead</userName>
? ? </sensor>

and from our panel file, the format is different in that systemname and userName are no longer tolerated?in the first <sensor line.

Did any of the JMRI version convert the panel file to the newer format?

Thx
Leo P

On Mon, Nov 25, 2019 at 10:38 AM leo pesce via Groups.Io <lpescester=[email protected]> wrote:
I just answered my question. The newer JMRI version requires a username. I had forgotten that this changes was placed in JMRI.

I placed a username and the parse error went to the next oblock. I also found out that is userName="" is removed, that also fixes the parse error.

Now I am getting a different error

Thx
Leo P

On Mon, Nov 25, 2019 at 10:20 AM leo pesce via Groups.Io <lpescester=[email protected]> wrote:
Hello all,

I am trying to help a friend that has been running with a very old version of JMRI (I do not know which, but it predates the JAVA change to a new format that did not allow backwards compatibility.

The error we get is a cvc-minLength-valid error. I took a picture of this.?

The code is for OBLOCKS and here is an example:

<oblock systemName="OB121" userName="" length="1" curve="0">
? ? ? <sensor systemName="CS121" />
? ? ? <path pathName="Path144-122" blockName="OB121" fromPortal="Port144-121" toPortal="Port121-122" fromDirection="0" toDirection="0" />
? ? ? <portal portalName="Port144-121">
? ? ? ? <fromBlock blockName="OB144">
? ? ? ? ? <path pathName="Path143-121" blockName="OB144" />
? ? ? ? </fromBlock>
? ? ? ? <toBlock blockName="OB121">
? ? ? ? ? <path pathName="Path144-122" blockName="OB121" />
? ? ? ? </toBlock>
? ? ? </portal>
? ? ? <portal portalName="Port121-122">
? ? ? ? <fromBlock blockName="OB121">
? ? ? ? ? <path pathName="Path144-122" blockName="OB121" />
? ? ? ? </fromBlock>
? ? ? ? <toBlock blockName="OB122">
? ? ? ? ? <path pathName="Path121-123" blockName="OB122" />
? ? ? ? ? <path pathName="Path121-136" blockName="OB122" />
? ? ? ? ? <path pathName="Path121-Saw" blockName="OB122" />
? ? ? ? </toBlock>
? ? ? </portal>
? ? </oblock>

Is it because the userName is ""?

Please let us know.

Thank you
Leo P
Locked Re: Parse error with a very old file

 

Ok, I guess I need to find an early version of JMRI so I can load the file.?

The next parse error is

? ? <sensor systemName="CS1" inverted="true" userName="TOFB City Lead">
? ? ? <systemName>CS1</systemName>
? ? ? <userName>TOFB City Lead</userName>
? ? </sensor>

and from our panel file, the format is different in that systemname and userName are no longer tolerated?in the first <sensor line.

Did any of the JMRI version convert the panel file to the newer format?

Thx
Leo P

On Mon, Nov 25, 2019 at 10:38 AM leo pesce via Groups.Io <lpescester=[email protected]> wrote:
I just answered my question. The newer JMRI version requires a username. I had forgotten that this changes was placed in JMRI.

I placed a username and the parse error went to the next oblock. I also found out that is userName="" is removed, that also fixes the parse error.

Now I am getting a different error

Thx
Leo P

On Mon, Nov 25, 2019 at 10:20 AM leo pesce via Groups.Io <lpescester=[email protected]> wrote:
Hello all,

I am trying to help a friend that has been running with a very old version of JMRI (I do not know which, but it predates the JAVA change to a new format that did not allow backwards compatibility.

The error we get is a cvc-minLength-valid error. I took a picture of this.?

The code is for OBLOCKS and here is an example:

<oblock systemName="OB121" userName="" length="1" curve="0">
? ? ? <sensor systemName="CS121" />
? ? ? <path pathName="Path144-122" blockName="OB121" fromPortal="Port144-121" toPortal="Port121-122" fromDirection="0" toDirection="0" />
? ? ? <portal portalName="Port144-121">
? ? ? ? <fromBlock blockName="OB144">
? ? ? ? ? <path pathName="Path143-121" blockName="OB144" />
? ? ? ? </fromBlock>
? ? ? ? <toBlock blockName="OB121">
? ? ? ? ? <path pathName="Path144-122" blockName="OB121" />
? ? ? ? </toBlock>
? ? ? </portal>
? ? ? <portal portalName="Port121-122">
? ? ? ? <fromBlock blockName="OB121">
? ? ? ? ? <path pathName="Path144-122" blockName="OB121" />
? ? ? ? </fromBlock>
? ? ? ? <toBlock blockName="OB122">
? ? ? ? ? <path pathName="Path121-123" blockName="OB122" />
? ? ? ? ? <path pathName="Path121-136" blockName="OB122" />
? ? ? ? ? <path pathName="Path121-Saw" blockName="OB122" />
? ? ? ? </toBlock>
? ? ? </portal>
? ? </oblock>

Is it because the userName is ""?

Please let us know.

Thank you
Leo P
Locked Re: Parse error with a very old file

 

I just answered my question. The newer JMRI version requires a username. I had forgotten that this changes was placed in JMRI.

I placed a username and the parse error went to the next oblock. I also found out that is userName="" is removed, that also fixes the parse error.

Now I am getting a different error

Thx
Leo P

On Mon, Nov 25, 2019 at 10:20 AM leo pesce via Groups.Io <lpescester=[email protected]> wrote:
Hello all,

I am trying to help a friend that has been running with a very old version of JMRI (I do not know which, but it predates the JAVA change to a new format that did not allow backwards compatibility.

The error we get is a cvc-minLength-valid error. I took a picture of this.?

The code is for OBLOCKS and here is an example:

<oblock systemName="OB121" userName="" length="1" curve="0">
? ? ? <sensor systemName="CS121" />
? ? ? <path pathName="Path144-122" blockName="OB121" fromPortal="Port144-121" toPortal="Port121-122" fromDirection="0" toDirection="0" />
? ? ? <portal portalName="Port144-121">
? ? ? ? <fromBlock blockName="OB144">
? ? ? ? ? <path pathName="Path143-121" blockName="OB144" />
? ? ? ? </fromBlock>
? ? ? ? <toBlock blockName="OB121">
? ? ? ? ? <path pathName="Path144-122" blockName="OB121" />
? ? ? ? </toBlock>
? ? ? </portal>
? ? ? <portal portalName="Port121-122">
? ? ? ? <fromBlock blockName="OB121">
? ? ? ? ? <path pathName="Path144-122" blockName="OB121" />
? ? ? ? </fromBlock>
? ? ? ? <toBlock blockName="OB122">
? ? ? ? ? <path pathName="Path121-123" blockName="OB122" />
? ? ? ? ? <path pathName="Path121-136" blockName="OB122" />
? ? ? ? ? <path pathName="Path121-Saw" blockName="OB122" />
? ? ? ? </toBlock>
? ? ? </portal>
? ? </oblock>

Is it because the userName is ""?

Please let us know.

Thank you
Leo P
Locked Parse error with a very old file

 

Hello all,

I am trying to help a friend that has been running with a very old version of JMRI (I do not know which, but it predates the JAVA change to a new format that did not allow backwards compatibility.

The error we get is a cvc-minLength-valid error. I took a picture of this.?

The code is for OBLOCKS and here is an example:

<oblock systemName="OB121" userName="" length="1" curve="0">
? ? ? <sensor systemName="CS121" />
? ? ? <path pathName="Path144-122" blockName="OB121" fromPortal="Port144-121" toPortal="Port121-122" fromDirection="0" toDirection="0" />
? ? ? <portal portalName="Port144-121">
? ? ? ? <fromBlock blockName="OB144">
? ? ? ? ? <path pathName="Path143-121" blockName="OB144" />
? ? ? ? </fromBlock>
? ? ? ? <toBlock blockName="OB121">
? ? ? ? ? <path pathName="Path144-122" blockName="OB121" />
? ? ? ? </toBlock>
? ? ? </portal>
? ? ? <portal portalName="Port121-122">
? ? ? ? <fromBlock blockName="OB121">
? ? ? ? ? <path pathName="Path144-122" blockName="OB121" />
? ? ? ? </fromBlock>
? ? ? ? <toBlock blockName="OB122">
? ? ? ? ? <path pathName="Path121-123" blockName="OB122" />
? ? ? ? ? <path pathName="Path121-136" blockName="OB122" />
? ? ? ? ? <path pathName="Path121-Saw" blockName="OB122" />
? ? ? ? </toBlock>
? ? ? </portal>
? ? </oblock>

Is it because the userName is ""?

Please let us know.

Thank you
Leo P
Locked Re: speed matching

 

George -

It doesn't take much to be an NMRA compliant decoder.

There are only a handful of Mandatory CVs.
? ?1- the primary address
? ? 7 & 8 - the manufacture id
? ? 29 - the configuration data

There are a few "recommended" CVs.
? ? 2 - Vstart
? ? 3 & 4 Acceleration and Deceleration momentum.
? ? 11 - packet time-out value (nothing you'll change)

Everything else is "optional."

I had a locomotive with a Bachmann decoder and it was pretty useless until I replaced it with a more capable decoder.

gs
??
Locked Re: Issue recognizing locomotive - Atlas N MP15DC

 

Have you checked that the tabs from the motor are making contact with the pads on the bottom of the decoder?? I've had them become misaligned so the motor was no longer connected to decoder.

Michael Mosher
Member SFRH&MS
DCC Master PVSMR

On 11/22/2019 6:43 PM, Chuckaknuckle wrote:
I'm able to select lights to toggle front/rear when selecting forward or reverse, so they are at least switching to the correct direction.

I'll end up switching out this chip for the Digitrax that I should have soon, so hopefully that will work instead.
Locked Re: Signaling feedback to Panels

 

Bob,

Oh no :( Our hardware can not properly control this signal using aspect messages because we do not have any internal control on flash rate options. This is the first time that I have heard of a signal system that differentiated aspects by flash rate.

Dick :)

On 11/24/2019 5:48 PM, Bob Jacobsen wrote:
Locked Re: Signaling feedback to Panels

 

Bob,

My gut reaction is that arbitrarily adding 'aspects' to cover the lit and not lit cases is probably not a good idea. My feeling is that we should always move closer to the prototype, not away from it. I appreciate what you are trying to accomplish by this, and that is central control of everything by JMRI. However if that is the case, then JMRI can simply keep the information internally, and control the signal by sending 'dark'. If you add in an extra set of 'aspects' to include the lit/unlit information then the local signal logic would need to somehow sort that information back out of the aspect data, and I wouldn't want to send any users down that path. Too many orcs and goblins.

I also seriously doubt that any given CROR mast would ever be called upon to show all 31 signal aspects that would be possible to display, but that begs the question.

Dick :)

On 11/24/2019 11:04 PM, billybob experimenter wrote:
Dick wrote "I would like to hear about the rule set that requires more than 32 aspects."

FIY - The following existing JMRI mast definitions implement more than 30 aspects:
- CROR-2008 - 3A-Hi : 31 aspects - see .
- CROR-2008 - 3D-Hi : 31 aspetcts - see .
- CROR-2008 - 3-Hi: 31 aspects - see .

If one were to add duplicate aspects to reflect "Dark but would otherwise be displaying XXX" aspects as I have suggested for discussion purposes, it would double the count of aspects, and exceed the available number of DCC Extended Accessory Decoder aspect values.

I would not be surprised to find that one or more non-US signal system would have a mast which could display more than 32 aspects...

A few other existing JMRI signal mast definitions appear to implement more than 30 aspects but are named as "test" masts or appear to include images for multiple mast types where they would typically define only a single mast type per "appearance" file, so the actual aspect count is suspect.

Regards,
Billybob
Locked java Exception when try to add a second internal sensor

 

Hi
I've noticed a problem for a while (I cannot remember exactly when it started) when trying to add multiple internal sensors. The situation can be created as follows:
  • Open PanelPro (no panel required)
  • Use MERG CAN Simulation connection
  • Go to Tables->Sensors and click "Add"
  • Enter internal sensor with hardware address "sensor1", click Create (NB It's odd that the term "Hardware address" is used for an internal sensor rather than "user name")
  • Note: Dialog disappears and sensor created as expected
  • Click Add
  • Note: No dialog appears and java exception thrown in console window (see below)
  • Click Add again
  • Dialog appears but it only has menu items "Window" and "Help", but is otherwise blank (no entry fields)
  • No more exceptions at this stage
  • Pressing Add again results in the same result
  • Close Tables and reopen again
  • A single new internal sensor can now be added
The situation seems to be similar for turnouts.
It is different for Memory Variables as in this case the dialog remains open (much easier to use!) and new variables can be edited/added.

I've included my startup log so that you can see some profile details.

JMRI 4.17.6
Ubuntu 19.10
Java 11.0.5-ea (en)

Initially I put it down to finger trouble, and I had a work around by closing and opening the Tables dialog - but clearly all is not well!

Looking at the exception it's obviously related to CBUS, but I'm not sure why any validation is going on when I open the dialog for the second time. In this case I was going to create a new 'internal'? sensor, whereas it seems to be validating the previous sensor and concluding that the name is invalid in MERG/CBUS terms (which it is since it's an internal sensor).

If I add a MERG/CBUS sensor with a valid hardware address and create, I can then add new ones successfully i.e. the problem only occurs after adding an internal sensor.

Regards
Andy

Startup Log:

2019-11-25 10:15:52,466 apps.Apps???????????????????????????? INFO? - Starting with profile DefaultIconIssue.3f0a07d9 [main]
2019-11-25 10:15:52,556 node.NodeIdentity???????????????????? INFO? - Using f481328e-da9a-11e8-8000-001372e824b0 as the JMRI storage identity for profile id 3f0a07d9 [AWT-EventQueue-0]
2019-11-25 10:15:52,700 configurexml.ConnectionConfigXml????? INFO? - CAN Simulator Started [main]
2019-11-25 10:15:52,721 simulator.CbusSimulator?????????????? INFO? - Starting CBUS Network Simulation Tools [AWT-EventQueue-0]
2019-11-25 10:15:52,728 simulator.CbusDummyCS???????????????? INFO? - Simulated Command Station: Standard Command Station [AWT-EventQueue-0]
2019-11-25 10:15:52,740 simulator.CbusDummyNode?????????????? INFO? - Simulated CBUS Node: SLIM [AWT-EventQueue-0]
2019-11-25 10:15:52,743 simulator.CbusEventResponder????????? INFO? - Simulated Event Responses: Random On / Off [AWT-EventQueue-0]
2019-11-25 10:15:52,748 eventtable.CbusEventTableDataModel??? INFO? - Starting MERG CBUS Event Table [main]
2019-11-25 10:15:53,040 util.FileUtilSupport????????????????? INFO? - File path program: is /home/andy/Applications/JMRI-4.17.6/ [main]
2019-11-25 10:15:53,040 util.FileUtilSupport????????????????? INFO? - File path preference: is /home/andy/railwayShare/docs/jmri/DefaultIconIssue.jmri/ [main]
2019-11-25 10:15:53,040 util.FileUtilSupport????????????????? INFO? - File path profile: is /home/andy/railwayShare/docs/jmri/DefaultIconIssue.jmri/ [main]
2019-11-25 10:15:53,041 util.FileUtilSupport????????????????? INFO? - File path settings: is /home/andy/.jmri/ [main]
2019-11-25 10:15:53,041 util.FileUtilSupport????????????????? INFO? - File path home: is /home/andy/ [main]
2019-11-25 10:15:53,041 util.FileUtilSupport????????????????? INFO? - File path scripts: is /home/andy/Applications/JMRI-4.17.6/jython/ [main]
2019-11-25 10:15:53,417 server.WebServer????????????????????? INFO? - Starting Web Server on port 12080 [WebServer]
2019-11-25 10:15:53,886 server.WebServer????????????????????? INFO? - Starting ZeroConfService _http._tcp.local for Web Server with properties {path=/, json=5.1.0} [WebServer]
2019-11-25 10:15:53,927 PanelPro.PanelPro???????????????????? INFO? - Main initialization done [main]
2019-11-25 10:17:05,419 audio.JoalAudioFactory??????????????? INFO? - Initialised JOAL using OpenAL: vendor - OpenAL Community version - 1.1 ALSOFT 1.15.1 [Listed Table Generation]


Exception:

2019-11-25 10:18:23,110 ptionhandler.UncaughtExceptionHandler ERROR - Uncaught Exception caught by jmri.util.exceptionhandler.UncaughtExceptionHandler [AWT-EventQueue-0]
java.lang.IllegalArgumentException: Wrong number of events in address: sensor1
??? at jmri.jmrix.can.cbus.CbusAddress.validateSysName(CbusAddress.java:381)
??? at jmri.jmrix.can.cbus.CbusSensorManager.validateAddressFormat(CbusSensorManager.java:162)
??? at jmri.jmrix.can.cbus.CbusSensorManager.validateSystemNameFormat(CbusSensorManager.java:131)
??? at jmri.Manager.makeSystemName(Manager.java:155)
??? at jmri.managers.AbstractManager.makeSystemName(AbstractManager.java:83)
??? at jmri.Manager.makeSystemName(Manager.java:126)
??? at jmri.swing.SystemNameValidator.getValidation(SystemNameValidator.java:77)
??? at com.alexandriasoftware.swing.JInputValidator.verify(JInputValidator.java:195)
??? at jmri.swing.SystemNameValidator.setManager(SystemNameValidator.java:118)
??? at jmri.jmrit.beantable.AddNewHardwareDevicePanel.lambda$1(AddNewHardwareDevicePanel.java:132)
??? at java.desktop/javax.swing.JComboBox.fireActionEvent(JComboBox.java:1264)
??? at java.desktop/javax.swing.JComboBox.setSelectedItem(JComboBox.java:589)
??? at jmri.swing.ManagerComboBox.setManagers(ManagerComboBox.java:63)
??? at jmri.swing.ManagerComboBox.setManagers(ManagerComboBox.java:80)
??? at jmri.jmrit.beantable.AbstractTableAction.configureManagerComboBox(AbstractTableAction.java:232)
??? at jmri.jmrit.beantable.SensorTableAction.addPressed(SensorTableAction.java:134)
??? at jmri.jmrit.beantable.AbstractTableTabAction$TabbedTableItem.lambda$0(AbstractTableTabAction.java:221)
??? at java.desktop/javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1967)
??? at java.desktop/javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2308)
??? at java.desktop/javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:405)
??? at java.desktop/javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:262)
??? at java.desktop/javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:279)
??? at java.desktop/java.awt.Component.processMouseEvent(Component.java:6632)
??? at java.desktop/javax.swing.JComponent.processMouseEvent(JComponent.java:3342)
??? at java.desktop/java.awt.Component.processEvent(Component.java:6397)
??? at java.desktop/java.awt.Container.processEvent(Container.java:2263)
??? at java.desktop/java.awt.Component.dispatchEventImpl(Component.java:5008)
??? at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2321)
??? at java.desktop/java.awt.Component.dispatchEvent(Component.java:4840)
??? at java.desktop/java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4918)
??? at java.desktop/java.awt.LightweightDispatcher.processMouseEvent(Container.java:4547)
??? at java.desktop/java.awt.LightweightDispatcher.dispatchEvent(Container.java:4488)
??? at java.desktop/java.awt.Container.dispatchEventImpl(Container.java:2307)
??? at java.desktop/java.awt.Window.dispatchEventImpl(Window.java:2772)
??? at java.desktop/java.awt.Component.dispatchEvent(Component.java:4840)
??? at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:772)
??? at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:721)
??? at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:715)
??? at java.base/java.security.AccessController.doPrivileged(Native Method)
??? at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
??? at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:95)
??? at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:745)
??? at java.desktop/java.awt.EventQueue$5.run(EventQueue.java:743)
??? at java.base/java.security.AccessController.doPrivileged(Native Method)
??? at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:85)
??? at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:742)
??? at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
??? at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
??? at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
??? at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
??? at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
??? at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
Locked Re: Issue recognizing locomotive - Atlas N MP15DC

 

Hey all,
?
Just providing an update on this issue. I think this message might not have attached to this topic originally, so just doing so now.
?
I received the Digitrax decoder and got it installed. I found that the pins that connect to the motor might have incidentally been slightly bent, as to prevent the decoder from connecting to the motor. I corrected the angle of the connections and everything seems to be working now.

I went back and tried out the original decoder again but didn't see any differences there, so it might be a bad chip, or at least one that neither the SPROG 3 or my new Digitrax DCS52 seem to want to pick up. I might eventually do some more tinkering with it.
?
I really appreciate all the suggestions! I¡¯m just glad it¡¯s working now with the new decoder.
Locked Re: Signaling feedback to Panels

 

Dick wrote "I would like to hear about the rule set that requires more than 32 aspects."

FIY - The following existing JMRI mast definitions implement more than 30 aspects:
- CROR-2008 - 3A-Hi : 31 aspects - see .
- CROR-2008 - 3D-Hi : 31 aspetcts - see .
- CROR-2008 - 3-Hi: 31 aspects - see .

If one were to add duplicate aspects to reflect "Dark but would otherwise be displaying XXX" aspects as I have suggested for discussion purposes, it would double the count of aspects, and exceed the available number of DCC Extended Accessory Decoder aspect values.

I would not be surprised to find that one or more non-US signal system would have a mast which could display more than 32 aspects...

A few other existing JMRI signal mast definitions appear to implement more than 30 aspects but are named as "test" masts or appear to include images for multiple mast types where they would typically define only a single mast type per "appearance" file, so the actual aspect count is suspect.

Regards,
Billybob
Locked Re: Help with JMRI and nce usb,sb5,aiu01,bd20 (On the Verge of Chucking out my SBS)

 

Ken,

On 25 Nov 2019, at 2:44 PM, Ken Cameron <kcameron@...> wrote:

I've found better results with the 7.3.7 (all jumpers on) setting.
Effectively it says the USB will attempt to pass all commands to the command
station. All the other settings have combinations of restrictions that match
different versions of different command station.
The original USB V7 documentation showed 7.3.7 for ALLSYS.

The revised USB V7 documentation shows 7.3.7 for PowerCab.
The revised USB V7 documentation shows 7.3.1 for SB5 (19,200).
The revised USB V7 documentation no longer shows ALLSYS.

Dave in Australia
Locked Re: Help with JMRI and nce usb,sb5,aiu01,bd20 (On the Verge of Chucking out my SBS)

 

I've found better results with the 7.3.7 (all jumpers on) setting.
Effectively it says the USB will attempt to pass all commands to the command
station. All the other settings have combinations of restrictions that match
different versions of different command station.

-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.org
www.syracusemodelrr.org
Locked Re: Help with JMRI and nce usb,sb5,aiu01,bd20 (On the Verge of Chucking out my SBS)

 

¿ªÔÆÌåÓý

Dan,

On 25 Nov 2019, at 1:05 PM, Dan Boudreau <daboudreau@...> wrote:

Valid cab addresses (for cabs in) a Powercab system are 2,3,4, or 5. Total of 4 actual cabs. 6 and 7 are unused. 8,9 and 10 can be used for other cab devices (AIU,USB) only.

?Valid cab addresses (for cabs) in an SB5 system are 2,3,4,5, 6 and 7. Total of 6 actual cabs. ?8,9 and 10 can be used for other cab devices (AIU,USB) only.

?If the AIU cab address is higher than 10 it will not work due to the limits of the command stations.


Correct, but there's further qualification needed regarding firmware versions:

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.

Dave in Australia
Locked Re: Help with JMRI and nce usb,sb5,aiu01,bd20 (On the Verge of Chucking out my SBS)

 

¿ªÔÆÌåÓý

Dan,

On 25 Nov 2019, at 1:28 PM, Dan Boudreau <daboudreau@...> wrote:

Here's a link to a table that shows how to properly configure the jumpers for the USB.? I believe you should set up your jumpers so you get a 7.3.1 response, not a 7.3.7 that's showing in your console text.

You are quite correct, as I had posted in an earlier message on this thread, which shows exactly what jumper and JMRI settings to use. It appears Russ may not have seen it:

Dave in Australia
Locked Re: Help with JMRI and nce usb,sb5,aiu01,bd20 (On the Verge of Chucking out my SBS)

 

Here's a link to a table that shows how to properly configure the jumpers for the USB.? I believe you should set up your jumpers so you get a 7.3.1 response, not a 7.3.7 that's showing in your console text.



Dan
Locked Re: Help with JMRI and nce usb,sb5,aiu01,bd20 (On the Verge of Chucking out my SBS)

 

Found this on the NCE site with regards to AIUs:

Valid cab addresses (for cabs in) a Powercab system are 2,3,4, or 5. Total of 4 actual cabs. 6 and 7 are unused. 8,9 and 10 can be used for other cab devices (AIU,USB) only.

?Valid cab addresses (for cabs) in an SB5 system are 2,3,4,5, 6 and 7. Total of 6 actual cabs. ?8,9 and 10 can be used for other cab devices (AIU,USB) only.

?If the AIU cab address is higher than 10 it will not work due to the limits of the command stations.
Locked Re: Help with JMRI and nce usb,sb5,aiu01,bd20 (On the Verge of Chucking out my SBS)

 

In your system console text, it shows that there is a response to the command to poll the AIU, a "30" which means command not supported.? I believe you need to have your AIUs in a lower address range for it to work in your setup.? So I think your very close to getting it working.

Dan
73841 - 73860 of 239565