Skip to main content

Good evening:

I have a situation with a PS3 locomotive when attempting to upload its corresponding chain files after a sound file upgrade.  I am at a point where I would like to share the problem with the group prior to further troubleshooting.

BASE ISSUE:

I start with uploading a PS3 sound file, found on the respective locomotive's MTH page.  This is successful, and the unit performs an audio start-up.  The unit can be added to the remote and respond to audio / visual related commands, (bell horn, headlights, markers, etc).  It also could have already been in said remote previously, and respond to the same audio / visual commands in like manner.  Any movement command via the thumb-wheel or manual entering of speed via the remote have no effect, which I might expect prior to the chain file upload.  Next, the attempt is made to load the respective chain zip file.  The DCS Loader finds the locomotive and successfully queries the electronics up to the EIS information.  The following error is returned at the point of the EIS query :

The error perpetuates regardless of the number of 'Retry' attempts.

 

RELATED NOTES:

  1.  The environment is Windows 7, x64, running DCS Loader 5.0.
  2.  The TIU runs DCS 5.0, and shows no issue in any respect.  The remote runs DCS 5.0 and also shows no issue in any respect.
  3.  The DCS Loader always sees the TIU and PS3 board successfully.
  4.  Any attempt to load a *.mth sound file is always successful.  Any subsequent attempt to load the *.srec chain files, (loaded as the *.zip file the DCS   Loader calls for), always fails with the error above.
  5.  At no point was any upgrade process attempt interrupted or halted prematurely.  
  6.  The process of sound file and chain file uploading was previously successful 3 times on this PS3 board, using different sound files.

 

REMEDIATION STEPS ATTEMPTED:

  1.  The locomotive, TIU and PC were fully power cycled (>15 minutes) repeatedly.
  2.  Fresh copies of the sound and chain files (from the MTH website corresponding to this engine), were used.  The sound file upload is successful, the chain file upload fails with the error above.
  3.  The original factory sound file, previously backed up, was used.  The sound file upload is successful, the chain file upload fails with the error above.
  4.  A non-exhaustive search of the DCS Companion, the ORG Forum, and Google, (in that order), were performed with no results.
  5.  The topic now shared on the OGR Forum.

 

REMEDIATION STEPS NOT ATTEMPTED:

  1.  The use of a different PC.  I see no need for that given the successful DCS / hardware communication in all other respects with this system.  It also would be a pain in the neck, which I would like to avoid unless recommended here.
  2.  Testing the sound / chain upload process on a different locomotive.  Until I get some idea of what is happening here, I will not attempt upload process on any other locomotive.
  3.  Replacement of the PS3 board.  I don't have one, nor do I intend to acquire one at the moment.
  4.  The upgrading of the system to DCS 6.0.  Further troubleshooting should be done using the DCS version used in troubleshooting to this point.

 

This may be explained in that PS3 boards are not designed for numerous (3 or more) sound uploads.

Otherwise, the board appears to require work beyond that which I am equipped to perform.

I would appreciate any contributions or suggestions with regard to this issue.  Thank you.

Attachments

Images (1)
  • mceclip0
Original Post

Replies sorted oldest to newest

First off, put the locomotive on a short test track powered by a fixed TIU channel.  Second, power the TIU channel with filtered DC voltage, it makes loading files to PS/3 and even PS/2 go much smoother.  I have found that loading sound and chain files on my test bench with DC from a bench supply goes faster and with less errors than using an AC supply.

Are you getting morse code beeps when you apply power?  There are faults that can occur to a section of memory, that should not be written too, but it can happen.  If so, you can't load the chain file via the DCS loader.  Instead it has to go to MTH to load with special fixture.

When loading Chain Files it is always best to apply power and then wait for 15 seconds.  If the board stays silent, load chain file.  IF the board starts beeping, let it continue as it is checking new chain file data against old data, and writing to memory.  Once it does, it will start up conventionally.  Once start up is complete, load the new chain file.   You will get this cycle to repeating after that chain file load.  Once it does the beeping on the next power up.  It will be fine and not do it again, until AFTER the next time you load a chain file.

If you do continue to get morse code beeps, even if it starts up and works, after EVERY power application, it has to go back to MTH. 

It is troubling no motion after loading soundfile, the PS-3 boards have test all chain file of an SD-70 so everything should work.   G

Thank you for the replies.

GGG -- The Morse code beeping happened only during 2 successful sound / chain upload processes.  All the other times, including failed upload attempts, there is an alternating flash of the forward and rear headlights for roughly 5 seconds.  This is followed by a relay click after which the headlights shut off.  I have typically then waited a minute or so after the headlights go out prior to attempting any uploads.  The failures are then as described above.

There is another tidbit I failed to mention.  After a successful sound file upload, motion commands are ignored while audio / visual commands are performed, which I mentioned this above.  What I failed to mention is that after the subsequent chain file upload fails, the unit no longer responds to any command from the remote.  However, the unit is still visible for the next sound file upload attempt, which follows the same loop as described above.

I have yet to attempt any upload using a DC power supply, but I will post the results of that test after I am able to perform it.

Thank you.

Last edited by Pantenary

Thank you again for the replies.

John:  The collective instructions on power-cycling are clear.  I have always (as far as I remember anyway) allowed at least a minute or two after an initial power-up, prior to attempting an upload.  I also allowed a minute or two after an upload attempt (success or failure), before any power-down.  I would then leave it powered down for a few minutes before attempting the process again.  I have not had a chance to try the DC power supply method, but the plan is to do that this weekend.

C.J:  I will attempt what has been suggested, and if that fails I will attempt a factory reset.  The latter had been my next move anyway, but I thought it wise to consult those wiser in DCS than I before proceeding to that step.

Marty:  Indeed I did use the 'flash' button for all attempts to load chain files, as prescribed in the Companion.  This was previously successful.  Did I miss anything?

GGG:  This board yielded the beep code one time, upon a start-up after a successful upload attempt.  Since then, start-up after at least one successful upload attempt and all the failed upload attempts have yielded the flashing headlight code.  I have not noted what the code actually is.

6/26/17 UPDATE:

On the advice I received from this thread, I attempted an upload of chain files again for the problem locomotive.  A different set of conditions was used for this test, which are listed below:

  1.   A different Windows 7 PC was used, one that has run various DCS updates successfully in the past.
  2.   A different TIU was used, one that has also been a part of successful sound and DCS operating system updates in the past.
  3.   The test rig was an isolated 40" section of Atlas track, powered by a regulated 16VDC supply.  This powered Fixed Channel #1 on the TIU.

 

The procedure was performed as listed below.

  1.   The TIU was powered up, followed by a ~60 second hold.
  2.   The locomotive was powered up, followed by a ~60 second hold.  (NOTE: the alternate headlight flashing behavior was observed).
  3.   A factory reset of the locomotive's P3 board was performed via the remote, followed by a ~120 second hold.
  4.   The locomotive was powered down, followed by a ~120 second hold.
  5.   The locomotive was powered up, and 'started' via the remote.  Sound and visual effects were normal, however there was no response to motion commands from the remote.
  6.   The locomotive was 'shutdown' via the remote, and a sound file upload initiated via the DCS 5.0 loader.  This ran successfully, resulting in the same effects behavior reported in step #5.  This was followed by a ~120 second hold.
  7.   The locomotive was 'shutdown' via the remote, and a chain file upload initiated via the DCS 5.0 Loader, using the 'Flash' button as prescribed in the DCS Companion.  This resulted in the same failure screen as was originally reported.  This was followed by a ~120 second hold.
  8.   The locomotive was powered down, followed by a ~120 second hold.
  9.   The locomotive was powered up, and the alternate headlight flashing behavior was observed.  The was followed by a ~120 second hold.
  10.   An attempt was made to 'start' the locomotive via the remote.  There was no response to any commands from the remote. 

 

At this point, it appears this locomotive needs to be sent to MTH for a true 'factory reset'.  If there is any part of this procedure that is not correct, or I performed erroneously, please let me know.  Otherwise, thank you all for your input and advice.

Add Reply

Post
The DCS Forum is sponsored by

OGR Publishing, Inc., 1310 Eastside Centre Ct, Suite 6, Mountain Home, AR 72653
800-980-OGRR (6477)
www.ogaugerr.com

×
×
×
×
Link copied to your clipboard.
×
×