Is there a way to slow down the pulse rate of an LED set to gyra lite in JMRI? On the lights tab I’ve tried adjusting oscillating light modulating, oscillating light latency, and momentary pulse but the pulse remains unchanged. And, yes - I did write the changes.
Thanks,
Tom
Hi, Tom
You bring up a good question. I pretty much settled for “out-of-the-box” settings but it would be nice to customize such an effect.
I did find this in the TCS users manual:
TCS_effect by Edmund, on Flickr
http://tcsdcc.com/sites/default/files/2018-04/Comprehensive%20Programming%20Guide.pdf
That may be helpful. So far I haven’t found the same adjustments available for ESU. Soundtraxx mentions a CV 59 with a range of 0-15 for “Hyperlight” flash rate. Not to be confused with phase A and B outputs for ditch lights.
Good Luck, Ed
Does the decoder in question support adjusting the pulse rate? Remember, JMRI is only a GUI - It can’t magically change what the decoder is capable of.
But if the decoder doc indicates it does support that adjustment, that doc should also give you the CV(s) and value(s). If those haven’t been incorporated into the JMRI definition for that decoder type (that’s up to the author of that definition), just use either the CV tab or the single CV programmer in JMRI to write the correct value(s) to the correct CV(s).
Oh, and if you’re using an NCE Power Pro, keep in mind that an issue in the NCE Power Pro firmware causes the wrong CV to be written to in Program Track mode for any CV>256. No way of telling if that applies in this case since we don’t know the decoder brand/model/CV(s) involved.
Steve,
I’m using a Power Cab with a TCS FL4 decoder. I’ve adjusted the lighting CVs for a Loksound Select (IIRC, they’re CV252 and >) a couple of weeks ago and I had no issues.
Tom
Using the manual page Ed provided, adjust the settings on the ‘Lights’ page of your roster entry.
Peter
The Power Cab doesn’t have that issue, only the Power Pro when using the programming track (POM works okay).
Also, ESU has provided a workaround for their decoders that has been incorporated into JMRI, so you’d only see the issue with an ESU decoder if you used the cab rather than JMRI on the Power Pro programming track.
However, the ESU workaround in JMRI doesn’t help when writing to CV’s >256 on non-ESU decoders with the Power Pro programming track. For those you’ll need to use POM.
Having said all that, it looks like (I don’t use TCS decoders) what you need is on page 11 of this document.
Thanks for the TCS decoder manual, Ed. I increased CV 113 (Max Bright Duration) from “9” to “35” and that helped give the LEDs the mars lighting effect of a 1-sec pulse rate, which is what I observed on the Aerotrain DVD that I have. The default of the FL4 decoder was closer to 0.5-sec.
I might play around with the other CVs on pg. 10 a bit more but I’m pretty happy with the results. I’m also hoping to be able to post a video of the results here sometime in the near future.
Tom
Glad that worked for you, Tom.
There are SO many options on decoders today that it can be overwhelming. Add to that the variables in architecture of each manufacturer’s design and it can be a real challenge to keep track of it all.
Regards, Ed
Just another reason I stick to one (or two) types of decoders. And that may go down to one in the future (though I will not replace any existing motoor-only TCS decoders) as I plan to start installing Lokpilots for non-sound use to go along with my Loksound sound decoders.
–Randy
I wonder if we should stock up on Loksound decoders, though?
Version 5 is around the corner. How much different will it be than the V4? Loksound Select will be dropped as from what I hear, there are components that are no longer available?
http://www.esu.eu/en/products/loksound/loksound-5-loksound-5-dcc/
Regards, Ed
The 5 is just more better. Seems mostly the same just with an improved drive and even higher quality sound. I’m not worried about a mix of version, I still have my two T1’s with v3.5 decoders in them. Hopefully they get the North American sound projects converted over. The selection is somewhat limited at the moment - no Alcos for one.
The Select and the V4 were the same hardware. Only different firmware made it a Select, where you had to load the entire sound project and not just change individual sounds, vs a v4 where you could change individual sounds. I was actually using v4s for my RS3s, because the Select RS3 project did not include the horn I needed, even though the horn was available in the ESU sound library. A minor change like that where the sound file already exists in the correct format was easy, just as easy as swapping the whole project on a Select. No sound editing needed, just set the desired sound from the library to the old horn slot using the Lokprogrammer.
–Randy
That’s good news, Randy. I’m looking forward to trying one out.
Thank You, Ed
Well, I promised a video of the results so here it is:
I designed and put together a universal testing platform for the task. In the video the primary decoder (foreground) is a Loksound Select micro and the secondary decoder (background) a TCS FL4. The Loksound decoder will operate the motor/sound and front headlights and the TCS decoder the rear taillights. Both are programmed to the same address “1001”.
The rear taillight default is gyralight. The red tailight (left) operates in forward and white taillight in reverse. Pressing F5 changes either one to constant lighting. F6 activates the inside pair of front headlights in gyrolight mode and only in forward.
The only thing remaining that I would like to accomplish is the ability to activate the inside pair of front headlights so that they are either constant on or off. That would allow them to be activated in three distinct modes: constant on, gyralight, or off. Currently I can program it to either constant on/off or gyralight on/off but not all three.
I tried reprogramming F7 to accomplish that but have been unsuccessful so far. If anyone has any solutions I’m open to them.
Thanks,
Tom
Just use 2 function outputs, one set for constant on and one set for gyralite. Both off, light is off. Gyralite one is on, you get Gyralite effect. Constant on one is on, with or without the Gyralite one, you get a constant on.
Even if the ESU conditional functions can handle this, you;d need 2 different buttons to get all 3 states. But more than one function wire can connect to th same LED so that more than one key and/or effect can be involved with a given light.
–Randy
Randy,
On the Select micro, F0F is used for the two outside headlights, F0R for the center red headlight, and AUX 1 & 2 (green & purple) for the two inner headlights. Wouldn’t I need a 6-function decoder to tie AUX 3 & 4 to AUX 1 & 2 for the 3-state condition? The Select micro is only 4-function. Perhaps an excuse for purchasing one of the new Loksound V5 micros?
Tom
You could upload the video to youtube.
I tried to post your video in the trains test forum and it works there. No idea why it won’t work here.
Do the two inner headlights need independent functions?
Every time I see threads with all kinds of strange lighting requirements (and this one puts most SP locos to shame!) I am forever more greatful that my prototype never messed around with that stuff.
Otherwise, you need more functions. And the oonly Loksounds that have more than 4 are the ones with the 21 pin connector so you need a motherboard. The 21MTC Select has 8 total outputs, but you need to use the style of motherboard with the drievers on it as the 4 highest ones are logic level only (which is how they get so many functions on such a small decoder).
The Loksound v5 Micro says is has 6 amplified functions plus one additional logic level, so the newer decoder may be what you need to get all this.
–Randy
Yea, Henry. I found it worked in the test forum and in PMs but not when posted here on the forum. The present forum software is quirky that way and has been for years. [:S]
[Edit: I took your suggestion, Henry: I uploaded the video to Youtube, inserted it in the thread, and it appears to be working fine. Thanks for the shove in that direction. [:)]]
Tom
Randy,
The DVD footage I have of the NYC Aerotrain (Green Frog Productions) shows it operating in a variety of lighting combinations:
Front headlights:
Rear taillight:
I don’t know if the F0R white taillight (right) ever operated in the gyralight state but it was convenient to wire it up/remap it similar to the left red taillight so that it activated to constant when pressing F5.
There isn’t much room under the
Hmm, I wouldn;t have thought a Gyralite would always stop at the same position when the movement was turned off, meaning htat if you just lit up those lights in constant on, they’d possibly point in all sorts of directions. Are you sure they sometimes act like gyralites and sometimes are steady, and it’s not just a filming issue, like a still made to look like a motion shot or something?
–Randy