Zimo MX10 with ROCO 10808 via Canbus is running crooked.

[Rupert van Swol]

Dear Forum,
I am still learning how to use the Zimo MX10, StEin 88V and the Roco Z21 detector 10808, which is equipped with a Roco@CAN bus.

I understand from Vienna that the Roco CAN bus works on the CAN bus of the Zimo MX10.
I have managed to assign a main address to the Roco detector, in this case Address 8. The Roco 10808 also has 8 local railcom message receivers.

Sie dürfen diesen Dateianhang nicht ansehen.

In WinDigipet 2025 , the output 8.3 of the Roco detector 10808 is assigned to WDP detector 57.
In the track plan, detector 57 therefore functions correctly on the occupied status of the RoCo 10808.  See data log.

What does not work is the Railcom message.
At first, I thought that this Railcom was not working.
But the data log shows that the Railcom message was received at a different address than the expected address of 8.3

Sie dürfen diesen Dateianhang nicht ansehen.
 
The log clearly shows what happens when Detector 57 changes from Free to Occupied.  The current status detection  from  the locomotive comes in via the Roco@Can at address 8.3.  The Railcom messages from the loco decoder with DCC address 22 have a different route and  also a different address, and is send tot 7.31 instead of 8.3.
 
However, if I set the address for Train Recognition to 7.3 in IFAZ no. 57, the Railcom messages do arrive, but the current detection remains inactive.
The data log shows Roco@Can Address 8: Connection 3 occupied.

Sie dürfen diesen Dateianhang nicht ansehen.

I'm not sure if this is related to the recent firmware release from Zimo. I wanted to report it here first.
Best regards,
Rupert

[Markus Herzog]

Hello Rupert,

I recognized a change in numbering with the Roco 10808 some weeks ago (I can not see when this changed maybe related with a firmware update) and I changed something code for the next update (offset of 1).

But at the moment this shouldn´t even be problem because you can select the detection module number/input number from the occupation module number/input number,
First configure the occupation message that it works.
Then only got to the detection configuration for the vehicle number display and enter there a module number +1 or -1 (not sure without testing it) at the moment.

Regards
Markus