New issue

[fire-bot]

Sent by (j.barkowsky@web.de). Created by fire.

---

Hi there,

I upgraded my Arduino Mega from DCC++ to DCC_EX 4.1.2 and am discovering some peculiar behavior. I can enter a turnout with <T 1 DCC 1 0>, when I check on in with , I get

<H 1 DCC 1 0 1>

<H 1 1 0 1>.

Deleting with won’t work. I have to delete with <T 1>. All that is not in accordance with your documentation.

I am using JMRI 5.2 on Linux Mint. Scripts involving the command

turnouts.provideTurnout("1").setState(CLOSED)

aren’t executed any more. That is a real issue for me.

I tried discord, as you seem to prefer that platform, but their interface is confusing and full of pop-ups.

Regards,

JohnJ

[Ash-4]

You may need to provide further detail on where the documentation does not agree with what you are seeing. It appears to be working as defined. https://dcc-ex.com/reference/software/command-reference.html#defining-setting-up-a-turnout

When you see two returns from a command, one of them is retained for legacy compatibility.

Suggest using JMRI DCC++ Traffic Monitor with 'show raw data' box checked. Perhaps you will see if your jython scripting is failing to send the expected commands, etc.

While the discord server has some annoyances, it has proven to be a very useful discussion platform. Try the topic # JMRI

Some JMRI users have had issues when they do not have Java 11 installed.

[habazut]

You may want to try the latest tagged devel version.

https://github.com/DCC-EX/CommandStation-EX/tree/v4.2.6-Devel

Let us know what the raw data is like Ash suggested

Give Discord another try, I don't see popups but at first login but I might have a general popup block active.

Regards, Harald.

PS:

$ cat /etc/issue
Linux Mint 20 Ulyana

[jb60]

Ash-4:

Fred Decker pointed out to me, that

[e] erases everything from EEPROM but not from the CS, so I would have to reboot the CS to lose them too. Opening a serial monitor resets the CS. (Pointed brackets won't show here.)

That helps me understand better, what goes on. Your "legacy compatibility" hint is another answer. I will be looking at the raw data. Thank you, Harald, too.

John

[jb60]

Harald:

The raw data didn't show anything in response to the script command

turnouts.provideTurnout("1").setState(CLOSED)

I found, that I had to address my turnout 1 as DT1, the turnout system name:

turnouts.provideTurnout("DT1").setState(CLOSED)

The JMRI example scripts don't have the DT. I rewrote all my turnout scripts accordingly.

Thank you all for your help. I don't know how to close the issue, but all my questions have been answered.

John

[habazut]

Ok, this was more a JMRI documentation issue then. Good that you solved the problem. I will close. Harald.