(solved) Unexpected IN event

cds
Moderator
Posts: 5160
Joined: 03.02.2012, 19:24
Location: Tullnerbach, Austria

Re: Unexpected IN event

Post by cds » 03.02.2018, 14:07

Hi Tom!
Any idea why that has anything to do with the sensor reading the wrong value?
Sorry, no.

rjversluis
Site Admin
Posts: 41593
Joined: 10.04.2006, 08:48
Location: Speyer, Germany
Contact:

Re: Unexpected IN event

Post by rjversluis » 03.02.2018, 14:11

Hi Tom,
smitt48 wrote: Thanks for your help, I wonder if Rob has an answer for this.
can you compress this issue down with a small example?
I know its extra work 4you, but my time cannot be extended to 48h/d. 8)

smitt48
Moderator
Posts: 5966
Joined: 04.04.2014, 01:07
Location: Kralendijk, Bonaire - Dutch Caribbean

Re: Unexpected IN event

Post by smitt48 » 03.02.2018, 15:38

Hi Rob,

No problem, I hope it is small enough! :roll:
Error still appears, as Claus noted it disappears when removing checkmark by Reserve second next block.

In automode start loc in block B15, block B12 and B1D are reserved, click on sensor F1A (ENTER of block B12) and sensor is read as an IN, resulting in a ghost.

Thanks for your help, Tom
Attachments
rocview.002.trc
(41.44 KiB) Downloaded 1 time
Plan.zip
(17.87 KiB) Downloaded 2 times

hermannk
Moderator
Posts: 1025
Joined: 06.07.2014, 12:32
Location: Kiel Germany

Re: Unexpected IN event

Post by hermannk » 03.02.2018, 22:54

Hi Tom, hi Rob,
some additional hints:
a) if you delete the blockgroup "BG01" the ghost is gone;
b) as Claus pointed out: if you disable "Reserve second next block" the ghost is gone.
c) although we have 4 blocks, is it a carousel if we use this blockgroup or "Reserve second next block"??? I don't know.
Rocrail 13449
macOS 10.12.6
your Rocrail plan file from 03.02.2018, 13:54
Regards
Hermann

smitt48
Moderator
Posts: 5966
Joined: 04.04.2014, 01:07
Location: Kralendijk, Bonaire - Dutch Caribbean

Re: Unexpected IN event

Post by smitt48 » 04.02.2018, 00:43

Hi Hermann,

Gould be! The blockgroup is only one Block. Without the blockgroup, you would get a deadlock everytime.
I even thought about splitting up block B15 into two blocks (enter2in) and only using them together as a virtual block (enter/in).
But the fact remains that a sensor defined as ENTER is reported as an IN. That should never be! Without that error it would work.

Tom
Last edited by smitt48 on 04.02.2018, 10:07, edited 1 time in total.

rjversluis
Site Admin
Posts: 41593
Joined: 10.04.2006, 08:48
Location: Speyer, Germany
Contact:

Re: Unexpected IN event

Post by rjversluis » 04.02.2018, 08:15

Hi,

this trace snippet shows that the loco coming is not known where it comes from...

Code: Select all

20180203.102544.626 r9999a BR 221 ( OBlock   2722 block [B1D] group locked for [BR 221 (B&C)]
20180203.102544.626 r9999I BR 221 ( OBlockGr 0256 remove all prereservations in blockgroup BG01
20180203.102544.626 r9999I BR 221 ( OBlockGr 0135 checking blockgroup BG01 condition first/from [B1D] for loco [BR 221 (B&C)] from [B1D] enterside cond=2 loco=1
20180203.102544.626 r9999I BR 221 ( OBlockGr 0135 checking blockgroup BG01 condition first/from [B1D] for loco [BR 221 (B&C)] from [B1D] enterside cond=1 loco=1
20180203.102544.626 r9999a BR 221 ( OBlock   2484 block [B12] already locked for loco [BR 221 (B&C)] routeid=?
20180203.102544.626 r9999a BR 221 ( OBlock   2635 block B12 locked for [BR 221 (B&C)][BR 221 (B&C)][(null)] in [normal] direction, indelay=0



20180203.102554.066 r9999a 00002450 OBlock   0678 Block [B12] no event found for fromBlockId [?], try to find one for all with key [F1A-all-reverse]...
20180203.102554.066 r9999a 00002450 OBlock   0702 Block[B12] id=F1A fbid=F1A-all-reverse state=true code=[] fbfrom=all-reverse fbaction=in from=? byroute=? loco=BR 221 (B&C)

rjversluis
Site Admin
Posts: 41593
Joined: 10.04.2006, 08:48
Location: Speyer, Germany
Contact:

Re: Unexpected IN event

Post by rjversluis » 04.02.2018, 08:44

Hi Tom,

I just made a fix for this issue.

smitt48
Moderator
Posts: 5966
Joined: 04.04.2014, 01:07
Location: Kralendijk, Bonaire - Dutch Caribbean

Re: Unexpected IN event

Post by smitt48 » 04.02.2018, 10:04

Hi Rob,

Thanks!
13493 2018-02-04 09:13:27 +0100 blockgroup: only lock a reserve block if its not already locked
13492 2018-02-04 08:43:31 +0100 block: do not save the from block ID in case its not set (Lock by block group)
I used version 13493, I assume that is the final fix.
My test plan works with this version with vcs. It is only 5 0'clock so the test on the actual layout will have to wait!

Tom

smitt48
Moderator
Posts: 5966
Joined: 04.04.2014, 01:07
Location: Kralendijk, Bonaire - Dutch Caribbean

Re: Unexpected IN event

Post by smitt48 » 04.02.2018, 14:48

Hi Rob,

Tested for about 2 hours. All seems well! :thumb_up: I will set this post to solved.
However when I started I noticed that Loc Swiss (in B15) reserved 2 parallel blocks (B12 & B18). Did not seem to hurt, loc took the block with the green signal (B18) and the second time through it took the other block (B12). After that I did not notice it again, maybe because one of these blocks was already occupied. If you want me to, I can see if I can capture it.
double block.PNG
Tom

cds
Moderator
Posts: 5160
Joined: 03.02.2012, 19:24
Location: Tullnerbach, Austria

Re: (solved) Unexpected IN event

Post by cds » 04.02.2018, 15:29

Hello Tom!

I've noticed this behaviour during my tests as well.

rjversluis
Site Admin
Posts: 41593
Joined: 10.04.2006, 08:48
Location: Speyer, Germany
Contact:

Re: (solved) Unexpected IN event

Post by rjversluis » 04.02.2018, 15:34

Hi,

how to reproduce? Which Plan file?

smitt48
Moderator
Posts: 5966
Joined: 04.04.2014, 01:07
Location: Kralendijk, Bonaire - Dutch Caribbean

Re: (solved) Unexpected IN event

Post by smitt48 » 04.02.2018, 15:46

Hi Rob,

I will try to reproduce it. If I can I will create another issue.
The plan used is attached to the first post:
Block B16 closed to force the train (here Swiss) to go from block B15 to either B12 or B18.

Tom

Post Reply

Return to “General”