Keyboard Shortcuts
Likes
- Jmriusers
- Messages
Search
|
Locked
Re: Added sensors and logix to panels. The sensors and logix have disappeared
Scott,
toggle quoted message
Show quoted text
What do you mean virtual sensors? Normally Internal sensors are used when there is no related hardware. I only see LocoNet sensors. The list in the xml matches Tools >> Sensors. The xml sensor list is not sorted so comparisons are more difficult. The content of the user name has no impact. The xml and Logix table match, with one Logix with 25 conditionals. If you set zoom to 1 and scroll to x: 1168, y: 4980 you will see a turnout. The toolbar shows the current zoom and mouse location. Dave Sand On Nov 8, 2018, at 4:03 PM, Scott Walton <jscottwalton@...> wrote: |
|
Locked
Re: Adding new "info" field to the Cars and Loco tab in Oospore
Paul D,
Since this is a user group discussion, I was focusing on the concepts. So yes to your first part. The developer group is where the discussion of the second part takes place. While I know the form of the roster data and how that worked (I've used it). I don't know the form of the data in the Operations data tables. So I don't know either how simple or not the same idea would be to implement. But discussions like this spot the 'givens and druthers' of the ideas. From that developers get the guidance of which solutions might be worth the effort to implement. -Ken Cameron, Member JMRI Dev Team www.jmri.org www.fingerlakeslivesteamers.org www.cnymod.com www.syracusemodelrr.org |
|
Locked
Re: Layout Editor, too much for RPi3?
Tried increasing memory in jmri.com,?default_options="-J-Xmx768m", but that didn't help. Then noticed I was getting a stack trace in system console whenever I clicked. Does that shed any light? I also get a stack of bad blockname errors when I open the panel in case that's related. I've pasted that at the bottom. The block table does get populated with these blocks though. 2018-11-08 18:13:46,463 ptionhandler.UncaughtExceptionHandler ERROR - Uncaught Exception caught by jmri.util.exceptionhandler.UncaughtExceptionHandler [AWT-EventQueue-0] |
|
Locked
Re: Mentor for JMRI DecoderPro in Central MA?
Doug,
toggle quoted message
Show quoted text
A lot of the information out there can be misleading. This appears to be the first time you have requested help. Below is a correct set of instructions. -- Dave Heap (a member of the JMRI development team and an NCE hardware technical expert) NCE USB on Windows ================ - The NCE USB uses the SiLabs CP2102 chipset. Download and install SiLabs CP210x drivers from <> - There is a Universal driver for Windows 10. - The downloaded file will be a ".zip" - You open that file and then open the file called: "CP210xVCPInstaller_x86.exe" or "CP210xVCPInstaller_x64.exe" depending on whether your Windows is 32 bit or 64 bit. - After doing this you should get the SiLabs device appearing as a new COM port in Windows Device Manager when you plug it in. - Sometimes you may need to install the driver again after plugging in the NCE USB to get rid of the error symbol in Windows Device Manager. - If you still have questions marks, try removing driver in Device Manager and try again as above - When you have it working properly, the COM port should appear/disappear as you plug/unplug the NCE USB. - Do not try to set the baud rate in Windows Device Manager. - Ignore all other documentation to the contrary (there is some incorrect information in places) and set up as below: - It also explains how to read the version of your NCE USB (only the first digit counts, the last three report how your jumpers 2-4 are set and jumper 1 is ignored on all systems). Configuration Instructions =================== Here are the best settings for JMRI and jumpers for Power Cab (and also SB5). Make sure you always unplug/replug both cables on the NCE USB after changing jumpers. It also explains how to read the version of your NCE USB (only the first digit counts, the last three report how your jumpers 2-4 are set and jumper 1 is ignored on all systems). Power Cab Instructions ================= The correct settings for a Power Cab V1.65 or V1.28 (as shown when the Power Cab starts up) and an NCE USB V6 (or you are not sure of the USB version) are: - All USB Jumpers off (or at least 2, 3 & 4. Jumper 1 is ignored). - JMRI preferences are: -- System manufacturer: NCE -- System connection: NCE USB -- Serial port: <whatever is appropriate for your system> -- USB version: V6.x.x -- System: PowerCab -- Additional Connection Settings checkbox ON --- Baud rate: 9600. The JMRI console log should then report V6.3.0. If it reports V7.3.0 and your Power Cab is V1.65, use the settings below instead. If you don't get a version number or the system does not work, Use Help->System Console...->Copy to clipboard and paste into a post for us to see. The correct settings for a Power Cab V1.65 or V1.65b and an NCE USB V7 are: - All USB Jumpers on (or at least 2, 3 & 4. Jumper 1 is ignored). - JMRI preferences are: -- System manufacturer: NCE -- System connection: NCE USB -- Serial port: <whatever is appropriate for your system> -- USB version: V7.x.x -- System: PowerCab -- Additional Connection Settings checkbox ON --- Baud rate: 19200. The JMRI console log should then report V7.3.7. SB5 Instructions ============ The correct settings for an SB5 and an NCE USB V7 are: - USB Jumper 4 on. All others off (or at least 2 & 3. Jumper 1 is ignored). - JMRI preferences are: -- System manufacturer: NCE -- System connection: NCE USB -- Serial port: <whatever is appropriate for your system> -- USB version: V7.x.x -- System: SB5 -- Additional Connection Settings checkbox ON --- Baud rate: 19200. The JMRI console log should then report V7.3.1. General Troubleshooting ================== If the system does not work after this: - If your SB5/Power Cab is V1.65 rather than V1.65B, you may have been affected by a firmware issue (triggered by a System Reset). - Your NCE USB may be set to a bad cab address (V7 only). - There is a potential hardware issue with the NCE USB/Power Cab combination. In either case, go through the following : - Quit JMRI. - Ensure neither LED on the NCE USB is stuck ON. If so, power cycle the USB by unplugging it from the cab bus cable. - Ensure you have no other throttles connected. - Restart JMRI and immediately go to Configure USB Interface under the NCE menu. - Set the Cab ID to 3. - Attempt a JMRI operation (use a throttle, Identify a decoder). - The status line should stay green and it should work -If this does not work, do not fiddle with any other settings but instead: -- Observe whether the Cab Bus LED on the NCE USB is stuck on and report back. -- Use Help->System Console...->Copy to clipboard and paste into a post for us to see. On 9 Nov 2018, at 8:44 AM, Doug Lowing <delowing1903@...> wrote: |
|
Locked
Re: Adding new "info" field to the Cars and Loco tab in Oospore
Ken...not sure I understand your statement. If you are asking if the extension method used for the loco roster would be workable if that same method was applied to the cars file, I would find that very workable.? If I could add columns to the cars file, I would be happy.
However, if you are asking if the loco roster method could be applied (technically) to the cars file, I don't have a clue. I am not a programmer nor am I savvy on the JMRI coding. Paul D |
|
Locked
Ops: Order within a spur
In operations, the option is available for both yard and C/I tracks to select Normal, First In First Out, or Last In First Out. I see that the status of spurs is always displayed as Normal. Is there a way to have the FIFO and LIFO options for spurs as well? I use custom loads and schedules for all my spurs, and I have a reverse loop at a power plant for coal unloading. I'd like the program to apply the custom schedule and unload coal hoppers on this spur?in the order they are received.
Micheal Farley Bismarck, ND www.facebook.com/yellowstonedivision |
|
Locked
Re: panel xml file corrupted
Jim,
toggle quoted message
Show quoted text
JmriFunctions.py is the source for the invalid properties that have been added to the sensors. The property is a listener that has been created to provide notifications of changes within JMRI. When JmriFunctions needs to update the listeners, it uses the property content to identify old ones to be deleted before adding a new one. If the panel xml file is saved before JMRI is shutdown, the property changes are retained. This causes XML validation errors on startup. If validation is disabled, each property generates a Java error since the listener reference is unknown to JMRI. There are a couple of alternate methods that might work to address this requirement. Did you create this or did it come from someone else? If someone else, they might be aware of the issue and have made the necessary changes. Or they are not aware of it but should be and can develop a change. I could try making a change but there is no way that I can test it. Dave Sand On Nov 8, 2018, at 2:42 PM, James Anderson <james_anderson_999@...> wrote: |
|
Locked
Re: Mentor for JMRI DecoderPro in Central MA?
¿ªÔÆÌåÓýDoug?Are using updated drivers for windows 10. I been using win 10 with nice power cab and pro. Had problems with the pro system until I got a newer updated usb to serial adapter.? Bob C On Nov 8, 2018, at 4:44 PM, Doug Lowing <delowing1903@...> wrote:
|
|
Locked
Re: Mentor for JMRI DecoderPro in Central MA?
Well, I know Sudro is in the area. He's been a long time part of the Amherst
Railway group that does the Springfield show at the end of January. I think he watches this list and may chime in. If not before the end of January, if you come to the show, I'll be there doing my clinics and help desk. -Ken Cameron, Member JMRI Dev Team www.jmri.org www.fingerlakeslivesteamers.org www.cnymod.com www.syracusemodelrr.org |
|
Locked
Re: NCE not reading AIU
Thanks guys. I will check when I get home and let you know. I do know that the leds on the AIU do light up as the locomotive moves across the layout. But wasn¡¯t able to get anything to read on layout editor.
toggle quoted message
Show quoted text
On Nov 8, 2018, at 1:33 PM, Dave Heap <dgheap@...> wrote: |
|
Locked
Re: Added sensors and logix to panels. The sensors and logix have disappeared
When I open up the "Tables->Sensors" I see many sensors (i have quite a few real sensors), but the ones that I added (virtual sensors) that are placed on the Panel (to form buttons) are missing. I see that they are in the XML though. Switching over to the Logix table, it's just an empty gray page (it might even be trying to show something but failing. And the panels seem to be incomplete -- the one panel is missing the virtual sensors I added. I sorted the list several times and they are clearly not in the displayed list. All the ones I added had Usernames and many, but not all, of the real sensors had Usernames.
I first added virtual sensors as a range (16 of them) and it pyut a colon (":") in the username. I didn't remove that from all of them Could that be part of the issue? Scott |
|
Locked
Re: Mentor for JMRI DecoderPro in Central MA?
¿ªÔÆÌåÓýDo you have a raspberry pi around? There¡¯s an image you can download with auto detection. Connection for NCE Powercab and DCC++ Arduino both worked at boot with 0 tinkering.
|
|
Locked
Mentor for JMRI DecoderPro in Central MA?
Doug Lowing
Hi all -
Anyone around the Amherst-Northampton MA area willing to help with JMRI Decoder Pro, in person? I could drive an hour or more if we set a time. I finally give up trying to get JMRI Decoder Pro to work on Win 10, communicating with either NCE PowerCab or DCC++ base station I have done the due diligence. I have read many messages, pages, and tried many configurations. I do not give up easily. And I have some knowledge of coding and communications. I even got it to work several years ago in earlier versions of JMRI and Win. Thanks much |
|
Locked
Re: Layout Editor, too much for RPi3?
Thanks but that doesn't work either. And I don't have this issue on an earlier layout with less sections so it just feels like the RPi is hitting an element limit for it's memory. Here's a picture of the same turnout working on the Pi on the simpler layout. My connection is over VNC which may also contribute. I'll have to test directly.
I noticed another oddity. If you turn off the grid in edit mode a lot of the "construction lines" get cut off on the right side. Happens on windows too. What are all those lines and what is there purpose. And regarding the?track segment control circles, their size gets adjusted when you adjust the turnout circle size option which doesn't seem like they should. |
|
Locked
Re: NCE not reading AIU
In the NCE Command Monitor:
toggle quoted message
Show quoted text
- If all AIU lights are off the return value should be 3f ff - If AIU light 1 is on and all others are off the return value should be 3f fe - If all AIU lights are on the return value should be 00 00 - If an AIU is not present at the specified address, the return value will be 00 00 -- Dave in Australia On 9 Nov 2018, at 5:00 AM, Michael Murphy <smurfmm@...> wrote: |
|
Locked
Re: Layout Editor, too much for RPi3?
On Linux and macOS, a control click will normally be more consistent in displaying the context menu.
toggle quoted message
Show quoted text
Dave Sand On Nov 8, 2018, at 2:39 PM, j_bernardini@... wrote: |
|
Locked
Re: BD20 block detection
¿ªÔÆÌåÓýAddress Range If your Power Cab firmware (second screen at startup of your Power Cab, after the "Pro Cab V1.3" message) is: - "V1.28C" the only valid addresses for extra cabs are 3 & (unofficially) 4. - "V1.65" the only valid addresses for extra throttles ?are 3, 4 and 5. Non-throttle devices such as the NCE USB, Mini Panel or AIU can also use addresses 8, 9 & 10. However if you have ever done a System Reset, you will have lost all the extra addresses and be back to the V1.28C restrictions. - "V1.65B" the only valid addresses for extra throttles ?are 3, 4 and 5. Non-throttle devices such as the NCE USB, Mini Panel or AIU can also use addresses 8, 9 & 10. Similar ?comments apply to the SB3/5 with the range 2-5 for V1.28 and 2-7 for V1.65B. Configuration Instructions Here are the best settings for JMRI and jumpers for Power Cab (and also SB5). Make sure you always unplug/replug both cables on the NCE USB after changing jumpers.? It also explains how to read the version of your NCE USB (only the first digit counts, the last three report how your jumpers 2-4 are set and jumper 1 is ignored on all systems). Power Cab Instructions The correct settings for a Power Cab V1.65 or V1.28 (as shown when the Power Cab starts up) and an NCE USB V6 (or you are not sure of the USB version) ?are: - All USB Jumpers off (or at least 2, 3 & 4. Jumper 1 is ignored). - JMRI preferences are: -- System manufacturer: NCE -- System connection: ?NCE USB -- Serial port: <whatever is appropriate for your system> -- USB version: V6.x.x -- System: PowerCab -- Additional Connection Settings checkbox ON --- Baud rate: 9600. The JMRI console log should then report V6.3.0. If it reports V7.3.0 and your Power Cab is V1.65, use the settings below instead. If you don't get a version number or the system does not work, Use Help->System Console...->Copy to clipboard and paste into a post for us to see. The correct settings for a Power Cab V1.65 or V1.65b and an NCE USB V7 ?are: - All USB Jumpers on (or at least 2, 3 & 4. Jumper 1 is ignored). - JMRI preferences are: -- System manufacturer: NCE -- System connection: ?NCE USB -- Serial port: <whatever is appropriate for your system> -- USB version: V7.x.x -- System: PowerCab -- Additional Connection Settings checkbox ON --- Baud rate: 19200. The JMRI console log should then report V7.3.7. SB5 Instructions The correct settings for an SB5 and an NCE USB V7 ?are: - USB Jumper 4 on. All others off (or at least 2 & 3. Jumper 1 is ignored). - JMRI preferences are: -- System manufacturer: NCE -- System connection: ?NCE USB -- Serial port: <whatever is appropriate for your system> -- USB version: V7.x.x -- System: SB5 -- Additional Connection Settings checkbox ON --- Baud rate: 19200. The JMRI console log should then report V7.3.1. General Troubleshooting If the system does not work after this: - If your SB5/Power Cab is V1.65 rather than V1.65B, you may have been affected by a firmware issue (triggered by a System Reset). - Your NCE USB may be set to a bad cab address (V7 only). ?In either case, go through the following : - Quit JMRI. - Ensure neither LED on the NCE USB is stuck ON. If so, power cycle the USB by unplugging it from the cab bus cable. - Ensure you have no other throttles connected. - Restart JMRI and immediately go to Configure USB Interface under the NCE menu. - Set the Cab ID to 3. - Attempt a JMRI operation (use a throttle, Identify a decoder). - The status line should stay green and it should work? -If this does not work, do not fiddle with any other settings but instead: -- Observe whether the Cab Bus LED on the NCE USB is stuck on and report back. -- Use Help->System Console...->Copy to clipboard and paste into a post for us to see. --? Dave in Australia On 9 Nov 2018, at 7:15 AM, Derekr <m1arfm0dfx@...> wrote:
Dave do all these settings for the PowerCab and AIU,s hold good for an SB5 i.e. USB jumpers and cab IDs. |
Ken Cameron
Paul Davidson
Bob