|
|
Post by nebrzephyr on Apr 3, 2022 12:28:27 GMT -8
Does the ESU speed tune function (CV54=0, F1) only work for sound decoders?
Bob
|
|
|
|
Post by edwardsutorik on Apr 4, 2022 7:15:42 GMT -8
No.
Instructions for Lokpilot 5 show the same option.
Ed
|
|
|
|
Post by nebrzephyr on Apr 4, 2022 14:18:25 GMT -8
Apparently not for V4
|
|
|
|
Post by edwardsutorik on Apr 5, 2022 8:12:13 GMT -8
I just did a search on the Loksound group for "v4 AND autotune" and turned up a topic starting with message #24615, where it was stated that autotune DOES work in a V4 Lokpilot. None of the responders disagreed.
Ed
|
|
|
|
Post by nebrzephyr on Apr 5, 2022 12:03:50 GMT -8
Ed, after doing more testing,yes it works for V4. It does not appear to work for LokPilot Standard. which was the decoder that got me thinking it only worked for sound decoders.
Bob
|
|
|
|
Post by Gino Damen on Apr 10, 2022 10:12:53 GMT -8
Hi,
LokPilot Standard is the budget decoder. A bit like the ESU essential sound in some Walhers and ScaleTrains engines. It getsnthe job done, the control logic is the same but a lot of other options are stripped.
|
|
|
|
Post by nebrzephyr on Apr 13, 2022 12:34:07 GMT -8
V4 LokPilot decoder.
I guess I'm still not understanding how this is suppose to work. Using the ESU programmer I do the CV54=0, F1 and it works as advertised. I check the CV52-55 values and they have change from the default values. I do the "write decoder data" and save the project. When I later open the project the CV52-55 values are back to the default values.
Doesn't maker any difference if I'm using the programming track, or the ESU hardware programmer. Or if I check "over write default values" when doing the "write decoder data".
BUT, if I use Decoder Pro, open the that decoder, change CV52-55 to the revised values from running CV54=0, F1, and save, those CV values stick to the revised values.
I must be missing something. 
Bob
|
|
|
|
Post by jonklein611 on Apr 13, 2022 12:45:24 GMT -8
V4 LokPilot decoder.
I guess I'm still not understanding how this is suppose to work. Using the ESU programmer I do the CV54=0, F1 and it works as advertised. I check the CV52-55 values and they have change from the default values. I do the "write decoder data" and save the project. When I later open the project the CV52-55 values are back to the default values.
Doesn't maker any difference if I'm using the programming track, or the ESU hardware programmer. Or if I check "over write default values" when doing the "write decoder data".
BUT, if I use Decoder Pro, open the that decoder, change CV52-55 to the revised values from running CV54=0, F1, and save, those CV values stick to the revised values.
I must be missing something.
Bob
The tune is meant to be completed on a "normal" piece of track, not the programming section. It sounds like you're overwriting the tuned data with the defaults from the Lokprogrammer. |
|
|
|
Post by nebrzephyr on Apr 14, 2022 5:33:16 GMT -8
Oops, I should have said that the "auto-Tune" was run on main line track. That still doesn't explain why I can't get the values saved.
Bob
|
|
|
|
Post by jonklein611 on Apr 14, 2022 8:08:44 GMT -8
Oops, I should have said that the "auto-Tune" was run on main line track. That still doesn't explain why I can't get the values saved. Bob You need to read those values from the decoder and then save it to the project. You're overwriting the tune data with the defaults saved in the project file. |
|
|
|
Post by nebrzephyr on Apr 15, 2022 10:08:35 GMT -8
OK, here's what I have found. You want to run "auto tune" as the very last thing you do in configuring a new loco. As jonkleim611 stated if you save the project the new CV53-55 are saved. BUT, if you after that need to change some value, say a light function, which requires a "write decoder data", it restores the CV52-55 to default values.
Seems strange to me that it works that way. Am I missing something else?
Bob
|
|
|
|
Post by edwardsutorik on Apr 16, 2022 6:41:17 GMT -8
This is sounding like a problem that only comes up with the Lokprogrammer.
Otherwise, if I just change one CV with my command station, I would have to auto-tune again.
And so it seems a matter of the proper protocol for connecting a locomotive to the Lokprogrammer.
Ed
|
|
|
|
Post by nebrzephyr on Apr 16, 2022 12:04:53 GMT -8
This is sounding like a problem that only comes up with the Lokprogrammer. Otherwise, if I just change one CV with my command station, I would have to auto-tune again. And so it seems a matter of the proper protocol for connecting a locomotive to the Lokprogrammer. Ed Yes Ed, that's the way it seems to work. I don't understand why the changed CVs aren't kept. Bob |
|
|
|
Post by Gino Damen on Apr 17, 2022 12:48:40 GMT -8
Seems strange to me that it works that way. Am I missing something else? Bob Yes, complete your programming with the programmer and save the project. Now write the speed tune setting to CV54 and close the project (don't save it) and reopen it again. Next run the speed tune. When done, put the engine back on the programming track and read the decoder. When asked allow the settings to be added to the current project. Now the new settings are added to your project. Save it and your good. |
|
