#535 Upgrades causing problems

[Geoffrey Fields]

Old problem back with a VENGANCE plus other anomalies.
JMRI version: 4.01
System: Lenz LVZ100 version 3.5
Interface: Lenz LIUSB
Computer: Intel core i7, 8gb ram, windows 10, usb port 57600, 8, none, 1, hardware.
Having upgraded from a fully working, no problems JMRI 3.8 and Windows Vista to that listed above the following problems have manifest.

1. Repeated attempts to burn-out my point motors. The log shows that JMRI sends commands to turn on outputs and then followed by 2 or 3 commands to turn off again. But intermittently the off commands are not actioned by the command station so leaving a point motor permanently energised. There are no dreaded "command station busy" appearing in the log.
2. Scripts that functioned fine before now don’t. Similar in a way to point motors, Loco’s do not respond to all commands sent from JMRI. Again the log shows the correct commands going to the command station but are just ignored. To correct this problem I have had to edit all my scripts to make every command for loco change of speed etc. to be repeated twice. This has solved or at least persuaded the command station to respond every time.

[Geoffrey Fields]

Further info:
Now tried reverting back to JMRI ver. 3.8 and problem persists and if anything maybe slightly worse so reinstalled 4.0.1 again.
USB Driver: FTDI 2.12.6.0 10/07/2015
All commands no matter how frequent and with multiple hand throttles operated simultaniously are actioned perfectly with no issues.
My finger of suspicion is now pointing at Win 10 and USB comms.
I cannot go back to Windows Vista has the failure of that computer prompted the upgrade to new.
HELP!

[Walter Thompson]

I do not find this reported in the uses group and dont find Geoffrey Fields as a member of the users group.
Walt

[Geoffrey Fields]

I am on the users group (geoffreyfields911)? I have put these comments on a thread that was already active. I have also sent more details direct to Paul Bender who I have dealt with before.

Regards,

Geoff

From: Walter Thompson [mailto:walter71342@users.sf.net]
Sent: 24 December 2015 20:58
To: [jmri:bugs]
Subject: [jmri:bugs] #535 Upgrades causing problems

I do not find this reported in the uses group and dont find Geoffrey Fields as a member of the users group.
Walt

---

[bugs:#535] http://sourceforge.net/p/jmri/bugs/535/ Upgrades causing problems

Status: open
Group: Broad_impact
Created: Thu Oct 22, 2015 10:19 AM UTC by Geoffrey Fields
Last Updated: Thu Oct 22, 2015 02:24 PM UTC
Owner: nobody

Old problem back with a VENGANCE plus other anomalies.
JMRI version: 4.01
System: Lenz LVZ100 version 3.5
Interface: Lenz LIUSB
Computer: Intel core i7, 8gb ram, windows 10, usb port 57600, 8, none, 1, hardware.
Having upgraded from a fully working, no problems JMRI 3.8 and Windows Vista to that listed above the following problems have manifest.

1. Repeated attempts to burn-out my point motors. The log shows that JMRI sends commands to turn on outputs and then followed by 2 or 3 commands to turn off again. But intermittently the off commands are not actioned by the command station so leaving a point motor permanently energised. There are no dreaded "command station busy" appearing in the log.
2. Scripts that functioned fine before now don’t. Similar in a way to point motors, Loco’s do not respond to all commands sent from JMRI. Again the log shows the correct commands going to the command station but are just ignored. To correct this problem I have had to edit all my scripts to make every command for loco change of speed etc. to be repeated twice. This has solved or at least persuaded the command station to respond every time.

---

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/jmri/bugs/535/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

[Geoffrey Fields]

Yes it is and yes I am. See thread: JMRI v4.0 and Lenz commands delay​