Got a shiny new SPROG3, all installed properly with JMRI, got my first loco on the program track, and it seems to read it just fine but when I hit the Program button in JMRI, it gives me access to every tab EXCEPT "Function Map" which is grayed out. Why on earth can I not look at the Function Map? I have JMRI 4.2.1, Windows 10 computer, loco is a Walthers Proto 1000 F3 with a LokSound 3.5 decoder (yeah, its a bit older but it works just fine).
Because no one ever wrote the function mapping in the definition for the Loksound 3.5. You're kind of on your own there. It's much easier than a v4/Select though because there aren't quite as many options. You can download the manuals from ESU's web site.
--Randy
Modeling the Reading Railroad in the 1950's
Visit my web site at www.readingeastpenn.com for construction updates, DCC Info, and more.
You're really better off posting a JMRI question like yours on the JMRI Yahoo list:
https://groups.yahoo.com/neo/groups/jmriusers/info
Although you'll probably get an answer here, the folks who actually write the JMRI code (and the decoder definitions) hang out on that list.
So if there IS a missing definition, or something that doesn't work properly, you're far more likely to have it corrected if you post your question/issue there.
I know that to be true from experience - My posting on that list, and subsequent off-list conversations with the developers, have resulted in both a major change to how JMRI Ops handles alternate tracks, and also the creation of the Athearn RTR SD40 Soundtraxx decoder definition (I supplied the raw CV data).
That's good to know (Yahoo usergroup), thanks for the tip! Hard to believe no one has ever written the mapping for the LokSound 3.5. I had that decoder installed back in 2009 and due to personal circumstances I had to shevle my model rairoading for several years. I have forgotten what sounds are mapped where so I was hoping JMRI would just tell me when it read the function mapping. Oh well!
It's not a missing decoder definition - I checked on my JMRI, the function remaps aren't even in the definition, but there is a Loksound 3.5 definition. I'd have to peek at the Loksound 3.5 manual to see exactly how the function maps work, I know it is a LOT easier than a v4, but mainly because there's aren't as many options. I remapped F4 and F2 on my PCM locos because the alternate whistle supplied on F4 was more accurate for the model than the one they had on F2.
I don't think the remap table would show what sounds are on each f key, it may show which physical output wire is assigned to each F key. The best it could tell with sounds is what sound slot is assigned to what key. As to hat sound is actually in that sound slot - you'd need Lokprogrammer to see that.
I know it's not a missing decoder definition.
My point was that no matter what the issue/deficiency might be, the chances of it getting fixed are just about nil if it's posted here instead of on the JMRI list.
The JMRI developers hang out there and are very active in problem resolution. But AFAIK, none of them visit here very often if at all.
Don't think I've seen anyone fromt ehre post here, at least about JMRI, other than people who are in both places.
Rememebr the decoder definitions get rolled up in each new release s unless someone JUST updated the Loksound v3.5 definition, it it's been updated it will be in the latest production release. Admittedly I do not check for such things, but I doubt there have been any updates made to that old definition. I never used it with my locos, in fact since I got a Lokprogrammer and swapped some of the sounds for real ones recorded off an actual T-1, I also swapped the sound slots so F2 had the freight whistle and I no longer needed function remapping. The only non-default CV values are the long address and some volumes. I like to keep it simple
rrinker Don't think I've seen anyone fromt ehre post here, at least about JMRI
Don't think I've seen anyone fromt ehre post here, at least about JMRI
That's exactly my point - The JMRI developers don't frequent this forum, so if an issue is posted only here, they won't know about it.
rrinker Rememebr the decoder definitions get rolled up in each new release s unless someone JUST updated the Loksound v3.5 definition, it it's been updated it will be in the latest production release.
Rememebr the decoder definitions get rolled up in each new release s unless someone JUST updated the Loksound v3.5 definition, it it's been updated it will be in the latest production release.
Right, but there is a caveat to that - If you created a roster entry with an old definition (that is, an older version of JMRI) and that definition later gets updated, your roster entry won't automatically get updated to use that newer definition even if it is included with a later release of JMRI.
The only way to update your roster entries is to select "Update Decoder Definitions" under the Action menu in DecoderPro or the Debug menu in Panelpro. See the "Updates and Migration" section of this page: http://jmri.org/help/en/html/apps/DecoderPro/CreateDecoderAdvanced.shtml
With all that in mind, my guess is that the OP created his roster entry(s) BEFORE the Function Map pane was fully-functional. If he hasn't refreshed his roster entry(s) as outlined in the linked section above, that may be why that pane is greyed out.
Why do I think that? Well, even though I don't have any LokSound V3.5 decoders, I just opened each of the three V3.5 definitions (LokSound V3.5, LokSound Micro V3.5, and LoksoundXL Version 3.5) in JMRI 4.7.2.
In all three of them, the Function Map pane was present and active.
EDIT: Link wasn't clickable for some reason. Fixed now I hope!
I see the OP has taken his question to the JMRI list and has gotten the attention of the developer who has written both the Locsound decoder definitions and the special JMRI code they require.
The main issue is that 4.2.1 is way too old for these decoders. Not having any of them myself, I completely missed that.
There is also the secondary issue of the OP having received bad/outdated info on the latest version of JMRI that can be used with his SPROG3 and Win10. He was advised to update to JMRI 4.6 or later.
(As an aside, on my Win10 layout computer I almost always run the latest test release of JMRI, and on occasion even unreleased daily builds to test/take advantage of fixes or new functionality. Never had an issue...)
Read the POST on JMRI User Forum and went looking for who was providing false info : - ) found this thread.
The information re ' functions ' is present in JMRI 4.2.1 for the ESU 3.5 decoders. Just not under FUNCTIONS..
It is under " Button Behavior " and " Effects ".
So if you simply issue a " READ ALL SHEETS " (and go get coffee or beer) you will capture all the information.
This was later changed/corrected/reorganized in JMRI 4.3.2 to give it a certain ' standard ' feel. Somewhere around te to 4.5.2 this conversion was completed and it was all under FUNCTION MAP pane.
Since you are new to JMRI, the recommendation is to load Production release 4.6 and not some TEST version. There is no issue running JMRI, Sprog III, under Win10. I contribute to the JMRI definition files.
Marc N Fournier, Quebec
(PS: I have not been in here for a long, long time)
I did update to JMRI 4.6 and that did fix the problem. Like I said, I am new at all of this so it's a slow learning process! Thanks for all of the replies.
" With all that in mind, my guess is that the OP created his roster entry(s) BEFORE the Function Map pane was fully-functional. If he hasn't refreshed his roster entry(s) as outlined in the linked section above, that may be why that pane is greyed out.
Why do I think that? Well, even though I don't have any LokSound V3.5 decoders, I just opened each of the three V3.5 definitions (LokSound V3.5, LokSound Micro V3.5, and LoksoundXL Version 3.5) in JMRI 4.7.2. "
Well not quite.
I loaded JMRI 4.2.1, created a roster entry using 3.5 ESU. The Function MAP was grey out. Used the " Button Behavior " and "Effects " panes instead. Saved the roster entry.
Upgraded to JMRI 4.5.2. All content of " Button Behavior" and "Effects" panes were merged into the "Function Map" pane without any intervention. Both "Button Behavior" and "Effects" are gone in JMRI 4.5.2
Upgrade to 4.7.2. My roster entry for ESU 3.5 decoder was still valid.