JMRI is querying for the status of devices connecting to the LocoNet. But for some reason, perhaps because layout power is off, the command station is rejecting the requests (that’s the “Switch request failed!” message). JMRI then retries it, as it has no way to know whether the cause has cleared up or not.

For more info:

Bob

On Aug 7, 2018, at 7:35 AM, John Griffin <johng.sst@...> wrote:

If I have JMRI running on my computer and then plug it into my Digitrax command station this comes across the loconet monitor screen (just a sample of the full trace)

Interrogate LocoNet Turnouts/Sensors with bits a/c/b of 1/0/1; addresses..
41-48, 105-112, 169-176, 233-240, 297-304, 361-368, 425-432, 489-496,
553-560, 617-624, 681-688, 745-752, 809-816, 873-880, 937-944, 1001-1008,
1065-1072, 1129-1136, 1193-1200, 1257-1264, 1321-1328, 1385-1392, 1449-1456, 1513-1520,
1577-1584, 1641-1648, 1705-1712, 1769-1776, 1833-1840, 1897-1904, 1961-1968, 2025-2032.
LONG_ACK: Switch request Failed!
Interrogate LocoNet Turnouts/Sensors with bits a/c/b of 1/0/1; addresses...
41-48, 105-112, 169-176, 233-240, 297-304, 361-368, 425-432, 489-496,
553-560, 617-624, 681-688, 745-752, 809-816, 873-880, 937-944, 1001-1008,
1065-1072, 1129-1136, 1193-1200, 1257-1264, 1321-1328, 1385-1392, 1449-1456, 1513-1520,
1577-1584, 1641-1648, 1705-1712, 1769-1776, 1833-1840, 1897-1904, 1961-1968, 2025-2032.
LONG_ACK: Switch request Failed!
Interrogate LocoNet Turnouts/Sensors with bits a/c/b of 1/0/1; addresses...
41-48, 105-112, 169-176, 233-240, 297-304, 361-368, 425-432, 489-496,
553-560, 617-624, 681-688, 745-752, 809-816, 873-880, 937-944, 1001-1008,
1065-1072, 1129-1136, 1193-1200, 1257-1264, 1321-1328, 1385-1392, 1449-1456, 1513-1520,
1577-1584, 1641-1648, 1705-1712, 1769-1776, 1833-1840, 1897-1904, 1961-1968, 2025-2032.
LONG_ACK: Switch request Failed!
Interrogate LocoNet Turnouts/Sensors with bits a/c/b of 1/0/1; addresses...
41-48, 105-112, 169-176, 233-240, 297-304, 361-368, 425-432, 489-496,
553-560, 617-624, 681-688, 745-752, 809-816, 873-880, 937-944, 1001-1008,
1065-1072, 1129-1136, 1193-1200, 1257-1264, 1321-1328, 1385-1392, 1449-1456, 1513-1520,
1577-1584, 1641-1648, 1705-1712, 1769-1776, 1833-1840, 1897-1904, 1961-1968, 2025-2032.
LONG_ACK: Switch request Failed!
Interrogate LocoNet Turnouts/Sensors with bits a/c/b of 1/0/1; addresses..
41-48, 105-112, 169-176, 233-240, 297-304, 361-368, 425-432, 489-496,
553-560, 617-624, 681-688, 745-752, 809-816, 873-880, 937-944, 1001-1008,
1065-1072, 1129-1136, 1193-1200, 1257-1264, 1321-1328, 1385-1392, 1449-1456, 1513-1520,
1577-1584, 1641-1648, 1705-1712, 1769-1776, 1833-1840, 1897-1904, 1961-1968, 2025-2032.


This goes on for about a minute and swamps loconet. When done everything is ok. If I plug the computer into the command station and then start JMR this trace doesn't occur.

Developers, what's going on here? This isn't causing problems because it eventually stops. I'm just curious.

--
John Griffin
__________________________________
Your best friend isn't the one that bails you out of jail. He's the one sitting next to you saying "Dude, that was freaking awesome!!".

--
Bob Jacobsen
rgj1927@...

Hi Paul, ?? I mentioned in an earlier message that I hadn't been able to recover a largely working layout from a number of changes and updates etc., most of which were relatively minor, however it did include making a separate JK accessory bus and all solid state PC.
During this time we had a lightening strike which destroyed the router; given your comments and seeing that XpressNet Traffic Monitor shows a lot of "Normal Operations Resumed after timeout" message I think there is a possibility that the adapter was damaged by the lightening strike.?
I assume that we do not have a way of testing it ??
The replacement PC is unlikely to be the cause as it was not installed at that time.? Most things I've been through in fine detail so there isn't much else other than the LZV100!
Best regards,
Alan

Hi Dave

All these items you have come up with were caused I think by me following the suggestion in the Check menu as mentioned previously. I think I will have a look through my backup files and find the one that was created after I installed 4.12 and compare it with what you have produced now. I could perhaps have saved you a lot of effort if I had thought to try that before but I was only reminded of the existence of the backups when I was in my profile folder to store the first corrected file you posted.

As I said before, I really do appreciate your effort here

Thanks

Fraser

Option Reset previous Aspect does not affect the result.

When I switch the turnouts from the Turnout Table, there is no delays.

07:05:05.726: [packet: 52 1A 88 C0]? Accessory Decoder Operations Request: Turnout Address 105(Base Address 26,Sub Address 0) Turn Output 0 On.
07:05:05.735: [42 1A 29 71]? Feedback Response: Turnout with Feedback Turnout: 105 State: Thrown Left; Turnout: 106 State: Thrown Right
07:05:05.836: [packet: 52 1A 80 C8]? Accessory Decoder Operations Request: Turnout Address 105(Base Address 26,Sub Address 0) Turn Output 0 Off.
07:05:05.866: [01 04 05]? Command Successfully Sent/Normal Operations Resumed after timeout
07:05:05.968: [packet: 52 1A 80 C8]? Accessory Decoder Operations Request: Turnout Address 105(Base Address 26,Sub Address 0) Turn Output 0 Off.
07:05:06.001: [01 04 05]? Command Successfully Sent/Normal Operations Resumed after timeout
07:05:06.102: [packet: 52 1A 80 C8]? Accessory Decoder Operations Request: Turnout Address 105(Base Address 26,Sub Address 0) Turn Output 0 Off.
07:05:06.135: [01 04 05]? Command Successfully Sent/Normal Operations Resumed after timeout
07:05:06.206: [packet: 52 1A 8A C2]? Accessory Decoder Operations Request: Turnout Address 106(Base Address 26,Sub Address 1) Turn Output 0 On.
07:05:06.393: [42 1A 25 7D]? Feedback Response: Turnout with Feedback Turnout: 105 State: Thrown Left; Turnout: 106 State: Thrown Left
07:05:06.494: [packet: 52 1A 82 CA]? Accessory Decoder Operations Request: Turnout Address 106(Base Address 26,Sub Address 1) Turn Output 0 Off.
07:05:06.525: [01 04 05]? Command Successfully Sent/Normal Operations Resumed after timeout
07:05:06.625: [packet: 52 1A 82 CA]? Accessory Decoder Operations Request: Turnout Address 106(Base Address 26,Sub Address 1) Turn Output 0 Off.
07:05:06.659: [01 04 05]? Command Successfully Sent/Normal Operations Resumed after timeout
07:05:06.660: [packet: 52 1A 8C C4]? Accessory Decoder Operations Request: Turnout Address 107(Base Address 26,Sub Address 2) Turn Output 0 On.
07:05:06.685: [42 1A 39 61]? Feedback Response: Turnout with Feedback Turnout: 107 State: Thrown Left; Turnout: 108 State: Thrown Right
07:05:06.786: [packet: 52 1A 82 CA]? Accessory Decoder Operations Request: Turnout Address 106(Base Address 26,Sub Address 1) Turn Output 0 Off.
07:05:06.817: [01 04 05]? Command Successfully Sent/Normal Operations Resumed after timeout
07:05:06.918: [packet: 52 1A 84 CC]? Accessory Decoder Operations Request: Turnout Address 107(Base Address 26,Sub Address 2) Turn Output 0 Off.
07:05:07.124: [01 04 05]? Command Successfully Sent/Normal Operations Resumed after timeout
07:05:07.125: [packet: 52 1A 8E C6]? Accessory Decoder Operations Request: Turnout Address 108(Base Address 26,Sub Address 3) Turn Output 0 On.
07:05:07.143: [42 1A 35 6D]? Feedback Response: Turnout with Feedback Turnout: 107 State: Thrown Left; Turnout: 108 State: Thrown Left
07:05:07.244: [packet: 52 1A 84 CC]? Accessory Decoder Operations Request: Turnout Address 107(Base Address 26,Sub Address 2) Turn Output 0 Off.
07:05:07.273: [01 04 05]? Command Successfully Sent/Normal Operations Resumed after timeout
07:05:07.374: [packet: 52 1A 84 CC]? Accessory Decoder Operations Request: Turnout Address 107(Base Address 26,Sub Address 2) Turn Output 0 Off.
07:05:07.408: [01 04 05]? Command Successfully Sent/Normal Operations Resumed after timeout
07:05:07.509: [packet: 52 1A 86 CE]? Accessory Decoder Operations Request: Turnout Address 108(Base Address 26,Sub Address 3) Turn Output 0 Off.
07:05:07.543: [01 04 05]? Command Successfully Sent/Normal Operations Resumed after timeout
07:05:07.638: [packet: 52 1B 88 C1]? Accessory Decoder Operations Request: Turnout Address 109(Base Address 27,Sub Address 0) Turn Output 0 On.
07:05:07.795: [42 1B 25 7C]? Feedback Response: Turnout with Feedback Turnout: 109 State: Thrown Left; Turnout: 110 State: Thrown Left
07:05:07.897: [packet: 52 1A 86 CE]? Accessory Decoder Operations Request: Turnout Address 108(Base Address 26,Sub Address 3) Turn Output 0 Off.
07:05:07.918: [01 04 05]? Command Successfully Sent/Normal Operations Resumed after timeout
07:05:08.019: [packet: 52 1A 86 CE]? Accessory Decoder Operations Request: Turnout Address 108(Base Address 26,Sub Address 3) Turn Output 0 Off.
07:05:08.053: [01 04 05]? Command Successfully Sent/Normal Operations Resumed after timeout
07:05:08.154: [packet: 52 1B 80 C9]? Accessory Decoder Operations Request: Turnout Address 109(Base Address 27,Sub Address 0) Turn Output 0 Off.
07:05:08.187: [01 04 05]? Command Successfully Sent/Normal Operations Resumed after timeout
07:05:08.289: [packet: 52 1B 80 C9]? Accessory Decoder Operations Request: Turnout Address 109(Base Address 27,Sub Address 0) Turn Output 0 Off.
07:05:08.525: [01 04 05]? Command Successfully Sent/Normal Operations Resumed after timeout
07:05:08.626: [packet: 52 1B 80 C9]? Accessory Decoder Operations Request: Turnout Address 109(Base Address 27,Sub Address 0) Turn Output 0 Off.
07:05:08.660: [01 04 05]? Command Successfully Sent/Normal Operations Resumed after timeout

Manos,

Ok, here is a few quick clues. First if you do a save in the tables, it
creates a file that is same as if you did Panels->Save Panel, but the tables
only saves the table items. I always use the panels one, most of the time I
end up adding a few graphic things (display panels) and they would not be
saved via the Tables->Save Table.

Next you load either one via the Panels->Open Panel. Also in the
Edit->Preferences->Startup, you have the option of entering an item to load
the file there too. That makes it automatic while JMRI is starting. Here you
add an 'Action' of 'Open File...', then select the file name.

Last is if you make changes, I suggest saving with a different name. Just in
case the old file works better than what you changed. That gives you a
chance to try again. And if you changed the file name, then you have to go
back to the Startup and click on the file name in the name list. That will
give you the option to pick a different file.

Anytime you make any changes in the Preferences, you will have to click the
'Save' to keep those changes.

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

Hi Ken, I did save the parameters but could not find a way to reload from the same menu (tools->tables->turnouts). Reloading was my first thought but I guess this happens from the startup of the program. I am quite new on JMRI but I think now I understand where to look at to resolve the matter.
Thanks again....
Manos SV1IW

Thank you for so much careful testing! Much appreciated.

Let me know if you find any untranslated pieces, please.

Bob

On Aug 6, 2018, at 10:35 AM, alain c via Groups.Io <acarasso_fr@...> wrote:

Hi Bob

I downloaded and tested built #2618 and it looks fine. Here are a few test I've made

Using DP and PP with preferences already set to English
1) Lauching Panel pro using the Profile selector, then selecting my RR, the main menu and all sub menus I've opened are in English so it looks Fine :)

2) Lauching Decoder Pro which starts directly with my profile (no profile selection), it also works fine with menu and sub menus in English.

Modifying the local langage
3) I then switched the local langage to French, restarted Decoder Pro, and Menu and Sub menus were in French as expected

4) I finally reverted to US English, restarted Decoder Pro, and it was in US English as expected.

So AFAIK, it looks fine to me.

--
Bob Jacobsen
rgj1927@...

Manos,

After you name the turnouts, did you save the panel file? Then you'd have to
set the 'Startup' to load that file. That should make the user names hang
around.

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

开云体育

We would like to point out that this list is for discussion of the TECHNICAL
aspects of JMRI, and is intended to be a place that people, particularly
beginners, can turn to for help with their problems from more experienced users.
SPAM of any kind, politics, legal issues, and other off-topic matters should NOT
be posted to the list and will be subject to deletion by the moderators, as will
any responses to such off-topic matters. New members still on moderated
status will find that off-topic posts will not be approved for posting, and old
members making such posts may find themselves back on moderated status.

BUY / SELL and ADVERTISING is NOT PERMITTED

Let's keep things simple for all of us, and keep the discussion here on-topic.

Your moderators
--
Peter Ulvestad

JMRI Users Group Moderator - ( )
Tam Valley Group Moderator - ( )
Sprog-DCC Group Moderator - ( )
Edmonton Model Railroad Association -

Hi all
I have a small N scale basic layout with US locos and trying to find my way in JMRI. When I define turnouts everything works as expected but one thing. The "user name" of the turnouts vanishes after a reboot. I know this is not a serious problem, still annoying at times. I have tried to troubleshoot but can't find something. JMRI is on a rpi version is? 4.12 Rb6a9bb1 and I use DCC++ (Uno+motorshield) as interface. I have stored configuration to file but didn't help. Any ideas / suggestions is much appreciated...
Thank you in advance

Manos SV1IW

Tom:

Off topic except for zen and repairs...

My 10 yo BMW station wagon had both rear window "regulators" die the same day... pop door covering off... easy pull regulator out pie of cake... after market replacement piece of cake...

Oh yes the dumb head light little ring light is out., okay... I have to take the wheels off?

In short repairs... you never know...

Oh yes I didn't expect a rattle just something a little loose... In NCE land there is this extra board that always comes loose... no rattle... just don't work...

Jim Albanowski

Hi Bob

I downloaded and tested built #2618 and it looks fine. Here are a few test I've made

Using DP and PP with preferences already set to English
1) Lauching Panel pro using the Profile selector, then selecting my RR, the main menu and all sub menus I've opened are in English so it looks Fine :)

2) Lauching Decoder Pro which starts directly with my profile (no profile selection), it also works fine with menu and sub menus in English.

Modifying the local langage
3) I then switched the local langage to French, restarted Decoder Pro, and Menu and Sub menus were in French as expected

4) I finally reverted to US English, restarted Decoder Pro, and it was in US English as expected.

So AFAIK, it looks fine to me.

A BIG Thank U Bob

Alain

On Mon, Aug 6, 2018 at 03:07 PM, Paul Bender wrote:

There are a combination of things that can cause this. Let me do some digging and see if I can figure out what needs to change. It might be a decoder definition issue, but I may need to change something in the code.

Paul

Thanks for your time, Paul.
Please note that I have the timeout error also if I write CVs with the "Simple programmer" in POM mode, so I don't think this issue is relate to a specific decoder definition.

On Mon, Aug 6, 2018 at 06:12 PM, Mick Moignard wrote:

Is it possible that when in POM write mode the Z21 is not actually responding to JMRI at all, but just doing the write as requested, no acknowledgement. ?That would trigger a 306, would it not?

I'm not an expert of JMRI/DecoderPro, but this could be an idea.

Moreno


Moreno

Benny,

The “setSingleSegmentRoute" method was added to support new Logix actions.

You “might” be able to get it to work by simulating the NX sensor button clicks.

Since there are a lot of issues with 4.10, I recommend that you use 4.12.


Dave Sand

Is it possible that when in POM write mode the Z21 is not actually responding to JMRI at all, but just doing the write as requested, no acknowledgement. ?That would trigger a 306, would it not?

Mick
______________________________________________________________________
Mick Moignard
Specialising in DCC Sound
p: +44 7774 652504
e: mick@...
skype: mickmoignard
IBM Notes and Domino: still has what it takes as an App Dev and Collaboration platform.

Also, do you have the program starting directly into your desired profile, or do you have it show the profile selector box at start up? I suspect, but haven’t been able to track down, that the profile selector box causes part of the problem here. If you don’t need it, you might get better results by going to Preferences -> Config Profiles and telling it to start up in the selected profile. I’d still like to track down the underlying cause, though.

Bob

On Aug 6, 2018, at 8:25 AM, Bob Jacobsen <rgj1927@...> wrote:

There should be a bit more progress on this in the most recent development build. Installers are here:



Really fixing this is a slow process, because I have to track down individual items that are getting initialized too early. There’s more improvement (since 4.13.1) in DecoderPro than in PanelPro, but both should be a bit better.

Would appreciate it if you could try the most recent changes (build #2618 or later at above link) and let me know of a few examples that are still not right. Easiest for me would be if you could add screenshots to the GitHub issue (), but any kind of pointers would be appreciated.

Thanks.

Bob

On Aug 5, 2018, at 11:30 AM, alain c via Groups.Io <acarasso_fr@...> wrote:

Hi Bob and team

Have you been able to look at the startup menu and found why it's partly using the local Windows language instead of the one selected in the preference menu?

I currently use 4.13.1 and still have the menu partly in French instead of US English or UK English selected in the preference menu.

Thanks.

Alain

--
Bob Jacobsen
rgj1927@...

--
Bob Jacobsen
rgj1927@...