Unless you enjoy
this, I would not put time on it.
???? Not going but would give it to
someone, who has the time, for the cost of postage.
--
Jon Miller
For me time stopped in 1941
Digitrax Chief/Zephyr systems,
SPROG, JMRI User
NMRA Life member #2623
Member SFRH&MS
|
Locked
Re: OpenLCB - Lights - using 7.14.4ish -- WORKING
Hi Again Steve.
All lights are setup on the Fast Clock.
In doing the programming I would like to request that:
1. The Time Entry Dialog be changed to have the time "roll over"
when using the arrows.
2. It would be nice to have a total entry number at the bottom of
the Lights Table.
3. I could use a printout of the total Lights Table including On
and Off times. Output would be to a file like a .csv file for
entry into a program like Excel. I find it very useful to be able
to sort on times On and Off. This is a good check to make sure
that a bunch of lights are not turning on at the exact same time.
??Might be late October before a video is made.
Tim
On 9/5/2019 10:44 AM, steve young via
Groups.Io wrote:
toggle quoted message
Show quoted text
Hi Tim,
None of the lights posted above are set up for Fast Clock
Controllers ???
All on and off times for a single Light need to be unique.
I've developed a tweak to properly enforce this in the UI which
I'll submit to Github soon.
Hoping you post a video link when it's all up and running, I'm
intrigued how it's looking in real life!
Steve
|
Hi Tim,
I wrote an article on JMRI Operations that was published in the October 2013 issue of Model Railroad Hobbyist magazine.? I believe it's still available to download for free.? It's a bit out of date but the overall concepts are still valid.? Here's the link:
Hope this helps.
Cheers, Dennis Drury
Dayton, NV
The miracle is this: the more we share the more we have.
Leonard Nimoy
Hi Folks:
New member here -- looking at operations to generate switch lists for my N scale San Luis and Rio Grande.? Ive got the demo files loaded, but im kinda at a loss how to proceede from here -- is there a tutorial or video or something out there on how to use Operations within JMRI?
Thanks
TIM
|
Locked
Re: Scripting question - how to check if sensor or turnout name is valid
Thanks all, lots of good ways of doing it there.
I don't know how I missed that Jython has Try-Except - that will be very useful in other situations as well.?? Has it always had that capability?
|
The Umelec
ATL2054? is in DecoderPro
??? OK was able to read the CVs, I think.? I'm
using SPROG and DP.? However after reading CVs (motor was active
then) and then using the throttle I got no response from the
motor or forward/reverse lights (green, forward light stuck
on).? There is also an indication in the pane for the 2054 that
it's a sound decoder.? Is it?? There are solder pads on the
decoder that would indicate that additional wires need to be
added by the purchaser.? And maybe additional circuits.
--
Jon Miller
For me time stopped in 1941
Digitrax Chief/Zephyr systems,
SPROG, JMRI User
NMRA Life member #2623
Member SFRH&MS
|
Locked
Re: Error loading panel in 4.17.3
This is likely to be fixed in JMRI 4.17.4, due out in a day or two. Bob On Sep 9, 2019, at 7:57 AM, KEN <boomer17@...> wrote:
When JMRI ver. 4.15.8 is running, loading my panel does not show any errors in the system console.
I updated to 4.17.3 and my panel loads with these errors. Can I get some help please? Is there an east fix?
Thanks,Ken
2019-09-09 10:15:38,926 managers.AbstractManager ERROR - systemName is already registered. Current system name: IS01. New system name: IS1 [AWT-EventQueue-0]
2019-09-09 10:15:38,926 configurexml.ErrorHandler ERROR - Could not create sensor System name "IS1" in adaptor of type jmri.jmrix.internal.configurexml.InternalSensorManagerXml
See for possibly more information. [AWT-EventQueue-0]
2019-09-09 10:16:16,729 managers.AbstractManager ERROR - systemName is already registered. Current system name: IS010. New system name: IS10 [AWT-EventQueue-0]
2019-09-09 10:16:16,729 configurexml.ErrorHandler ERROR - Could not create sensor System name "IS10" in adaptor of type jmri.jmrix.internal.configurexml.InternalSensorManagerXml
See for possibly more information. [AWT-EventQueue-0]
2019-09-09 10:16:19,510 managers.AbstractManager ERROR - systemName is already registered. Current system name: IS011. New system name: IS11 [AWT-EventQueue-0]
2019-09-09 10:16:19,510 configurexml.ErrorHandler ERROR - Could not create sensor System name "IS11" in adaptor of type jmri.jmrix.internal.configurexml.InternalSensorManagerXml
See for possibly more information. [AWT-EventQueue-0]
2019-09-09 10:16:24,276 managers.AbstractManager ERROR - systemName is already registered. Current system name: IS012. New system name: IS12 [AWT-EventQueue-0]
2019-09-09 10:16:24,276 configurexml.ErrorHandler ERROR - Could not create sensor System name "IS12" in adaptor of type jmri.jmrix.internal.configurexml.InternalSensorManagerXml
See for possibly more information. [AWT-EventQueue-0]
2019-09-09 10:16:25,042 managers.AbstractManager ERROR - systemName is already registered. Current system name: IS013. New system name: IS13 [AWT-EventQueue-0]
2019-09-09 10:16:25,042 configurexml.ErrorHandler ERROR - Could not create sensor System name "IS13" in adaptor of type jmri.jmrix.internal.configurexml.InternalSensorManagerXml
See for possibly more information. [AWT-EventQueue-0]
2019-09-09 10:16:25,698 managers.AbstractManager ERROR - systemName is already registered. Current system name: IS014. New system name: IS14 [AWT-EventQueue-0]
2019-09-09 10:16:25,698 configurexml.ErrorHandler ERROR - Could not create sensor System name "IS14" in adaptor of type jmri.jmrix.internal.configurexml.InternalSensorManagerXml
See for possibly more information. [AWT-EventQueue-0]
2019-09-09 10:16:32,808 managers.AbstractManager ERROR - systemName is already registered. Current system name: IS02. New system name: IS2 [AWT-EventQueue-0]
2019-09-09 10:16:32,808 configurexml.ErrorHandler ERROR - Could not create sensor System name "IS2" in adaptor of type jmri.jmrix.internal.configurexml.InternalSensorManagerXml
See for possibly more information. [AWT-EventQueue-0]
2019-09-09 10:16:34,059 managers.AbstractManager ERROR - systemName is already registered. Current system name: IS03. New system name: IS3 [AWT-EventQueue-0]
2019-09-09 10:16:34,059 configurexml.ErrorHandler ERROR - Could not create sensor System name "IS3" in adaptor of type jmri.jmrix.internal.configurexml.InternalSensorManagerXml
See for possibly more information. [AWT-EventQueue-0]
2019-09-09 10:16:34,605 managers.AbstractManager ERROR - systemName is already registered. Current system name: IS04. New system name: IS4 [AWT-EventQueue-0]
2019-09-09 10:16:34,605 configurexml.ErrorHandler ERROR - Could not create sensor System name "IS4" in adaptor of type jmri.jmrix.internal.configurexml.InternalSensorManagerXml
See for possibly more information. [AWT-EventQueue-0]
2019-09-09 10:16:35,152 managers.AbstractManager ERROR - systemName is already registered. Current system name: IS05. New system name: IS5 [AWT-EventQueue-0]
2019-09-09 10:16:35,152 configurexml.ErrorHandler ERROR - Could not create sensor System name "IS5" in adaptor of type jmri.jmrix.internal.configurexml.InternalSensorManagerXml
See for possibly more information. [AWT-EventQueue-0]
2019-09-09 10:16:35,699 managers.AbstractManager ERROR - systemName is already registered. Current system name: IS06. New system name: IS6 [AWT-EventQueue-0]
2019-09-09 10:16:35,699 configurexml.ErrorHandler ERROR - Could not create sensor System name "IS6" in adaptor of type jmri.jmrix.internal.configurexml.InternalSensorManagerXml
See for possibly more information. [AWT-EventQueue-0]
2019-09-09 10:16:36,246 managers.AbstractManager ERROR - systemName is already registered. Current system name: IS07. New system name: IS7 [AWT-EventQueue-0]
2019-09-09 10:16:36,246 configurexml.ErrorHandler ERROR - Could not create sensor System name "IS7" in adaptor of type jmri.jmrix.internal.configurexml.InternalSensorManagerXml
See for possibly more information. [AWT-EventQueue-0]
2019-09-09 10:16:36,762 managers.AbstractManager ERROR - systemName is already registered. Current system name: IS08. New system name: IS8 [AWT-EventQueue-0]
2019-09-09 10:16:36,762 configurexml.ErrorHandler ERROR - Could not create sensor System name "IS8" in adaptor of type jmri.jmrix.internal.configurexml.InternalSensorManagerXml
See for possibly more information. [AWT-EventQueue-0]
2019-09-09 10:16:37,324 managers.AbstractManager ERROR - systemName is already registered. Current system name: IS09. New system name: IS9 [AWT-EventQueue-0]
2019-09-09 10:16:37,324 configurexml.ErrorHandler ERROR - Could not create sensor System name "IS9" in adaptor of type jmri.jmrix.internal.configurexml.InternalSensorManagerXml
See for possibly more information. [AWT-EventQueue-0]
-- Bob Jacobsen rgj1927@...
|
Locked
Re: Error loading panel in 4.17.3
Ken,
Sometime in the last year a number of internal changes have happened with
treatment of system names. It would seem the rule being applied to Internal
system names was treating the part after the "IS" as a value and not a
simple string. For some system connections, that's important. For Internal,
that may not be true. Anyway it is seeing IS01 and IS1 as the same sensor,
and your old panel seems to have both. Same with the others, it doesn't
think the ones with a leading zero are different. Right now the simple
solution is to change those names.
If you need help with that trick, let me know. I've not seen your name
around lately.
-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.org
www.syracusemodelrr.org
|
Jim,
With respect , The only thing that the LokProgrammer does is provide the user to load new firmware into the decoder. All other aspects of programming a decoder are available in DecoderPro. Since the firmware is proprietary to ESU, just like QSI, Lionel, and MTH, you cannot reasonably expect anyone to give up their intellectual property.? They spent the money for the research and development .
If you purchase enough Loksound decoders, then the purchase of the programmer is nominal since you can then install new sound files, upgrade firmware and even change them from steam to diesel. I am by no means wealthy but I purchased enough of both ESU and QSI decoders to make the investments. If you think about it , all you need to do is use the money for one sound decoder and speaker and put it towards the programmer and you have solved your problem.
If you belong to a club or have a regular group you model with, you could each chip in for it and even make group purchases of decoders to get a better deal.
Just a few thoughts.
Enjoy the fun and keep modeling, Nick Kulp
"I'm not a failure. I started at the bottom and I found it easily attainable. Life is too short to set unattainable goals"
- Nick Kulp
An addition to JMRI that was a LOK programmer pgm would be fantastic. ESU would not like it because it would cut into their LokProgrammer ($145.00) sales.
Jim K
|
Locked
Error loading panel in 4.17.3
When JMRI ver. 4.15.8 is running, loading my panel does not show any errors in the system console.
I updated to 4.17.3 and my panel loads with these errors. Can I get some help please? Is there an east fix?
Thanks,Ken
2019-09-09 10:15:38,926 managers.AbstractManager????????????? ERROR - systemName is already registered. Current system name: IS01. New system name: IS1 [AWT-EventQueue-0]
2019-09-09 10:15:38,926 configurexml.ErrorHandler???????????? ERROR - Could not create sensor System name "IS1" in adaptor of type jmri.jmrix.internal.configurexml.InternalSensorManagerXml
See http://jmri.org/help/en/package/jmri/configurexml/ErrorHandler.shtml for possibly more information. [AWT-EventQueue-0]
2019-09-09 10:16:16,729 managers.AbstractManager????????????? ERROR - systemName is already registered. Current system name: IS010. New system name: IS10 [AWT-EventQueue-0]
2019-09-09 10:16:16,729 configurexml.ErrorHandler???????????? ERROR - Could not create sensor System name "IS10" in adaptor of type jmri.jmrix.internal.configurexml.InternalSensorManagerXml
See http://jmri.org/help/en/package/jmri/configurexml/ErrorHandler.shtml for possibly more information. [AWT-EventQueue-0]
2019-09-09 10:16:19,510 managers.AbstractManager????????????? ERROR - systemName is already registered. Current system name: IS011. New system name: IS11 [AWT-EventQueue-0]
2019-09-09 10:16:19,510 configurexml.ErrorHandler???????????? ERROR - Could not create sensor System name "IS11" in adaptor of type jmri.jmrix.internal.configurexml.InternalSensorManagerXml
See http://jmri.org/help/en/package/jmri/configurexml/ErrorHandler.shtml for possibly more information. [AWT-EventQueue-0]
2019-09-09 10:16:24,276 managers.AbstractManager????????????? ERROR - systemName is already registered. Current system name: IS012. New system name: IS12 [AWT-EventQueue-0]
2019-09-09 10:16:24,276 configurexml.ErrorHandler???????????? ERROR - Could not create sensor System name "IS12" in adaptor of type jmri.jmrix.internal.configurexml.InternalSensorManagerXml
See http://jmri.org/help/en/package/jmri/configurexml/ErrorHandler.shtml for possibly more information. [AWT-EventQueue-0]
2019-09-09 10:16:25,042 managers.AbstractManager????????????? ERROR - systemName is already registered. Current system name: IS013. New system name: IS13 [AWT-EventQueue-0]
2019-09-09 10:16:25,042 configurexml.ErrorHandler???????????? ERROR - Could not create sensor System name "IS13" in adaptor of type jmri.jmrix.internal.configurexml.InternalSensorManagerXml
See http://jmri.org/help/en/package/jmri/configurexml/ErrorHandler.shtml for possibly more information. [AWT-EventQueue-0]
2019-09-09 10:16:25,698 managers.AbstractManager????????????? ERROR - systemName is already registered. Current system name: IS014. New system name: IS14 [AWT-EventQueue-0]
2019-09-09 10:16:25,698 configurexml.ErrorHandler???????????? ERROR - Could not create sensor System name "IS14" in adaptor of type jmri.jmrix.internal.configurexml.InternalSensorManagerXml
See http://jmri.org/help/en/package/jmri/configurexml/ErrorHandler.shtml for possibly more information. [AWT-EventQueue-0]
2019-09-09 10:16:32,808 managers.AbstractManager????????????? ERROR - systemName is already registered. Current system name: IS02. New system name: IS2 [AWT-EventQueue-0]
2019-09-09 10:16:32,808 configurexml.ErrorHandler???????????? ERROR - Could not create sensor System name "IS2" in adaptor of type jmri.jmrix.internal.configurexml.InternalSensorManagerXml
See http://jmri.org/help/en/package/jmri/configurexml/ErrorHandler.shtml for possibly more information. [AWT-EventQueue-0]
2019-09-09 10:16:34,059 managers.AbstractManager????????????? ERROR - systemName is already registered. Current system name: IS03. New system name: IS3 [AWT-EventQueue-0]
2019-09-09 10:16:34,059 configurexml.ErrorHandler???????????? ERROR - Could not create sensor System name "IS3" in adaptor of type jmri.jmrix.internal.configurexml.InternalSensorManagerXml
See http://jmri.org/help/en/package/jmri/configurexml/ErrorHandler.shtml for possibly more information. [AWT-EventQueue-0]
2019-09-09 10:16:34,605 managers.AbstractManager????????????? ERROR - systemName is already registered. Current system name: IS04. New system name: IS4 [AWT-EventQueue-0]
2019-09-09 10:16:34,605 configurexml.ErrorHandler???????????? ERROR - Could not create sensor System name "IS4" in adaptor of type jmri.jmrix.internal.configurexml.InternalSensorManagerXml
See http://jmri.org/help/en/package/jmri/configurexml/ErrorHandler.shtml for possibly more information. [AWT-EventQueue-0]
2019-09-09 10:16:35,152 managers.AbstractManager????????????? ERROR - systemName is already registered. Current system name: IS05. New system name: IS5 [AWT-EventQueue-0]
2019-09-09 10:16:35,152 configurexml.ErrorHandler???????????? ERROR - Could not create sensor System name "IS5" in adaptor of type jmri.jmrix.internal.configurexml.InternalSensorManagerXml
See http://jmri.org/help/en/package/jmri/configurexml/ErrorHandler.shtml for possibly more information. [AWT-EventQueue-0]
2019-09-09 10:16:35,699 managers.AbstractManager????????????? ERROR - systemName is already registered. Current system name: IS06. New system name: IS6 [AWT-EventQueue-0]
2019-09-09 10:16:35,699 configurexml.ErrorHandler???????????? ERROR - Could not create sensor System name "IS6" in adaptor of type jmri.jmrix.internal.configurexml.InternalSensorManagerXml
See http://jmri.org/help/en/package/jmri/configurexml/ErrorHandler.shtml for possibly more information. [AWT-EventQueue-0]
2019-09-09 10:16:36,246 managers.AbstractManager????????????? ERROR - systemName is already registered. Current system name: IS07. New system name: IS7 [AWT-EventQueue-0]
2019-09-09 10:16:36,246 configurexml.ErrorHandler???????????? ERROR - Could not create sensor System name "IS7" in adaptor of type jmri.jmrix.internal.configurexml.InternalSensorManagerXml
See http://jmri.org/help/en/package/jmri/configurexml/ErrorHandler.shtml for possibly more information. [AWT-EventQueue-0]
2019-09-09 10:16:36,762 managers.AbstractManager????????????? ERROR - systemName is already registered. Current system name: IS08. New system name: IS8 [AWT-EventQueue-0]
2019-09-09 10:16:36,762 configurexml.ErrorHandler???????????? ERROR - Could not create sensor System name "IS8" in adaptor of type jmri.jmrix.internal.configurexml.InternalSensorManagerXml
See http://jmri.org/help/en/package/jmri/configurexml/ErrorHandler.shtml for possibly more information. [AWT-EventQueue-0]
2019-09-09 10:16:37,324 managers.AbstractManager????????????? ERROR - systemName is already registered. Current system name: IS09. New system name: IS9 [AWT-EventQueue-0]
2019-09-09 10:16:37,324 configurexml.ErrorHandler???????????? ERROR - Could not create sensor System name "IS9" in adaptor of type jmri.jmrix.internal.configurexml.InternalSensorManagerXml
See http://jmri.org/help/en/package/jmri/configurexml/ErrorHandler.shtml for possibly more information. [AWT-EventQueue-0]
|
Hi Tim
If you're an NMRA member you can view my clinic on JMRI Ops from Cleveland 2014?
If that doesn't work the slides are on my website ?www. bhamrails. info ?under model railroading?
|
Locked
Re: Handling of RPI-JMRI (instead of Re: Engine Driver problems)
Jim
Several roads lead to Rome, as we say. No matter how, with Pi accessories or a computer, important is to make a backup.
Of course, every write/copy should follow a verify. Half a century ago this needed a second command under C/PM or DOS. I don't know if the Pi accessory variant makes that automatically, Etcher does when writing an image onto the SD-card, Win32DiskImager needs a second click on the verify button, after reading an SD-card and writing its contents into an image file on the computer or after writing an image file onto the SD-card..
Testing is only applicable if you backup to another SD-card. But verifying the data is mandatory in my eyes. Maybe I'm too much used to it, that I forgot to mention.
Daniel Sieber
Zurich, Switzerland
|
Here's the link to the help files:
There's a reference to a tutorial in the Quick Start Help section.
Dan
|
Locked
Re: Handling of RPI-JMRI (instead of Re: Engine Driver problems)
Peter, Daniel:
On the Pi, if being run with keyboard mouse and video (or VNC remote) you can use the onboard tool to copy your SD. Accessories > SD Copier... I've used that to copy to SD and USB drives directly from the Pi. So a few less steps to back up.
Quite right Daniel... no such thing as too many back ups... as long as they're dated and occasionally tested... With the Pi that's easy burn the SD and boot from the back up.
The tested is critical, I had back up software that an update didn't run correctly and didn't change to a new data format. Years later when I needed it the data wasn't readable... outdated format that the vendor no longer supported. And they were not interested in helping... Name? they're gone and wonder why?
Jim Albanowski
|
Locked
Handling of RPI-JMRI (instead of Re: Engine Driver problems)
Peter ? This is actually not an Engine Driver problem but one of you(r Pi). ? Obviously, you made your own RPI-JMRI installation on your Pi with using NOOBS ¨C only then you have the OS re-installation feature with the shift-key, which caused/causes loss not only of your JMRI installation but also of all later updates and all your configurations (Raspbian and JMRI) ¨C AND you did not save an image of your SD-card as long as it was functioning (aka BACKUP your data). ? Because you seem to have a Pi3 I¡¯d suggest to use the RPI-JMRI image prepared by Steve Todd (download from ). ? If you intend to setup all by yourself again, start with a ¡°Raspbian Buster with desktop¡± image rather than with NOOBS (download from - here you don¡¯t have the re-installation option/risk with the shift-key). Particularly if you¡¯re using an 8 GB SD-card. ¨C NOOBS uses a considerable amount of memory by itself and installs plenty ¡°recommended software¡± you won¡¯t ever need on an RPi-JMRI access point to control trains. Both eat up a lot of SD-card memory and soon there is not enough for JMRI, if your SD-card is not at least 16 GB or bigger. ? I think, this is quicker than trying to repair the mess you¡¯ve made. ? Bring your Raspian Buster to latest state with update/upgrade in every case. ? Once you have an RPi-JMRI installation configured and working on your Pi, then _SAVE_ that SD-card image into a file on your computer with Win32DiskImager (download from ). Although raspberrypi.org recommends Etcher for flashing images onto SD-cards, Etcher cannot save SD-card contents into an image file on the computer. Win32DiskImager can do both. ¨C I personally like to use Etcher to flash SD-cards and Win32DiskImager to save SD-card contents into an image file on the computer. ? _REPEAT SAVING_ ?your SD-card image every time after you changed something (f.e. Raspian updates, changes in or of JMRI). Use different file names for each saved SD-card image (f.e. include a date code like 2019-09-08 at the beginning or within the file name, maybe even with time or an added suffix like a, b, c, d, ¡ for more than one image saved at the same day). Then, you can relax next time and only fire your latest image again onto the SD-card. If something goes wrong, you can easily use the previous state of your SD-card image. Delete malfunctioning images as soon as you have a newer good one, only keep good image files. ? Additionally, I recommend transferring/saving the whole directory ¡°/home/pi/JMRI_UserFiles¡± with WinSCP (download from ) from the Pi to your computer (over WLAN or Ethernet) whenever you are saving the SD-card image. Therein are all your JMRI configurations and rooster files. If you have to do a new installation, transfer this directory back onto your Pi with WinSCP (what is not possible out of a saved SD-card image file). You might need to do a rebuild rooster within JMRI after installation of a newer JMRI but all your locos and decoder data is there (unless you don¡¯t have this directory assigned for user files in the JMRI preferences, which is strongly recommended. Never use the JMRI program directory for user files as this is deleted by a JMRI update.). ? Sure, I love redundancy. But better have two backups than none. My last loss of some data occurred 1988 (during an intercontinental move of my home). Ever since no computer crash, disk failure, virus or user mishap caused me headache, only needed a bit of time for restoration. ? ? Daniel Sieber Zurich, Switzerland ?
|
Locked
Re: Multiple Openlcb Conections
Don,
To amplify a little bit on what Bob has just said. The nature of LCC is that there will be no conflicts created by connecting the two systems to each other to make it into one. Because it is a peer-peer network, that extends to running multiple computers such as a Windows or Mac machine for one purpose and Linux on a Pi for experimenting or some other purpose. All messages will show up at any node that wants to use them. For example just as soon as you get some experimental Arduino talking to LCC, its functionality will be available to your 'main' system. You could build a JMRI CTC panel on one machine and do your CDI configuration with the other. The system can support both functions simultaneously on the same network bus.
If your wiring doesn't allow you to loop one network into the other easily, then use a Repeater to join the two segments. If your concern is power isolation, then place the Repeater between two Power Points. That will allow you to power down one segment without disturbing the other.
Dick :)
toggle quoted message
Show quoted text
On 9/8/2019 11:05 PM, Bob Jacobsen wrote: If messages are to show up on both, why are you trying to keep them separate? Is there some other isolation you¡¯d like to enforce?
You could write a script to listen for frames on one interface and send them to the other, and vice-versa. JMRI also has the start of work on an internal hub that¡¯s meant to combine connections but (1) it was meant for network connections, not wired ones; I¡¯m not sure whether that makes a difference and (2) as far as I know it was never completed. It might be easier for somebody to finish that than to write a new script.
Bob
On Sep 6, 2019, at 1:57 PM, dsj782@... wrote:
I am also trying two different LCC/Openlcb buss's. The main one is RR-CIRKTS cards. The second is for testing with Raspberry PIs and Arduinos.
I would like an event to show up on both busses. --
Bob Jacobsen
rgj1927@...
|
Locked
Re: Multiple Openlcb Conections
If messages are to show up on both, why are you trying to keep them separate? Is there some other isolation you¡¯d like to enforce? You could write a script to listen for frames on one interface and send them to the other, and vice-versa. JMRI also has the start of work on an internal hub that¡¯s meant to combine connections but (1) it was meant for network connections, not wired ones; I¡¯m not sure whether that makes a difference and (2) as far as I know it was never completed. It might be easier for somebody to finish that than to write a new script. Bob On Sep 6, 2019, at 1:57 PM, dsj782@... wrote:
I am also trying two different LCC/Openlcb buss's. The main one is RR-CIRKTS cards. The second is for testing with Raspberry PIs and Arduinos.
I would like an event to show up on both busses. -- Bob Jacobsen rgj1927@...
|
Locked
Re: Multiple Openlcb Conections
Nom,
Your original posting does not indicate whether you want two-way communication or only need master-slave communication. Followup postings seem to indicate that you are concerned with Sensors and Turnouts, but perhaps other kinds of device messages might also be involved. Do your turnouts provide feedback status reports?
I have no hands-on experience with OpenLCB, but it seems fair to ask if one bus can be hardware connected to the other. If even remotely possible, that might provide a more robust method for sharing message events.
It is not clear to me that this TurnoutsMasterSlave script even partially answers your question or even provides some clues to your puzzle. The default prefixes for DCC connections have changed since it was written, so some careful editing would be necessary.
Even if it works for Turnouts Master-Slave messages, a lot of work would be needed for two-way communication. Some further work would also be required for Sensors in either case.
Cliff in Baja SoCal
|
It's been a hard weekend.
A fellow club member had set up a Raspberry Pi so we could use our smart phones as throttles to operate the layout using Engine Driver.
It was working a treat until just after he left mid afternoon when suddenly the throttles lost contact with the modem. I tried various things, ending with a couple of reboots of the whole system, but to no avail.
It was then that I lost my presence of mind as someone once put it, and as the Pi booted up I held down Shift. I did get a warning about losing all my data but didn't heed it. It seems I then reinstalled the OS and in the process deleted all the JMRI stuff.
I realised I was then in deep trouble but not to worry I thought, I can make an image file from the JMRI download, follow the instructions and all will be sweet.
Well, no actually. I did as it says. With the DCC system all connected and the Pi turned off I inserted the SD card with image file on it and then powered up the Pi. Once it had booted some lines of code started filling the screen but it only got about 4/5 the way down the first screen when it hung.
There are two image file versions on the JMRI website so 'maybe I'm using the wrong one' I thought. Much time went by while I download the other zip file, unzipped it, Diskimagered it and wrote it to the SD card. I then followed the procedure, exact same result.
So I then turned to my laptop. I got some help from this group last year with getting this to work, and it did, last year. Same equipment, same everything, but this time the phones and the modem refused to speak to each other.
The DCC system is Lenz LZV100 with 23151 USB interface.
Pi is over a year old, so I assume a 3.
I've uploaded screenshots into a photo album named Petrosnz showing the hung Pi, the working DecoderPro throttle and the non-working Wi Throttle.
The phones were not receiving any broadcast and entering its IP address and the correct port into a phone did not work. (The phones were of course connected by wi fi to the modem ... and the interface connected by cable to a Lan port on the modem.)
The DecoderPro throttle was working fine, so the problem appears to be with the modem/phone communication ... which had been working the previous day, you may recall.
The previous day's IP address didn't work either, by the way.
As I've said, there are a couple of photos.
Can somebody make sense of this please.
Peter
---
This email has been checked for viruses by AVG.
|
Locked
Re: Seeking advice on session planning using Operations and CATS
Gary
I'm responsible for my layout as well as 3 others. I've incorporated automations into all of them so there is less "human" input when the JMRI input is needed. But remember, if train 1234 is at your main class yard, the cars are not available for another train until train 1234 leaves. I've added a lot of things into the other layouts so the building of trains and the creation of the paperwork is all choreographed with the movement of the JMRI train icons on the JMRI dispatchers panel. Using CATS is only done here on my layout. But the automations are still the same. The need to think how the program sees the availability of cars is a must for great car movements. When a train arrives into a class yard, just have the automation move that train and the next automation can now create a new one with the cars in that class yard made available for the build.
later
Dave
Trempealeau WI
|
Jim, On 9 Sep 2019, at 9:38 AM, Jim Kirwan via Groups.Io <cact25@...> wrote:
An addition to JMRI that was a LOK programmer pgm would be fantastic. ESU would not like it because it would cut into their LokProgrammer ($145.00) sales. The ESU LokProgrammer uses special undisclosed proprietary hardware and undisclosed proprietary communications protocol to communicate with the decoder. No other DCC system is hardware capable of this and JMRI can't do it. Dave in Australia
|
Bob Jacobsen
Ken Cameron