---------- Original Message ----------
From: "Mitchell via groups.io" <mitchell.scott93@...>
Date: May 9, 2020 at 1:05 AM


Hi Steve,

Did you end up finding out about the stopping speed bug?
--
Thanks
Mitch

On May 9, 2020, at 3:10 AM, Dave Heap <dgheap@...> wrote:

?Marc,

On 9 May 2020, at 3:13 PM, forfoum@... wrote:

How about this is speed Step related ? 14, versus 28/128 . JMRI virtual throttle and WiFithrottle are known to have issues with speed step option.

I was actually thinking along the same lines...

- I discovered that both V1.28 and V1.65 Power Cab firmware have a known occasional issue with 28 speed step commands via the USB interface. The NCE documentation suggested to always use 128 step commands.

JMRI 4.19.5 now has an option to select between 14, 28, 128 for the JMRI virtual throttle.

- I thought that was available for JMRI Virtual Throttles but the option seemed to be gone for me in 4.19.5. We don't know what version Scott is using.

- Likewise I couldn't see how to do this with WiThrottle or Throttle preferences.

Everything was being sent as 128 step commands. Maybe this is to avoid the known Power Cab bug, but it seemed to be the same with other hardware profiles I checked.

The fact the E-stop does not work sort of points to a speed step setting.

Agreed.

But I did suggest to Scott that he posted a copy of the NCE Command Monitor output so we could see what is being sent.

As an aside, let's not forget to debunk they mythology surrounding 14/28/128 step modes:
<>

Dave in Australia

My question: Can JMRI Issue a BASH command to set STTY?

I am using a 9-pin MS100 connected to my 9 pin serial port on my Dell D610 laptop (with 2048 MB memory and a Pentium M #06D8 running at 1.86 GHz). I am running JMRI 4.17.7 with Java 1.8.0_211 on Ubuntu 18.10 (CodeName Cosmic). My Desktop is LXQt version 0.13.0. The LocoNet cable goes to my Command Station, a Zephyr DCS50.

To make this work (and it works well), as discussed in the JMRI help page for MS100, I have to first start JMRI, then open another Terminal and issue a command 'stty -F /dev/ttyS0 38400'.? Until I do that extra step, I can successfully send Track Power On or Off to the Command Station, but JMRI always says that the Power is Unknown and nothing shows in the LocoNet Monitor.

After I send the extra stty command, the system works great, including Programming: for example, I can read from and write to my Tsunami TSU-1000 equipped loco on the DCS50 Programming Track.

I had thought that I could use my Bash script that starts JMRI and merely add that command after JMRI in the script, but that does not work.?

I had written a script that executed at startup that would issue that command after 10 seconds, but that did not work.? (Hmmm, maybe I need to make that 30 seconds?)

So I thought, maybe JMRI can send out a command to the Linux operating system using a script or Logix!? So I am asking for any thoughts that might help.? If JMRI cannot do this, my extra step can always be done, or some other Linux trick might be the solution..

I also thought (apparently incorrectly) that somewhere a conf file could be tweaked to fix the tty, but no Google or duckduckgo searches bore fruit.? I am a Linux newbie, so I rely on Google more than I would like.

I am just trying to make the system boot up, run JMRI and connect to the DCS50 by itself, and although I am making progress with the auto login and scripts at startup, with this stty thing I have completely failed.

Thanks for any advice or helpful suggestions.? I have three PR3's and an LNWI, but was given this MS100 and since my old laptop has the 9 pin serial port, I got it working.? I just would prefer it to automatically run when booted.

Phil in gorgeous Young Harris, Georgia, USA