I recently installed JMRI version 4.18+R37ad3d0 on a relatively new desktop PC running Windows 10 home, using a Digitrax PR3 with intent to use the Decoder Pro application. ?The install went fine, but the connection was a bit more challenging. My PC has two serial ports on the front; ?after a few trial-and-error changes of moving the PR3 USB cable between the two ports, and changing the serial port designation on the "Connections" screen between the various choices (COM 4, 1, and 3) I was pleased that communication was established with the loco on the programming track using one of the physical USB ports and COM3. ?I was able to program several locomotives, JMRI is a real pleasure to use. I used direct byte and specified programming track.

I shut down for the night, and returned the next day to program a few more locos. ?I cannot get the connection to work. ?I don't recall changing anything.?

By 'work', my experience is that the loco on the programming track moves a bit and may flash its lights when read/write is working correctly. The PR3 unit also flashes a combination of green and red lights (sorry for the non-technical description). I cannot find any combination of selecting different usb ports and changing the "COM" settings on the connection screen that establish communication with the loco.

I typically get the following error message box when attempting to start the Decoder Pro: "Unable to create connection "LocoNet" (L). Serial port COM4 not found. Unable to run startup actions due to earlier failures. Please check the log for more details. ?If you need to plug in or turn on anything, do so before restarting".?

I am stumped. ?It seems to be a connection issue, as Decoder Pro worked flawlessly before. There don't seem to be all that many connection items that I can change (I've now spent several hours changing every permutation and combination (where I change the PR3 cable attach port on the computer, and change COM port settings on the connection pane). ?When I move the cable between USB ports the Decoder Pro seems to see it, as it then gives alternative COM settings to choose from (sometimes just COM 1, then sometimes adds COM3 or COM4 or other choices when I move the cable around).

As I attempt to write to the loco, the programming pane (basic speed control for example) gives messages saying it is writing to the CV, but always then says "Programmer error: Timeout talking to the command station (306)". ?The loco does not move or flash, the graphics on my computer screen around the speed variables turn red and stay red. ?When Decoder Pro worked correctly it cycled quickly through the variables and the screen didn't stay red, as I recall. I don't think the loco is talking to anything.

I've tried other usb ports. ?Both the PC and Decoder Pro seem to recognize that something has changed - Windows tells me it has set up the new serial port (say COM6), and that COM selection appears on the connection screen in Decoder Pro, but I always get an error message on startup saying that port (COM6 in this example) is in use.

I've restarted the system a couple dozen times as I change combinations of the cable attach point/ COM setting. I've read the documentation on error messages and couldn't figure out a debug approach. I don't know what else to try. ?Any suggestions are welcome, thank you for reading this far.

What is a? "template " are you referring too ?

My assumption would be "Function Map "

Marc

Can the Digitrax templates be made like the Soundtraxx templates?
Jim K

Hi Dave.
Good question now that I think about it. I don't believe the CATS group was moved. Plus I do not know who would do that.
Later
Dave

Mike,

On 1 Feb 2020, at 5:27 AM, Mike Swederska <shur-way@...> wrote:

Thanks. I’m going to look into using Dropbox. I’m already using Dropbox for work.

As well as the Dropbox use link:
<>

There's a more in-depth description of what JMRI stores where at:
<>

Dave in Australia

Thanks. I’m going to look into using Dropbox. I’m already using Dropbox for work.?

Dave,
I don't think a WireShark log will be helpful in diagnosing the crash. It is in JMRI.
I've created a GitHub issue to track it:?
While collecting the debug log, if you find a repeatable way to cause the error, please provide those steps.
--SteveT

JMRI DecoderPro

The "Reset to defaults"? you are presented with when you open a roster entry only affects the roster entry.? These are the "Defaults" as called out by the DecoderPro definition file.? You would need to write out these "Reseted Values'? to the decoder to complete the reset.? These might not be the true factory defaults as they were input by the author of the definition file.

For a true " Factory reset "? one must use the RESET feature of the decoder. For this you must :

1 - Find the 'RESET'? at top of the roster entry, it is next to ' File '.
2 - Select ' Factory Reset '
3 - Select one of the reset options that are available. Digitrax will have a "Reset All CV's" or " Reset All CV's except speed table "
4 - Hit the "OK" button

Marc

You can omit the <show> elements.

On the screen, JMRI displays little icon files. Those don’t depend on what <show> says.

On the layout, JMRI has to drive hardware to display the right appearance. That’s done through various kinds of signal masts. Some of those depend on the <show> elements, some don’t. The ones that do use <show> won’t work unless that’s there, but others will.

Bob

On Jan 31, 2020, at 8:32 AM, tnt23 <tim.tashpulatov@...> wrote:

If the <show> tags can be totally left out, this would also suit me.

Is there a particular type of signal mast you’d like to start with? I could look more specifically.
I am starting with the simple (and cute) dwarf signal, see the picture. Carrying two lights, Lunar and Blue, it can dispay two aspects: Blue = Stop, Lunar = Proceed.



I have copied XML files from Basic signalling setup, and edited appearance files a bit. When running XML check I get error message regarding non-standard color (Blue) in <show> field.

Regards
Tim

--
Bob Jacobsen
rgj1927@...

The reset operation in the menu bar sends the commands to have the decoder do a local reset. You should do a Read All Sheets after that to make sure DecoderPro knows the new values.

The button to set to defaults sets DecoderPro’s values to the values in the decoder definition. You should do a Write All Sheets after that to make sure the decoder is updated with the new values.

Bob

On Jan 31, 2020, at 8:16 AM, Dale DeWitt <dcdewitt@...> wrote:

I have a couple of Digitrax motor decoders that need to be reset to factory defaults. When I choose reset to default in JMRI, does that simply reset the JMRI values shown on the screen to the template defaults or does it actually reset the decoder its self to the default settings. Pardon this very basic question.

--
Bob Jacobsen
rgj1927@...

开云体育

If the <show> tags can be totally left out, this would also suit me.

Is there a particular type of signal mast you’d like to start with? I could look more specifically.

I am starting with the simple (and cute) dwarf signal, see the picture. Carrying two lights, Lunar and Blue, it can dispay two aspects: Blue = Stop, Lunar = Proceed.



I have copied XML files from Basic signalling setup, and edited appearance files a bit. When running XML check I get error message regarding non-standard color (Blue) in <show> field.

Regards
Tim

I have a couple of Digitrax motor decoders that need to be reset to factory defaults.? When I choose reset to default in JMRI, does that simply reset the JMRI values shown on the screen to the template defaults or does it actually reset the decoder its self to the default settings.? Pardon this very basic question.

Dale

It’s straight-forward to allow additional colors in the XML files.

But it’s not clear what they should _do_. Most (perhaps all) of the code wouldn’t know about those if they occurred in the file.

Is there a particular type of signal mast you’d like to start with? I could look more specifically.

Bob

On Jan 31, 2020, at 6:41 AM, tnt23 <tim.tashpulatov@...> wrote:

Thanks Petr, will do.

My question stems from optional <show> elements in Aspects definition:

<appearance>
<aspectname>Clear</aspectname>
<show>green</show>
<show>red</show>
<reference></reference>
<delay></delay>
<imagelink></imagelink>
</appearance>

The ?SD signalling scheme does not use them. What are they used for?

Regards
Tim

--
Bob Jacobsen
rgj1927@...

Thanks Petr, will do.

My question stems from optional <show> elements in Aspects definition:

<appearance>
    <aspectname>Clear</aspectname>
    <show>green</show>
    <show>red</show>
    <reference></reference>
    <delay></delay>
    <imagelink></imagelink>
  </appearance>

The ?SD?signalling scheme does not use them. What are they used for?

Regards
Tim

Dave,?
If the problem persists, it would be helpful if you could enable WiThrottle server debugging and post your session.log file after some of these crashes. Steps to enable this are here:?
--SteveT

Hey Dave,
Yes, that looks like a crash in a WiThrottle Server instance. Do you have several of those at nearly the same time, or are they at different times?

Most recent Android versions try to use cell data, but that prevents the initial connection, I've not heard of it causing drops later. More info on that here:?

I don't see any recent changes to this code, so I'm not sure why you're seeing this now when you did not before.

--SteveT