Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- Jmriusers
- Messages
Search
|
Locked
Lightening Storm w/ Digitrax - How to Protect for G Scale
This may not be related to JMRI but I am sure some of you are using the Digitrax Loconet electronics and some may have experienced this so I am putting this on the board for discussion.
I have have been building my train G-Scale layout for the past 18 months. Everything was running fine and I had a big electrical storm 3 weeks ago that basically fried all of the Digitrax electronics. My house including the layout power supplies are protected via a a whole house surge protection system. The only item that failed during the storm were network type devices including my wifi router, netgear switch, apple TVs, and wifi extenders. The major point of failure seems to be the Locotnet network connection for the Digitrax components. All Digitrax power supplies for the electronic boards were fine. No power was on during the storm. There was no sign of burned wires of any entry of a surge into the system. I have had no problems for the past 15 years at this house with any type of electrical storm but of course it hit as I was finishing up my G-Scale layout. Below is my track configuration. This is an outdoor layout with fulll Digitrax electronics. I have all of the Digitrax electronics installed in 4 major metal enclosures. All of the wires connecting the metal enclosures are connected via plastic conduit, with many minor connections from the boxes to smaller boxes connected via conduits. Any advice on how to prevent this in the future would be great. I have added grounding rods (8' in the ground) for each of my electrical boxes. When not running the layout I am isolating the Loconet connections into and out of the boxes so if there is a problem it won't affect all components. Digitrax has been great and I am returning many of the components for repair and I have asked them for help too but I thought maybe someone has been through this here and could offer some advice. I realize that having an outdoor layout fully electronic is probably not the best situation but I suspect that even if this was inside my house the same problem could have happened. The storm fried many of my components connected to my internal ethernet cabling system of which the Digitrax system was not connected too. Again, this may not happen again for the next 15 years and this is why I have insurance but I would like to protect my system as best I can for any future electrical storms. Thanks, Michael Carney Details of my System ----------------------------------- Track Electronics Digitrax, DCS200 ¡.. just upgraded to DCS240 powered by PS2012 PR3 Xtra (2) One connected to Macbook Pro One connected to Raspberry Pi UR92 (2) BDL168 (6) AR1 (3) SE8C (5) DS64 (9) Track LGB G-Scale track (90) track detection zones using BDL168 (20) ID detection section using DBL168 and RX4s LGB Turnouts (50) LGB turnouts Signal Heads from South Bend Signal controlled by SE8Cs Wiring Loconet split into 3 sections one connected to DCS and half of BDLs, DS64s, SE8Cs one connected to DCS and other half of components and (2) UR92s track fore Train control BDL168, SE8C, DS64 are not connected to track for Loconet Wiring Locatons (4 major boxes connected via plastic conduit) Pool Area 2 exterior boxes West Mountain 1 exterior box Circus City 1 exterior box West City 1 exterior box All connected via conduit |
|
Locked
Re: Locobuffer locking up from data overload?
Steve,
I've done some SE8c bench-testing for the concept to use the "LDT LS-DEC" signal head type. The concept is sound, and seems to work well. I tried the concept with the SE8c in "fourth aspect flashing yellow" setting, and the Southern 1981 "signal system". It was the only "signal system" (in 4.7.4) which only used one color of "flashing" head appearance and did not use "dark". In the head settings, I used two "internal" turnouts for the "Dark", "Flashing green" and "Flashing red" items, with unique encoding across the three aspects. I used the _same_ internal turnouts for each head I defined - this was ok since the "signal system" never made use of those head appearances, so there was never a conflict. When setting a mast aspect (or head aspect) which included a flashing head, the only LocoNet traffic involved was to set the appropriate switch for the appropriate state. JMRI did not generate the repetitive sequence of LocoNet traffic which is normally associated with SE8c flashing (with the "fourth aspect is dark" setting). LocoNet traffic was just about as minimal as it could be, and the SE8c was allowed to perform its own "flashing". With all this in mind, I think that this concept could be applied to a signaling system like what you've proposed - where the only "flashing" aspect defined in the JMRI "signal system" is "flashing red", and where the SE8c is used in "fourth aspect is flashing red" mode. Regards, Billybob |
|
Locked
Re: Odd problems with latest test version 4.9.1 Windows 10
Really glad you found some issues Dave. I am also seeing a 'null' when
trying to set routes and it seems to have stopped working again... maybe something I edited wrong in the XML... I hope not. I have been seening random <comment/> entries (by themselves!) other things... but enough for now! It is a test version after all! John |
|
Locked
Re: Locobuffer locking up from data overload?
Bob,
Thank you for this explanation, I've never seen it explained that way! You're right, I assumed 4 states meant 2 bits, either of which might be 0 or 1, every time. I truly appreciate your contribution to our hobby: not only your stewardship of JMRI itself, but the depth of knowledge you've had to gain in order to provide this fantastic tool and the unbelievably good support. In fact I'm going right now to the site to donate to the JMRI project. Thanks again! Sincerely, Steve Davis KCS 3rd Sub |
|
Locked
Re: Speed tables
Harry
toggle quoted message
Show quoted text
I only have one Bachman Locomotive and the decoder that came with it was a very poor quality decoder. ?I wanted to add sound to the locomotive anyway so I replaced the decoder with a Soundtrax decoder that supported speed step programming. ?I do recall that the Bachman decoder did not support speed steps. ? David On Tuesday, August 1, 2017 1:39 PM, "Model Railroad Builder modelrailroadbuilder@... [jmriusers]" <jmriusers@...> wrote:
? Harry, It may be that the specific decoder that you have does not implement speed tables. Can you give us the details on the decoder model and make. Bachman has used SoundTraxx decoders in many of their models and to my knowledge most of those do allow speed tables. Mark Juett Ace Services LLC Your First Choice www.modelrailroadbuilder.com Begin forwarded message: From: "harry_kane2000@... [jmriusers]" <jmriusers@...>[Non-text portions of this message have been removed] #yiv9992690103 -- #yiv9992690103ygrp-mkp {border:1px solid #d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;}#yiv9992690103 #yiv9992690103ygrp-mkp hr {border:1px solid #d8d8d8;}#yiv9992690103 #yiv9992690103ygrp-mkp #yiv9992690103hd {color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px 0;}#yiv9992690103 #yiv9992690103ygrp-mkp #yiv9992690103ads {margin-bottom:10px;}#yiv9992690103 #yiv9992690103ygrp-mkp .yiv9992690103ad {padding:0 0;}#yiv9992690103 #yiv9992690103ygrp-mkp .yiv9992690103ad p {margin:0;}#yiv9992690103 #yiv9992690103ygrp-mkp .yiv9992690103ad a {color:#0000ff;text-decoration:none;}#yiv9992690103 #yiv9992690103ygrp-sponsor #yiv9992690103ygrp-lc {font-family:Arial;}#yiv9992690103 #yiv9992690103ygrp-sponsor #yiv9992690103ygrp-lc #yiv9992690103hd {margin:10px 0px;font-weight:700;font-size:78%;line-height:122%;}#yiv9992690103 #yiv9992690103ygrp-sponsor #yiv9992690103ygrp-lc .yiv9992690103ad {margin-bottom:10px;padding:0 0;}#yiv9992690103 #yiv9992690103actions {font-family:Verdana;font-size:11px;padding:10px 0;}#yiv9992690103 #yiv9992690103activity {background-color:#e0ecee;float:left;font-family:Verdana;font-size:10px;padding:10px;}#yiv9992690103 #yiv9992690103activity span {font-weight:700;}#yiv9992690103 #yiv9992690103activity span:first-child {text-transform:uppercase;}#yiv9992690103 #yiv9992690103activity span a {color:#5085b6;text-decoration:none;}#yiv9992690103 #yiv9992690103activity span span {color:#ff7900;}#yiv9992690103 #yiv9992690103activity span .yiv9992690103underline {text-decoration:underline;}#yiv9992690103 .yiv9992690103attach {clear:both;display:table;font-family:Arial;font-size:12px;padding:10px 0;width:400px;}#yiv9992690103 .yiv9992690103attach div a {text-decoration:none;}#yiv9992690103 .yiv9992690103attach img {border:none;padding-right:5px;}#yiv9992690103 .yiv9992690103attach label {display:block;margin-bottom:5px;}#yiv9992690103 .yiv9992690103attach label a {text-decoration:none;}#yiv9992690103 blockquote {margin:0 0 0 4px;}#yiv9992690103 .yiv9992690103bold {font-family:Arial;font-size:13px;font-weight:700;}#yiv9992690103 .yiv9992690103bold a {text-decoration:none;}#yiv9992690103 dd.yiv9992690103last p a {font-family:Verdana;font-weight:700;}#yiv9992690103 dd.yiv9992690103last p span {margin-right:10px;font-family:Verdana;font-weight:700;}#yiv9992690103 dd.yiv9992690103last p span.yiv9992690103yshortcuts {margin-right:0;}#yiv9992690103 div.yiv9992690103attach-table div div a {text-decoration:none;}#yiv9992690103 div.yiv9992690103attach-table {width:400px;}#yiv9992690103 div.yiv9992690103file-title a, #yiv9992690103 div.yiv9992690103file-title a:active, #yiv9992690103 div.yiv9992690103file-title a:hover, #yiv9992690103 div.yiv9992690103file-title a:visited {text-decoration:none;}#yiv9992690103 div.yiv9992690103photo-title a, #yiv9992690103 div.yiv9992690103photo-title a:active, #yiv9992690103 div.yiv9992690103photo-title a:hover, #yiv9992690103 div.yiv9992690103photo-title a:visited {text-decoration:none;}#yiv9992690103 div#yiv9992690103ygrp-mlmsg #yiv9992690103ygrp-msg p a span.yiv9992690103yshortcuts {font-family:Verdana;font-size:10px;font-weight:normal;}#yiv9992690103 .yiv9992690103green {color:#628c2a;}#yiv9992690103 .yiv9992690103MsoNormal {margin:0 0 0 0;}#yiv9992690103 o {font-size:0;}#yiv9992690103 #yiv9992690103photos div {float:left;width:72px;}#yiv9992690103 #yiv9992690103photos div div {border:1px solid #666666;min-height:62px;overflow:hidden;width:62px;}#yiv9992690103 #yiv9992690103photos div label {color:#666666;font-size:10px;overflow:hidden;text-align:center;white-space:nowrap;width:64px;}#yiv9992690103 #yiv9992690103reco-category {font-size:77%;}#yiv9992690103 #yiv9992690103reco-desc {font-size:77%;}#yiv9992690103 .yiv9992690103replbq {margin:4px;}#yiv9992690103 #yiv9992690103ygrp-actbar div a:first-child {margin-right:2px;padding-right:5px;}#yiv9992690103 #yiv9992690103ygrp-mlmsg {font-size:13px;font-family:Arial, helvetica, clean, sans-serif;}#yiv9992690103 #yiv9992690103ygrp-mlmsg table {font-size:inherit;font:100%;}#yiv9992690103 #yiv9992690103ygrp-mlmsg select, #yiv9992690103 input, #yiv9992690103 textarea {font:99% Arial, Helvetica, clean, sans-serif;}#yiv9992690103 #yiv9992690103ygrp-mlmsg pre, #yiv9992690103 code {font:115% monospace;}#yiv9992690103 #yiv9992690103ygrp-mlmsg * {line-height:1.22em;}#yiv9992690103 #yiv9992690103ygrp-mlmsg #yiv9992690103logo {padding-bottom:10px;}#yiv9992690103 #yiv9992690103ygrp-msg p a {font-family:Verdana;}#yiv9992690103 #yiv9992690103ygrp-msg p#yiv9992690103attach-count span {color:#1E66AE;font-weight:700;}#yiv9992690103 #yiv9992690103ygrp-reco #yiv9992690103reco-head {color:#ff7900;font-weight:700;}#yiv9992690103 #yiv9992690103ygrp-reco {margin-bottom:20px;padding:0px;}#yiv9992690103 #yiv9992690103ygrp-sponsor #yiv9992690103ov li a {font-size:130%;text-decoration:none;}#yiv9992690103 #yiv9992690103ygrp-sponsor #yiv9992690103ov li {font-size:77%;list-style-type:square;padding:6px 0;}#yiv9992690103 #yiv9992690103ygrp-sponsor #yiv9992690103ov ul {margin:0;padding:0 0 0 8px;}#yiv9992690103 #yiv9992690103ygrp-text {font-family:Georgia;}#yiv9992690103 #yiv9992690103ygrp-text p {margin:0 0 1em 0;}#yiv9992690103 #yiv9992690103ygrp-text tt {font-size:120%;}#yiv9992690103 #yiv9992690103ygrp-vital ul li:last-child {border-right:none !important;}#yiv9992690103 |
|
Locked
Re: CTI-Electronics Acela Interface Connection
Ken U,
Thank you for saying this. I just checked the latest code and it is having an error while starting the CTI config pane. This should be simple enough to trace and fix. I've entered an issue on our tracking site, so you can follow the issue. -Ken Cameron, Member JMRI Dev Team www.jmri.org www.fingerlakeslivesteamers.org www.cnymod.com www.syracusemodelrr.org |
|
Locked
Re: Speed tables
H_kane,
I just did a quick look at Bachmann's website and for sure at least some of their EZ Control line models have only basic decoders that do not support speed tables. I was able to see that their 2 function decoder had a spec sheet and no speed table. So if you have those models, and you want speed tables, you will need to swap out the factory decoders for some other brand or model that supports it. Many to choose from. If your locomotives came with more sophisticated decoders than that, please report back and I am sure someone can steer you to figuring it out. Tom Wilson |
|
Locked
Re: CTI-Electronics Acela Interface Connection
Ken Cameron,
I have a new Windows 10 desktop and I installed JMRI 4.8. I have successfully setup the Digitrax connection with a PR3 interface and a DCS51 command station. All works correctly. However, I still can not setup a connection to the CTI Acela interface. The dialog box does not offer a port selection at all. I then tried JMRI 4.9.1 and this does not work either. I verified that the Acela interface is fully functional using the CTI software, so this is not a hardware or OS issue. This was broken with the JMRI 4.* release, but worked back with JMRI 3.10. I complained about this some time back and another user has as well. I would appreciate that this got some attention. Kenneth Underwood |
|
Locked
Re: Speed tables
H_kane,
Can you tell us what locomotive models you have from Bachmann? Even the Bachmann model number off the box? If those are sound equipped, you should be getting speed tables. If they are Bachmann's DCC on board line with no sound, they may be very basic decoders that dont have that capability. Their manufacturer model numbers will help to figure to that out by searching Bachmann's web site. Tom Wilson |
|
Locked
Speed tables
Model Railroad Builder
Harry,
toggle quoted message
Show quoted text
It may be that the specific decoder that you have does not implement speed tables. Can you give us the details on the decoder model and make. Bachman has used SoundTraxx decoders in many of their models and to my knowledge most of those do allow speed tables. Mark Juett Ace Services LLC Your First Choice www.modelrailroadbuilder.com Begin forwarded message: From: "harry_kane2000@... [jmriusers]" <jmriusers@...> |
|
Locked
Re: Using PR3 on layout room laptop.
Howdy Jack. In the log posted, I counted 76 roster DateModified errors and 15 turnout errors.
Do you really have 76 roster entries? I have not had the problem with dates, but the format changed at some revision of JMRI and I recall much discussion. Regarding the turnouts, there were 15 errors. Unless you have the actual hardware attached, it may not like having non-existent turnouts in the turnout table/panel. Sorry to be vague, but I was trying to recall my struggle as I was planning my new layout. I had an XtrkCad plan, and made a panel using LocoNet Simulator on Layout Editor. Many of my turnouts were entered as LT, but on another day, during WiThottle testing when I connected to my Zephyr with a PR3, I loaded the panel but it didn't work as I planned, since I had nothing actually built yet. But I could be all wet 'cause Bob probably nailed it about the connection... Phil in gorgeous Young Harris, Georgia. USA |
|
Locked
Re: reading/programming Digitrax SFX006 standalone using JMRI
Hi Dirk
Try removing the PBT from the circuit. I have programmed these just fine with a pr3 + ps14. They are best done by themselves without a second decoder being on the track at the same time. Steve G |
|
Locked
Re: Speed tables
Terry
toggle quoted message
Show quoted text
Visit My Web site@ Harry ? (You didn't sign your post) so just guessing I have a Bachmann 4-8-2 Mountain With DCC on Board and I am able to access speed tables Using JMRI production Version 4.8 You might check to see if you are using the correct decoder definition Pretty sure they are listed separate under Soundtraxx Throttle up~~ Bachmann Steam OEM ~And there are 13 different HO engine types Mine is listed as a 4-8-2 USRA Heavy Terry -----Original Message-----
From: harry_kane2000@... [jmriusers] <jmriusers@...> To: jmriusers <jmriusers@...> Sent: Tue, Aug 1, 2017 2:19 am Subject: [jmriusers] Speed tables I'm very new to this JMRI stuff so bear with me. I have successfully loaded JMRI and have successfully run trains from my laptop, I've even managed to run two trains at a time from my smart phone using the Engine Driver app. However the main reason I started with JMRI was to use the nifty speed table page to adjust the speed curves on my locos. I have 4 locomotives, all Bachman with DCC on board, and none of these will allow that table to come up. It says this page is not available and suggests I choose another tab. I this a problem with Bachman decoders not allowing the setting of these tables? Help! |
|
Locked
Re: Using PR3 on layout room laptop.
There are a couple problems indicated here.
First, you seem to have some extra libraries hanging around somewhere. This is the ¡°jackson¡± message you see. There something in the release note about that: It¡¯s a problem that the JMRI installer on Windows automatically fixes, so I suggest downloading a copy of JMRI 4.8 and installing that. (Download link above) Second, I suspect that you have the LocoNet connection configured to ¡°PR3 Standalone Programmer¡± instead of as a connection to your command station (or as a Standalone LocoNet, depending on how things are wired). That would show the symptoms you see. Bob On Jul 31, 2017, at 5:44 PM, jceiermann@... [jmriusers] <jmriusers@...> wrote:
-- Bob Jacobsen rgj1927@... |
|
Locked
Re: System Console Warning Message
On Jul 31, 2017, at 1:59 PM, wmseapc@... [jmriusers] <jmriusers@...> wrote:Ok. Let me pull out the LIUSB-Ethernet I have and connect it to a mac so I can check the port name assigned. That might take me a day or two. I moved recently and there are some things that still need to be unpacked. Paul |
|
Locked
Re: Odd problems with latest test version 4.9.1 Windows 10
John,
Metrics -- These are part of "layoutblocks", which is an extension of "blocks". The layout blocks schema is missing the metrics element. I can fix that. The default value is 200 which is not written to the panel xml file. It took a while but I think I have figured out the "missing" NX data. It is actually there but not accessible. The startup process was creating 2 EntryExit managers. The first one was created at the beginning of startup and was used during the loading of the panel xml file data. This is what allows the NX processes to work. The second one was created at the end of the startup process, but it is empty. That is why selecting "Tools >> Entry Exit..." is always blank after the JMRI startup. I think I have a fix for this issue. I need to finish testing to make sure I don't break something else. I tested stacking on my sample NX config (referenced in the previous message), and it worked as expected. The problems you are seeing may be caused by the "2 managers" issue. The "double cross-over" block routing problem also affects signal mast logic. I just delete the impossible signal mast logic. When Path routing starts messing up, usually due to changes to the track plan, I go to Tools >> Blocks >> Paths >> Delete Paths... After a save and restart, the paths are automatically rebuilt during startup. There is no way I would try to change them manually. If you want to try and understand block routing, the following URL might help: Dave Sand |
|
Locked
Speed tables
I'm very new to this JMRI stuff so bear with me. I have successfully loaded JMRI and have successfully run trains from my laptop, I've even managed to run two trains at a time from my smart phone using the Engine Driver app. However the main reason I started with JMRI was to use the nifty speed table page to adjust the speed curves on my locos. I have 4 locomotives, all Bachman with DCC on board, and none of these will allow that table to come up. It says this page is not available and suggests I choose another tab. I this a problem with Bachman decoders not allowing the setting of these tables? Help!
|
|
Locked
Re: Test version 4.9.1 further bug with setting sensors on turnouts
John,
I have been building a sample NX setup to test out your problems. I was able to re-create the "turnout" issue for sensors by not adding a turnout to the icon. After adding the turnout name, I was able to add the sensors. Just now I expanded my sample system to include the signal masts. This time the "turnout" name problem showed up for the signal masts. I faked out the system by adding one mast at a time. You might try adding the sensors one at a time. Dave Sand |
|
Locked
PanelPro Logix Consequent Action randomly changing Signal Head Appearance for same Signal Head and Action
Good evening
I have been observing this problem for quite a while and was hoping I might see a change in JMRI 4.8 but have not. It is an intermittent problem that occurs after confirming the Signal Head Appearance is correct in the Consequent Action Edit window and all criteria meet the requirements. The next action requesting this Consequent Action displays an incorrect Signal Head Appearance. Building signal head logix manually using Logix table with three conditionals on main logix screen called Red, Yellow, and Green. Here is a Browse of one of my logix experiencing the problem in both live and SIM modes: IX:AUTO:0058C1 Red Antecedent: (R1 or (R2 and R3)) R1 IF Turnout "NT124" state is Turnout Thrown R2 AND Turnout "NT124" state is Turnout Closed R3 AND Sensor "LS123" state is Sensor Active THEN When Triggered True, Set Signal Head Appearance, "IH:SE8C:"LT315";"LT316"" to Red IX:AUTO:0058C2 Yellow R1 IF Turnout "NT124" state is Turnout Closed R2 AND Sensor "LS123" state is Sensor Inactive R3 AND Turnout "NT127" state is Turnout Closed THEN When Triggered True, Set Signal Head Appearance, "IH:SE8C:"LT315";"LT316"" to Yellow <==this is the changing value --> IX:AUTO:0058C3 Green R1 IF Turnout "NT124" state is Turnout Closed R2 AND Sensor "LS123" state is Sensor Inactive R3 AND Turnout "NT126" state is Turnout Closed R4 AND Turnout "NT127" state is Turnout Thrown R5 AND Sensor "LS87" state is Sensor Inactive THEN When Triggered True, Set Signal Head Appearance, "IH:SE8C:"LT315";"LT316"" to Green I have even included the conditional from the JMRI file here: <conditional systemName="IX:AUTO:0061C2" userName="Yellow" antecedent="R1 and R2" logicType="1" triggerOnChange="yes"> <systemName>IX:AUTO:0061C2</systemName> <userName>Yellow</userName> <conditionalStateVariable operator="4" negated="no" type="4" systemName="NT121" dataString="" num1="0" num2="0" triggersCalc="yes" /> <conditionalStateVariable operator="1" negated="no" type="2" systemName="LS121" dataString="" num1="0" num2="0" triggersCalc="yes" /> <conditionalAction option="1" type="3" systemName="IH:SE8C:"LT325";"LT326"" data="4" delay="0" string="Yellow" /> </conditional> Problem is here: I am looking at IX:AUTO:0058C2 Yellow and expecting a Yellow signal head since all the IF statements are true. Initially the Signal Head was correct, but isn't after changing the signal conditions to Red, or Green, then back to a Yellow condition. It will not return to Yellow afterwards The Consequent Actions (the 'then' part) says the signal head should be yellow, but if I edit the Consequent Action, the Signal Head Appearance says "Green" despite how many times I change it back to Yellow (and save the file, quit the program and restart/reload the file). All I have to do is change a condition that will change the signal head correctly, then go back to a Yellow condition, but it will either say Red or Green in the Consequent Action. Obviously, this can be very frustrating because it doesn't happen with every Logix I've created (30+). Is the fact that I am not using the SSL tool causing this problem? What can I do to isolate this problem, or more better describe it to anyone looking at this. OS is Win7 running JMRI 4.8 now, but have experienced this in much earlier releases. Any and all help will be great appreciated. Wain Schroeder Clinton Central Model Railroad www.ccmrr.org |
|
Locked
Re: DecoderPro print problems
Hi Rick I spent the day going thru' every print combination I could think of on Windows 10 and Windows XP. All of them came out as ~5 lines per inch, ~12pt courier, correctly sized and spaced, which is slightly bigger than the old typewriter standard. The only way I could get anything close to not that, is by messing with the printer properties, and not setting Page Setup -->Page Layout --> Normal Size.
I think you or me may have miss read something, I wasn't aware that JMRI 4.6 ran under java 7u80. It didnt work for me. Steve G. |
Ken Cameron
Bob Jacobsen
to navigate to use esc to dismiss