开云体育

Dave, Thank you for that. It is much appreciated. May I take this opportunity to wish you a Happy and Peaceful New Year. Dave

Dave, 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

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

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,

The red x is caused by lack of logic. It's telling you that that head has no clue what it should be displaying. [email protected] wrote:

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

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

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

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

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

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

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

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

Hi Graham, Here is a small video, showing VSD in JMRI simulator mode (of course VSD is also working connected to my layout): https://www.youtube.com/watch?v=L3ZbcR9DPss Klaus Am 31.12.2018 um 14:56

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

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

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

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

Yes, sorry, this response has to do with my thread Decoder Pro Problems, please go to that thread!

Yes, sorry, this i a response to my original thread (Decoder Pro Problems)? Please go to that thread!