¿ªÔÆÌåÓý

  1. Jmriusers
  2. Topics

Locked VSD CLASS 64 COASTING WEIRDNESS

 

Strange coasting behavior.? Boy, this took a while to decipher.

With the JMRI throttle no coasting regardless on slider action.? Nada, nil, zip!

With Digitrax DT400R throttle coasting works with semi-rapid decrease in throttle, including brake_short.wav when coasting to a stop (step 0).? However, if not going to step zero, coasting sounds remain on until a one step increase in throttle (say 12 to 13).? Decreasing (say 12 to 11 or any amount) has no effect.? Always need a one step increase to get back to engine sounds.? When in coasting "state"? the coasting sounds are responding to decreases in throttle.? I assume this to be related to driver rpms.? When step 3 is reached loco goes to idle_sound.wav.? NOTE: Digitrax "steps" are displayed throttle numbers (1 to 100).

With Engine Driver Wi-throttle maybe a coast once in a while but usually jumps and/or? "notch" lock-ups, or a complete engine silence at any throttle setting (just idle sound).? When this happens (silence), other functions work but no reset with engine start/stop.? Only way to reset is to delete loco then, with decoder manager >> add decoder then select a profile? >> Class64.

Takeaway - Coasting is a very nice VSD?sound effect for steam locos.? This implementation sounds great but I think it needs to be understood that it doesn't have deceleration built in.? One has to manually decrease the throttle to zero to come to a complete stop.? Or give a slight uptick in the throttle to keep on going at a lower speed.

?Are there any solutions for the JMRI and Wi-Throttle problems?

Conrad
 

Am 17.09.2019 um 18:32 schrieb conrad:
Strange coasting behavior.? Boy, this took a while to decipher.
With the JMRI throttle no coasting regardless on slider action.? Nada, nil, zip!
1) Have you tried the keyboard key "Page Down" twice?

2) If the throttle decreases to much, try a left-mouse-click beneath the slider handle followed by a "Page Down"

3) Try to increase the value <decel-trigger-rpms>8</decel-trigger-rpms> in your config.xml. The value defines how many rpms within 0.5 seconds shall trigger the coasting action.

4) (1) - (3) deals with auto-coasting. Besides there is also key-coasting, i.e. coasting can be switched on or off with a throttle key. See (sroll down to section "More throttle key functions ... Coast-Key).


With Digitrax DT400R throttle coasting works with semi-rapid decrease in throttle, including brake_short.wav when coasting to a stop (step 0).? However, if not going to step zero, coasting sounds remain on until a one step increase in throttle (say 12 to 13).? Decreasing (say 12 to 11 or any amount) has no effect.? Always need a one step increase to get back to engine sounds.? When in coasting "state"? the coasting sounds are responding to decreases in throttle.? I assume this to be related to driver rpms.? When step 3 is reached loco goes to idle_sound.wav.? NOTE: Digitrax "steps" are displayed throttle numbers (1 to 100).
Right.


With Engine Driver Wi-throttle maybe a coast once in a while but usually jumps and/or? "notch" lock-ups, or a complete engine silence at any throttle setting (just idle sound).? When this happens (silence), other functions work but no reset with engine start/stop.? Only way to reset is to delete loco then, with decoder manager >> add decoder then select a profile? >> Class64.
It looks like a sound crash in VSD. Is this crash easy to generate and repeatable and only related to auto-coasting?


Takeaway - Coasting is a very nice VSD?sound effect for steam locos.? This implementation sounds great but I think it needs to be understood that it doesn't have deceleration built in.? One has to manually decrease the throttle to zero to come to a complete stop.? Or give a slight uptick in the throttle to keep on going at a lower speed.
There is no build in deceleration on coasting, right. VSD is listening to a throttle and has no control over it, for example, to do speed-setting. This might be a limitation, but decreasing to speed zero while coasting is doable. See


Are there any solutions for the JMRI and Wi-Throttle problems?
Unfortunately I don't have the hardware to test it. So it would be very helpful to have a console log file, if this is possible at all.


Klaus
 

Klaus,

I got JMRI throttle coasting to work.? Page down and left mouse/page down did not work.? BUT, I stumbled on right mouse, saw properties and a check box for
"track slider in real time".? It works and makes some sort of sense.? One problem is that I have to access this property every time I open a throttle.

My decoder is a lokpilot nano that has a functioning "shunt speed" however no success with VSD.? COAST, however works fine.
Here are my triggers:
<trigger name="HALF_SPEED" type="THROTTLE">
<event-name>F8</event-name>
<target-name>ENGINE</target-name>
<action>NOTHING</action>
? ? ? </trigger>
? ? ? <trigger name="COAST" type="THROTTLE">
<event-name>F9</event-name>
<target-name>ENGINE</target-name>
<action>NOTHING</action>
? ? ? </trigger>
and variations of the trigger name -? "ENGINE_HALF_SPEED", "ENGINE_HALFSPEED" and "HALFSPEED" alone

For the Engine Driver Wi-throttle things are better.? It no longer locks up, function F9 (COAST) works and with a reasonable sliding decrease in throttle I can get
it to coast.? It's a little flaky.? Slider action has to be just so to make it coast - too slow and just a normal slow down, too fast and skipping.? No lockup though.??
Think I'll work on your suggestion to?increase the value <decel-trigger-rpms>8</decel-trigger-rpms>.

Here's my console log file (doesn't seem to have any throttle info).? My console info does not look like yours on

2019-09-17 17:56:05,283 util.Log4JUtil? ? ? ? ? ? ? ? ? ? ? ? INFO? - * JMRI log ** [main]
2019-09-17 17:56:05,361 util.Log4JUtil? ? ? ? ? ? ? ? ? ? ? ? INFO? - This log is appended to file: C:\Users\conrad\JMRI\log\messages.log [main]
2019-09-17 17:56:05,361 util.Log4JUtil? ? ? ? ? ? ? ? ? ? ? ? INFO? - This log is stored in file: C:\Users\conrad\JMRI\log\session.log [main]
2019-09-17 17:56:05,376 apps.Apps? ? ? ? ? ? ? ? ? ? ? ? ? ? ?INFO? - PanelPro version 4.16+R6f9aced starts under Java 1.8.0_221 on Windows 10 x86 v10.0 at Tue Sep 17 17:56:05 EDT 2019 [main]
2019-09-17 17:56:07,079 apps.Apps? ? ? ? ? ? ? ? ? ? ? ? ? ? ?INFO? - Starting with profile My_JMRI_Railroad.3f132008 [main]
2019-09-17 17:56:07,517 node.NodeIdentity? ? ? ? ? ? ? ? ? ? ?INFO? - Using jmri-osZcIaSGWhOiaaabMr20Sa-3f132008 as the JMRI storage identity for profile id 3f132008 [AWT-EventQueue-0]
2019-09-17 17:56:07,876 xml.AbstractSerialConnectionConfigXml INFO? - Starting to connect for "LocoNet" [main]
2019-09-17 17:56:08,595 pr3.PR3Adapter? ? ? ? ? ? ? ? ? ? ? ? INFO? - PR3 adapter set hardware flow control, mode=2 RTSCTS_OUT=2 RTSCTS_IN=1 [main]
2019-09-17 17:56:08,611 locobuffer.LocoBufferAdapter? ? ? ? ? INFO? - COM4 port opened at 57600 baud with DTR: true RTS: true DSR: false CTS: false? CD: false [main]
2019-09-17 17:56:08,689 loconet.LnPacketizer? ? ? ? ? ? ? ? ? INFO? - lnPacketizer Started [main]
2019-09-17 17:56:12,658 util.FileUtilSupport? ? ? ? ? ? ? ? ? INFO? - File path program: is C:\Program Files (x86)\JMRI\ [main]
2019-09-17 17:56:12,674 util.FileUtilSupport? ? ? ? ? ? ? ? ? INFO? - File path preference: is C:\Users\conrad\JMRI\My_JMRI_Railroad\ [main]
2019-09-17 17:56:12,689 util.FileUtilSupport? ? ? ? ? ? ? ? ? INFO? - File path profile: is C:\Users\conrad\JMRI\My_JMRI_Railroad\ [main]
2019-09-17 17:56:12,689 util.FileUtilSupport? ? ? ? ? ? ? ? ? INFO? - File path settings: is C:\Users\conrad\JMRI\ [main]
2019-09-17 17:56:12,689 util.FileUtilSupport? ? ? ? ? ? ? ? ? INFO? - File path home: is C:\Users\conrad\ [main]
2019-09-17 17:56:12,689 util.FileUtilSupport? ? ? ? ? ? ? ? ? INFO? - File path scripts: is C:\Program Files (x86)\JMRI\jython\ [main]
2019-09-17 17:56:13,939 PanelPro.PanelPro? ? ? ? ? ? ? ? ? ? ?INFO? - Main initialization done [main]
2019-09-17 17:56:16,799 vsdecoder.VSDecoderPreferences? ? ? ? INFO? - Did not find VSDecoder preferences file.? This is normal if you haven't save the preferences before [AWT-EventQueue-0]
2019-09-17 17:56:16,960 audio.JoalAudioFactory? ? ? ? ? ? ? ? INFO? - Initialised JOAL using OpenAL: vendor - OpenAL Community version - 1.1 ALSOFT 1.15.1 [AWT-EventQueue-0]
2019-09-17 17:56:19,387 withrottle.FacelessServer? ? ? ? ? ? ?INFO? - Published ZeroConf service for 'my jmri railroad._withrottle._tcp.local.' on fe80:0:0:0:60ca:5e0e:ea89:ae2%eth4:12090 [WiThrottleServer]
2019-09-17 17:56:21,977 withrottle.FacelessServer? ? ? ? ? ? ?INFO? - Published ZeroConf service for 'my jmri railroad._withrottle._tcp.local.' on 192.168.1.14:12090 [WiThrottleServer]
2019-09-17 17:56:21,977 withrottle.FacelessServer? ? ? ? ? ? ?INFO? - Creating new WiThrottle DeviceServer(socket) on port 12090, waiting for incoming connection... [WiThrottleServer]
2019-09-17 17:56:51,275 loconet.LnThrottleManager? ? ? ? ? ? ?WARN? - slot 1 address 5514 is already in-use. [AWT-EventQueue-0]
2019-09-17 17:56:51,306 loconet.LnPacketizer? ? ? ? ? ? ? ? ? WARN? - LocoNet message with opCode: ef ended early. Expected length: 14 seen length: 4 unexpected byte: b4 [LocoNet receive handler]
2019-09-17 18:07:31,569 withrottle.FacelessServer? ? ? ? ? ? ?INFO? - Creating new WiThrottle DeviceServer(socket) on port 12090, waiting for incoming connection... [WiThrottleServer]
2019-09-17 18:07:31,569 withrottle.DeviceServer? ? ? ? ? ? ? ?INFO? - Received Name: Engine Driver 2cfd [DeviceServer-1]

Again, thank you for all your help.

Conrad
?
 

Conrad,

A left mouse click above the slider handle should increase the speed by one speed step, a click below should decrease the speed by one speed step.

You can save your throttle layout, see the File menu.

Your triggers are set up fine. HALF_SPEED is the correct name. The trick on HALF_SPEED is, that your lokpilot nano must be assigned to F8 as well (default is F3). You could also try assigning F3 in config.xml.

(BTW, in one of my last post, I gave you a false recommendation for engine gain. It's not <gain> but <engine-gain>. Sorry! The documentation on is correct)

Thanks for the console log. I don't see a VSD sound crash there. But the LocoNet "WARN - slot 1 address 5514 is already in-use" could be a clue for a VSD issue. I assume that there isn't an engine sound at all. Maybe VSD could not listen to the throttle with address 5514. Wasn't there a steal question? Probably not, because of the headless mode.

On the console log output format. Especially for the video I changed the format.

Klaus


Am 18.09.2019 um 00:36 schrieb conrad:

Klaus,
I got JMRI throttle coasting to work.? Page down and left mouse/page down did not work.? BUT, I stumbled on right mouse, saw properties and a check box for
"track slider in real time".? It works and makes some sort of sense.? One problem is that I have to access this property every time I open a throttle.
My decoder is a lokpilot nano that has a functioning "shunt speed" however no success with VSD.? COAST, however works fine.
Here are my triggers:
<trigger name="HALF_SPEED" type="THROTTLE">
<event-name>F8</event-name>
<target-name>ENGINE</target-name>
<action>NOTHING</action>
</trigger>
<trigger name="COAST" type="THROTTLE">
<event-name>F9</event-name>
<target-name>ENGINE</target-name>
<action>NOTHING</action>
</trigger>
and variations of the trigger name -? "ENGINE_HALF_SPEED", "ENGINE_HALFSPEED" and "HALFSPEED" alone
For the Engine Driver Wi-throttle things are better.? It no longer locks up, function F9 (COAST) works and with a reasonable sliding decrease in throttle I can get
it to coast.? It's a little flaky.? Slider action has to be just so to make it coast - too slow and just a normal slow down, too fast and skipping.? No lockup though.
Think I'll work on your suggestion to increase the value <decel-trigger-rpms>8</decel-trigger-rpms>.
Here's my console log file (doesn't seem to have any throttle info).? My console info does not look like yours on
2019-09-17 17:56:05,283 util.Log4JUtil? ? ? ? ? ? ? ? ? ? ? ? INFO? - * JMRI log ** [main]
2019-09-17 17:56:05,361 util.Log4JUtil? ? ? ? ? ? ? ? ? ? ? ? INFO? - This log is appended to file: C:\Users\conrad\JMRI\log\messages.log [main]
2019-09-17 17:56:05,361 util.Log4JUtil? ? ? ? ? ? ? ? ? ? ? ? INFO? - This log is stored in file: C:\Users\conrad\JMRI\log\session.log [main]
2019-09-17 17:56:05,376 apps.Apps? ? ? ? ? ? ? ? ? ? ? ? ? ? ?INFO? - PanelPro version 4.16+R6f9aced starts under Java 1.8.0_221 on Windows 10 x86 v10.0 at Tue Sep 17 17:56:05 EDT 2019 [main]
2019-09-17 17:56:07,079 apps.Apps? ? ? ? ? ? ? ? ? ? ? ? ? ? ?INFO? - Starting with profile My_JMRI_Railroad.3f132008 [main]
2019-09-17 17:56:07,517 node.NodeIdentity? ? ? ? ? ? ? ? ? ? ?INFO? - Using jmri-osZcIaSGWhOiaaabMr20Sa-3f132008 as the JMRI storage identity for profile id 3f132008 [AWT-EventQueue-0]
2019-09-17 17:56:07,876 xml.AbstractSerialConnectionConfigXml INFO? - Starting to connect for "LocoNet" [main]
2019-09-17 17:56:08,595 pr3.PR3Adapter? ? ? ? ? ? ? ? ? ? ? ? INFO? - PR3 adapter set hardware flow control, mode=2 RTSCTS_OUT=2 RTSCTS_IN=1 [main]
2019-09-17 17:56:08,611 locobuffer.LocoBufferAdapter? ? ? ? ? INFO? - COM4 port opened at 57600 baud with DTR: true RTS: true DSR: false CTS: false? CD: false [main]
2019-09-17 17:56:08,689 loconet.LnPacketizer? ? ? ? ? ? ? ? ? INFO? - lnPacketizer Started [main]
2019-09-17 17:56:12,658 util.FileUtilSupport? ? ? ? ? ? ? ? ? INFO? - File path program: is C:\Program Files (x86)\JMRI\ [main]
2019-09-17 17:56:12,674 util.FileUtilSupport? ? ? ? ? ? ? ? ? INFO? - File path preference: is C:\Users\conrad\JMRI\My_JMRI_Railroad\ [main]
2019-09-17 17:56:12,689 util.FileUtilSupport? ? ? ? ? ? ? ? ? INFO? - File path profile: is C:\Users\conrad\JMRI\My_JMRI_Railroad\ [main]
2019-09-17 17:56:12,689 util.FileUtilSupport? ? ? ? ? ? ? ? ? INFO? - File path settings: is C:\Users\conrad\JMRI\ [main]
2019-09-17 17:56:12,689 util.FileUtilSupport? ? ? ? ? ? ? ? ? INFO? - File path home: is C:\Users\conrad\ [main]
2019-09-17 17:56:12,689 util.FileUtilSupport? ? ? ? ? ? ? ? ? INFO? - File path scripts: is C:\Program Files (x86)\JMRI\jython\ [main]
2019-09-17 17:56:13,939 PanelPro.PanelPro? ? ? ? ? ? ? ? ? ? ?INFO? - Main initialization done [main]
2019-09-17 17:56:16,799 vsdecoder.VSDecoderPreferences? ? ? ? INFO? - Did not find VSDecoder preferences file.? This is normal if you haven't save the preferences before [AWT-EventQueue-0]
2019-09-17 17:56:16,960 audio.JoalAudioFactory? ? ? ? ? ? ? ? INFO? - Initialised JOAL using OpenAL: vendor - OpenAL Community version - 1.1 ALSOFT 1.15.1 [AWT-EventQueue-0]
2019-09-17 17:56:19,387 withrottle.FacelessServer? ? ? ? ? ? ?INFO? - Published ZeroConf service for 'my jmri railroad._withrottle._tcp.local.' on fe80:0:0:0:60ca:5e0e:ea89:ae2%eth4:12090 [WiThrottleServer]
2019-09-17 17:56:21,977 withrottle.FacelessServer? ? ? ? ? ? ?INFO? - Published ZeroConf service for 'my jmri railroad._withrottle._tcp.local.' on 192.168.1.14:12090 [WiThrottleServer]
2019-09-17 17:56:21,977 withrottle.FacelessServer? ? ? ? ? ? ?INFO? - Creating new WiThrottle DeviceServer(socket) on port 12090, waiting for incoming connection... [WiThrottleServer]
2019-09-17 17:56:51,275 loconet.LnThrottleManager? ? ? ? ? ? ?WARN? - slot 1 address 5514 is already in-use. [AWT-EventQueue-0]
2019-09-17 17:56:51,306 loconet.LnPacketizer? ? ? ? ? ? ? ? ? WARN? - LocoNet message with opCode: ef ended early. Expected length: 14 seen length: 4 unexpected byte: b4 [LocoNet receive handler]
2019-09-17 18:07:31,569 withrottle.FacelessServer? ? ? ? ? ? ?INFO? - Creating new WiThrottle DeviceServer(socket) on port 12090, waiting for incoming connection... [WiThrottleServer]
2019-09-17 18:07:31,569 withrottle.DeviceServer? ? ? ? ? ? ? ?INFO? - Received Name: Engine Driver 2cfd [DeviceServer-1]
Again, thank you for all your help.
Conrad
 

Klaus,

"You can save your throttle layout, see the File menu."

I did save the throttle and that solved the "track slider in real time" problem.? Thanks


On Wed, Sep 18, 2019 at 03:44 AM, Klaus Killinger wrote:
The trick on HALF_SPEED is, that your lokpilot nano must be assigned to F8 as well
Yes, I did check that F8 was correct.? Program manager shows it and, more importantly, the loco slows when F8 is activated.? I'll switch all to F3 as a test though.

BTY HOW DOES ONE GET THE NICE VERTICAL BAR ON CUT/PASTE QUOTES? I DID THIS BY AN UNKNOWN ACCIDENT

"(BTW, in one of my last post, I gave you a false recommendation for engine gain. It's not <gain> but <engine-gain>."

Interesting, for as far as I can tell I have not had?<engine-gain>0.8</engine-gain> in the config file.? I have now put it in and I think it has made throttle "sliding" harder.
What does it do?

"Thanks for the console log. I don't see a VSD sound crash there. But the LocoNet "WARN - slot 1 address 5514 is already in-use" could be a clue for a VSD issue. I assume that there isn't an engine sound at all. Maybe VSD could not listen to the throttle with address 5514. Wasn't there a steal question? Probably not, because of the headless mode"

Yes, I sometimes get the steal question on my digitrax throttle when also running JMRI.? I forget to use the loconet "monitor slots" to clear my DB150.? I have played with the decel triggers; 12 seems to be working for me on all throttles (JMRI, Digitrax, and Enigine Driver); see below?

<!-- trigger value for brake event - e.g. 8, or 999 to switch off -
? ? ? ? number of rpms within 0.5 sec to trigger coasting (8 default)?
? ? ? ? tried 16, too much 12 seems good -->
? ? ? ? <decel-trigger-rpms>12</decel-trigger-rpms>

Enough for now.

Conrad
 

Klaus,

In my previous msg I said:

"Interesting, for as far as I can tell I have not had?<engine-gain>0.8</engine-gain> in the config file.? I have now put it in and I think it has made throttle "sliding" harder.
What does it do?"

I just checked the untouched github file Class64.vsd and the config file does not have <engine-gain>0.8</engine-gain>.? ?hmmm.

Conrad
 

Am 18.09.2019 um 15:55 schrieb conrad:
Yes, I did check that F8 was correct.? Program manager shows it and, more importantly, the loco slows when F8 is activated.? I'll switch all to F3 as a test though.
I'll check it out.


BTY HOW DOES ONE GET THE NICE VERTICAL BAR ON CUT/PASTE QUOTES? I DID THIS BY AN UNKNOWN ACCIDENT
Mark the text you want to quote before you click on "Reply".


"(BTW, in one of my last post, I gave you a false recommendation for engine gain. It's not <gain> but <engine-gain>."
Interesting, for as far as I can tell I have not had?<engine-gain>0.8</engine-gain> in the config file.? I have now put it in and I think it has made throttle "sliding" harder.
What does it do?
OK, I found it. In message /g/jmriusers/message/163562 I recommended to use <gain>, but it should mean <engine-gain>. Please check your config.xml of your NW2 VSD file. The engine sound is a special sound and I have "engine-gain" intended for it.


Klaus
 

Am 18.09.2019 um 20:55 schrieb conrad:
I just checked the untouched github file Class64.vsd and the config file does not have <engine-gain>0.8</engine-gain>.? ?hmmm.
Right. Class64.vsd is older than the introduction of "engine-gain". But it's fine. The value is optional.


Klaus
 

Klaus,

Thanks.? ? just cleaning, consolidating, sorting and send all VSD to DropBox backup.? 1,800 files!? ?geeez.? Need a course in data management.

Conrad
 

On Wed, Sep 18, 2019 at 08:57 PM, Klaus Killinger wrote:
Am 18.09.2019 um 15:55 schrieb conrad:
Yes, I did check that F8 was correct.? Program manager shows it and, more importantly, the loco slows when F8 is activated.? I'll switch all to F3 as a test though.
I'll check it out.
I did a test on my layout today. HALF_SPEED works, but there is one thing to keep in mind. If the assigned function key is pressed while driving, the loco decoder changes its status immediately. VSD, on the other hand, changes its status only when the speed changes.

Klaus
 

Klaus,

"I did a test on my layout today. HALF_SPEED works, but there is one thing to keep in mind. If the assigned function key is pressed while driving, the loco decoder changes its status immediately. VSD, on the other hand, changes its status only when the speed changes."

Nothing like success even if I didn't initially understand what was going on.

Test 1) Ran Kato Mikado 4-8-2 from idle to throttle 50 out of 100, chuffs rose to "level" 6.? Engaged HALF_SPEED (F8)?and loco speed dropped by maybe a half but chuffs stayed same at "level" 6.? Decreased throttle one step to 49 and chuffs slowly decreased to "level" 4.

Test 2) Ran Kato Mikado 4-8-2 from idle to throttle 50 out of 100, chuffs rose to "level" 6.? Engaged HALF_SPEED (F8)?and loco speed dropped by maybe a half but chuffs stayed same at "level" 6.? Increased throttle one step to 51 and chuffs slowly decreased to "level" 4.

Test 3) With HALF_SPEED engaged, ran Kato Mikado 4-8-2 from idle to throttle 50 out of 100? chuffs rose to "level" 4 with loco going slow.? Released HALF_SPEED (F8) and loco speed increased by maybe double but chuffs stayed a "level" 4.? Decreased throttle one step to 49 and chuffs rapidly increased to "level" 6.

Test 4) With HALF_SPEED engaged, ran Kato Mikado 4-8-2 from idle to throttle 50 out of 100? chuffs rose to "level" 4 with loco going slow.? Released HALF_SPEED (F8) and loco speed increased by maybe double but chuffs stayed a "level" 4.? Increased throttle one step to 51 and chuffs rapidly increased to "level" 6.

Sometimes, but not usually, when starting with HALF_SPEED (F8) engaged and the running, the release of HALF_SPEED will result in increased chuff rate.? Note: this may be caused by unintended throttle movement by me:(

Thus, am I correct in understanding that VSD's engine code is only responding to LocoNet "Set speed of loco in slot 2 to xx" packets?? I say this because watching my JMRI LocoNet Monitor I see that toggling HALF_SPEED (F8) does not result in speed packets being sent.? This makes sense as HALF_SPEED?just tells the decoder to cut or increase the speed, say by half, independent of throttle setting.? So the code for HALF_SPEED goes to say F8, but is not linked to the engine functions.

As always, thank you for your sage advice.

Conrad
 

Conrad,

I think that the loco decoder and VSD are in sync when the HALF_SPEED key is switched and the loco is not running.

Prerequisite: the basic acceleration and deceleration times of the loco decoder and VSD are in sync.

If the HALF_SPEED key is changed while the loco is running, things are not fully synchronized.

I admit I haven't read the NMRA recommendations on half-speed.


Thus, am I correct in understanding that VSD's engine code is only responding to LocoNet "Set speed of loco in slot 2 to xx" packets?? I say this because watching my JMRI LocoNet Monitor I see that toggling HALF_SPEED (F8) does not result in speed packets being sent.? This makes sense as HALF_SPEED?just tells the decoder to cut or increase the speed, say by half, independent of throttle setting.? So the code for HALF_SPEED goes to say F8, but is not linked to the engine functions.
The answer to your question is yes. JMRI provides a speed value between 0 and 1. If HALF_SPEED is active, VSD divides the value by 2. That's it. There are no speed setting packages on the LocoNet. VSD then uses momentum to adjust the speed. And it looks like the loco decoder doesn't do this.

Klaus
 

Conrad,

I have now created a change request regarding HALF_SPEED, see https://github.com/JMRI/JMRI/pull/7455

Klaus

1 - 13 of 13