I have two problems with my MRC Prodigy Wireless System: 1st) Sometimes, there is a delay between command and execution, but not always; 2nd) It memorizes some cabin numbers of previously used locos, and cannot delete them from the control's memory: that is, if I press the "Del" key on it, it momentarily deletes all locos from the list, except the first one listed . And, if I turn off the system at the outlet, when I turn it back on, the control has all the previously deleted locos in its memory. Anyone who has had these problems and solved them, could you help me please?
Oh my! This problem is not new and has been bothering me for some time. I would really appreciate it if someone who has already gone through this problem could help me, please, even if they have a system other than mine (Digitrax, NCE, Lenz, etc). Thanks.
It's been many years since I have used the Prodigy system, I believe the recall stack stores the last 10 or 12 locomotive numbers that were used. When you use a new loco the oldest one drops off the list. You can not clear the list or delete locos, I believe.
Thanks for your answer. I believed that, if I continuously pressed the "Del" key on the control, the system would delete all the locos stored in its memory, ending the operation registering the number 0003 (the factory setting)...
I power my 17' by 18' double decked HO scale layout with the original MRC Prodigy Advance DCC system although I had to have the firmware updated to the "Squared" level when I purchased the wireless conversion and throttles. I have tethered throttles, wireless throttles and the MRC WiFi module (up to eight smart phone throttles) in use. I recently hosted an operating session where we had as many as five HO scale trains operating simultaneously. While the system works quite nicely, I have run into a couple of problems (mine, not MRC's) that you might want to check.
First, there a couple of things to check regarding the response delay. If you are using less than 9 throttles, make sure the slide switch on the command unit is set to the Cab #1-#8 position. If this does not help, make sure that every throttle cab has its own address. If two cabs have the same address, it will confuse the command unit and cause delays or no response. If a tethered throttle and a wireless throttle both have the same address, the command unit with ignore the wireless throttle completely. I have run into this problem at two different operating sessions where operators brought their own throttles but we forgot about the throttle addresses.
As far as the recall stack, the throttle will toggle through the last five locos you entered into the throttle. Yes, you can delete locos from the stack by pressing and holding the DEL button. However, it will not clear all of the locos and default to address 003. Instead, it will clear all entered locos but one, whatever that address happpens to be. If you want to save certain locos in a tethered throttle's stack, make sure the locos you desire are entered in the stack, then disconnect the throttle's tether from the throttle bus/jack. If you want to save certain locos on a wireless throttle, make sure the locos you desire are entered in the stack, then press the SAVE button and power off the throttle. If you want the throttle to save address 003, you must enter that address before saving it. The system does not default to address 003.
One other tip in case you want to add the MRC WiFi module. You must have at least one circuit breaker between the command station and track to make the MRC WiFi module work well with multiple operators. If you rely only on the command station circuit breaker, every short will not only cut power to the track and throttle bus, but to the WiFI module as well (it just plugs into the throttle bus). This means that every time some dope derails his train, everyone using a smart throttle not only loses command of their trains but they lose their WiFi connection, too. Once the short is cleared, these operators have to first reconnect with the WiFi module, then reacquire their trains -- each and every time a short occurs. I installed an NCE EB1 solid state circuit breaker on my layout to avoid this problem. The trip response of this breaker can be adjusted to trip faster than the command station breaker but slower than any auto reverse modules or frog juicers you might have installed.
I hope this helps.
Hornblower
Wow, thanks for the lesson, Homblower. According to "Jack the Ripper", 'let's go by parts': 1) I didn't do a firmware update; 2) I don't have the MRC wifi module, because my system (Prodigy Wireless already came with it); 3) each of my controls (9) have a different address; 4) I still don't understand why deleting the loci listed in his memory, they are erased; however, if I turn the system off at the wall socket, after turning it back on, behold, the addresses "recently deleted" appear again. Thanks.