Keyboard Shortcuts
Likes
- Jmriusers
- Messages
Search
Locked
Re: UNWANTED BLOCKS & TURNOUTS IN LISTING
Hi Dave
Odd. Is there nothing on the JMRI console? Did the changes Dave Sands made make a difference? Dave Sands Thanks for looking at the script. I learned something new about panels and their relationship to the tables John |
Locked
Re: UNWANTED BLOCKS & TURNOUTS IN LISTING
¿ªÔÆÌåÓýDave,Thank you for that. It is much appreciated. May I take this opportunity to wish you a Happy and Peaceful New Year. Dave
|
Locked
Re: UNWANTED BLOCKS & TURNOUTS IN LISTING
Dave,
toggle quoted message
Show quoted text
Try using the modified version of the script that I uploaded. The CSV files are created in the user files location (the panel file location) and it correctly handles checking blocks for use within panels. Dave Sand On Dec 31, 2018, at 9:18 AM, Dave Roberts <dccdaveroberts@...> wrote: |
Locked
Re: Decoder Pro problems
Mark,? I just reread your original post from a few days ago and see you are connected through a PR4. Ignore my last question about what system you are using. I have nothing more I can contribute to this thread. I trust others will be able to help you. Good luck. Tom Wilson Colorado Springs, CO On Mon, Dec 31, 2018, 10:46 AM Tom Wilson via Groups.Io <thomasthetrainengine=[email protected] wrote:
|
Locked
Re: Decoder Pro problems
Mark, What DCC system are you using to interface to JMRI? That is confusing from your description of your problem. If you are interfacing through your already determined to be damaged Digitrax system, Jmri will not be able to overcome the damaged hardware to do anything for you. It would be helpful to all who are trying to help you to know what you have connected that is supplying your program track with a signal.? ?Jmri, in and of itself cannot do this. It needs an operating DCC system or specialized programming hardware to do anything for a decoder.? Tom Wilson Colorado Springs, CO On Mon, Dec 31, 2018, 6:38 AM <mvdeschane@... wrote: I have attempted to change the direction of travel on the loco (SW1200) on my Program Track.? Then, I placed the loco on my layout and nothing worked!? Used Digitrax SoundLoader to do a Factory Reset, then changed address to 106.? Placed on layout and everything O.K.? Placed on the Program Track again with JMRI Running; but, did not attempt to do anything and the loco was still functional! |
Locked
Re: PanelPro icon sets question
The red x is caused by lack of logic. It's telling you that that head has no clue what it should be displaying.? On Sun, Dec 30, 2018, 10:48 Nick via Groups.Io <cornwall9=[email protected] wrote: Friends, |
Locked
Re: Decoder Pro problems
I always give two reasons to change the id 3 to something else. First is
that many locos when you first put them on the track will be id 3. So every time you go to test a new loco (I always test first, then program), you would have a conflict if you left another loco that is id 3 on the layout, both would move. Second is that many decoders will reset to id 3 if something happens internally and it has to do a 'factory reset' because its memory got scrambled (bad checksum on startup). Again, this loco would be the same id 3. I apply that logic to everything on the layout. Test at the default id, then change to something else that doesn't conflict with anything else. Thankfully LCC doesn't have this issue. -Ken Cameron, Member JMRI Dev Team www.jmri.org www.fingerlakeslivesteamers.org www.cnymod.com www.syracusemodelrr.org |
Locked
Re: Run tests:
Paul D,
Keep in mind the Digitrax decoder will work just fine as a 106 long address. It just won't be accessible on a Digitrax system. It would run just fine on a NCE system and a few others. The address limit of 1-127 must be short address is a command station/throttle restriction that Digitrax adopted. -Ken Cameron, Member JMRI Dev Team www.jmri.org www.fingerlakeslivesteamers.org www.cnymod.com www.syracusemodelrr.org |
Locked
New file uploaded to [email protected]
[email protected] Notification
Hello, This email message is a notification to let you know that a file has been uploaded to the Files area of the [email protected] group. File: Table print DS.py Uploaded By: Dave Sand Description: You can access this file at the URL: Cheers, |
Locked
Re: Decoder Pro problems
On Sun, Dec 30, 2018 at 01:33 PM, Marc wrote:
Andrew:?Thanks Marc. Mine are probably not first gen tsunamis. Unless walthers is pulling a fast one, ?(they are installed in newly released end EMD GP7) I would suspect it's very contemporary version. Given that, should I still look to replace the power supply for the PS4?? I have seen others mention that it's a good idea to change ID from 3 to something else. I'm wondering why that is suggested- other than there may be other locos with that default on the layout?? |
Locked
Re: UNWANTED BLOCKS & TURNOUTS IN LISTING
¿ªÔÆÌåÓýJohn,I have followed your instructions but nothing appears to have happened. (1) I have created a backup copy of the SDR file and am using a copy of ? ?the original file to test the Script on. (2) I opened the new duplicated file. It is showing no errors as it loaded the Master Panel and all of the Sub-Panels. (3) I Went into JMRI Panel Pro and selected the ¡°Panels¡± menu and then selected ¡°Run Scripts¡±. (4) I Browsed to file location and selected the print file to open. Nothing appears to have happened. I have checked for the creation of any new .csv files but found nothing on the computer. I cannot figure out what I am doing wrong. There is no indication that anything has happened at all. Your help and guidance would be greatly appreciated at this point. Dave
|
Locked
Re: Run tests:
106 is a SHORT address in Digitrax decoders. If you set it for 106 as a LONG address, it will not work. Digitrax only uses 1-127 as short addresses. Go back to DecoderPro and rogram it as 106 but call it a SHORT address. I had same confusion what I first tried to set up a loco with a 111 address.
|
Locked
Re: Run tests:
Switch back the Digitrax SoundLoader, do a factory reset and then re-address to 106 and the loco was found to operate correctly.? .? ??So decoderpro IS programming the loco, just not to the address you are expecting. What address does Soundloader claim the loco is set to BEFORE you do the reset? Does the loco operate correctly if you then attempt to run it on the layout using that address? It sounds to me like DecoderPro is setting it to Long Address 106, but you are setting it to short address 106 using Soundloader. |
Locked
Re: Decoder Pro problems
¿ªÔÆÌåÓý? In the light of your comments about the damaged/broken Zephyr (awaiting a return to Digitrax when they have a repair service operating again),? please clarify the equipment and connections between equipment used in the failed attempt to change direction on the Programming Track. ? Following the comments about damaged Zephyr, the only option which I would expect to work is ¡°stand alone¡±, ie same hardware setup as used for SoundLoader.? But, current JMRI preferences don¡¯t list a PR4 interface, so selections are for PR3. http://jmri.org/help/en/html/hardware/loconet/PR4.shtml ?? ? ? ? ? -????????? Nigel ? From: [email protected] [mailto:[email protected]]
On Behalf Of mvdeschane@...
Sent: 31 December 2018 13:38 To: [email protected] Subject: Re: [jmriusers] Decoder Pro problems ? I have attempted to change the direction of travel on the loco (SW1200) on my Program Track.? Then, I placed the loco on my layout and nothing worked!? Used Digitrax SoundLoader to do a Factory Reset, then changed address to 106.? Placed
on layout and everything O.K.? Placed on the Program Track again with JMRI Running; but, did not attempt to do anything and the loco was still functional! |
Locked
Re: VSDecoder: Problems with xml and sound
#vsdecoder
#rpi
#ubuntu
Hi Graham,
toggle quoted message
Show quoted text
Here is a small video, showing VSD in JMRI simulator mode (of course VSD is also working connected to my layout): Klaus Am 31.12.2018 um 14:56 schrieb SettleDown: Hi Karl |
Locked
Re: NMRA/JMRI/Arduino
Graham:
Oddly the DCC++ does a lot of you want to do if you use the Arduino Mega and enable it's I/O pins through the DCC++ software. Except for finding all the parts it's rather straight forward in the code supplied. It's also straight forward to get all to talk to JMRI. Almost all approaches to what you would like to do will have a learning curve for both hardware and software. Going other routes with Arduino might have the additional complexity of an additional connection to the PC and JMRI. There is a bunch of stuff from a commercial source, MRCS that might fit in () Also there is an Arduino? Yahoo! support group Arduini... Buy if DIY doesn't appeal there will be support from both JMRI and (pick a brand) communities. Happy New Year! JMRI |
Locked
Re: UNWANTED BLOCKS & TURNOUTS IN LISTING
¿ªÔÆÌåÓýHi Wouter,I think that perhaps we may have a cross posting here. My postings have been to do with trying to eliminate as many errors as possible from the Master xml file so that we can reduce the search area within the error logs when looking for the more illusive errors. I started by developing a Naming scheme that would identify every item on every Named Sub-Panel within every Table so that everything on that panel was kept together. This saved me from having to go through the whole listing as I could break the Master File down into its different sub-panels. Several people have been looking into the various Tables trying to identify those entries that are not used by the xml file and are redundant to requirements. These records can then be safely deleted, reducing the file size as we proceed. For example, both Turnouts and Blocks have, by default, just two connections when they are first created. By using this fact a Script has been created that checks whether and entry is in use on not and flags that that are not in use. It then created an excel format spreadsheet listing all of the entries in a Table that also identifies those that can be deleted. These can then be deleted manually later on. Ideally, it would be great if, as part of the "Save using a New Name¡± scenario, the redundant entries in every Table could be identified and marked for deletion and the user asked at the end if they wanted to also delete this data so that no entries are carried over into the newly Named file as it is created. This should greatly reduce the error logs that we have to search through to find and Correct/Delete the more illusive errors that we sometimes get. I am about to go down this path later today so we will have to see what happens. Dave
|
Locked
Re: VSDecoder: Problems with xml and sound
#vsdecoder
#rpi
#ubuntu
SettleDown
Hi Karl
As reported I now have audio when pressing the buttons in VSD Manager but on further testing I realise that I get nothing when running a loco identified in the Manager and saved to the Roster.? I've read all the documentation you suggested, but maybe I'm missing a step somewhere or else the errors reported in Problem 1 are preventing the decoders from sending speed data back to VSD to generate ClickClack or Chuffs etc.? I have Locos running LokPilot Basic 1.0 decoders, one using a Digital Plus (Lenz)?4 function decoder (36-550), and one LokPilot v4.0 DCC decoder.? Are any/all of these capable of sending the loco data to power VSD ? Cheers Graham - @SettleDown |
Locked
Re: NMRA/JMRI/Arduino
SettleDown
Hi Paul
Thanks for the DCC++ link.? I took a look at it, but I'm thinking it may be a bit above my pay grade !? At this stage all I'm thinking about doing is using an Arduino to detect loco positions on my smallish layout and to initiate sounds via VSDecoder, and maybe raise and lower crossing gates and turn building lights on and off and other simpler things like that.? My first challenge is to get VSDecoder working and then setting up an Arduino to manage it. Many thanks Graham - @ SettleDown |
Locked
Re: Run tests:
Yes, sorry, this response has to do with my thread Decoder Pro Problems, please go to that thread!
|