Installed and tested v5 decoders. Seemed to be working ok. Changed the speakers over, now the deciders are misbehaving. They only respond in6 14 speed steps - anything above step 14 brings the loco to a halt. The sound function buttons have gone haywire. Pressing on any function button makes a random selection of sounds lock on.

I've tried a decoder reset; tried reprogramming to 128 speed steps; tried restarting jmri; tried restarting the sprog controller and decoder pro. Nothing seems to help.?

Anyone got any advice I could try?

On Sep 6, 2019, at 11:31 AM, Jon Miller <atsfus@...> wrote:
I have a very very early decoder I have lost the instructions
to. The only ID I have is the sticker on the chip. It reads;

MELEC TL2054

It may or may not be a sound decoder so maybe someone could tell me what they think it is. Also I tried to read the pertinent CVs using JMRI and couldn't.

If it is old enough, it may not support anything but the standard NMRA registers. Try reading register 1 in register mode.

I have a couple of old decoders I have to do this with.

Paul

On Thu, Sep 5, 2019 at 07:44 AM, Dave Sand wrote:

/g/jmriusers/files/Script%20examples//LinkedTurnouts.py

Thanks so much Dave for spending time on this. I will try it out over the weekend!

Dave B

Roger,

Yes, same deal with custom icons etc..., keep them in the user directories.
The idea is you repeat the same tree as the production content and most of
the tools know to look for them there in addition to the production files.
And for some cases, like signal rules, if the same file name is in both
places, it should use the one from the user directory tree instead of the
production version. Handy for testing ideas and customizing stuff. But I'm
not sure exactly which cases it works automatically, and which need help.
Where it really helps is when you need help. You can zip up your custom
directories of stuff and then the panels find all their parts.

-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.org
www.syracusemodelrr.org

Thanks bob!


Roger

开云体育

 ??? I have a very very early decoder I have lost the instructions 
to.? ? The only ID I have is the sticker on the chip.? It reads;

MELEC TL2054

 ??? It may or may not be a sound decoder so maybe someone could tell me what they think it is.? Also I tried to read the pertinent CVs using JMRI and couldn't.

-- 
Jon Miller
For me time stopped in 1941
Digitrax  Chief/Zephyr systems, 
SPROG, JMRI User
NMRA Life member #2623
Member SFRH&MS

Although it’s perfectly fine for people to run their own modified scripts, it’s also nice to have ones that do what people want. So I’ve added a jython/SetUnknownTurnoutsClosed.py script that just sets the UNKNOWN-state turnouts.



It’ll be in the next test release.

Bob

On Sep 5, 2019, at 4:23 PM, Roger Merritt <merritt_roger@...> wrote:

Bob,

Found the problem.

Since I had moved from a bootleg script that clears all UNKNOWN states of sensors and turnouts to the official scripts that is when the problem came up. Seems the the script "SetAllTurnoutsToClosed.py" closes all the turnouts, even the signalheads for the SE8Cs. After changing the 'IF (turnout) is not closed' to 'IF (turnout) is UNKNOWN' To set the turnout to closed cured the problem.

Now I have to remember to keep this altered script in my USER file section each time I do a update to new version.

--
Bob Jacobsen
rgj1927@...

Conrad,


I repeat your points from the referenced posting and put my answers below.

Yes, I did read the Zimo page you referenced but I did not see a

explicit copyright disclaimer, something akin to the open source licence with JMRI, etc. All of my work is for my own private use. I just don't know if I can share it (for free). It's my hobby, not a business (too old anyway).

I think we agree here.

Of course, once i stumbled on Zimo I dropped my work on clicks, pops,

and funny volumes and went right into trying to create a vsd file from their NW2 zip file. So far no success. I used an original NW2 vsd config file as a template and moved Zimo's wav files from their zip file to the vsd "sounds" sub-folder. I also tested each wav file for format and identity as they are in german - kompressor vs. compressor:). The result so far is failure. In the "configure new VSDecoder" window I can "load VSD file" but nothing appears in the "select a profile" drop-down window. This is where I'm at.

Your approach is right. Please make sure the profile name in config.xml is valid. I recommend to open the JMRI System console (Menu "Help", then click on "System console") to see if there are any messages.

I am not sure what you mean by the zip files being easy to adapt to

config.xml format. I only see the wav files and a zpr folder which, unlike vsd, I cannot rename as zip and extract. In addition, what do you mean by the wav files being bound to Zimo? Is that why I am stuck on the NW2 project?

I meant to copy the files to a VSD folder, as you already have done. "adapt" was not a good choice by me. The .zpr file is a special ZIMO format and therefore not relevant.

PS I'm up to sharing a config file.

Me too.


Regards,
Klaus





Am 06.09.2019 um 16:36 schrieb conrad:

To all:
We'll be off babysitting all day.? If this was not the correct way to start a new post, feel free to edit/delete or add.
Conrad

Suggestion for Steve Todd -

It would probably be helpful to many users if you were to post a new image with the most recent changes to Raspian Buster applied.

Yesterday I was working with a friend that was using a 4Gb, Raspberry Pi specifically because he has two monitors. In the June 20 version of Buster, this board can have boot failures and other problems when connected to two monitors. (Not always, some monitors work better.)

We disconnected one of the monitors, connected to the internet and did an update/upgrade. This solved the boot/monitor problems, and as a bonus, significantly sped up the Rpi.

Given the number of relatively non-technical users of your image, it's probably a good idea to update the image with the most recent updates applied to Buster.? Even those that aren't experiencing problems would appreciate the speed increase.

Thanks for putting the image together.? It's making JMRI much easier to install for many model railroaders.

gs

To all:

We'll be off babysitting all day.? If this was not the correct way to start a new post, feel free to edit/delete or add.

Conrad

I'm working on creating VSD files using the wav files from ZIMO.? see referenced post:

/g/jmriusers/message/163579

Conrad

PS hopefully this is how one starts a new topic

Ken,

? ? Thanks for the tip.? Does this also apply for those oddball panel icons too?

Roger

There is also the method validateSystemNameFormat that can be used:

name = [...get from external program...] try: sensors.validateSystemNameFormat(name) except jmri.NamedBean.BadSystemNameException: print 'invalid name'

Which will check if the name is potentially valid (i.e. could be used), but will not create a Sensor. Note that this method does not check if the sensor name in question is really associated with a sensor, but merely checks if the name could be used.

Am 06.09.2019 um 00:35 schrieb conrad:

Of course, once i stumbled on Zimo I dropped my work on clicks, pops, and funny volumes and went right into trying to create a vsd file from their NW2 zip file.

Conrad,

Right, that's obviously a new topic and I recommend to start a new one.

There you can reference to the your last posting with /g/jmriusers/message/163579 (if you like).

I will then answer there. Thanks in advance.

Regards,
Klaus

Roger,

Easiest is to keep the file in your 'user' section and reference it there.
No need to do anything else with it,

-Ken Cameron, Member JMRI Dev Team
www.jmri.org
www.fingerlakeslivesteamers.org
www.cnymod.org
www.syracusemodelrr.org

--

Yes, I have always used my Locobuffer with the Digitrax software

Tom in Texas