Page 1 of 1

Wiki Demo question

Posted: 19.04.2019, 13:25
by smitt48
Hi Rob,

Here is a modified Demo plan, the modification is that in Block 02, I changed a sensor to ENTER2IN and ignored the second sensor.
I am confused about the trace file.
20190419.080324.728 r9999a E03 OBlock 0818 Block[04] id=enter state=true code=[-] fbfrom= fbaction=enter2in from=02 byroute=[02+]-[04-] loco=E03
20190419.080324.728 r9999a E03 OBlock 0499 event [enter2in] in block [04]
20190419.080324.728 r9999a E03 OBlock 0890 loco [E03] found
20190419.080324.728 r9999a E03 OBlock 0499 event [enter2in] in block [04]

20190419.080329.872 r9999a E03 OBlock 0818 Block[02] id=enter state=true code=[-] fbfrom= fbaction=enter2in from=01 byroute=[01+]-[02-] loco=E03
20190419.080329.872 r9999a E03 OBlock 0499 event [enter2in] in block [02]
20190419.080329.883 r9999a E03 OBlock 0890 loco [E03] found
20190419.080329.883 r9999a E03 OBlock 0499 event [enter2in] in block [02]
The loc starts in Block 02 and goes to block 04, then 01 and stops in 02, why does the ENTER2IN event references block 04. I would expect that an ENTER2IN reference should only occur in block 02.

Thanks Tom

Re: Wiki Demo question

Posted: 19.04.2019, 17:12
by cds
Hello Tom,

probably I've noticed a configuratio mistake in block 02 for route "all enter -": you've set the timer no. 2 to "5000" but you did not mark "T2" for event "ENTER2IN" for sensor "fb2a".

Re: Wiki Demo question

Posted: 19.04.2019, 17:58
by smitt48
Hi Claus,

It is not a mistake! :D
Rob does not like timers, so I only send the trace with no timers active.
I wanted to test the T2 timer for a French user, who said it does not work.
So I wanted to run, with the timer and without the timer, during the "without" test I noted that the "enter2in" was in multiple blocks, eventhough I only added it to one block.

By the way with T2 checked/not checked; enter2in is marked in every block.
Tom

Re: Wiki Demo question

Posted: 20.04.2019, 10:04
by rjversluis
Hi Tom,

I cannot reproduce your issue.

Re: Wiki Demo question

Posted: 20.04.2019, 13:11
by smitt48
Hi Rob,
I cannot reproduce your issue.
What does that mean? Did you run and your trace did not show that "enter2in" is noted in each block?
I noted the trc file was not downloaded, if you look at it and search on "enter2in" you will see it shows 9 entries, 3 for each block
20190419.080329.872 r9999a E03 OBlock 0818 Block[02] id=enter state=true code=[-] fbfrom= fbaction=enter2in from=01 byroute=[01+]-[02-] loco=E03
20190419.080329.872 r9999a E03 OBlock 0499 event [enter2in] in block [02]
20190419.080329.883 r9999a E03 OBlock 0890 loco [E03] found
20190419.080329.883 r9999a E03 OBlock 0499 event [enter2in] in block [02]
This is the only good entry in the trace, the other entries are bogus. It is difficult to explain issues to people if you can not rely on the data in the trace files.

Bogus entries:
20190419.080324.728 r9999a E03 OBlock 0818 Block[04] id=enter state=true code=[-] fbfrom= fbaction=enter2in from=02 byroute=[02+]-[04-] loco=E03
20190419.080324.728 r9999a E03 OBlock 0499 event [enter2in] in block [04]
20190419.080324.728 r9999a E03 OBlock 0890 loco [E03] found
20190419.080324.728 r9999a E03 OBlock 0499 event [enter2in] in block [04]

20190419.080327.274 r9999a E03 OBlock 0818 Block[01] id=enter state=true code=[-] fbfrom= fbaction=enter2in from=04 byroute=[04+]-[01-] loco=E03
20190419.080327.274 r9999a E03 OBlock 0499 event [enter2in] in block [01]
20190419.080327.290 r9999a E03 OBlock 0890 loco [E03] found
20190419.080327.290 r9999a E03 OBlock 0499 event [enter2in] in block [01]

Re: Wiki Demo question

Posted: 20.04.2019, 13:23
by rjversluis
Hi Tom,
What does that mean? Did you run and your trace did not show that "enter2in" is noted in each block?
Thats what I meant.

Re: Wiki Demo question

Posted: 20.04.2019, 13:40
by rjversluis
Hi Tom,

I let the loco run two times this oval:

Code: Select all

MBA2019:forum2 robversluis$ grep "enter2in" *.trc
20190420.143905.371 r9999a tid0xE56 OBlock   0818 Block[02] id=fb2a state=true code=[] fbfrom=all-reverse fbaction=enter2in from=01 byroute=[01+]-[02-] loco=E03
20190420.143905.371 r9999a tid0xE56 OBlock   0499 event [enter2in] in block [02]
20190420.143905.371 r9999a tid0xE56 OBlock   0499 event [enter2in] in block [02]
20190420.143944.180 r9999a tid0xE56 OBlock   0818 Block[02] id=fb2a state=true code=[] fbfrom=all-reverse fbaction=enter2in from=01 byroute=[01+]-[02-] loco=E03
20190420.143944.180 r9999a tid0xE56 OBlock   0499 event [enter2in] in block [02]
20190420.143944.181 r9999a tid0xE56 OBlock   0499 event [enter2in] in block [02]

Re: Wiki Demo question

Posted: 20.04.2019, 13:52
by smitt48
Hi Rob.

Thanks, still don't understand why I get "enter2in" on all blocks!

Tom

Re: Wiki Demo question

Posted: 20.04.2019, 13:58
by rjversluis
Hi Tom,

maybe you are locally testing with another plan.xml?

Re: Wiki Demo question

Posted: 20.04.2019, 14:08
by smitt48
Hi Rob,

Here is today's test (this time virtuel automatic). I ran it twice and I get 18 "enter2in" entries.

Tom

Re: Wiki Demo question

Posted: 20.04.2019, 14:12
by rjversluis
Hi Tom,

same result with the new plan.xml:

Code: Select all

MBA2019:forum2 robversluis$ grep "enter2in" *.trc
20190420.151038.345 r9999a tid0x78E OBlock   0818 Block[02] id=fb2a state=true code=[] fbfrom=all-reverse fbaction=enter2in from=01 byroute=[01+]-[02-] loco=E03
20190420.151038.345 r9999a tid0x78E OBlock   0499 event [enter2in] in block [02]
20190420.151038.345 r9999a tid0x78E OBlock   0499 event [enter2in] in block [02]
20190420.151118.100 r9999a tid0x78E OBlock   0818 Block[02] id=fb2a state=true code=[] fbfrom=all-reverse fbaction=enter2in from=01 byroute=[01+]-[02-] loco=E03
20190420.151118.100 r9999a tid0x78E OBlock   0499 event [enter2in] in block [02]
20190420.151118.100 r9999a tid0x78E OBlock   0499 event [enter2in] in block [02]

Re: Wiki Demo question

Posted: 20.04.2019, 14:33
by rjversluis
Hi Tom,
Here is today's test (this time virtuel automatic).
if you let run the loco in virtual automatic mode, the real sensors are not used, but enter2in is generated for every block.
Should be documented in the Wiki.
https://wiki.rocrail.net/doku.php?id=vi ... tomatic-en
The virtual mode only needs the virtual command station and will generate an enter2in for the block expecting this train. The defined block sensors are ignored inclusive the linked actions.

Re: Wiki Demo question

Posted: 20.04.2019, 15:02
by smitt48
Hi Rob,
but enter2in is generated for every block.
Good to know :o
That is why it sometimes was OK and sometimes not!
I updated the wiki.

Thanks Tom

Re: Wiki Demo question

Posted: 20.04.2019, 15:14
by rjversluis
Hi Tom,

it was already documented:
https://wiki.rocrail.net/doku.php?id=vi ... en#virtual
:|

Re: Wiki Demo question

Posted: 20.04.2019, 15:38
by smitt48
Hi Rob,

Now it is documented twice. :mrgreen:
The Virtual Automatic Mode is NOT usable for testing functionality but only for checking the train flow.
The Virtual Automatic Mode is NOT suited for continuous operation.
The Virtual Automatic Mode is NOT supported in the Forum.
The Virtual Automatic Mode generates "enter2in" for each sensor, the actual sensors are not evaluated.
Tom