search

DCC-EX / CommandStation-EX

EX-CommandStation firmware from DCC-EX. Includes support for WiFi and a standalone WiThrottle server. A complete re-write of the original DCC++.
https://dcc-ex.github.io/
GNU General Public License v3.0
156 stars 108 forks source link

Bug Report: EX-RAIL omits settings CV4 when using speed(0) in AUTOMATION(id) #307

Closed AlbertG53 closed 1 year ago

AlbertG53 commented 1 year ago

Version

4.1.2

Bug description

SPEED(0) stops the locomotive without the delay in CV4 as in an emergency break. And it only appears in AUTOMATION(id), not in SEQUENCE(id).

Steps to reproduce the bug

When I use this: SEQUENCE(12) FWD(30) AT(22) SPEED(0) The locomotive brakes according to the setting of CV 4, so with a little delay to 0 as it should be.

When I use this with Engine Driver to start the same locomotive: AUTOMATION(12, "From 1 to 2") FWD(30) AT(22) SPEED(0)

The locomotive brakes as with an emergency stop, so no delay according to CV4. The function (F4) on the locomotive to deactivate CV4/ABV is switched off. Can anyone give a solution to this problem? (When I drive the locomotive with the throttle and press Stop it stops with the delay according to CV4)

Expected behaviour

The locomotive should brake smoothly according to the setting in CV4

Screenshots

No response

Hardware in use

Arduino Mega + standard motor shield, no specific brand.

Additional context

No response

Asbelos commented 1 year ago

The speed setting 0 in exrail sends the 0 stop message and has no knowlege of cv4, functions or whether the script was started by Ed...

What is after SPEED(0) in your script?

Asbelos commented 1 year ago

If your automation reaches a DONE statement or the task is terminated in any other way, that will estop your loco..
You can avoid this by changing the current loco on the task, (SETLOCO(0) ) or using a delay

AlbertG53 commented 1 year ago

I posted this problem on Discord. The respons was it is a bug in EX-RAIL and I had to create an Bug Report. So I did. I wonder why noboby on Discord came up with this answer. This was my script with the problem: AUTOMATION(12, "From 1 to 2") FWD(30) AT(22) SPEED(0) DONE

I changed the script according to your message in AUTOMATION(12, "From 1 to 2") FWD(30) AT(22) SPEED(0) DELAY(1000) DONE

And the problem is solved. I think your answer of yesterday should be documented on the EX-RAIL pages

If your AUTOMATION reaches a DONE statement or the task is terminated in any other way, that will estop your loco.. You can avoid this by changing the current loco on the task, (SETLOCO(0) ) or using a delay

Asbelos commented 1 year ago

My assessment of this problem was based on an assumption about what you didn't tell us on discord or in this bug report... For future reference, its better to give all the info rather than jump to conclusions.