Determination of the direction of motion of the locomotive

All issues about RailCom

Determination of the direction of motion of the locomotive

Postby ergunov » 02.07.2018, 09:08

Hi Rob
So, briefly about the essence of the matter. DR5088 allows you to determine the direction of motion of the locomotive. For what in the module there is a correction to the address of the block or locomotive. Data on the direction of movement is added to their addresses. Karst promised to soon prepare an expanded guide, where everything will be detailed.
Is it possible at the moment to implement the correct address determination with active correction, with correction to the addresses is added Block is +2048 loco is + 4096
Vyacheslav E.
ergunov
 

Re: Determination of the direction of motion of the locomoti

Postby rjversluis » 02.07.2018, 09:35

Hi,

I do not know what you mean with block address.
In Rocrail blocks do not have a RailCom 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 - CANGCx ] - [ G: CBUS - CANGCx ]
rjversluis
Site Admin
 

Re: Determination of the direction of motion of the locomoti

Postby ergunov » 02.07.2018, 10:19

I'm talking about the module's login address, today or tomorrow I'll do a log with an activated correction, so it will be clearer.
Vyacheslav E.
ergunov
 

Re: Determination of the direction of motion of the locomoti

Postby ergunov » 03.07.2018, 18:13

Hi Rob
Here is an example of a correction for a locomotive.
To the address of the locomotive was added 4096, Instead of 212 it was defined as 4308, but responds to commands as 212.
You do not have the required permissions to view the files attached to this post.
Vyacheslav E.
ergunov
 

Re: Determination of the direction of motion of the locomoti

Postby rjversluis » 04.07.2018, 06:31

Hi,

still do not know what you want. -o
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 - CANGCx ] - [ G: CBUS - CANGCx ]
rjversluis
Site Admin
 

Re: Determination of the direction of motion of the locomoti

Postby ergunov » 04.07.2018, 18:27

rjversluis wrote:still do not know what you want.

Rob I do not argue,
without the information that there is in an additional package, doing something is impossible.
But so far in theory, can you make such a correction?
Vyacheslav E.
ergunov
 

Re: Determination of the direction of motion of the locomoti

Postby peter&basti » 04.07.2018, 20:47

Hi Vyacheslav,

i read your post about 3 times, but i have still no glue on the sense of such kind of development.
It sounds a little bit weird from my point of view, without any background information, far away from usual specifications.

A Host Program like Rocrail knows any time the direction of the movement of a loco since they was placed initially correct on the layout, no additional information needed. The initial placing is already supported via Railcom, the placing information is already part of the Railcom feedback.

Please enlight us with the use case behind.

doing something is impossible


What is something?
Liebe Grüße / best regards
Peter


System: DCC 2-Leiter H0, Rocrail 64bit auf Win10 Pro 64
Traktion: OpenDCC GBM
Fahrweg: RocNetNode & GCA PI01/2/3, GCA41/Arduino RFID, GCA145 Drehscheibe, etc.
Decoder: 99% Zimo
Experimentell: MQTT & Node-Red
peter&basti
 

Re: Determination of the direction of motion of the locomoti

Postby ergunov » 05.07.2018, 19:06

peter&basti wrote:Please enlight us with the use case behind.

Peter
Rocrail determines the direction of the locomotive only indirectly.
In the Railcom specification, there is no way to determine the direction. The DR5088 module correctly determines the direction of movement and allows you to translate this information into LocoNet. This is implemented as a correction on the locomotive or block.
Here is the developer's response to the correction.

Karst Drenth Вячеслав Ергунов The Feedback address is never altered/changed. The Block address IS altered in case you select "In Address"
Example: Suppose both Feedback and Block are at 100 and 200.
Then when a loco with address 10 and Backwards enters the DR5088 section following will happen:
1) A 'normal' Feedback is generated: F:100:1 this indicates occupation of the section (current sensing)
2) A 'block enter' Feedback is generated F:200:1 10 < this indicates Loco 10 entered the DR5088 section with Backwards direction

Now, when a loco with address 10 and Forwards enters the DR5088 section following will happen:
1) A 'normal' Feedback is generated: F:100:1 this indicates occupation of the section (current sensing)
2) A 'block enter' Feedback is generated F:2248:1 10 > this indicates Loco 10 entered the DR5088 section with Forward direction but... the DR5000 detects the "+2048" and displays in the log: F:200:1 10 >

This all happens on LocoNet level, so you might want to use JMRI to monitor the LocoNet to see what really happens ;)
I hope it is more clear to you now ;)
Vyacheslav E.
ergunov
 

Re: Determination of the direction of motion of the locomoti

Postby rjversluis » 06.07.2018, 09:17

Hi Vyacheslav,

this extension is not part of the LNPE; Not public.
Without detailed information on how the LocoNet packet ist composed, I cannot implement it.

Rocrail knows directly by the block sensors in which direction a loco moves.
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 - CANGCx ] - [ G: CBUS - CANGCx ]
rjversluis
Site Admin
 

Re: Determination of the direction of motion of the locomoti

Postby ergunov » 05.08.2018, 13:42

Hi Rob
So the situation with the direction of movement cleared up.
The bunch of the DR5000 / DR5088 does this in several ways.
Correction to the locomotive adds 4096 to the locomotive number, and operates on the basis of the prints designed by Bluecher. The method is not convenient since it is added only when moving in the opposite direction.
The correction on the block adds to block number 2048.
At the same time, with both methods, the direction data is transmitted by the standard LocoNet protocol.
In the new version of firmware 5088 the method MULTI_SENSE_Long appeared which removes many of the cuts.
manual DR5088

Is it possible to implement all this in Rocrail?

p.s.
The data on the direction with correction to the locomotive, work successfully in TC.
Last edited by ergunov on 05.08.2018, 13:55, edited 1 time in total.
Vyacheslav E.
ergunov
 

Re: Determination of the direction of motion of the locomoti

Postby rjversluis » 05.08.2018, 13:51

Hi Vyacheslav,

I need the protocol specification; Just adding a number makes no sense to me.
You can ask Digikeijs to inform me directly if the have interrest.

TC is probably Digitrax LocoNet licensee.
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 - CANGCx ] - [ G: CBUS - CANGCx ]
rjversluis
Site Admin
 

Re: Determination of the direction of motion of the locomoti

Postby ergunov » 05.08.2018, 13:57

Rob then do you need a description of the data transfer direction at the protocol level? In this case it will be possible to do this.
Vyacheslav E.
ergunov
 

Re: Determination of the direction of motion of the locomoti

Postby rjversluis » 05.08.2018, 14:00

ergunov wrote:Rob then do you need a description of the data transfer direction at the protocol level? In this case it will be possible to do this.

Yes! 8)
Licensees will become this kind of information automatically.
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 - CANGCx ] - [ G: CBUS - CANGCx ]
rjversluis
Site Admin
 

Re: Determination of the direction of motion of the locomoti

Postby ergunov » 05.08.2018, 17:14

Rob
The functional description of OPC_MULTI_SENSE_L will probably be taken in Digikeijs.
I'll write when it's possible.
Vyacheslav E.
ergunov
 


Return to RailCom

cron