Keyboard Shortcuts
Likes
- Jmriusers
- Messages
Search
Locked
Re: Instance Manager
Additional information that I neglected in the previous note: The documentation found at supplies no clues as to what might or might not have been a 'configureManagerInstance' attribute for that class. Cliff |
Locked
Re: MRC Prodigy Advance 2
¿ªÔÆÌåÓýThanks for the log. Things are going badly wrong fairly quickly here. It appears to be having problems transmitting Function group updates when you use JMRI throttles. There's possibly an incorrect setting, but I'm not familiar with either the MRC hardware or the JMRI code for it so I hope someone else can help here. --? Dave in Australia
|
Locked
Re: Instance Manager
Norm, Several issues come to mind: The most recent production version is 4.12, not 4.10 which had a lot of problems. Perhaps you simply had a typo? Searching the release notes from through does not turn up any reference to 'jmri.InstanceManager' or to 'configureManagerInstance' but perhaps there was an earlier notification of 'configureManagerInstance' being depreciated and then simply disappearing between those versions. Without some context as to what problem the quoted line from your script is trying to do, I am not able to figure out how to offer any useful options. Maybe one of the developers will recognize something that he or she fixed in that time-frame and be able to provide better information. Otherwise, uploading your script to the Problems Being Worked On portion of the Files section would be in order. Be aware that most of us would only work with versions 4.12 or later. For the sake of sanity, there are no more than one production version and one test version active on this computer at a time. Other group members may have reasons to keep older versions around. Cliff in Baja SoCal |
Locked
Re: Instance Manager
There's a new import line I believe you need. Unfortunately I don't recall it, but now you know what to search for. Also 4.10 has 'issues', so strongly advise to go to 4.12 On Wed, Nov 21, 2018, 19:07 Nom dInet via Groups.Io <nomdinet=[email protected] wrote:
|
Locked
Re: MRC Prodigy Advance 2
Thank you Dave for the feedback...please see the bellow:
2018-11-22 09:46:49,135 util.Log4JUtil??????????????????????? INFO? - * JMRI log ** [main] 2018-11-22 09:46:49,153 util.Log4JUtil??????????????????????? INFO? - This log is appended to file: C:\Users\David Atwater II\JMRI\log\messages.log [main] 2018-11-22 09:46:49,154 util.Log4JUtil??????????????????????? INFO? - This log is stored in file: C:\Users\David Atwater II\JMRI\log\session.log [main] 2018-11-22 09:46:49,162 apps.AppsBase???????????????????????? INFO? - DecoderPro version 4.12+Rb6a9bb1 starts under Java 1.8.0_191 on Windows 7 amd64 v6.1 at Thu Nov 22 09:46:49 PST 2018 [main] 2018-11-22 09:46:49,415 gui3.Apps3??????????????????????????? INFO? - Starting with profile My_JMRI_Railroad.3f0ca4fd [main] 2018-11-22 09:46:49,685 node.NodeIdentity???????????????????? INFO? - Using jmri-n2t1ZdvEGhNiaaajd-Uj0d-3f0ca4fd as the JMRI Node identity [AWT-EventQueue-0] 2018-11-22 09:46:49,834 xml.AbstractSerialConnectionConfigXml INFO? - Starting to connect for "MRC" [main] 2018-11-22 09:46:50,728 serialdriver.SerialDriverAdapter????? INFO? - Serial timeout was observed as: 0 false [main] 2018-11-22 09:46:50,729 serialdriver.SerialDriverAdapter????? INFO? - input buffer 0 [main] 2018-11-22 09:46:50,731 serialdriver.SerialDriverAdapter????? INFO? - COM3 port opened at 38400 baud, sees? DTR: true RTS: true DSR: false CTS: false? CD: false [main] 2018-11-22 09:46:51,153 util.FileUtilSupport????????????????? INFO? - File path program: is C:\Program Files (x86)\JMRI\ [main] 2018-11-22 09:46:51,153 util.FileUtilSupport????????????????? INFO? - File path preference: is C:\Users\David Atwater II\JMRI\My_JMRI_Railroad\ [main] 2018-11-22 09:46:51,154 util.FileUtilSupport????????????????? INFO? - File path profile: is C:\Users\David Atwater II\JMRI\My_JMRI_Railroad\ [main] 2018-11-22 09:46:51,155 util.FileUtilSupport????????????????? INFO? - File path settings: is C:\Users\David Atwater II\JMRI\ [main] 2018-11-22 09:46:51,155 util.FileUtilSupport????????????????? INFO? - File path home: is C:\Users\David Atwater II\ [main] 2018-11-22 09:46:51,156 util.FileUtilSupport????????????????? INFO? - File path scripts: is C:\Program Files (x86)\JMRI\jython\ [main] 2018-11-22 09:50:14,270 jmrit.XmlFile???????????????????????? INFO? - No C:\Users\David Atwater II\JMRI\My_JMRI_Railroad\roster\UP_FEF_3__839.xml file to backup [AWT-EventQueue-0] 2018-11-22 09:51:40,378 mrc.MrcPacketizer???????????????????? WARN? - Ignore Mrc packet with bad checksum: Loco 4094 Function Group 1: F0 Off F1 Off F2 On F3 Off F4 Off [Mrc receive handler 10] 2018-11-22 09:51:40,393 mrc.MrcPacketizer???????????????????? WARN? - run: unexpected MrcMessageException: {0} [Mrc receive handler 10] jmri.jmrix.mrc.MrcMessageException ??? at jmri.jmrix.mrc.MrcPacketizer$RcvHandler.run(MrcPacketizer.java:447) ??? at java.lang.Thread.run(Unknown Source) 2018-11-22 09:51:40,924 mrc.MrcPacketizer???????????????????? WARN? - Ignore Mrc packet with bad checksum: Loco 4014 Function Group 1: F0 Off F1 Off F2 Off F3 Off F4 Off [Mrc receive handler 10] 2018-11-22 09:51:40,924 mrc.MrcPacketizer???????????????????? WARN? - run: unexpected MrcMessageException: {0} [Mrc receive handler 10] jmri.jmrix.mrc.MrcMessageException ??? at jmri.jmrix.mrc.MrcPacketizer$RcvHandler.run(MrcPacketizer.java:447) ??? at java.lang.Thread.run(Unknown Source) 2018-11-22 09:51:49,488 mrc.MrcPacketizer???????????????????? WARN? - Ignore Mrc packet with bad checksum: Loco 4014 Function Group 1: F0 Off F1 Off F2 On F3 Off F4 Off [Mrc receive handler 10] 2018-11-22 09:51:49,488 mrc.MrcPacketizer???????????????????? WARN? - run: unexpected MrcMessageException: {0} [Mrc receive handler 10] jmri.jmrix.mrc.MrcMessageException ??? at jmri.jmrix.mrc.MrcPacketizer$RcvHandler.run(MrcPacketizer.java:447) ??? at java.lang.Thread.run(Unknown Source) 2018-11-22 09:51:50,611 mrc.MrcPacketizer???????????????????? WARN? - Ignore Mrc packet with bad checksum: Loco (L) 4014 128ss Rev Speed 113 [Mrc receive handler 10] 2018-11-22 09:51:50,611 mrc.MrcPacketizer???????????????????? WARN? - run: unexpected MrcMessageException: {0} [Mrc receive handler 10] jmri.jmrix.mrc.MrcMessageException ??? at jmri.jmrix.mrc.MrcPacketizer$RcvHandler.run(MrcPacketizer.java:447) ??? at java.lang.Thread.run(Unknown Source) 2018-11-22 09:52:04,277 mrc.MrcPacketizer???????????????????? WARN? - Ignore Mrc packet with bad bit: Loco -48638 Function Group 1: F0 Off F1 Off F2 On F3 Off F4 Off [Mrc receive handler 10] 2018-11-22 09:52:04,277 mrc.MrcPacketizer???????????????????? WARN? - run: unexpected MrcMessageException: {0} [Mrc receive handler 10] jmri.jmrix.mrc.MrcMessageException ??? at jmri.jmrix.mrc.MrcPacketizer$RcvHandler.run(MrcPacketizer.java:452) ??? at java.lang.Thread.run(Unknown Source) 2018-11-22 09:52:47,850 mrc.MrcPacketizer???????????????????? WARN? - Ignore Mrc packet with bad bit: Loco -48638 Function Group 1: F0 Off F1 Off F2 On F3 Off F4 Off [Mrc receive handler 10] 2018-11-22 09:52:47,850 mrc.MrcPacketizer???????????????????? WARN? - run: unexpected MrcMessageException: {0} [Mrc receive handler 10] jmri.jmrix.mrc.MrcMessageException ??? at jmri.jmrix.mrc.MrcPacketizer$RcvHandler.run(MrcPacketizer.java:452) ??? at java.lang.Thread.run(Unknown Source) 2018-11-22 09:52:48,177 mrc.MrcPacketizer???????????????????? WARN? - Ignore Mrc packet with bad checksum: Loco 770 Function Group 1: F0 Off F1 Off F2 On F3 Off F4 Off [Mrc receive handler 10] 2018-11-22 09:52:48,177 mrc.MrcPacketizer???????????????????? WARN? - run: unexpected MrcMessageException: {0} [Mrc receive handler 10] jmri.jmrix.mrc.MrcMessageException ??? at jmri.jmrix.mrc.MrcPacketizer$RcvHandler.run(MrcPacketizer.java:447) ??? at java.lang.Thread.run(Unknown Source) 2018-11-22 09:52:48,723 mrc.MrcPacketizer???????????????????? WARN? - Ignore Mrc packet with bad checksum: Loco 839 Function Group 1: F0 Off F1 Off F2 On F3 Off F4 Off [Mrc receive handler 10] 2018-11-22 09:52:48,723 mrc.MrcPacketizer???????????????????? WARN? - run: unexpected MrcMessageException: {0} [Mrc receive handler 10] jmri.jmrix.mrc.MrcMessageException ??? at jmri.jmrix.mrc.MrcPacketizer$RcvHandler.run(MrcPacketizer.java:447) ??? at java.lang.Thread.run(Unknown Source) 2018-11-22 09:52:51,984 mrc.MrcPacketizer???????????????????? WARN? - Ignore Mrc packet with bad checksum: Loco (L) -48638 [Mrc receive handler 10] 2018-11-22 09:52:51,984 mrc.MrcPacketizer???????????????????? WARN? - run: unexpected MrcMessageException: {0} [Mrc receive handler 10] jmri.jmrix.mrc.MrcMessageException ??? at jmri.jmrix.mrc.MrcPacketizer$RcvHandler.run(MrcPacketizer.java:447) ??? at java.lang.Thread.run(Unknown Source) 2018-11-22 09:55:17,610 mrc.MrcPacketizer???????????????????? WARN? - Ignore Mrc packet with bad checksum: Loco 4014 Function Group 1: F0 Off F1 Off F2 On F3 Off F4 Off [Mrc receive handler 10] 2018-11-22 09:55:17,610 mrc.MrcPacketizer???????????????????? WARN? - run: unexpected MrcMessageException: {0} [Mrc receive handler 10] jmri.jmrix.mrc.MrcMessageException ??? at jmri.jmrix.mrc.MrcPacketizer$RcvHandler.run(MrcPacketizer.java:447) ??? at java.lang.Thread.run(Unknown Source) 2018-11-22 09:55:20,402 mrc.MrcPacketizer???????????????????? WARN? - Ignore Mrc packet with bad checksum: Loco 4014 Function Group 1: F0 On F1 Off F2 On F3 On F4 On [Mrc receive handler 10] 2018-11-22 09:55:20,402 mrc.MrcPacketizer???????????????????? WARN? - run: unexpected MrcMessageException: {0} [Mrc receive handler 10] jmri.jmrix.mrc.MrcMessageException ??? at jmri.jmrix.mrc.MrcPacketizer$RcvHandler.run(MrcPacketizer.java:447) ??? at java.lang.Thread.run(Unknown Source) 2018-11-22 09:55:20,933 mrc.MrcPacketizer???????????????????? WARN? - Ignore Mrc packet with bad checksum: Loco 4014 Function Group 1: F0 Off F1 Off F2 On F3 Off F4 Off [Mrc receive handler 10] 2018-11-22 09:55:20,933 mrc.MrcPacketizer???????????????????? WARN? - run: unexpected MrcMessageException: {0} [Mrc receive handler 10] jmri.jmrix.mrc.MrcMessageException ??? at jmri.jmrix.mrc.MrcPacketizer$RcvHandler.run(MrcPacketizer.java:447) ??? at java.lang.Thread.run(Unknown Source) |
Locked
Re: NCE light it as signal decoder
Dave,
toggle quoted message
Show quoted text
Added the panel.xml file. It¡¯s under test layout. Please let me know if you found it. I really do appreciate all the help. I have one NCE light it wired in right now and 3 virtual masts. The masts will work correctly by clicking them in the screen. Signal names EB 1 is the NCE decoder and the rest are virtual. I can¡¯t get them to detect the train in the blocks. Also in the file you¡¯ll see a crossover and a siding. Is there anything I need to do to signal those? Thanks Michael On Nov 21, 2018, at 7:47 PM, Dave Sand <ds@...> wrote: |
Locked
Re: Instance Manager
Nom: On totally unrelated software I had a recent problem when updating from a very old version directly to the latest version. The vendor recommended updating in several smaller steps i.e. 4.4 to 4.6 to 4.8 to 4.10 for example. That worked for me so might be worth a try in your case. Don't? forget too that java needs to be kept up to date. Others know which java version is needed by which jmri version.
Jan |
Locked
Re: NCE AUI Sensors not detecting active or inactive - timeout message
Windows changing the COM Port number when different USB ports are used is often an issue on portable systems where different people might plug the system together. Generally have to choose a physical USB port for the USB to serial convertor and then mark it and always use it.
You can usually change the COM port that WIndows assigns to a USB to serial convertor in the driver porperties. That might be useful if you have to use a different USB socket due to damage and dont want to change the setup on JMRI. Open Device Manager, Select Ports(COM&LPT) and double click your device e.g. "USB Serial Port(COM6)". Then in the Properties that opens select the Port Settings Tab, then the Advanced button and in there you can change the COM port number assigned to that device plugged into that USB socket. Dave |
Locked
How to sort manual backups in operations
frankjoanw
I keep about 50 manual backups in order to run trains in a different sequence at different times. ?Currently the manual backups are kept in a RANDOM order so when I want to RESTORE I have to search thru all 50 (could be more) checking the dates or backup number to find the one I want to use. ?Each backup has a date but the dates are stored in a random order rather than in date order. ?
Is there a way to SORT the backups so they will appear in DATE ORDER when I want to restore an older backup? I am using The latest revision 4.13.5 released just yesterday. ?THANK YOU...Frank |
Locked
Re: ShuttlePro Throttle on Linux
On Tue, 20 Nov 2018 05:18:16 -0800 "phil haw" <feyip@...> wrote:
I use a Contour ShuttleProAccording to the internet, Linux will create an entry under /dev/input for the ShuttlePro, and you can test it with evtest. After you have that working, it looks like the Jynstrument USBThrottle.jyn can be adapted for most input devices. The relevant JMRI help pages are: JMRI: USB Input Control <> Custom Throttle with Jynstruments section of Advanced Throttle Control <> JMRI: Jynstruments <> My experience with this is limited to plugging in a USB joystick and watching JMRI's USB input control respond to button presses. Jim |
Locked
Re: NCE GET Macro caused loss of existing Macros and loss of existing consists
Ken, Clinton Central Model Railroad www.ccmrr.org |
Locked
Re: NCE GET Macro caused loss of existing Macros and loss of existing consists
PS: Our number system is that even numbers, like 4.10, 4.12, 4.14 are
production versions. 4.11.* was the beta series that became 4.12, 4.13.* is what becomes 4.14. -Ken Cameron, Member JMRI Dev Team www.jmri.org www.fingerlakeslivesteamers.org www.cnymod.com www.syracusemodelrr.org |
Locked
Re: NCE GET Macro caused loss of existing Macros and loss of existing consists
Wain,
The 4.13.* series is our beta versions that will turn into 4.14 coming out in December. We figured out the fix just after the 4.12 production version was released. The bug was known, but not the fix. Right now the 4.13.5 is close to what will be 4.14 in another month. Either make completely sure to not try the macro command or update to 4.13.5. I would update, it means you don't have to worry about somebody trying it. Also there are the usual new decoders that would be found that have been created since the beginning of summer. -Ken Cameron, Member JMRI Dev Team www.jmri.org www.fingerlakeslivesteamers.org www.cnymod.com www.syracusemodelrr.org |
Locked
Re: NCE GET Macro caused loss of existing Macros and loss of existing consists
Ken and Dan,
Yes, we are running 4.12 currently.? I see that there is a 4.13.5 test release, but do not see a 4.13 production release (I see it might be a December release time frame though).? I can try to load 4.13.5 but we are just starting our 2018/2019 Open House season -we're located near Lock Haven, PA if anyone is interested (www.ccmrr.org/events.html) - and I don't think the club would like to try anything new right now. Ken - thanks for confirming the symptom(s) - first and last time I remember seeing this behavior, so hoping nothing similar occurs during Open House (yes - I WILL stay away from macros in JMRI 4.12!). Regards, Wain Schroeder |
Locked
Re: NCE AUI Sensors not detecting active or inactive - timeout message
¿ªÔÆÌåÓýThanks Dave, All works fine now. Mike Canada ? From: [email protected] <[email protected]> On Behalf Of Dave Heap
Sent: Thursday, November 22, 2018 1:53 AM To: [email protected] Subject: Re: [jmriusers] NCE AUI Sensors not detecting active or inactive - timeout message ? Mike, Those settings will get you into trouble with other features (like programming) ? The correct settings for a Power Pro system via the Serial Port ?are: - On the Power Pro, Set Up Command Station -- AIU Broadcast must be Disabled. -- ?RS232 Port Baud Rate must be set to 9,600 - JMRI preferences are: -- System manufacturer: NCE -- System connection: ?Serial -- Serial port: <whatever is appropriate for your setup, as per Windows Device Manager> -- Additional Connection Settings checkbox ON --- Baud rate: 9600. --- Command Station EPROM: 2006 or later (unless you have a very old system). ? The JMRI console log should then report V6.2.x (where "x" is most likely "1"). ? When you install the USB-Serial driver, the Windows installer should take care of avoiding COM port conflicts. ? If you bought other than the recommended USB-Serial cables, you may find that Windows capriciously changes the COM port later and you'll have to change JMRI settings to match. This is because many cables do not have a unique serial number, and is most likely to happen if you plug into a different USB port on your computer. ? --? Dave in Australia ? ? On 22 Nov 2018, at 5:20 PM, michelplouffe4748@... wrote:
|
Locked
Re: NCE GET Macro caused loss of existing Macros and loss of existing consists
Ken,
Good catch, the NCE macro was fixed in 4.13.1. Dan |
Locked
Re: NCE GET Macro caused loss of existing Macros and loss of existing consists
The prior behavior of the macro editor, while it was broken, fit your
description. What would happen is it would effectively wipe the memory in the command station. What I don't recall is which version JMRI was the first one with the fix. So that is the thing to confirm, when was it fixed and which version you had. I think you said 4.12. -Ken Cameron, Member JMRI Dev Team www.jmri.org www.fingerlakeslivesteamers.org www.cnymod.com www.syracusemodelrr.org |
Locked
Throttle for Microsoft Phone?
A friend is wanting to use an old Microsoft phone with Withrottle.
Is there an app available for that? Regards Peter Pennycuick 0407916570 |
Locked
Re: Lenz Compact/XpressNet
¿ªÔÆÌåÓý
If it has the version 3.2 firmware ( which I think was the last one released ) it supports consisting.
It is possible that the compact doesn¡¯t support the directed emergency stop. ?This is what is triggered by the stop button on most XpressNet systems. ?I still have an Atlas Commander ( which is a rebadged compact ) around here. ?I probably can¡¯t get to this until Saturday, but I can check and see what the compact does and, if needed, I can make JMRI send speed 0 instead of a directed emergency stop. The idle button just sets the speed to zero. Paul |
Locked
Re: NCE AUI Sensors not detecting active or inactive - timeout message
¿ªÔÆÌåÓýMike, Those settings will get you into trouble with other features (like programming) The correct settings for a Power Pro system via the Serial Port ?are: - On the Power Pro, Set Up Command Station -- AIU Broadcast must be Disabled. -- ?RS232 Port Baud Rate must be set to 9,600 - JMRI preferences are: -- System manufacturer: NCE -- System connection: ?Serial -- Serial port: <whatever is appropriate for your setup, as per Windows Device Manager> -- Additional Connection Settings checkbox ON --- Baud rate: 9600. --- Command Station EPROM: 2006 or later (unless you have a very old system). The JMRI console log should then report V6.2.x (where "x" is most likely "1"). When you install the USB-Serial driver, the Windows installer should take care of avoiding COM port conflicts. If you bought other than the recommended USB-Serial cables, you may find that Windows capriciously changes the COM port later and you'll have to change JMRI settings to match. This is because many cables do not have a unique serial number, and is most likely to happen if you plug into a different USB port on your computer. --? Dave in Australia
|