开云体育

JMRI: ?5.8+

Command Station: DCC++ Version 5.0.7

Host; MacBook Pro Sonoma 14.6.0

?

I have created my layout in the layout editor. It has six Kato turnouts (defined in DCC++ and exported to JMRI).

When I click on the turnout circle on the layout panel, the turnout works but the display on the layout panel momentarily shows correct state and then goes back to open (i.e no lines connected to either main track or throw track).?

?

Why does it happen this way? What should I need to debug this?

?

--

+==========
|. Vimal

+==========

The turnout image indicates that the turnout has an inconsistent state. ?You can verify this by looking at the turnout table with the "Show Feedback information" option enabled. ?If that is the case, what is the feedback mode?

Dave Sand

The feedback mode has to be BSTURNOUT since it is defined in DCC++ using VIRTUAL_TURNOUT macro.?

the other fields in the feedback form are all set to default values.?

out of 6 turnouts, 3 are showing correct state but others are showing inconsistent state.?

I am not able to figure out why it would show this.?

the DCC monitor log shows the commas station sending back the <H ..> reply for each Close/Throw command

?

?

--

+==========
|. Vimal

+==========

Regards,

?

Ash__?

I tried what Ash suggested. ?Here are the results:

?

After I sent the 'T' command to DCC, all turnouts on the layout panel showed current status.?

But as soon as I clicked on one of the 'bad' one, it went back to inconsistent state.?

I captured the DCC traffic when toggling a good and a bad turnout. Here is the difference in DCC traffic between the two:

?

Good

10:22:09.466: TX: Turnout Cmd: ID: 204, State: THROWN

10:22:09.469:? RX: DIAG: Turnout(204,t)?

10:22:09.470:? RX: Turnout Reply: ID: 204, Dir: THROWN

10:22:09.570:? RX: DIAG: EXRAIL(0) Turnout Throw204?

?

Bad

0:22:42.021: TX: Turnout Cmd: ID: 200, State: CLOSED

10:22:42.021:? RX: DIAG: Turnout(200,c)?

10:22:42.022:? RX: Turnout Reply: ID: 200, Dir: CLOSED

10:22:42.025:? RX: DIAG: EXRAIL(0) Turnout Close200?

10:22:42.223: TX: Turnout Cmd: ID: 200, State: CLOSED

10:22:42.229:? RX: DIAG: Turnout(200,c)?

10:22:42.232: TX: Turnout Cmd: ID: 200, State: CLOSED

10:22:42.232:? RX: DIAG: EXRAIL(0) Turnout Close200?

10:22:42.234:? RX: DIAG: Turnout(200,c)?

10:22:42.238:? RX: DIAG: Recursive ONCLOSE(200)?

?

?

?

--

I am not sure why the traffic is different between the two turnouts.?

Here is the turnout table defined in JMRI:

?

Here is the feedback pane of TL0 (which is inconsistent one):

?

I have also added an AUTOSTART sequence in DCC++ to set all turnout to known state (i.e CLOSE) at DCC startup.

Any ideas what is going on here?

?

+==========
|. Vimal

+==========

J. Vimal,
I tried to duplicate the issue, but have not found where layout panel was different than turnout tables.

?

I have not seen this previously.

RX: DIAG: Recursive ONCLOSE(200)??

?

What is different for 200 vs 204?

Do you have logic which is reliant on turnout 200?

You showed the feedback pane -- what do you see in the usage tab?

?

There is also information provided if you click the Delete button on the Turnouts table

.. you can answer NO.

?

You may decide you want to delete the record and then save - store panels, etc.

The next time you start JMRI, the record will be added in the Turnouts table.
You will load panels, and add back Turnout 200.? Then save.

?

?

Ash__

?

?

OK, I found out that the Signal Heads that I had added were interfering with the turnout logic.

Only for first 3 turnouts were connected with the signal heads and hence they were showing inconsistent state.

Not sure why it would do that but once I removed all signal heads and masts, the turnout started showing consistent state.

?

I will have to revisit the signal heads and figure out what I did wrong in setting them

?

--

+==========
|. Vimal

+==========