Re: For Andrew (Andy) and his Walthers GP7

Hi Marc,

I've been getting conflicting info. Some say that you also program on the main using "blast" mode, or get the PTB-100. It sounds like you're saying I should scrap the idea (at least for now)of using these components with the computer and just swicth the PR4 to programmer?

Andy?

Show quoted text

On Thu, Jan 3, 2019 at 2:10 AM Marc <forfoum@...> wrote:

Andrew,? The DCS51, on it's own,? will not read a Tsunami decoder without the PTB-100 present.?

Since you have the PR4, attache the program track to it and use the provided PS14 that came with the PR4 or use the power pack from your Zephyr.
It's higher output will certainly help out.?

Remember to change the PREFERENCES, Command Station Type to PR3 Standalone or it will not work. With this change you must restart DecoderPro.

Marc

--

Andrew Roberts

Re: JMRI Not Identifying Locomotives Properly

#155330

开云体育

The "Identify" button on the main DecoderPro window already reads the following CVs, in the order listed below:

CV29

CV17 & CV18 OR CV1 (depending on the result from CV29)

CV7

CV8

All the uses cases I checked (long and short addresses, no address match, unique address match, multiple address match) exhibited this behaviour.

So the "Identify" button is already reading CVs 7 and 8. We don't need to add them.

I don't have time to check the code at present to see if it actually uses the read values of ?CVs 7 and 8 nor in what way.

Tea time over here now and time to slow down for the day... Not to mention the thunderstorms starting...

--?

Dave in Australia

Show quoted text

On 3 Jan 2019, at 4:35 PM, Bob Jacobsen <rgj1927@...> wrote:

In turn, that selectLoco operation knows whether one or more matched. That would be a good place for the program to reason about whether any additional reads (CV7, CV8, etc) would be able to distinguish the different choices, and if need be, spend the time to do them.

Re: For Andrew (Andy) and his Walthers GP7

#155329

The error "programmer already in use" below indicates you've probably clicked a second time on "Read Type from Decoder" before it had finished trying the first time.

I can take several minutes to complete, particularly if it isn't able to read as it will retry several times in Direct Mode and then retry several times in Paged mode (very slow).

You need to watch the status bar at the bottom of the "Create New Loco" window.
-- 
Dave in Australia

Show quoted text

On 3 Jan 2019, at 3:28 PM, Andrew <soundrew@...> wrote:

2019-01-02 22:49:09,827 loconet.SlotManager                   INFO  - programmer already in use by jmri.jmrit.symbolicprog.CombinedLocoSelPane$7@1653d9 [AWT-EventQueue-0]
2019-01-02 22:49:51,066 jmrit.AbstractIdentify                WARN  - No acknowledge from locomotive (308), trying Paged mode [AWT-EventQueue-0]
2019-01-02 22:49:54,396 jmrit.AbstractIdentify                WARN  - Stopping due to error: No acknowledge from locomotive (308) [AWT-EventQueue-0]
2019-01-02 22:49:54,396 jmrit.AbstractIdentify                WARN  - Restoring Direct Byte mode [AWT-EventQueue-0]
2019-01-02 22:50:54,760 jmrit.AbstractIdentify                WARN  - No acknowledge from locomotive (308), trying Paged mode [AWT-EventQueue-0]
2019-01-02 22:50:58,091 jmrit.AbstractIdentify                WARN  - Stopping due to error: No acknowledge from locomotive (308) [AWT-EventQueue-0]
2019-01-02 22:50:58,091 jmrit.AbstractIdentify                WARN  - Restoring Direct Byte mode [AWT-EventQueue-0]

Re: VSDecoder: Problems with xml and sound #vsdecoder #rpi #ubuntu

#155328

On Jan 2, 2019, at 2:53 PM, SettleDown <wgrushton@...> wrote:

BTW. Is there any provision for including photos in the jmriusers posts ?  I wanted to include a shot of the RasPi JMRI UI as seen by my iPad.
Can be, but the moderators turned it off as it attracted _lots_ of spam on the old Yahoo group.  Not sure if groups.io is better or not, but that’s up to the moderators (who work very diligently on these kinds of things!  Much thanks are due…)

As a workaround, you can put the picture in the Photos section (i.e. /g/jmriusers/photo/50510/1?p=Name,,,20,1,0,0 ) and link to it.

Bob
--
Bob Jacobsen
rgj1927@...

Re: JMRI Not Identifying Locomotives Properly

#155327

The identify-locomotive engine is here:

It’s just a simple state machine that reads CV29 to decide whether the short or long address is in use, then reads the appropriate CVs to get the address. 

It’s used in several places, but a typical one is here:

where the address is used to do a selectLoco operation.  

In turn, that selectLoco operation knows whether one or more matched. That would be a good place for the program to reason about whether any additional reads (CV7, CV8, etc) would be able to distinguish the different choices, and if need be, spend the time to do them.

If somebody wants to write that, the process is described here:

and related pages in the left index.

Bob

--
Bob Jacobsen
jacobsen@... +1-510-708-5988 AIM, Skype JacobsenRG

Re: Trouble with JMRI to JMRI client/server

#155326

This looks like the LocoNet Simulator might not fully handle the connection as a server.  (The Simulator connection isn’t intended to simulate an entire layout; it just has stand-ins for various things)

Try setting up the server as a real Loconet connection.  There doesn’t need to be real hardware out there, just a serial port it dump commands out.

Bob

On Jan 2, 2019, at 4:09 PM, mabooker76 <mabooker76@...> wrote:

Another try with more robust iMac as client to same RPI server.

Log file:
2019-01-02 16:05:46,872 node.NodeIdentity                     INFO  - Using jmri-lVjxtcZsGhNiaaypSc6P96-3eeb2581 as the JMRI Node identity [AWT-EventQueue-0]

2019-01-02 16:05:47,253 locormi.LnMessageClient               ERROR - Exception while trying to connect: java.rmi.ConnectException: Connection refused to host: 192.168.1.15; nested exception is: 

 java.net.ConnectException: Connection refused (Connection refused) [main]

2019-01-02 16:05:47,255 configurexml.ConnectionConfigXml      ERROR - Error opening connection to 192.168.1.15 was: {} [main]

jmri.jmrix.loconet.LocoNetException: Failed to Connect to Server: 192.168.1.15

 at jmri.jmrix.loconet.locormi.LnMessageClient.configureRemoteConnection(LnMessageClient.java:93)

 at jmri.jmrix.loconet.locormi.configurexml.ConnectionConfigXml.load(ConnectionConfigXml.java:110)

 at jmri.jmrix.ConnectionConfigManager.initialize(ConnectionConfigManager.java:106)

 at jmri.implementation.JmriConfigurationManager.initializeProvider(JmriConfigurationManager.java:264)

 at jmri.implementation.JmriConfigurationManager.lambda$3(JmriConfigurationManager.java:260)

 at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)

 at java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:580)

 at jmri.implementation.JmriConfigurationManager.initializeProvider(JmriConfigurationManager.java:259)

 at jmri.implementation.JmriConfigurationManager.lambda$3(JmriConfigurationManager.java:260)

 at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)

 at java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:580)

 at jmri.implementation.JmriConfigurationManager.initializeProvider(JmriConfigurationManager.java:259)

 at jmri.implementation.JmriConfigurationManager.lambda$1(JmriConfigurationManager.java:183)

 at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)

 at java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:580)

 at jmri.implementation.JmriConfigurationManager.load(JmriConfigurationManager.java:182)

 at jmri.implementation.JmriConfigurationManager.load(JmriConfigurationManager.java:170)

 at apps.Apps.<init>(Apps.java:261)

 at apps.PanelPro.PanelPro.<init>(PanelPro.java:40)

 at apps.PanelPro.PanelPro.main(PanelPro.java:120)

2019-01-02 16:05:47,286 locormi.ConnectionConfig              WARN  - Unexpected call to setInstance, multi-replica capability not yet present [main]

2019-01-02 16:05:47,293 jmrix.ConnectionConfigManager         ERROR - Unable to create jmri.jmrix.loconet.locormi.configurexml.ConnectionConfigXml for [Element: <connection/>], load returned false [main]

2019-01-02 16:05:47,295 plementation.JmriConfigurationManager ERROR - Exception initializing jmri.jmrix.ConnectionConfigManager: Unable to create connection "LocoNet" (L). [main]

2019-01-02 16:05:47,646 jmri.InstanceManager                  ERROR - Should not set default of type jmri.CommandStation to null value [main]

2019-01-02 16:05:47,647 managers.ManagerDefaultSelector       WARN  - SystemConnectionMemo for LocoNet (class jmri.jmrix.loconet.LocoNetSystemConnectionMemo) provides a null interface jmri.CommandStation instance [main]

2019-01-02 16:05:47,648 plementation.JmriConfigurationManager ERROR - Exception initializing jmri.managers.ManagerDefaultSelector: System connection LocoNet provides a null manager for interface jmri.CommandStation [main]

2019-01-02 16:05:47,720 plementation.JmriConfigurationManager ERROR - Exception initializing apps.StartupActionsManager: jmri.util.prefs.InitializationException: Unable to run startup actions due to earlier failures. [main]

There is no firewall that I am aware of on the RPI.

Thanks,
Martin Booker

--
Bob Jacobsen
rgj1927@...

Re: For Andrew (Andy) and his Walthers GP7

#155325

Hi Marc,

I have seen conflicting reports as to the compatability of the PR4 with my controller or loco or loconet. Without some definitive test, i'm loathe claim that is the issue. Until I am convinced by you (or someone else) i wil hold off on buying the booster.

Program track is connected to pRG A and B terminals on the DCS51. DCS is connected to PR4 via homemade loconet cable (tested good with Digitrax tester).

Thanks again!

Andy

Show quoted text

On Wed, Jan 2, 2019 at 11:30 PM Marc <forfoum@...> wrote:

That is an older Tsunami decoder. You can use the Zephyr's BLAST mode. Change OPSW 07. ? Just remove the layout wires from the back of the Zephyr
and use the PROG leads only.?

BLAST mode is sent out over the PROG A/B and RAIL A/B?? so you want to protect the engines on the layout from being inadvertently re programmed.

If this does not work (which is possible) then the PTB-100 is required to be able to read the decoder. Writing to decoder is not an issue if you use OPS mode but we want to read the CV's? so the PTB-100 is the proper tool. That or a SPROG or PR4 with 15 volt ( not more than 20V) power.

Marc

--

Andrew Roberts

Re: For Andrew (Andy) and his Walthers GP7

#155322

Hello All,

I followed the protocol as requested from Dave Heap when he was trying to help Mark. Here is my report from the same process:

The Basics: JMRI 4.14, windows laptop with 7 professional (SP1), Java 1.8.0? Digitrax PR4, home made loconet cable that gets four green lights on tester, loco is Walthers new GP7 with tsunami (decoder is TSU-WW56 REV A)

At main page the following was in status bar:

Service Mode Programmer: LocoNet is online (green)

Operations Mode Programmer: LocoNet is online (green)

Programmer Status: Idle (black)

At opening of "Create New Loco" page:

Status bar says idle (black)

After clicking on "read type from decoder" button:

clicking sounds through the loco speaker, green light flashing on PR4

"Stopping due to error. No acknowledgement from locomotive (308)

Here is the script from the system console page:

2019-01-02 22:46:06,956 util.Log4JUtil??????????????????????? INFO? - * JMRI log ** [main]
2019-01-02 22:46:06,976 util.Log4JUtil??????????????????????? INFO? - This log is appended to file: C:\Users\Andrew\JMRI\log\messages.log [main]
2019-01-02 22:46:06,976 util.Log4JUtil??????????????????????? INFO? - This log is stored in file: C:\Users\Andrew\JMRI\log\session.log [main]
2019-01-02 22:46:06,986 apps.AppsBase???????????????????????? INFO? - DecoderPro version 4.14+Rd060e0b starts under Java 1.8.0_191 on Windows 7 x86 v6.1 at Wed Jan 02 22:46:06 EST 2019 [main]
2019-01-02 22:46:12,577 gui3.Apps3??????????????????????????? INFO? - Starting with profile Green_Valley_RR.3f126047 [main]
2019-01-02 22:46:13,137 node.NodeIdentity???????????????????? INFO? - Using jmri-jxalgafLWhOiaakonh1tQg-3f126047 as the JMRI Node identity [AWT-EventQueue-0]
2019-01-02 22:46:13,297 xml.AbstractSerialConnectionConfigXml INFO? - Starting to connect for "LocoNet" [main]
2019-01-02 22:46:13,757 pr3.PR3Adapter??????????????????????? INFO? - PR3 adapter set hardware flow control, mode=2 RTSCTS_OUT=2 RTSCTS_IN=1 [main]
2019-01-02 22:46:13,767 locobuffer.LocoBufferAdapter????????? INFO? - COM4 port opened at 57600 baud with DTR: true RTS: true DSR: false CTS: false? CD: false [main]
2019-01-02 22:46:13,837 loconet.LnPacketizer????????????????? INFO? - lnPacketizer Started [main]
2019-01-02 22:46:14,307 util.FileUtilSupport????????????????? INFO? - File path program: is C:\Program Files (x86)\JMRI\ [main]
2019-01-02 22:46:14,307 util.FileUtilSupport????????????????? INFO? - File path preference: is C:\Users\Andrew\JMRI\Green_Valley_RR\ [main]
2019-01-02 22:46:14,307 util.FileUtilSupport????????????????? INFO? - File path profile: is C:\Users\Andrew\JMRI\Green_Valley_RR\ [main]
2019-01-02 22:46:14,307 util.FileUtilSupport????????????????? INFO? - File path settings: is C:\Users\Andrew\JMRI\ [main]
2019-01-02 22:46:14,307 util.FileUtilSupport????????????????? INFO? - File path home: is C:\Users\Andrew\ [main]
2019-01-02 22:46:14,307 util.FileUtilSupport????????????????? INFO? - File path scripts: is C:\Program Files (x86)\JMRI\jython\ [main]
2019-01-02 22:49:09,827 loconet.SlotManager?????????????????? INFO? - programmer already in use by jmri.jmrit.symbolicprog.CombinedLocoSelPane$7@1653d9 [AWT-EventQueue-0]
2019-01-02 22:49:51,066 jmrit.AbstractIdentify??????????????? WARN? - No acknowledge from locomotive (308), trying Paged mode [AWT-EventQueue-0]
2019-01-02 22:49:54,396 jmrit.AbstractIdentify??????????????? WARN? - Stopping due to error: No acknowledge from locomotive (308) [AWT-EventQueue-0]
2019-01-02 22:49:54,396 jmrit.AbstractIdentify??????????????? WARN? - Restoring Direct Byte mode [AWT-EventQueue-0]
2019-01-02 22:50:54,760 jmrit.AbstractIdentify??????????????? WARN? - No acknowledge from locomotive (308), trying Paged mode [AWT-EventQueue-0]
2019-01-02 22:50:58,091 jmrit.AbstractIdentify??????????????? WARN? - Stopping due to error: No acknowledge from locomotive (308) [AWT-EventQueue-0]
2019-01-02 22:50:58,091 jmrit.AbstractIdentify??????????????? WARN? - Restoring Direct Byte mode [AWT-EventQueue-0]

Thanks for your help in this

Andy

Show quoted text

On Wed, Jan 2, 2019 at 10:28 PM Andrew via Groups.Io <soundrew=[email protected]> wrote:

Hello Marc,
So I'm back home now and still not able to get my DCS51 or jmri to see this loco. I can tell you that I cracked open the engine and the decoder says TSU-WW56 REV A.

I will send you the open capture once I am able.

Andy

On Tue, Jan 1, 2019 at 2:52 AM Marc <forfoum@...> wrote:
Andrew, Walthers GP7? you mentionned.?

This is not in JMRI and I have started adding it (Pensy, CNW, NYC)? to the definition.? Need a favor from you
Need a capture of all CV's exported to a CSV file.? This can be done in an open ROSTER entry. of the GP7.

There is limited documentation avail from Walthers or Soundtraxx re this (these) engine(s).

Marc
foufoum-at-videotron-dot-ca

--
Andrew Roberts

--

Andrew Roberts

Re: JMRI Not Identifying Locomotives Properly

#155321

That is the problem. There's no way of uniquely determining the JMRI ID (user-created and stored in the roster entry) from what is stored in (and we can read back from) the decoder (DCC ID, CV7, CV8). (That is what the original poster asked for.)

JMRI attempts to do just that. In some cases you may be lucky, in other cases (see Gerry's, mine is similar) you are going to get many matches to the only readable information.

The Identify button is a blunt instrument. If it works for you, count yourself lucky.
-- 
Dave in Australia

Show quoted text

On 3 Jan 2019, at 2:19 PM, Stefan ` Bartelski <stefan@...> wrote:

...and is the discussion about the DCC ID or the JMRI ID? I am totally confused.

Re: Decoder Pro problems

#155320

Marc,

I've already checked that out and sent an image showing him what to fix on the Defaults screen.
-- 
Dave in Australia

Show quoted text

On 3 Jan 2019, at 1:30 PM, Marc <forfoum@...> wrote:

Dave,

What also surprises me is the two (2) Warn messages. I am also running 14.4 thru a PR3 and do not get these two warnings. 

I would in previous JMRI version  and knew how to resolve them. They have no effect in the case of a PR3 in Standalone mode 
but it is strange to see them still appearing in  14.4.

It is another of those INFERNAL default errors once more.

Re: Decoder Pro problems

#155319

Marc,
Thanks for your reply.? If the PR4 works with Soundloader but not JMRI, but my PR3 (same computer, same JMRI and same loco and same power supply) works fine with both SL and JMRI, does that not indicate that there IS some kind of difference between the two? Maybe not command wise, but hardware wise, which could have an influence on how it communicates with decoders.

Regarding #4, all I have been saying is that there are a number of messages in this forum of PR4 users exhibiting similar issues. aI know there are few messages that say "my PR4 works fine". So is the issue a DT quality control issue, that the PR4s that do not seem to accept JMRI are maybe on the edge of some tolerance. Or is there another factor??

One alternative I told my friend to try when his PR4 arrives back, is to use the PR4 to drive the control station programming, rather that using it standalone. Perhaps that is why the "my PR4 works" crowd is successful? But I will also suggest to him that we check his power pack (currently a PS14, if I am not mistaken, so not 12V)
--
Stefan Bartelski

Home layout: The Blue Ridge Line, an HO representation of the L&N Etowah Old Line from Etowah to Elizabeth, set in 1986 9under construction)
Modular Layout: Shoofly module of the Country RRoads Modular group

Re: Decoder Pro problems

#155318

That's why I want Mark to install V4.15.1. The log will then tell us what JMRI actually read.
-- 
Dave in Australia

Show quoted text

On 3 Jan 2019, at 1:23 PM, Marc <forfoum@...> wrote:

As per Mark 

"  The DH166D is not highlighted, what is highlighted is: DH123, DH121, DH120 and DZ120.  "

So it would appear the decoder was read and  the CV7 value  returned was  within the 33 to 46 range and the corresponding decoder type highlighted.
The DH166D CV7 range  is 51 to 64.

His DH166D would NOT be returning the proper CV7 response ?

Re: For Andrew (Andy) and his Walthers GP7

#155317

Hello Marc,

So I'm back home now and still not able to get my DCS51 or jmri to see this loco. I can tell you that I cracked open the engine and the decoder says TSU-WW56 REV A.

I will send you the open capture once I am able.

Andy

Show quoted text

On Tue, Jan 1, 2019 at 2:52 AM Marc <forfoum@...> wrote:

Andrew, Walthers GP7? you mentionned.?

This is not in JMRI and I have started adding it (Pensy, CNW, NYC)? to the definition.? Need a favor from you
Need a capture of all CV's exported to a CSV file.? This can be done in an open ROSTER entry. of the GP7.

There is limited documentation avail from Walthers or Soundtraxx re this (these) engine(s).

Marc
foufoum-at-videotron-dot-ca

--

Andrew Roberts

Re: JMRI Not Identifying Locomotives Properly

#155316

...and is the discussion about the DCC ID or the JMRI ID? I am totally confused.
--
Stefan Bartelski

Home layout: The Blue Ridge Line, an HO representation of the L&N Etowah Old Line from Etowah to Elizabeth, set in 1986 9under construction)
Modular Layout: Shoofly module of the Country RRoads Modular group

Re: JMRI Not Identifying Locomotives Properly

#155315

开云体育

I just reread this and are you thinking that once you identify the loco and create an entry, that any of that descriptive data is written to the decoder? ?So that the next time JMRI pulls up the correct entry?

The only descriptive data on the decoder is the CVs set by the manufacturer. Many times the same code is used for several different decoders.?

What we have is the solution given the source data.?

David Klemm

?

Show quoted text

From: [email protected] on behalf of dcesharkman via Groups.Io <dcesharkman@...>
Sent: Wednesday, January 2, 2019 14:57
To: [email protected]
Subject: [jmriusers] JMRI Not Identifying Locomotives Properly

?

I have many locomotives with proper road numbers that overlap with others. For example, I have a Kato NYC PA unit with the number of 4301, but I also have a Kato SD70ACE in MRL with the same number.? I have many instances of this same situation.? There must be a better way to assign the identity of a locomotive so that these miss-identities do not happen. I have 62 of these occurrences. This is where better indexing could keep this from happening.

Re: MQTT Connection in JMRI

#155314

On Wed, Jan 2, 2019 at 09:27 PM, Dave wrote:

Chris,

Re: 64 byte limit - I saw it in a message from Speed on 15 Dec. Yes, it is referring to ESP type devices, it's certainly not a problem with MQTT itself. Does anyone know what the smallest payload limit is on the devices we are likely to use for model railroads, perhaps NodeMCU ESP8266???

For signals, it may be simpler to use signal heads where the payload only needs to be the appearance - red, flashing yellow, dark, etc (also mentioned by Speed)? Masts can be built using Signal Head Controlled Mast driver, already available in JMRI.?

Simplest case payloads:

?

Device type? -? ?Payload options

?

Turnout - Closed | Thrown

Sensor - Active | Inactive (or 1 | 0 )?

Signal Head - Red | Yellow | Green | Dark | Flashing Red | Flashing Yellow | Flashing Green

and perhaps though maybe later down the track
Signal Mast - the aspect name (which isn't as simple as it sounds because there are in some railroads multiple appearance options for the same aspect name)?
? ? ? ? or? ? ? -? ?the combination of head appearances with comma separators e.g.? red,flashyellow,red
(Note: There appears to be some inconsistency between Heads and Masts currently in JMRI in the use of? flashyellow vs Flashing Yellow and where lunar is an option. I don't yet understand why that is so, will look a bit deeper)

Things start to get more complicated when you want to include more detailed configuration information to reduce the configuration information needing to be held in the actioning device or for having flexible devices and therefore requiring more instruction.? We can consider making allowance for this, perhaps using the Comments value in the JMRI table, or, at least as an interim step, just make it a requirement that such configuration is for the actioning device to sort out.?

- David.

Dave,?

I have some serious doubts that ESP8266 or ESP32 will have problems with JSON as shown in my last post. These two specific boards are very popular in the home automation spectrum and have the ability to parse these JSON:

{ "brightness": 255, "color_temp": 155, "color": { "r": 255, "g": 180, "b": 200, "x": 0.406, "y": 0.301, "h": 344.0, "s": 29.412 }, "effect": "colorloop", "state": "ON", "transition": 2, "white_value": 150 }

I am not saying there are limits, but I have some serious doubts a JMRI payload will reach 64 bytes. As long as the the simple things like turnouts and sensors are kept simple. I believe that lights, signals should have the ability to be in JSON and this should allow more dynamic things for example. Reporters can also be simple text or JSON. If JSON are used for reporters the user would have to probably develop a custom script, since they are more than likely doing something special.?

Chris

Re: JMRI Not Identifying Locomotives Properly

#155313

开云体育

???????

Here is just a small section of my roster - all have the same Road identification, most have the same road number, but different decoders. This roster only has 1,405 entries - some N Scale, Some HO and Some O scale. These locos are all green.

NSW 3801	3801	QSI Steam Ver. 7	Eureka C38 4-6-2
NSW 3801 ar	3801	Econami Steam	ECO-200 Steam
NSW 3801 bd	3801	Tsunami Steam	TSU-1000 Light Steam
NSW 3801 dt	3801	QSI Steam Ver. 7	Eureka C38 4-6-2
NSW 3801 gh	3801	Tsunami Steam	TSU-750 DRGW K-Class Steam
NSW 3801 gw	3813	QSI Steam Ver. 7	Eureka C38 4-6-2
NSW 3801 jb	3830	Tsunami Steam	TSU-750 DRGW K-Class Steam
NSW 3801 jp	3801	QSI Steam Ver. 7	Eureka C38 4-6-2
NSW 3801 js	3801	Tsunami Steam	TSU-1000 DRGW K-Class Steam
NSW 3801 mp	3801	QSI Steam Ver. 7	Eureka C38 4-6-2
NSW 3801 mw	3801	QSI Steam Ver. 7	Eureka C38 4-6-2
NSW 3801 mw fl4	3801	TCS Function Decoders	FL4
NSW 3801 SM	3801	QSI Steam Ver. 7	Eureka C38 4-6-2
NSW 3801 tsu	3801	Tsunami Steam	TSU-750 DRGW K-Class Steam
NSW 3801 wh	3801	Tsunami Steam	TSU-750 DRGW K-Class Steam
NSW 3801 wh2	3801	QSI Steam Ver. 7	Eureka C38 4-6-2
NSW 3802	3802	QSI Steam Ver. 7	QSI Revolution Steam
NSW 3802 ls	3802	Tsunami Steam	TSU-1000 DRGW K-Class Steam
NSW 3802 rb	3802	Tsunami Steam	TSU-1000 DRGW K-Class Steam

The locos with QSI decoders were factory fitted the others were fitted "after market" - in numerous cases they were upgrades to replace the QSI decoders. There are 63 locos in this group - not counting other roads with identical numbers such as UP and Rio Grande.

How could you make a database of all locos - the decoder is the only part of the equation that can be identified with Decoder Pro. It is only in recent years that Decoder Manufacturers have added an extra CV to identify the particular model of decoder.

Just my thoughts

Gerry

On 3/01/2019 12:35 pm, dcesharkman via Groups.Io wrote:

This is why the application needs a database engine under the hood. That would also allow picklists for road names and locomotive models. That would make it very easy for make an indexable ID system.?

-- 
Gerry Hopkins MMR #177 FNMRA
Great Northern Downunder




NMRA Australasian Region
Contest & AP Chairman
Web Administrator

Virus-free.

Re: MQTT Connection in JMRI

#155311

Chris,

Re: 64 byte limit - I saw it in a message from Speed on 15 Dec. Yes, it is referring to ESP type devices, it's certainly not a problem with MQTT itself. Does anyone know what the smallest payload limit is on the devices we are likely to use for model railroads, perhaps NodeMCU ESP8266???

For signals, it may be simpler to use signal heads where the payload only needs to be the appearance - red, flashing yellow, dark, etc (also mentioned by Speed)? Masts can be built using Signal Head Controlled Mast driver, already available in JMRI.?

Simplest case payloads:

?

Device type? -? ?Payload options

?

Turnout - Closed | Thrown

Sensor - Active | Inactive (or 1 | 0 )?

and perhaps though maybe later down the track
Signal Mast - the aspect name (which isn't as simple as it sounds because there are in some railroads multiple appearance options for the same aspect name)?
? ? ? ? or? ? ? -? ?the combination of head appearances with comma separators e.g.? red,flashyellow,red

(Note: There appears to be some inconsistency between Heads and Masts currently in JMRI in the use of? flashyellow vs Flashing Yellow and where lunar is an option. I don't yet understand why that is so, will look a bit deeper)

Things start to get more complicated when you want to include more detailed configuration information to reduce the configuration information needing to be held in the actioning device or for having flexible devices and therefore requiring more instruction.? We can consider making allowance for this, perhaps using the Comments value in the JMRI table, or, at least as an interim step, just make it a requirement that such configuration is for the actioning device to sort out.?

- David.

Re: MQTT Connection in JMRI

#155309

I don't know where we're at now with the MQTT extension proposal.I’m waiting for a consensus to emerge so I can code it.

I think that consensus has emerged for the addressing (the topic will be taken from the system name, so people can use what they want), but not for the payload.

I’ve learned to insist on a real, multi-person consensus on things like this because there’s a natural inclination for people to add more and more and more complexity based on their own experience and desires. JMRI needs something that will work for lots of people, from simple (which tends to not get valued in these conversations) to more complex.

It would be great if the roughly half-dozen people in this thread could agree on something that would work for all of them.
--
Bob Jacobsen
=============
I think the topic parts need to be two types.
Global
Individual
The global would be:
Trains/
Sensors/
Reporters/
Turnouts/
Signals/
Lights/

This way JMRI could send out a message to address every item of a type.
For an example would be: Trains/ ALL STOP
Trains/ ACK  .....This so that a keep alive function for the link. The item does not have to do anything but acknowledge the message.
Sensors/ STATUS   ....So you could get a status report of every sensor.

This way JMRI could ensure that all the connections remain alive if sent every couple of minutes.

The individual would the item name
BNSF_907/
NW_789/
Turnout_mile_104/
T_134/
North_section/
My_Town_Yard/

The last two are for those who have a node that connects more that one item.
My_Town_Yard/Ladder_1/
My_Town_Yard/Ladder_15/

Now this does mean that each node will need to subscribe to more than one main topic.
The BNSF_907 would have BNSF_907/#/ and Trains/#/

The WiFi Throttle would have to be able to subscribe to numerous locomotives in case of a consisting. But as the Message would need to be sent to all the locomotives in that consist separate anyhow a minor problem if the locomotives are using WiFi for the connection.

The setup of the items in JMRI would have the main link to the node as the main part; The item name; the payload.

The actual items on the layout would never send a global message.

As for the payloads.
Have some global define words
NOP is No Operations required.
ACK is Acknowledge for keep alive link.
STATUS is send a report of all the variables.
ALL STOP

Other things to include would be:
Quote marks for ASCII characters. This is so if someone need the word "Thrown" they can use it or send the binary value of Thrown (0/1).
The different definitions of how to send the values Like Logical/Binary/Hex/Integer/Floating...
Standard notation could be used for this.

As for the length of the messages. I would suggest an upper limit of 96 characters for each the topic section and the payload section.

Donald

Re: PanelPro icon sets question

#155308

Hi Nick.
Signal masts.
Create 2 or more. Disable aspects you don't want, so just leave clear and stop say.
Add signal mast icon to panel. - not assigned to block join or turnout or any of that stuff.
Red X appears. Left click, edit signal mast logic. Add route to another mast (that's why you need more than one). All the auto stuff at the top should be unchecked. Manually add turnouts, sensors, blah blah. Or none.
Save panel.?
Next time you open no red X. Click on icon to change aspect, or what ever you set in the logic.
Signal heads work the same way. Add Signal Head icon, not signals to block join or turn out.?
Free form.?
Steve G.
You can design your own signal mast system if you don't like any of the existing ones. To make simple ones, copy one that's over stocked and delete the bits you don't want..
Can't use these for auto engineer trains.