Keyboard Shortcuts
Likes
- Jmriusers
- Messages
Search
Locked
Re: restoring sensors and blocks
It's implied from the locobuffer that you're using a digitrax command station. If thats wrong, or things are more complicated, please list that info, and the version of JMRI you're using. The easiest way to populate the sensors table, would be to load the newest/most accurate panel, open up the loconet monitor, and trigger sensors , then give them 'human names' in the sensors panel. The reason for opening the loconet monitor is to give you an easy to view history of what just changed, instead of figuring out what just got added to the tables. The sensors should come up as LS####? eg LS1 - LS2044 (I think the top sensors are reserved, and think I'm remembering the range). If you've lost turnouts, can do the same thing with them, which will be LT#### note that on loconet, you can set sensors to be type 'turnout feedback'. They won't show up in the sensors table, if so, but in the loconet monitor messages reporting the actual position of the turnout (you'll see something like "LT1 set to THROWN. LT1 reports THROWN' My verbage is a bit off, but you'll see twice the messages than you would without the turnout feedback. Once you have the sensors and turnouts in your tables, on the table page save data and panels (under file). if you don't do this, all the sensors and turnouts previously found will be lost. You can then go in and link sensors and turnouts to where they should be on your panel(s). On Thu, Aug 1, 2019 at 2:26 PM Tom Cain <atsf93@...> wrote:
|
Changing names, sometimes requires saving and restarting so everything picks
up the name change. Many things get the change notice and work right away, but some, view like the name gets passed down a few times. The lower level didn't listen for the change. This isn't a great explanation, but worth keeping in mind. Now I would say this is more historic detail. I know in the prior and current development cycle they are making changes that could likely make differences here. Further testing with latest development code would be interesting. Now after doing the save and restart, did the Logix have the right names (and actions)? -Ken Cameron, Member JMRI Dev Team www.jmri.org www.fingerlakeslivesteamers.org www.cnymod.com www.syracusemodelrr.org |
Locked
Re: Help getting JMRI working on a new WIN10 computer
¿ªÔÆÌåÓýMarc, ? I¡¯d expected the same ¨C up and running in a few minutes.? Several hours later I¡¯ve experienced ¡®no joy:¡¯ ? Ross ? From: [email protected] <[email protected]> On Behalf Of
forfoum@...
Sent: Thursday, August 1, 2019 5:21 PM To: [email protected] Subject: Re: [jmriusers] Help getting JMRI working on a new WIN10 computer ? No problem found using USBSS port. JMRI working,?? Monitor Loconet Stats display 3 boxes populated with Ver 2040, ) Breaks 0, Errors 0. |
Locked
Re: DecoderPro &ESU LokSound Factory reset
¿ªÔÆÌåÓýFrank, First I go to NEW Locomotive and select ESU as decoder manufacturer ? Then I click on that and go thru the menu of decoders until I find "LokSound Select".. I select that and I have a new entry that I can use to program my new locomotive. Never attempt to guess the model of a modern ESU decoder. You must always use New Loco->Read Type from Decoder. This will uniquely identify any current ESU decoder.
Reading the full decoder is essential, particularly with ESU decoders where there are no "standard defaults". Each sound project has its own "factory defaults". All ESU sound decoders are manufactured effectively blank. When a Sound project is loaded to the decoder (using LokProgrammer software) part of the procedure is to write a new set of "factory defaults". Because of a known (but as yet unresolved) race condition with certain decoder settings variables in JMRI code: 1) Use "Read Full Sheet" on the CVs pane instead of "Read All Sheets". It is less likely to cause errors when reading a decoder with lots of CVs. Once finished, some may be missed (displayed in red). Use "Read Changes on Sheet" as many times as needed until no red items remain. (Hint: Click on the Status column in the CVs pane until you see a down arrow. All the Red items will then be at the top.) 2) After you make changes on a programming sheet, don't use Write/Read changes on that programming sheet. Instead, switch to the CVs pane and use Write/Read changes on (the CVs) sheet. The result is the same but it will never trigger the race condition. You'll also see a number of messages in the JMRI System Log like this: "ERROR - Variable=xxxxxx; Busy goes false with state IDLE" Ignore these as they don't indicate a real error, we'll fix the problem in a later JMRI release. Dave in Australia |
Locked
Re: Help getting JMRI working on a new WIN10 computer
¿ªÔÆÌåÓýMarc, ? Thank you for checking.? This may verify that we are not getting communication between the LocoBuffer and computer. ? I will re-check all of the cables.? I can also run a ¡®known-good¡¯ jumper from the DCS100 to the computer.? (Computer is remote from the DCS100). ? Ross ? From: [email protected] <[email protected]> On Behalf Of
forfoum@...
Sent: Thursday, August 1, 2019 5:29 PM To: [email protected] Subject: Re: [jmriusers] Help getting JMRI working on a new WIN10 computer ? On Thu, Aug 1, 2019 at 05:20 PM, Ross Kudlick wrote:
Same result using this French Win10 64 bit HP PC. |
Locked
Re: Help getting JMRI working on a new WIN10 computer
¿ªÔÆÌåÓýI installed the drivers from the RR-CirKits web site.? Dick Bronson confirmed they were correct from the data in the port properties. ? Ross ? From: [email protected] <[email protected]> On Behalf Of
forfoum@...
Sent: Thursday, August 1, 2019 4:53 PM To: [email protected] Subject: Re: [jmriusers] Help getting JMRI working on a new WIN10 computer ? Hum.. borrowed my wife's HP Probook 4540s running Win10 64 bit, 1809 - 17763.615.? Chucked the LB-USB in it and no driver found.
|
Locked
multi decoder control
Does?multi decoder control allow you to program multiple decoder locos?? If so how do I use it? Thanks.
Jim K |
Locked
Re: Help getting JMRI working on a new WIN10 computer
¿ªÔÆÌåÓýNigel, ? Thank you for the input. ? The COM ports seem to be correctly established, 1 for each LocoBuffer.? This was verified on Device Manager both before and after re-installing the drivers.? Dick Bronson and I walked thru this multiple times. ? The ports are a mix of USB-2 and USB-3.? I¡¯ll make sure I¡¯m using USB-2 ports next time I¡¯m at the club.? I have a powered USB hub I can try as well. ? Ross ? From: [email protected] <[email protected]> On Behalf Of
Nigel Cliffe
Sent: Thursday, August 1, 2019 4:41 PM To: [email protected] Subject: Re: [jmriusers] Help getting JMRI working on a new WIN10 computer ? ? I¡¯m assuming that you know to look at the Device Manager on the computer for the LocoBuffer connecting, and establishing a COM port ???? If that¡¯s not appearing to work, then¡.? ? Are the ports on the computer all USB-3 ??? I¡¯ve had issues with numerous older USB devices not working correctly on USB-3 ports.?? If stuck with all of them being USB-3, then I¡¯ve found that sometimes a USB-2 port repeater/hub will help (one USB to the main computer, the repeater/hub has four USB ports).?? ? ?
? From: [email protected] [mailto:[email protected]]
On Behalf Of Ross Kudlick ? I¡¯ve hit a road block establishing communication between JMRI and a Digitrax DCS100 using a LocoBuffer-USB interface.? This is a new installation in a computer replacing a recently failed unit.? ? After extensive trouble shooting, including a lengthy telephone trouble shooting consultation with Dick Bronson (RR-CirKits), I believe the issue is with the computer.? ? The trouble shooting has covered all of the ¡®usual suspects;¡¯? JMRI Configuration and Preferences; COM port confirmation, etc.?? Dick had me re-install the LocoBuffer-USB drivers (after removing them using a utility posted on the RR-CirKits web site).? ? The ¡®Monitor LocoNet Stats¡¯ window is blank.? The LocoBuffer is ¡®seeing¡¯ LocoNet activity per the flashing red LED when throttle commands are sent.? This would seem to indicate we are not getting communication between the computer and LocoBuffer.? Several different USB ports were tried; 3 different LocoBuffers were tried.? (The USB ports work with a wireless keyboard and mouse.) ? I substituted a different computer (MS Surface Pro 6 running WIN10 Pro) ?and successfully communicated with the DCS100 with 2 of the 3 LocoBuffers.? (I didn¡¯t try the 3rd LocoBuffer but have no reason to believe it wouldn¡¯t work.) ? Dick and I are at a loss and he suggested I post here to see if anybody has any additional thoughts.? I¡¯m open to any additional ¡®outside-the-box¡¯ ideas. ? Ross Kudlick ? ? Details: HP ProDesk 600 G1 SFF? (off-lease refurb) WIN 10 Pro 10.0.18362 JMRI 4.17.9? (version on the failed computer) JAVA 1.8.0_221;? changed to JAVA? 12.0.2? at Dick Bronson¡¯s suggestion during trouble shooting ? LocoBuffer-USB version 2.070 DCS100 firmware version FD |
Locked
Re: Help getting JMRI working on a new WIN10 computer
¿ªÔÆÌåÓýMarc, ? Thank you for the hint.? I will check next time I¡¯m at the club.? ? Doesn¡¯t explain why it works when the USB cable is unplugged from 1 computer and plugged into the other. ? Ross ? From: [email protected] <[email protected]> On Behalf Of
forfoum@...
Sent: Thursday, August 1, 2019 4:39 PM To: [email protected] Subject: Re: [jmriusers] Help getting JMRI working on a new WIN10 computer ? When it is operational those 8 boxes should only be 3. My experience,? cause of this is bad Loconet cable between LB-USB and DCSxx..? I can replicate this by disconnecting the loconet cable in my setup.?
|
Phil,
toggle quoted message
Show quoted text
I have created a simple test case which replicates your issue. I have a pretty good idea of what is happening but I don¡¯t have a solution yet. In the meantime, create a GitHub issue. Dave Sand On Aug 1, 2019, at 10:58 AM, Phil in gorgeous Young Harris via Groups.Io <philabernathy@...> wrote: |
Locked
Re: Help getting JMRI working on a new WIN10 computer
¿ªÔÆÌåÓýTypo ¨C S/B ?4.15.9 ? From: [email protected] <[email protected]> On Behalf Of
forfoum@...
Sent: Thursday, August 1, 2019 4:31 PM To: [email protected] Subject: Re: [jmriusers] Help getting JMRI working on a new WIN10 computer ? Is that JMRI version 4.17.9? a typo ??? Trying to replicate but not find 4.17.9 on Jenkins |
Locked
Re: Help getting JMRI working on a new WIN10 computer
¿ªÔÆÌåÓý? I¡¯m assuming that you know to look at the Device Manager on the computer for the LocoBuffer connecting, and establishing a COM port ???? If that¡¯s not appearing to work, then¡.? ? Are the ports on the computer all USB-3 ??? I¡¯ve had issues with numerous older USB devices not working correctly on USB-3 ports.?? If stuck with all of them being USB-3, then I¡¯ve found that sometimes a USB-2 port repeater/hub will help (one USB to the main computer, the repeater/hub has four USB ports).?? ? ? -????????? Nigel ? From: [email protected] [mailto:[email protected]]
On Behalf Of Ross Kudlick
Sent: 01 August 2019 20:21 To: [email protected] Subject: [jmriusers] Help getting JMRI working on a new WIN10 computer ? I¡¯ve hit a road block establishing communication between JMRI and a Digitrax DCS100 using a LocoBuffer-USB interface.? This is a new installation in a computer replacing a recently failed unit.? ? After extensive trouble shooting, including a lengthy telephone trouble shooting consultation with Dick Bronson (RR-CirKits), I believe the issue is with the computer.? ? The trouble shooting has covered all of the ¡®usual suspects;¡¯? JMRI Configuration and Preferences; COM port confirmation, etc.?? Dick had me re-install the LocoBuffer-USB drivers (after removing them using a utility posted on the RR-CirKits web site).? ? The ¡®Monitor LocoNet Stats¡¯ window is blank.? The LocoBuffer is ¡®seeing¡¯ LocoNet activity per the flashing red LED when throttle commands are sent.? This would seem to indicate we are not getting communication between the computer and LocoBuffer.? Several different USB ports were tried; 3 different LocoBuffers were tried.? (The USB ports work with a wireless keyboard and mouse.) ? I substituted a different computer (MS Surface Pro 6 running WIN10 Pro) ?and successfully communicated with the DCS100 with 2 of the 3 LocoBuffers.? (I didn¡¯t try the 3rd LocoBuffer but have no reason to believe it wouldn¡¯t work.) ? Dick and I are at a loss and he suggested I post here to see if anybody has any additional thoughts.? I¡¯m open to any additional ¡®outside-the-box¡¯ ideas. ? Ross Kudlick ? ? Details: HP ProDesk 600 G1 SFF? (off-lease refurb) WIN 10 Pro 10.0.18362 JMRI 4.17.9? (version on the failed computer) JAVA 1.8.0_221;? changed to JAVA? 12.0.2? at Dick Bronson¡¯s suggestion during trouble shooting ? LocoBuffer-USB version 2.070 DCS100 firmware version FD |
Locked
Re: Help getting JMRI working on a new WIN10 computer
¿ªÔÆÌåÓýMarc, ? All 8 boxes are blank. ? Ross ? From: [email protected] <[email protected]> On Behalf Of
forfoum@...
Sent: Thursday, August 1, 2019 4:29 PM To: [email protected] Subject: Re: [jmriusers] Help getting JMRI working on a new WIN10 computer ? On Thu, Aug 1, 2019 at 03:20 PM, Ross Kudlick wrote:
Is that? with 8 blank boxes or? 3 blank boxes ? |
Phil, Now that I understand that you were using one of the panel editors, what you describe seems to make sense, but only almost. Certainly it is common for the panel editors to each make any name change requested to be repeated for all occurrences within the file. In version 4.17.2 changing the user name of a memory variable does also change the use of that name in a Logix conditional. I have not tried to change a system name, but nothing you have written here indicates that you intended that kind of a change. Perhaps my attempt to duplicate what I think you have described is too simplistic. Cliff |
Locked
Re: DecoderPro &ESU LokSound Factory reset
You also need to do Read Type from Decoder, as new Loks from atlas, scale trains, etc are Loksound V5 decoders, not Selects. Add in Old V4.0 and Essential Sound Units, all of which are different, and for all the box says 'Loksound", and I never trust the box.
Quite a few differences between the various versions (Still sorting that out as the V5 are new this year.) And note that the factory documents still say Select ( or V4) even though the new Lok has a V5. (Don't get me started on Essential Sound Units) I Just added a pair of Atlas THB GP7 to my previous pair (Two years old). Old has Selects, new has V5. And lots more features to play with. Same paperwork! Just another tip. Thomas DeSoto, TX |
Locked
Help getting JMRI working on a new WIN10 computer
¿ªÔÆÌåÓýI¡¯ve hit a road block establishing communication between JMRI and a Digitrax DCS100 using a LocoBuffer-USB interface.? This is a new installation in a computer replacing a recently failed unit.? ? After extensive trouble shooting, including a lengthy telephone trouble shooting consultation with Dick Bronson (RR-CirKits), I believe the issue is with the computer.? ? The trouble shooting has covered all of the ¡®usual suspects;¡¯? JMRI Configuration and Preferences; COM port confirmation, etc.?? Dick had me re-install the LocoBuffer-USB drivers (after removing them using a utility posted on the RR-CirKits web site).? ? The ¡®Monitor LocoNet Stats¡¯ window is blank.? The LocoBuffer is ¡®seeing¡¯ LocoNet activity per the flashing red LED when throttle commands are sent.? This would seem to indicate we are not getting communication between the computer and LocoBuffer.? Several different USB ports were tried; 3 different LocoBuffers were tried.? (The USB ports work with a wireless keyboard and mouse.) ? I substituted a different computer (MS Surface Pro 6 running WIN10 Pro) ?and successfully communicated with the DCS100 with 2 of the 3 LocoBuffers.? (I didn¡¯t try the 3rd LocoBuffer but have no reason to believe it wouldn¡¯t work.) ? Dick and I are at a loss and he suggested I post here to see if anybody has any additional thoughts.? I¡¯m open to any additional ¡®outside-the-box¡¯ ideas. ? Ross Kudlick ? ? Details: HP ProDesk 600 G1 SFF? (off-lease refurb) WIN 10 Pro 10.0.18362 JMRI 4.17.9? (version on the failed computer) JAVA 1.8.0_221;? changed to JAVA? 12.0.2? at Dick Bronson¡¯s suggestion during trouble shooting ? LocoBuffer-USB version 2.070 DCS100 firmware version FD |
Locked
Re: Engine Only Responds to Short Address
There is a new board called a "decoder buddy" from NixTrains. Almost straight drop in for OEM QSI boards.
Gives you a 21 pin motherboard to install any 21-pin decoder (I prefer Loksound) Thomas DeSoto, TX |
Locked
Re: Engine Only Responds to Short Address
Nick
Friends, Just FYI on this off-topic thread. I BETA tested for QSI and the only decoders that had the short-circuit problem were the original OEM decoders OR those that were set for dual mode (analog operation) . Once the OEM decoders had the upgrade chips installed,? and analog operation disabled, they no longer had that problem , nor any other version from version 7 through the latest Titan. I too do decoder installs and have had no problems with any I've done over the past 10 years . Currently I have or 25 personal locos with QSI decoders in them ranging from upgraded OEM in Atlas and BLI locos to converted brass installs. I prefer them to tsunami but that is what makes this a great hobby. We have choices. On the other problem with the NCE system, I have run into an issue similar to that when a friend programmed some decoders on an NCE system. For some unknown reason, the NCE system somehow added a zero to the leading digit of the loco address. (They were 3-digit numbers) Digitrax would not recognize them but the NCE system did. Once I reprogrammed them on a Digitrax system, the problem disappeared. They were not programmed through JMRI on the NCE system but he used the throttle and a programming track. We never did figure out how it happened. Regards, 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 Concur with Thomas on the QSI opinion.?? I remove QSI decoders when I encounter one.?? I do DCC installs for others and I won't touch them.? Too problematic, time consuming, and fickle.??? I had one loco that came back to me 3 times, with the complaint that it wouldn't respond to commands on the individuals NCE layout, but when I placed it on my Digitrax layout ran like a champ.
|