Locked
Re: Test release 4.7.6 available
Good morning JMRI... I would very much like to "test" the newest release, BUT Norton on My Win10 machine tells me it is not safe and then deletes the download... It claims the threat is "WS.Reputation.1"... Tried it three times already this morning... On 6/17/2017 6:24 AM, Bob Jacobsen rgj1927@... [jmriusers] wrote: Test version 4.7.6 of JMRI/DecoderPro is available for download. [snip snip] -- Modular Railroading is FUN!!! See us at these shows: Jan 27 - 28, 2018: Amherst Railway Society, West Springfield, MA =========== Sudro ===========
|
Locked
Re: Signal Heads, signal masts, main and advance signals.
Are you trying to use it with SignalHeads or SignalMasts? If SignalHeads, make sure they¡¯re both defined before the script runs, e.g. in a panel file. It references the Heads without creating them. If SignalMasts, change these lines (the arrows are indents, which should be the same as the original) ->self.inSignal = signals.getSignalHead(inputName) ->self.outSignal = signals.getSignalHead(outputName) to ->self.inSignal = masts.getSignalMast(inputName) ->self.outSignal = masts.getSignalMast(outputName) and ->self.outSignal.setAppearance(self.inSignal.getAppearance()) to ->self.outSignal.setAspect(self.inSignal.getAspect()) Sorry for the trouble. I¡¯ll add a script that does that shortly. Bob On Jun 17, 2017, at 5:23 AM, oschreibke@... [jmriusers] <jmriusers@...> wrote:
Hi Bob,
I tried to use the SignalFollower.py script, but get errors logged.
Information from the log:
PanelPro version 4.6-R81496dc starts under Java 1.8.0_77 on Linux amd64 v4.4.0-79-generic at Sat Jun 17 13:22:37 CEST 2017 [main]
Starting with profile Inglenook_Sidings_Simulator.3e3d4a8e [main]
..
Run file /home/user/.jmri/Inglenook_Sidings_Simulator/SignalFollower.py [main]
python 2.7 is provided by jython 2.7.0 [main]
ECMAScript ECMA - 262 Edition 5.1 is provided by Oracle Nashorn 1.8.0_77 [main]
ERROR - Error in script /home/user/.jmri/Inglenook_Sidings_Simulator/SignalFollower.py. [main]
javax.script.ScriptException: AttributeError: 'NoneType' object has no attribute 'addPropertyChangeListener' in <script> at line number 30
My Script:
# Has one SignalHead follow the state of another/
# Use this is you have e.g. a "repeater" signal head
# on the fascia that shows the appearance of a head
# on the layout
#
# Author: Bob Jacobsen, copyright 2016
# Part of the JMRI distribution
import jmri
import java
# Define the listener.
class SignalFollowerListener(java.beans.PropertyChangeListener):
def set(self, inputName, outputName) :
self.inSignal = signals.getSignalHead(inputName)
self.outSignal = signals.getSignalHead(outputName)
self.inSignal.addPropertyChangeListener(self)
return
def propertyChange(self, event):
self.outSignal.setAppearance(self.inSignal.getAppearance())
return
# Example of use - add a line like the following
# that includes system or user names for the signal head to be repeated,
# and the signal head to repeat it onto. These must already exist.
# SignalFollowerListener().set("CH2001","CH2001R")
# SignalFollowerListener().set("CH2002","CH2002R")
# SignalFollowerListener().set("ih1","ih4")
SignalFollowerListener().set("SBB Main 3","SBB Vorsignal")
I've tried with both the system name and the user name: both fail.
Have I missed something in the set up?
Do the scripts in the jython folder of JMRI.4.6 get run at start up? If so have I created a duplicate class?
Regards
Otto
-- Bob Jacobsen rgj1927@...
|
Locked
Re: Signal Heads, signal masts, main and advance signals.
Hi Bob,
I tried to use the SignalFollower.py script, but get errors logged.
Information from the log:
PanelPro version 4.6-R81496dc starts under Java 1.8.0_77 on Linux amd64 v4.4.0-79-generic at Sat Jun 17 13:22:37 CEST 2017 [main]
Starting with profile Inglenook_Sidings_Simulator.3e3d4a8e [main]
...
Run file /home/user/.jmri/Inglenook_Sidings_Simulator/SignalFollower.py [main]
python 2.7 is provided by jython 2.7.0 [main]
ECMAScript ECMA - 262 Edition 5.1 is provided by Oracle Nashorn 1.8.0_77 [main]
ERROR - Error in script /home/user/.jmri/Inglenook_Sidings_Simulator/SignalFollower.py. [main]
javax.script.ScriptException: AttributeError: 'NoneType' object has no attribute 'addPropertyChangeListener' in <script> at line number 30
My Script:
# Has one SignalHead follow the state of another/
# Use this is you have e.g. a "repeater" signal head
# on the fascia that shows the appearance of a head
# on the layout
#
# Author: Bob Jacobsen, copyright 2016
# Part of the JMRI distribution
import jmri
import java
# Define the listener.
class SignalFollowerListener(java.beans.PropertyChangeListener):
def set(self, inputName, outputName) :
self.inSignal = signals.getSignalHead(inputName)
self.outSignal = signals.getSignalHead(outputName)
self.inSignal.addPropertyChangeListener(self)
return
def propertyChange(self, event):
self.outSignal.setAppearance(self.inSignal.getAppearance())
return
# Example of use - add a line like the following
# that includes system or user names for the signal head to be repeated,
# and the signal head to repeat it onto. These must already exist.
# SignalFollowerListener().set("CH2001","CH2001R")
# SignalFollowerListener().set("CH2002","CH2002R")
# SignalFollowerListener().set("ih1","ih4")
SignalFollowerListener().set("SBB Main 3","SBB Vorsignal")
I've tried with both the system name and the user name: both fail.
Have I missed something in the set up?
Do the scripts in the jython folder of JMRI.4.6 get run at start up? If so have I created a duplicate class?
Regards
Otto
|
Locked
Re: 1156 Bulbs On Switch Frogs
Richard:
The 1156 while unloved do work...
In your case though in working they are indicating a real short in the switch. Frequently in switch shorts they are solid as in running into a closed point but rather quick "flicks" where a wheel back brushes the open point. I would suspect that in those cases the slow action of the 1156 lets the wheel past it's contact and the engine keeps going.
A friend uses the 1156 over the entire RR with good results. This is almost fully sound equipped with all different brands of decoders. He does however have all DCC friendly switches.
Jim Albanowski
<snip>
|
Locked
Re: 1156 Bulbs On Switch Frogs
I've never been a fan of 1156 bulbs for current limiting. I prefer fast-acting/fast-reset DCC circuit breakers.
Your test light shows the problem. Draw sufficient current and the 1156 in the feeder from the Tortoise drops the voltage too much (only in the absence of a direct feed from a stock rail). The TCS WOW (along with many sound decoders) is relatively power hungry and the voltage drop of the combined decoder sound amplifier, internal logic chips plus motor and lights is sufficient to shut down the decoder briefly. The dropout voltage is usually quite high (varies from brand to brand) so not unexpected behaviour.
--
Dave in Australia
toggle quoted message
Show quoted text
On 17 Jun 2017, at 1:46 PM, rstamm4@... [jmriusers] <jmriusers@...> wrote:
I know this is not directly JMRI related, but I think this is the best DCC forum to mention this observation. For many years I have wired 1156 automotive light bulbs in series with my frog feeders to prevent a short at the switch points, such as from running a closed switch, from taking down my DCC system (Digitrax). I only make cuts on the frog rails on the side away from the points. So in theory, if I have a bad connection between the points and the stock rail, the connection to the frog, through the 1156, will supply power to the frog via the back contacts on a Tortise. Recently I noticed that I had several turnouts where the sound would disappear when a train went through (TCS WOW). Utilizing a test light (another 1156) I discovered that the light was only about half as bright in the areas where the sound disappeared. Cleaning the points and stock rail connection restore the light to full brightness and the sound returned. As an experiment I installed a thin piece of plastic between the stock rail and the points and observed the same situation. Before sound decoders, this wasn't an issue, but now it seems that preventing one problem (a short) can create another (loss of sound). Has anyone else observed this situation?
|
Locked
Test release 4.7.6 available
Test version 4.7.6 of JMRI/DecoderPro is available for download.
This is the next in a series of test releases that will culminate in a production release, hopefully in June 2017.
There have been a lot of updates in this version, so it should be considered experimental.
For more information on the issues, new features and bug fixes in 4.7.6 please see the release note:
<>
Note that JMRI is made available under the GNU General Public License. For more information, please see our copyright and licensing page.
<>
The download links, along with lots of other information which we hope you'll read, can be found on the release note page:
<>
Bob
--
Bob Jacobsen
rgj1927@...
|
Locked
Re: What protocol is easier for turnout/signals via arduino
Another option is OpenLCB, which according to its proponents is "the future".
It is an event message based approach. What this means is that it is not necessary to poll a sensor. It will send a message when a change happens.
I'm trying to implement the basic protocols on arduino nanos with an ESP8266 wifi gateway to JMRI. It's not yet complete, but what I have so far seems to be working.
If I read your post correctly, you haven't built the transport layer yet. OpenLCB uses a CAN bus rather than RJ45. MCP2515 SPI-CAN adapters are available cheaply from China. I got mine from Tx-Hang's ebay store.
Regards
Otto
|
Locked
Re: What protocol is easier for turnout/signals via arduino
OK thanks I'll look into it.
Emmanuel
|
Locked
Re: Signal Heads, signal masts, main and advance signals.
Thanks, Bob, for your reply.
I think I was fixed on the physical appearance of the mast. I like the suggestion of placing the two masts at the same location: simple, elegant and avoids having to define out the various combinations.
I'll take a look at the script you mentioned, that should do the trick.
Thanks again
Regards
Otto
|
Locked
Re: Test version 4.7.5 of JMRI/DecoderPro is available for download
Bob
I have loaded 4.7.5 onto my windows 10 PC running on the layout and on the simulator PC. The layout uses a digitrax dcs 100 and RR circuits USB rev n.
All panels, rosters, routes and logic working OK
An amazing program many hours of enjoyment operating the layout and Improving the layout panels
Still a long way to go though
Peter Riley
London.UK
toggle quoted message
Show quoted text
On 11 Jun 2017, at 19:53, DAVID KLEMM davidklemm7511@... [jmriusers] <jmriusers@...> wrote:
Bob,
I upgraded the NMMRC 5000 square foot layout from 4.5.2 to 4.7.5 today. All went well. I keep a copy of the club panels on my home laptop and do upgrades there first. You helped me with the one issue a couple weeks ago and since the panels had ran fine on 4.5.2 the whole time we made the jump.
Main motivation was we have a 240 that we had not put in to service due to timeout issues when programming devices. Given the work on the 240 and other bug fixes we made the jump. I hooked up the 240 and ran basic test today and all seems fine.
Only side note is our script to initialize sensors and turnouts seems to run slower. Gone from seconds to 10s of seconds, but less than a minute. That I will watch.
So far all is running fine controlling all our signals, turnouts etc.
David
________________________________
From: jmriusers@... <jmriusers@...> on behalf of Bob Jacobsen rgj1927@... [jmriusers] <jmriusers@...>
Sent: Friday, June 9, 2017 10:11 AM
To: mopacmike@... [jmriusers]
Subject: [jmriusers] Test version 4.7.5 of JMRI/DecoderPro is available for download
Test version 4.7.5 of JMRI/DecoderPro is available for download.
This is the next in a series of test releases that will culminate in a production release, hopefully in late June or early July 2017.
This is the last test release with significant changes before the production release. We¡¯d appreciate you testing it, as the earlier we can find any issues, the better.
If you use JMRI on Linux or Mac and are updating from an earlier version, there¡¯s a necessary migration step. (Not needed on Windows) Please see the release note for details: <>
For more information on the issues, new features and bug fixes in 4.7.5 please see the release note:
<>
Note that JMRI is made available under the GNU General Public License. For more information, please see our copyright and licensing page.
<>
The download links, along with lots of other information which we hope you'll read, can be found on the release note page:
<>
Bob
--
Bob Jacobsen
rgj1927@...
[Non-text portions of this message have been removed]
------------------------------------
------------------------------------
------------------------------------
Yahoo Groups Links
|
Locked
Re: 1156 Bulbs On Switch Frogs
Hi Richard, There's a lot of wiring expertise on this group, certainly, but actually, the best group for this is probably WiringForDCC. Wouter On 17 June 2017 at 04:46, rstamm4@... [jmriusers] < jmriusers@...> wrote:
I know this is not directly JMRI related, but I think this is the best DCC
forum to mention this observation. For many years I have wired 1156
automotive light bulbs in series with my frog feeders to prevent a short at
the switch points, such as from running a closed switch, from taking down
my DCC system (Digitrax). I only make cuts on the frog rails on the side
away from the points. So in theory, if I have a bad connection between the
points and the stock rail, the connection to the frog, through the 1156,
will supply power to the frog via the back contacts on a Tortise. Recently
I noticed that I had several turnouts where the sound would disappear when
a train went through (TCS WOW). Utilizing a test light (another 1156) I
discovered that the light was only about half as bright in the areas where
the sound disappeared. Cleaning the points and stock rail connection
restore the light to full brightness and the sound returned. As an
experiment I installed a thin piece of plastic between the stock rail and
the points and observed the same situation. Before sound decoders, this
wasn't an issue, but now it seems that preventing one problem (a short) can
create another (loss of sound). Has anyone else observed this situation?
Richard Stamm
Modeling the Colorado Midland in 1905
.
willcallhandyman.com/ColoradoMidland/
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
|
Locked
Re: Signal Heads, signal masts, main and advance signals.
For the first question, I suggest _not_ trying to combine them. Place two masts at the location, one defined to display as the ¡°home¡± for there, and separately one to show for the ¡°distant¡±. To have one signal completely follow another, no changes at all, I suggest writing a script like (That one's for SignalHeads, but you could do it for SignalMasts two if you¡¯d like) Bob On Jun 16, 2017, at 6:46 AM, oschreibke@... [jmriusers] <jmriusers@...> wrote:
Hi,
I am trying to figure out how signal heads, signal masts, main and advance signals (British: home/distant) work.
I'm trying to model Swiss Federal Railways (SBB/CFF/FFS) signalling - described in Wikipedia (). For simplicity I'm restricting myself to the four aspects which can be indicated on a four lamp advance signal; namely Halt, and Aspects 1-3. AFAIK they are the most common anyway.
I have two questions:
I have defined the various aspects for the main signal and the same for an advance signal. So far I've been able to create masts for the two signals separately which work as expected.
A common practice is to have a main signal and an advance signal (for the next main) on the same mast, as illustrated in the wikipedia article. Obviously they work independently (except if the main signal is showing Halt, then the advance signal is not lit). Do I need to code out the sixteen aspect combinations for the combined mast, or is there a way to reuse my existing definitions when defining a mast?
...
Basically, what I wanted to achieve was: If the main signal (ih1) changes aspect, show the same aspect on the advance signal (ih4). How do I best achieve this?
-- Bob Jacobsen rgj1927@...
|
Locked
Re: What protocol is easier for turnout/signals via arduino
I¡¯d suggest the C/MRI protocol. See There¡¯s Arduino code available on the web in several places: and even a Yahoo group that can help: Bob On Jun 16, 2017, at 4:51 PM, eallaud@... [jmriusers] <jmriusers@...> wrote:
Hi all,
I have a few sketches for my arduino to manage turnouts and sensors (each "sensor" can also be an output to control something). I would like to be able to hook that up to JMRI.
The address scheme I use is one node address (0->254) plus a subaddress (1->127) ; the arduinos are on a bus like network (rs485 probably). Each subaddress represents a turnout or a sensor; the whole setup (address+subaddres<->turnout/sensor correspondance) is saved in eeprom.
For now I am using messages that look like DCC++'s as that was my inspiration. This can be rearranged if needed.
What I need: address/subaddress to identify the turnout/sensor, a way to send commands (read sensor, write to sensor, throw turnout) and be able to receive async answer (mostly for turnouts as they are moved using servos moving slowly). Also all input sensors are checked periodically and in case some have changed, it is signalled.
I hope this is enough information to guide me to a suitable jmri supported protocol.
TIA
Emmanuel
-- Bob Jacobsen rgj1927@...
|
Locked
1156 Bulbs On Switch Frogs
I know this is not directly JMRI related, but I think this is the best DCC forum to mention this observation. For many years I have wired 1156 automotive light bulbs in series with my frog feeders to prevent a short at the switch points, such as from running a closed switch, from taking down my DCC system (Digitrax). I only make cuts on the frog rails on the side away from the points. So in theory, if I have a bad connection between the points and the stock rail, the connection to the frog, through the 1156, will supply power to the frog via the back contacts on a Tortise. Recently I noticed that I had several turnouts where the sound would disappear when a train went through (TCS WOW). Utilizing a test light (another 1156) I discovered that the light was only about half as bright in the areas where the sound disappeared. Cleaning the points and stock rail connection restore the light to full brightness and the sound returned. As an experiment I installed a thin piece of plastic between the stock rail and the points and observed the same situation. Before sound decoders, this wasn't an issue, but now it seems that preventing one problem (a short) can create another (loss of sound). Has anyone else observed this situation?
Richard Stamm
Modeling the Colorado Midland in 1905
|
Locked
What protocol is easier for turnout/signals via arduino
Hi all,
I have a few sketches for my arduino to manage turnouts and sensors (each "sensor" can also be an output to control something). I would like to be able to hook that up to JMRI.
The address scheme I use is one node address (0->254) plus a subaddress (1->127) ; the arduinos are on a bus like network (rs485 probably). Each subaddress represents a turnout or a sensor; the whole setup (address+subaddres<->turnout/sensor correspondance) is saved in eeprom.
For now I am using messages that look like DCC++'s as that was my inspiration. This can be rearranged if needed.
What I need: address/subaddress to identify the turnout/sensor, a way to send commands (read sensor, write to sensor, throw turnout) and be able to receive async answer (mostly for turnouts as they are moved using servos moving slowly). Also all input sensors are checked periodically and in case some have changed, it is signalled.
I hope this is enough information to guide me to a suitable jmri supported protocol.
TIA
Emmanuel
|
Locked
Re: Program an Engine from the Roster?
Hello Dave,
My issue is resolved.? I went into Preferences and to Defaults.? Not everything was set to NCE.? I changed the setting to all NCE and can program my Locos.? THANK VERY MUCH!!!!
Verner
toggle quoted message
Show quoted text
On Friday, June 16, 2017 3:06 PM, "Dave Heap dgheap@... [jmriusers]" <jmriusers@...> wrote: ? See below: On 17 Jun 2017, at 2:03 AM, Verner Shoup lucyshoup@... [jmriusers] <jmriusers@...> wrote:
I log into JMRI, after the Logo comes up, then JMRI goes to my roster. Before doing that I plug in the Power Cab and the two led's to flash, which would tell me that my computer and JMRI are talking to the NCE USB board. I checked my driver install to confirm that the correct driver is installed. After the JMRI logo shows on the screen, it goes to my roster. I have an engine of the program track that is listed on the roster. The engine can be controlled by the power cab (all functions). I can not though get JMRI to control the engine or make changes. What is going on? What have I "red wordings" on the page showing the engine and its information that I set up. Here is the information I get at this point:
1.8.0_131 on Windows 10 amd64 v10.0 at Fri Jun 16 09:39:08 MDT 2017 [main]2017-06-16 09:39:09,246 gui3.Apps3 INFO - Starting with profile First_tru.3c61a864 [main]2017-06-16 09:39:09,496 node.NodeIdentity INFO - Using jmri-68172961BC46-3c61a864 as the JMRI Node identity [main]2017-06-16 09:39:09,924 usbdriver.UsbDriverAdapter INFO - NCE USB COM3 port opened at 9600 baud [main]2017-06-16 09:39:10,065 nce.NceConnectionStatus INFO - NCE EPROM revision = 7.3.0 [AWT-EventQueue-0] The "INFO - NCE EPROM revision = 7.3.0" in the log indicates that you have JMRI settings correct, the NCE USB jumpers correct and that JMRI has been able to talk to the onboard microprocessor of the NCE USB and that it has told JMRI it is a V7 with all jumpers off. It also tells us that NCE USB is receiving power from the PCP (Power Cab Panel - everything connects to this) by wires 2 & 5 of the cab bus cable. So far so good. Since the connection status subsequently turns red, there are a few things to check next: - Go to Preferences->Defaults and make sure everything in there is set to NCE rather than internal. Then: - Check the log for messages like "incorrect or no response to ... command" followed by repeated "timeout responding to AA command" - Check if either LED on the NCE USB is stuck on If the log has these errors and/or the Cab Bus LED is stuck on (brief flashes from both LEDs is normal), the NCE USB is trying but cannot talk to the Power Cab via the PCP using wires 3 & 4 of the cab bus cable. This could be due to: - A wire or connector spring contact failure - check contacts, swap in spare cables in either position if you have any. - A Cab Bus lockup due to some incorrect chips accidentally supplied to NCE. The Cab Bus lockup can sometimes be temporarily avoided by unplugging the NCE USB Cab Bus cable turning the system on and off and then replugging the cable or even unplugging and replugging the Cab Bus cable while the system remains on. The proper fix is a hardware design modification to the PCP so the chips do not lock up. You can contact NCE to arrange this or fix it yourself if you are comfortable doing that. For details see: <> -- Dave in Australia #yiv5820988483 #yiv5820988483 -- #yiv5820988483ygrp-mkp {border:1px solid #d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;}#yiv5820988483 #yiv5820988483ygrp-mkp hr {border:1px solid #d8d8d8;}#yiv5820988483 #yiv5820988483ygrp-mkp #yiv5820988483hd {color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px 0;}#yiv5820988483 #yiv5820988483ygrp-mkp #yiv5820988483ads {margin-bottom:10px;}#yiv5820988483 #yiv5820988483ygrp-mkp .yiv5820988483ad {padding:0 0;}#yiv5820988483 #yiv5820988483ygrp-mkp .yiv5820988483ad p {margin:0;}#yiv5820988483 #yiv5820988483ygrp-mkp .yiv5820988483ad a {color:#0000ff;text-decoration:none;}#yiv5820988483 #yiv5820988483ygrp-sponsor #yiv5820988483ygrp-lc {font-family:Arial;}#yiv5820988483 #yiv5820988483ygrp-sponsor #yiv5820988483ygrp-lc #yiv5820988483hd {margin:10px 0px;font-weight:700;font-size:78%;line-height:122%;}#yiv5820988483 #yiv5820988483ygrp-sponsor #yiv5820988483ygrp-lc .yiv5820988483ad {margin-bottom:10px;padding:0 0;}#yiv5820988483 #yiv5820988483actions {font-family:Verdana;font-size:11px;padding:10px 0;}#yiv5820988483 #yiv5820988483activity {background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}#yiv5820988483 #yiv5820988483activity span {font-weight:700;}#yiv5820988483 #yiv5820988483activity span:first-child {text-transform:uppercase;}#yiv5820988483 #yiv5820988483activity span a {color:#5085b6;text-decoration:none;}#yiv5820988483 #yiv5820988483activity span span {color:#ff7900;}#yiv5820988483 #yiv5820988483activity span .yiv5820988483underline {text-decoration:underline;}#yiv5820988483 .yiv5820988483attach {clear:both;display:table;font-family:Arial;font-size:12px;padding:10px 0;width:400px;}#yiv5820988483 .yiv5820988483attach div a {text-decoration:none;}#yiv5820988483 .yiv5820988483attach img {border:none;padding-right:5px;}#yiv5820988483 .yiv5820988483attach label {display:block;margin-bottom:5px;}#yiv5820988483 .yiv5820988483attach label a {text-decoration:none;}#yiv5820988483 blockquote {margin:0 0 0 4px;}#yiv5820988483 .yiv5820988483bold {font-family:Arial;font-size:13px;font-weight:700;}#yiv5820988483 .yiv5820988483bold a {text-decoration:none;}#yiv5820988483 dd.yiv5820988483last p a {font-family:Verdana;font-weight:700;}#yiv5820988483 dd.yiv5820988483last p span {margin-right:10px;font-family:Verdana;font-weight:700;}#yiv5820988483 dd.yiv5820988483last p span.yiv5820988483yshortcuts {margin-right:0;}#yiv5820988483 div.yiv5820988483attach-table div div a {text-decoration:none;}#yiv5820988483 div.yiv5820988483attach-table {width:400px;}#yiv5820988483 div.yiv5820988483file-title a, #yiv5820988483 div.yiv5820988483file-title a:active, #yiv5820988483 div.yiv5820988483file-title a:hover, #yiv5820988483 div.yiv5820988483file-title a:visited {text-decoration:none;}#yiv5820988483 div.yiv5820988483photo-title a, #yiv5820988483 div.yiv5820988483photo-title a:active, #yiv5820988483 div.yiv5820988483photo-title a:hover, #yiv5820988483 div.yiv5820988483photo-title a:visited {text-decoration:none;}#yiv5820988483 div#yiv5820988483ygrp-mlmsg #yiv5820988483ygrp-msg p a span.yiv5820988483yshortcuts {font-family:Verdana;font-size:10px;font-weight:normal;}#yiv5820988483 .yiv5820988483green {color:#628c2a;}#yiv5820988483 .yiv5820988483MsoNormal {margin:0 0 0 0;}#yiv5820988483 o {font-size:0;}#yiv5820988483 #yiv5820988483photos div {float:left;width:72px;}#yiv5820988483 #yiv5820988483photos div div {border:1px solid #666666;min-height:62px;overflow:hidden;width:62px;}#yiv5820988483 #yiv5820988483photos div label {color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}#yiv5820988483 #yiv5820988483reco-category {font-size:77%;}#yiv5820988483 #yiv5820988483reco-desc {font-size:77%;}#yiv5820988483 .yiv5820988483replbq {margin:4px;}#yiv5820988483 #yiv5820988483ygrp-actbar div a:first-child {margin-right:2px;padding-right:5px;}#yiv5820988483 #yiv5820988483ygrp-mlmsg {font-size:13px;font-family:Arial, helvetica, clean, sans-serif;}#yiv5820988483 #yiv5820988483ygrp-mlmsg table {font-size:inherit;font:100%;}#yiv5820988483 #yiv5820988483ygrp-mlmsg select, #yiv5820988483 input, #yiv5820988483 textarea {font:99% Arial, Helvetica, clean, sans-serif;}#yiv5820988483 #yiv5820988483ygrp-mlmsg pre, #yiv5820988483 code {font:115% monospace;}#yiv5820988483 #yiv5820988483ygrp-mlmsg * {line-height:1.22em;}#yiv5820988483 #yiv5820988483ygrp-mlmsg #yiv5820988483logo {padding-bottom:10px;}#yiv5820988483 #yiv5820988483ygrp-msg p a {font-family:Verdana;}#yiv5820988483 #yiv5820988483ygrp-msg p#yiv5820988483attach-count span {color:#1E66AE;font-weight:700;}#yiv5820988483 #yiv5820988483ygrp-reco #yiv5820988483reco-head {color:#ff7900;font-weight:700;}#yiv5820988483 #yiv5820988483ygrp-reco {margin-bottom:20px;padding:0px;}#yiv5820988483 #yiv5820988483ygrp-sponsor #yiv5820988483ov li a {font-size:130%;text-decoration:none;}#yiv5820988483 #yiv5820988483ygrp-sponsor #yiv5820988483ov li {font-size:77%;list-style-type:square;padding:6px 0;}#yiv5820988483 #yiv5820988483ygrp-sponsor #yiv5820988483ov ul {margin:0;padding:0 0 0 8px;}#yiv5820988483 #yiv5820988483ygrp-text {font-family:Georgia;}#yiv5820988483 #yiv5820988483ygrp-text p {margin:0 0 1em 0;}#yiv5820988483 #yiv5820988483ygrp-text tt {font-size:120%;}#yiv5820988483 #yiv5820988483ygrp-vital ul li:last-child {border-right:none !important;}#yiv5820988483
|
Locked
New file uploaded to jmriusers
Hello,
This email message is a notification to let you know that
a file has been uploaded to the Files area of the jmriusers
group.
File : /Decoder files/TCS decoders/tcs-wow.zip
Uploaded by : mmosher5501 <mjmx1@...>
Description : updated
You can access this file at the URL:
To learn more about file sharing for your group, please visit:
Regards,
mmosher5501 <mjmx1@...>
|
Locked
New file uploaded to jmriusers
Hello,
This email message is a notification to let you know that
a file has been uploaded to the Files area of the jmriusers
group.
File : /Decoder files/Broadway Limited/BLI.zip
Uploaded by : mmosher5501 <mjmx1@...>
Description : Updated from latest manual
You can access this file at the URL:
To learn more about file sharing for your group, please visit:
Regards,
mmosher5501 <mjmx1@...>
|
Hi All
I am running Windows and update JMRI to the new 4.7.5 from version 4.0,
and trying to duplicate Bob Bucklew JMRI Panel Tutorial with this new
version for the sake of loaning all the many modifications updates done to
this version. Installation went fine, System Manufacturer NCE, connection
Simulator, the remaining preference OK also, created Tables all OK.
Stating Layout Edit and setting it up in edit mode, I have notice that the
top of layout Edit screen has changed somewhat than previous versions. On
the Turnout top line (Name box with the arrow head for selection) if clicked
the drop down menu will show turnouts user name, although if I enter a
System name for example NT1 makes no difference, it always shows user name
(Turnout1) when right click the Turnout circle in Layout Edit, hope it's not
a problem. What got me worry is the next box (Additional Name box label)
stays always gray out and the arrow head is only available the first time,
after that it's useless . Has anyone knows about this? I am looking for
directions to what is the right way to use those two boxes.
Thank you all that respond.
Vince
|
In theory the JSON socket supports consists using messages with type "consist". At this point, it's probably incomplete. You might want to look at the classes in the details of how it's handled.
Randall
toggle quoted message
Show quoted text
On May 30, 2017, at 17:03, adeakrr@... [jmriusers] <jmriusers@...> wrote:
I working on adding and deleting consist.
Consist work if I add the consist number first in the Consist tool.
Is there and way using add or delete consist using JSON socket?
Andrew Deak
|
Bob Jacobsen