Incorrect locomotive definition

All issues about RailCom
ergunov
Posts: 82
Joined: 03.11.2017, 10:26

Re: Incorrect locomotive definition

Post by ergunov » 09.12.2018, 10:59

rjversluis wrote:
09.12.2018, 09:02
In the monitor of the DigiKeijs software you can see the same behaviour.
Rob, I understand what you're talking about.
Here are two screens of the monitor DR5088
On one with RailCom, on the second without.
Do you have to go missing information about Block?
But after all, in version 13791 everything works as it should.
You do not have the required permissions to view the files attached to this post.

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

Re: Incorrect locomotive definition

Post by rjversluis » 09.12.2018, 11:00

BTW: If reporting with screen shots in the English forum, you should set the Rocview language to English too.

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

Re: Incorrect locomotive definition

Post by rjversluis » 09.12.2018, 11:03

But after all, in version 13791 everything works as it should.
Forget about it.

which firmware are you using in the 5088? Must I really ask every detail separately?

ergunov
Posts: 82
Joined: 03.11.2017, 10:26

Re: Incorrect locomotive definition

Post by ergunov » 09.12.2018, 11:05

rjversluis wrote:
09.12.2018, 11:00
to English too.
I agree

Firmware 1.4.0. installed in the summer.
rjversluis wrote:
09.12.2018, 11:03
Forget about it.
Why if everything in it worked as needed?

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

Re: Incorrect locomotive definition

Post by rjversluis » 09.12.2018, 11:09

Just tested the GL:

Code: Select all

20181209.110744.613 r9999I lnreader OLocoNet 0583 sensor=1001 value=0
20181209.110744.622 r9999a lnreader OModel   5050 trying to match sensor event: [dr5000-ln] 0:1001 uidname=[] state=0 code=
20181209.110744.623 r9999a lnreader OModel   5086 sensor key: 0_1001_dr5000-ln_
20181209.110744.623 r9999a lnreader OModel   5106 unregistered sensor event: [dr5000-ln] 0:1001 uidname=[]
20181209.110746.042 r9999I lnreader OLocoNet 0583 sensor=1001 value=1
20181209.110746.042 r9999a lnreader OModel   5050 trying to match sensor event: [dr5000-ln] 0:1001 uidname=[] state=1 code=
20181209.110746.042 r9999a lnreader OModel   5086 sensor key: 0_1001_dr5000-ln_
20181209.110746.042 r9999a lnreader OModel   5106 unregistered sensor event: [dr5000-ln] 0:1001 uidname=[]
It reports stable occupancy without RailCom.

With a RailCom Loco its also OK:

Code: Select all

20181209.110836.768 r9999c lnreader OLocoNet 0624 MultiSenseLong: detcode=0x0 present=0 block=1001 loco=2408 pol=0 dynid=0 dyndata=0x00
20181209.110836.768 r9999a lnreader OModel   5050 trying to match sensor event: [dr5000-ln] 0:1001 uidname=[] state=0 code=
20181209.110836.769 r9999a lnreader OModel   5086 sensor key: 0_1001_dr5000-ln_
20181209.110836.769 r9999a lnreader OModel   5106 unregistered sensor event: [dr5000-ln] 0:1001 uidname=[]
20181209.110836.841 r9999I lnreader OLocoNet 0583 sensor=1001 value=0
20181209.110836.841 r9999a lnreader OModel   5050 trying to match sensor event: [dr5000-ln] 0:1001 uidname=[] state=0 code=
20181209.110836.841 r9999a lnreader OModel   5086 sensor key: 0_1001_dr5000-ln_
20181209.110836.842 r9999a lnreader OModel   5106 unregistered sensor event: [dr5000-ln] 0:1001 uidname=[]
20181209.110838.056 r9999I lnreader OLocoNet 0583 sensor=1001 value=1
20181209.110838.056 r9999a lnreader OModel   5050 trying to match sensor event: [dr5000-ln] 0:1001 uidname=[] state=1 code=
20181209.110838.056 r9999a lnreader OModel   5086 sensor key: 0_1001_dr5000-ln_
20181209.110838.057 r9999a lnreader OModel   5106 unregistered sensor event: [dr5000-ln] 0:1001 uidname=[]
20181209.110838.373 r9999c lnreader OLocoNet 0624 MultiSenseLong: detcode=0x1 present=1 block=1001 loco=2408 pol=0 dynid=0 dyndata=0x00
20181209.110838.374 r9999a lnreader OModel   5050 trying to match sensor event: [dr5000-ln] 0:1001 uidname=[] state=1 code=2408
20181209.110838.374 r9999a lnreader OModel   5086 sensor key: 0_1001_dr5000-ln_
20181209.110838.374 r9999a lnreader OModel   5106 unregistered sensor event: [dr5000-ln] 0:1001 uidname=[]

So... What is your problem!?

ergunov
Posts: 82
Joined: 03.11.2017, 10:26

Re: Incorrect locomotive definition

Post by ergunov » 09.12.2018, 11:17

Here is the problem
In the log data from the sensor 160 is.
In monitoring, there is also
And on path map, the sensor did not work
You do not have the required permissions to view the files attached to this post.

ergunov
Posts: 82
Joined: 03.11.2017, 10:26

Re: Incorrect locomotive definition

Post by ergunov » 09.12.2018, 11:20

In the German branch, Stefan wrote to you that he tried to test with the Z21detector, decoders without RailCom are also not displayed on the scheme.

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

Re: Incorrect locomotive definition

Post by rjversluis » 09.12.2018, 11:32

are you testing with the loconet or z21 protocol?

ergunov
Posts: 82
Joined: 03.11.2017, 10:26

Re: Incorrect locomotive definition

Post by ergunov » 09.12.2018, 11:36

with Z21 protocol

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

Re: Incorrect locomotive definition

Post by rjversluis » 09.12.2018, 12:03

the standard GL address is 1001.
In Rocrail 1001 with bus 1.
The sensor with address 1:1001 shows in Rocview the correct status.
Do not get your problem...

ergunov
Posts: 82
Joined: 03.11.2017, 10:26

Re: Incorrect locomotive definition

Post by ergunov » 09.12.2018, 12:29

Here is a picture, with a big arrow and "NO" the sensor on the map is highlighted, it is free.
although judging by the server log and monitoring the sensors should be busy.

upd
sorry circled the wrong sensor
You do not have the required permissions to view the files attached to this post.
Last edited by ergunov on 09.12.2018, 12:35, edited 1 time in total.

ergunov
Posts: 82
Joined: 03.11.2017, 10:26

Re: Incorrect locomotive definition

Post by ergunov » 09.12.2018, 12:31

This is what should be on the map.
You do not have the required permissions to view the files attached to this post.

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

Re: Incorrect locomotive definition

Post by rjversluis » 09.12.2018, 13:15

check 14666.

vikr
Posts: 582
Joined: 20.05.2012, 09:53

Re: Incorrect locomotive definition

Post by vikr » 09.12.2018, 13:29

Hallo Rob, hallo Vyacheslav,

mochte Euch meinen Respekt zollen, mit welcher Geduld und Beharrlichkeit ihr versucht das Problem einzukreisen.
Dies ist der Grund warum ich Rocrail und dieses Forum so überaus hochschätze! :D

MfG

vik :beer:

ergunov
Posts: 82
Joined: 03.11.2017, 10:26

Re: Incorrect locomotive definition

Post by ergunov » 09.12.2018, 16:29

Rob, I updated to 14661, it all works as before.

Post Reply

Return to “RailCom”