开云体育

I am using JMRI with an NCE USB interface to program decoders.? I bought a used P2K GP7 that is not running.? I want to download the decoder settings such as address.? I have done what I think is the proper procedure but I am not sure of the results.

--
Don Bowen --AD0NB--

An addition to JMRI that was a LOK programmer pgm would be fantastic. ESU would not like it because it would cut into their LokProgrammer ($145.00) sales.

Jim K

I am also trying two different LCC/Openlcb buss's. The main one is RR-CIRKTS cards. The second is for testing with Raspberry PIs and Arduinos.
I would like an event to show up on both busses.

--
Don James
Member Detroit Model Railroad Club

Hi Folks:

New member here -- looking at operations to generate switch lists for my N scale San Luis and Rio Grande.? Ive got the demo files loaded, but im kinda at a loss how to proceede from here -- is there a tutorial or video or something out there on how to use Operations within JMRI?

Thanks
TIM

Steve,

Looks like you are good to go.? ready to step into the swamp.? My technique (which, when I don't follow it, leads to disaster) is as follows

copy and paste a BACKUP loco.vsd folder. I CANNOT STRESS THIS ENOUGH.??
make two desktop folders - one "vsd-zip" and the other "loco_blah_blah"
put the loco.vsd folder into the empty "vsd-zip" folder.
vsd is just an extension of a zip file so rename .vsd to .zip
extract the zip flles
now you will see a sound folder, a config file and maybe a text file with copyright info.
copy and paste the sound folder and config file from the "vsd-zip" folder to the empty "loco" folder
in the "loco" folder, look at the sound files (.wav) - almost always 8 bit, 11KHz sample, uncompressed, mono.? the format of all sound files has to be the same.
add your sounds to the particular sub folder (common, engine, horn) AND add the same sounds to the sound folder in the "vsd-zip" folder by file copy and paste.??

tedious, but I sometimes get a vsd crash if I just copy and paste the whole sound folder from "loco" folder to "vsd-zip" folder.? your option though.

now for the config file - open it from the "loco" folder? with an XML editor and change the particular wav file that you are working with (say bell to double clap bell).
each action has its own .wav file.? some have start, run, end .wav files.? engines are more complicated.
this is (I think) javascript so every character counts: caps, lower case, spaces, dashes, etc.? It will drive you crazy.
bty <!--? blah, blah, blah --> can be used for notes.? also can be used to "blank" out whole sections of the script.
save the xml file.

status - "loco" folder has updated sound folder and a modified config file? ----? ?"vsd-zip" folder has an extracted sound folder (updated), an unmodified config file
and a text file (maybe).

copy/overwrite the modified config file to the "vsd-zip" folder.
??backstep?? the "vsd-zip" folder so you end up with loco.zip.? ????backstep??? what kind of techie term is that?
now you can run JMRI's VSDecoder.? the program will accept the .zip file (this saves a step as you go back and forth adding changes).
when finished or your brain starts to melt, rename the loco.zip to loco.vsd and move it to the "loco_blah_blah" folder
you will now have an empty "vsd-zip" folder and a "loco_blah_blah" folder with the loco.vsd folder, a sound folder and the config file.
run a train to chill.? whew!

Conrad

ps go slow, make one or two changes then see if program runs.??

Group:

For those who wonder...

A member of our club donated the Pi development kit... so what do I do with it?

Here's the most evil kludge I think I've done (in photos my Pi album)... PI board, Mega, power supply... ?Real time clock... 3D printed holder for scrapped heat sink on driver chip... Realtek USB antenna so I have WiFi...

Enjoy

Oh yeah... Meyerstown Pa and the nifty NS (ex N&W) slug...

Jim Albanowski

Steve,
Need more info. I assume you are using JMRI since you are on this group. Have you downloaded the basic .vsd files? What specifically are your sound files? Are they .wav and what format (8/16 bit, sample rate, compressed/uncompressed)?
***
Conrad,

Thank you. I am using JMRI with an Arduino DCC++ setup. I have downloaded a couple of vsd files. Still trying to get the overall picture.

I will record these (diesel) sound files in a few days. They can be wav files in any required sample rate, uncompressed.

.

To make this all work you will need an .xml editor, an audio editor and an "unzipper" utility. And, per below, "You must also have the OpenAL or JavaSound audio system installed on your computer."


I'll have to get an xml editor. I have several audio editors, can unzip files, and have OpenAL.



I'd start here:

I have looked through that. Will keep looking through the JMRI site.


Also are you in linux, windows or apple?

Windows 10 in a Lenovo T410. One hard drive is solid state, making for quick access.




Once you get the basic going I'd search this site for VSD. You will see lots of info going back to 2011. I reversed the date scroll to look at earliest to latest.

Lots of work, but well worth it. You'll be shaking the walls.

Conrad

Dag Cato,

This is a known problem. I created an Git Issue, #6156, last November. As far as I know, no one is working on a fix.


Dave Sand

Thanks both. They are from Biffo. All working now. I think I was mis-reading Dave's comment about the best way to reset a decoder.

I'm now working back through my roster reading all CVs into JMRI. I've also got to work out why my Eurostar decoder gives a short-circuit error.?

GS:

You bet, right now from a base download of the July Buster the update/upgrade... it takes awhile...

For some reason Linux is still off putting... too much at the command line level... me thinks...

Jim Albanowski

Don - Buster runs on the 3 and the 4, but the 4 must have Buster.

Roger - You are correct.? Buster can be updated in the terminal window via the usual apt-get update/upgrade commands.? It's early times for Buster and the Pi-4, and there are lots of little fixes coming at a quick pace. Because I have a feeling that the majority of railroaders using Steve's image skew towards the non-technical end of the scale, I suggested that he update the Buster version in the image to avoid strange support problems.? ? For the non-technically inclined, just bringing up a terminal window is a big step, and watching hundreds of lines that will scroll by during the upgrade/update process is pretty scary.

gs

A clarification:

On the DS64, by default, the turnout addresses are _dependent_ on the board address. But the individual turnout addresses _may be changed_ from the default addresses which are _implied_ by the board address. This means that "independence" requires specific user programming actions.

Regards,
Billybob

Mack

Given you said earlier in the thread that these are Legomanbiffo sound projects, you can be confident about a "reset" being to the "defaults Biffo the sound writer has written into the decoder", and not to "out the ESU factory door". If it doesn't do that, Biffo has made a rare mess-up and you'd be also confident that he'd sought it out for you.


Biffo is one of the best sound writers for ESU in the UK, really knows what he's doing with ESU decoders and with recording sounds for them.


- Nigel

Congratulations, Conrad!

You got there very fast.

On your 12,24,36,48,60,72 & 80 values (ZIMO call them thresholds):
In the NW2 file Oliver Zoffi uses these thresholds: 36, 73, 109, 146, 182 & 219. I'm assuming that the first value is omitted. I also suppose these values are speedsteps. To transfer it to VSD format I divided every value by 255 (internal speedsteps of a decoder). That gives: n, 14, 29, 43, 57, 71 & 86. That's close to your values. The value for n must be below 14. Maybe it's worth a try.

On the Richtung-Zisch.wav file:
The NW2 documentation says, this loco sound is played when there is a change of direction.

Klaus



Am 07.09.2019 um 19:35 schrieb conrad:

Marc,
?On the DS64 the turnout addresses are independent of the board addresses.

Wayne,
JMRI (AFAIK) is not normally aware of DS64 board addresses. The exception to that is that when using the DS64 programming tool which you appear to have found. It asks you for the board address and will then send the programming command to the correct board.

I personally have kept around the last version of the no longer supported LocoNet Checker because it does a much better job with DS64's, including identifying board addresses.

HTH,
Steve
"Breezlys"

Hi BillyBob and Steve:
The console did not report anything unusual but when I disconnected EVERYTHING from the DCS240, left it for awhile and then reconnected, it reestablished the USB connection in both directions. ?Power cycling alone had not worked as well as disconnecting LocoNet. Everything needed to be disconnected. ?Seems to be working fine now. ?Thank you very much!!! I will also try the PR4 as an alternative as well.?
Bob

Mack,

On 8 Sep 2019, at 7:20 AM, Mack <bmcconalogue@...> wrote:

One question Dave - the factory reset option - I have a sound programmed (Legomanbiffo) decoder. I've only changed the address. The factory reset option you mentioned from the program window sounds like a full factory reset, not the same as the CV8=8 reset. Just wanted to check what that do to do the decoder if I used that in future?

The three are identical; Full Factory Reset, CV8=8, JMRI Decoder File Reset.

ESU only has one kind of reset.

But ESU differs from most other decoders in that the Factory Defaults are user changeable by using LokProgrammer. That is because there is no one correct set of defaults for the ~2,000CVs for the many (will soon be many hundreds of) Sound Files.

When a decoder leaves the ESU factory it contains a (deliberately) awful minimal sound project; you can drive the loco, start/stop the awful "prime mover", blow the awful "horn" - just enough to check basic decoder functionality.

It's the responsibility of whoever loads a Sound Project to ensure that the CV defaults for that project are written through to the "Factory Defaults" memory areas to overwrite forever the distributed defaults. In older versions of LokProgrammer this checkbox was not enabled by default and caused a huge problem for end-users if the person loading the sound File didn't enable it. ESU changed that to reduce the issues that was causing.

If an ESU decoder reset doesn't restore your decoder to as-received behaviour, there are several possibilities:
1) A CV15-16 lock (but then you wouldn't be able to read CVs either.
2) Failure of Sound Project Loader to write through appropriate factory defaults.
3) Corrupted decoder contents due to local event (short, electrical spike).
4) Damaged decoder due to local event.

With JMRI you can only rule out (1).

With a LokProgrammer and a new Sound Project file you can rule out (2) or (3).

Can you still read the Information Pane? If so, please do so and report back with the displayed Loco Name and Loco Type. Does it match what you expected? What did you expect?

Dave in Australia