Communication error - Lost messages

Uhlenbrock new generation CS-Line

Communication error - Lost messages

Postby fbpetersen » 18.08.2014, 18:45

Hi All
The documentation says that the Intellibox II sends some undocumented messages on the loconet. I think that I am hit by just that!

My setup is a 4.5 m2 H0 layout using Märklin M-track controlled by an Intellibox II.I use 2 viessmann 5233 and a 5217 S88 sensors connected through an Uhlenbrock 63880.

It works as expected, except that a single sensor message disappeared one in a while causing the trains to stop. Ether is it an ‘occupied’ message, causing a ghost train detect, or a missing ‘free’ message causing on free block.
As I see it, there is an ‘undocumented message: start=0x93’ at the time where the sensor message is missing.

Is there anyone that has an idea on how to fix this problem?

Best Regards
Finn
Märklin M-track, Uhlenbrock Intellibox II, DCC, Loconet
fbpetersen
 

Re: Communication error - Lost messages

Postby rjversluis » 19.08.2014, 09:01

Hi Finn,

it does not bother those undocumented LocoNet opcodes. (None LocoNet Personal Edition)
I guess you should swap the S88 unit to see if the problem moves to another address.
Best Regards, Rob.
:!: PS: Do not forget to attach the usual files.
:!: PS: Nicht vergessen die übliche Dateien an zu hängen.
[ macOS - Linux] - [ N: CBus - CAN-GCA ] - [ 0: RocNetNode - GCA-Pi ]
rjversluis
Site Admin
 

Re: Communication error - Lost messages

Postby fbpetersen » 19.08.2014, 20:35

Hi Rob

I haven't tried that, it not that easy, but anyway I see this error on different sensor addresses. May be, they are all on the same 5233. I have to test that.
Also when I look of the sensor status on the Intellibox, the status is correct.
I have also tried to log the LocoNet messages using Digitrax's DigiMon, both as loconet data, and raw data, and as far I can see (count) no messages is missing.
Is it in any way possible to log what rocrail is receiving?
I had a short look into the source code, and find something that looks like a trace statement. Is there some traces that can be enabled without re-compiling the code?

Best Regards
Finn
Märklin M-track, Uhlenbrock Intellibox II, DCC, Loconet
fbpetersen
 

Re: Communication error - Lost messages

Postby fbpetersen » 26.08.2014, 19:27

Hi All

I got closer to the problem with the lost sensor messages. I found the trace files, and how to change the trace level. The result of this is: I see 4 different non loconet messages each 3 byte long from the Intellibox:
32 00 E0, 32 00 F0, 93 00 00 and 93 00 80.
The two first result in 2 byte of garbage and an undocumented message.
The third one result in an undocumented message and 2 byte of garbage. Ether of this gives any problem,
but the last one does. The first byte gives an undocumented message followed by a one byte garbage, then the following byte (80) is interpreted as a start of a new 2 byte message eating the first byte of the next real loconet message. This results in 3 bytes of garbage.

From the trace file I see this sequence: 93 00 80 B2 0D 72 32. . The sequence is interpreted as:

93 - Undocumented message
00 – 1 byte of garbage
80 B2 – Loconet message, but the checksum check fails.
0D 72 32 – 3 bytes of garbage.

The B2 0D 72 32 is the sensor message there is lost.

Is this the right place to put this type of information, or is there a better place (Software, or other)

Best Regards
Finn
You do not have the required permissions to view the files attached to this post.
Märklin M-track, Uhlenbrock Intellibox II, DCC, Loconet
fbpetersen
 

Re: Communication error - Lost messages

Postby rjversluis » 27.08.2014, 06:12

Hi Finn,

you must use a current revision of Rocrail before reporting an issue; Update and test again.
http://rocrail.net/software/rocrail-snapshot/
https://launchpad.net/rocrail/+download

Forumsregeln
1) Read the Wiki first: http://wiki.rocrail.net
2) Vote for your Command Station(s).
3) Make sure that the subject used for your posting covers the content.
4) Update Rocrail first before reporting a problem!
5) If you are asking for support for Rocrail functionality, auto mode, switches, signals ... you have to post your rocrail.ini plan file and the trace file.
6) To view new English posts only use this URL: "http://forum.rocrail.net/search.php?search_id=newposts&fid[]=95"
7) The Avatar picture should show yourself, in all other cases: Leave the Avatar empty.
Best Regards, Rob.
:!: PS: Do not forget to attach the usual files.
:!: PS: Nicht vergessen die übliche Dateien an zu hängen.
[ macOS - Linux] - [ N: CBus - CAN-GCA ] - [ 0: RocNetNode - GCA-Pi ]
rjversluis
Site Admin
 

Re: Communication error - Lost messages

Postby fbpetersen » 27.08.2014, 16:32

Now I have tried with todays build (7843) and the problem is still the same.

BR.
Finn
You do not have the required permissions to view the files attached to this post.
Märklin M-track, Uhlenbrock Intellibox II, DCC, Loconet
fbpetersen
 

Re: Communication error - Lost messages

Postby rjversluis » 27.08.2014, 17:17

Hi Finn,

just test revision 7846 and report.
Best Regards, Rob.
:!: PS: Do not forget to attach the usual files.
:!: PS: Nicht vergessen die übliche Dateien an zu hängen.
[ macOS - Linux] - [ N: CBus - CAN-GCA ] - [ 0: RocNetNode - GCA-Pi ]
rjversluis
Site Admin
 

Re: Communication error - Lost messages

Postby fbpetersen » 27.08.2014, 17:53

Hi Rob

I will do that. Have just looked at your code commit. :mrgreen:

Thanks
Finn
Märklin M-track, Uhlenbrock Intellibox II, DCC, Loconet
fbpetersen
 

Re: Communication error - Lost messages

Postby fbpetersen » 28.08.2014, 20:31

Hi Rob

I have now used the evening with version 7849 and it works very well. :thumb_up:
Until now no missed sensor events.

Thanks again
Finn
Märklin M-track, Uhlenbrock Intellibox II, DCC, Loconet
fbpetersen
 

Re: Communication error - Lost messages

Postby fbpetersen » 10.09.2014, 19:37

Hi

I have had now got the time to run some more with the train. It still works much better than before.
But now, when the layout can run more than a few minutes I see new groups of 3 bytes from the Intellibox II causing problems.
This time after almost an hour. Until now I have detected 16 different groups, including the bytes A0, B0 and C0. witch is not good.
It could of cause be some sort of communication error, but I think that it is a little to nice.

The trace file shows, at I read it, a received block ( 30 00 C0) that cause a decoding error of the two following messages:
30 00 - 2 bytes of garbage
C0 B0 03 30 7C B2 - this isn't a correct LocoNet message
03 62 2C - 3 bytes of garbage.

Hilsen
Finn
You do not have the required permissions to view the files attached to this post.
Märklin M-track, Uhlenbrock Intellibox II, DCC, Loconet
fbpetersen
 

Re: Communication error - Lost messages

Postby rjversluis » 15.09.2014, 07:52

Hi Finn,

the trace does not show the invalid LocoNet Packets.
C0 has the MSB set so its a start of a LocoNet packet.
This Opcode is not part of the LocoNet PE.
Best Regards, Rob.
:!: PS: Do not forget to attach the usual files.
:!: PS: Nicht vergessen die übliche Dateien an zu hängen.
[ macOS - Linux] - [ N: CBus - CAN-GCA ] - [ 0: RocNetNode - GCA-Pi ]
rjversluis
Site Admin
 

Re: Communication error - Lost messages

Postby fbpetersen » 15.09.2014, 18:53

Hi Rob

This is exactly the problem. C0 is a valid LocoNet op-code, as is A0 and B0, but:
C0 B0 03 30 7C B2 is not a valid LocoNet message! None of the data byte can have the MSB set, and therefore ether the check-sum, and on top of that, the check-sum is not correct. the calculation for the message gives 8D and not FF.
If the byte sequence is evaluated as:

30 00 C0 - Unknown Intellibox message
B0 03 30 7C - Set switch 3 to close - check-sun OK
B2 03 62 2C - Sensor addr. 518 Free - check-sum OK

Both of this LocoNet message make sense.
Therefore it is my perception that the C0 is part of the Unknown Intellibox message, and not part of a LocoNet message.
Of curse this byte value as long as A0 and B0 can not be filtered in a simple way as with the other Intellibox messages that I have been seen.

Best Regards
Finn
Märklin M-track, Uhlenbrock Intellibox II, DCC, Loconet
fbpetersen
 

Re: Communication error - Lost messages

Postby rjversluis » 15.09.2014, 19:27

Hi Finn,

I just expanded the filter with C0.
Best Regards, Rob.
:!: PS: Do not forget to attach the usual files.
:!: PS: Nicht vergessen die übliche Dateien an zu hängen.
[ macOS - Linux] - [ N: CBus - CAN-GCA ] - [ 0: RocNetNode - GCA-Pi ]
rjversluis
Site Admin
 

Re: Communication error - Lost messages

Postby fbpetersen » 15.09.2014, 20:17

Hi Rob

It will not do it. I have also see both A0 and B0 in the the Intellibox message, and you can't filter those!
As long as I am the only one having this problems, I think that you should do nothing.
I will try to set up the build environment and build RocRail myself. I have some ideas on how to interpret the byte stream using the knowledge of a valid LocoNet message.
Then, when I got it to work, we can continue the discussion.

Best Regards
Finn

PS. If anyone else sees similar problems, let me know.
Märklin M-track, Uhlenbrock Intellibox II, DCC, Loconet
fbpetersen
 

Re: Communication error - Lost messages

Postby fbpetersen » 06.12.2014, 15:28

Hi Rob

Now I have made some changes to how the Locnet messages are decoded.
Instead of filtering what isn't Loconet messages, I filter on what is or could be Loconet messages. This way i should be possible to decode all loconet messages correct regardless of what combinations of bytes the Intellibox put in between the messages.
It works very well for me.

Only the __reader( void* threadinst ) method has been changed.

Best Regards
Finn
You do not have the required permissions to view the files attached to this post.
Märklin M-track, Uhlenbrock Intellibox II, DCC, Loconet
fbpetersen
 

Next

Return to IB-Basic IB-Com IB2