i downloaded a sound file from my engine and is said it is a PS 2 3 volt file,which was correct. but when i downloaded it on my other computer it said is was a 5 volt ps2 file, how can that be?
Both computers were running windows 7 and the same TIU was run on both!
so then i did a factory reset threw the TIU remote and downloaded it again and then it said it was a 3volt PS 2 file.
Why would that happen?
Alan
Replies sorted oldest to newest
If you went through the service link on the MTH site, perhaps you clicked on the 5V file. There are links for both on some engines if they were offered if a 5V board set.
No john i did not even go on the websight for downloads of sound files! I was saving the sound files from PS 2 3 volt processor boards, and i used the same board on 2 different computers so i expected the same results!
?
Alan
If you downloaded and used a specific sound file and never downloaded again, it's bound to be the same sound file. I really can't understand what you think it happening.
I have a RTR engine, definitely in the 5V era, from the special edition SF F3 Railking passenger RTR set.
Same problem, there is only 1 download file (as expected given the age of the engine), but the uploader claims it is a 3.3V file (from MTH). I suspect there is a compatibility problem with their latest uploader and older engine images.
My engine runs fine, I was just updating my engines and decided, "why not?", but it soon turned into "guess not".
Though it is interesting that with none of the software updates to the TIU, remote or engines, has the bug gone away where operation becomes unpredictable after using the mic function on the remote. The bug is that the FM receiver locks "on" inside the engines -- happens to them all, from 250$ RK engines to 1250$ Premiere --- and then the engine is unresponsive until pressing the mic button a couple more times. I suspect this must be some sort of flaw in the design of the MTH command protocol. The engine is for some reason placed back into FM receiver to speaker mode, and accepts no commands except the command to unlock the FM receiver. This is odd given that the engines don't have the problem with piped in constant audio (probably because the software is designed to take commands in this mode).
Maybe one day MTH will let us see their protocols, and us system engineer types could fix bugs like these. Till then, I guess I will have to live with it (or until my wifi-receiver-on-board idea comes to fruition - 1 guy has already did this on youtube).
The microphone issue has been around for some time, and I don't see any movement to fix it. You diagnosed the fix, just hit the button a couple of times.
I can't think of any good reason to be uploading sound files for locomotives that are functioning normally, why would you do that?
John is correct, and, as I recall, he has first-hand experience in that regard. 
No comment! 
None is required!
Access to this requires an OGR Forum Supporting Membership
