Skip to main content

Robert,

Not only do I not know the value (what is it?), I don't even know what FPGA, DSP, and ASIC mean

The following is from The DCS O Gauge Companion 2nd Edition, page 206. Look at the Differences column for the Rev. L TIU. The discussion of FPGA vs. ASIC for digital signal processing (DSP) is the same for PS3 engines, which will be further discussed in the 3rd edition:

 

  Untitled

All I know is that PS2 gives me reliable control of loco direction, speed, lights, whistle, bell, couplin etc., without being limited to blocks,

How is the any different with PS3?

It is also fairly repairable, according to GGG, does not have a troublesome 40-pin connector 

That's the price you pay for miniaturization of a more capable board. Regardless, for the vast majority of operators, who don't mess with the engine's electronics, this is a non-issue.

 

It's also a non-issue for those who install a future PS3 upgrade kit, since those upgrade boards (PS32 and the future 3 volt model) don't have the "troublesome" 40-pin connector (it's actually the wires that are the issue, not the connector).

 

FWIW, I don't particularly care for handling the 40-pin connector, either. However, if treated with respect, it's perfectly capable of being removed and replaced without any issues.

permits changing sound and control files (all in one file) easily.

That's just not true.

 

PS3 sound files allow one to change sound and speed control in exactly the same manner as do PS2 sound files.

 

PS3 Chain Files allow one to update/change other parameters in PS3 engines that simply cannot be changed at all in PS2 engines without special equipment that only MTH possesses.

Attachments

Images (1)
  • Untitled
Last edited by Barry Broskowitz

Well, those Beeps should only happen when you are actively loading the chain file.  If you have them now every time you start up or shutdown the engine, the chain file load did not go as planned and it is possible a section of the board memory was over written causing the processor not to function correctly.

 

Did the chain file load go normally?

 

If the processor memory is corrupted, you need to send the board back to MTH so they can reflash it with a pogo fixture.  Not something a tech or customer can do.   I had this happen once on my first load, but not since then, and I have gone through about 10-15 PS-32 chain file loads. 

 

This is the applicable portion of Barry's post above:

The PS3 engine's electronics are not permanently damaged. Rather, the engine's firmware code is overwritten and the engine's processor no longer has an operational program to follow. Therefore, the board's processor shuts down and the engine is no longer functional. Unfortunately, the correction of this problem is beyond the ability of the DCS operator to effect, since doing so requires the use of factory-type procedures that are currently available only to MTH.

  G

 

Ok,  That might be normal.  I guess we need to start back from the beginning now.

 

Now that you reloaded the PS-32 chain file.  If you start up your engine what does it do specifically?

 

If every thing runs fine but speed control, we can hone in on that.  Tach reader can be bad.  But gap, cleanliness of the tach tape matters.

 

If there is hardly any voltage change when reading orange wire on tach with red probe and blue with black probe.  The reader may be bad.  Replace tach reader and test engine again.  G

That's the price you pay for miniaturization of a more capable board.

My understanding from previous threads is that the PS3 board is actually slightly larger.  What are the additional capabilities?

PS3 Chain Files allow one to update/change other parameters in PS3 engines that simply cannot be changed at all in PS2 engines without special equipment that only MTH possesses

How does one change parameters, and what parameters can be changed, by the user, with programs available to Mr/Ms Average User?  To me, simply blindly trying a different chain file to see if it does more of what Average User wants, does not cut the mustard in this regards, but I'm always willing to learn if I'm missing something.

 

Notwithstanding the differences you note in the Companion, on my layout I've detected no differences in operation between using Rev G and Rev L TIUs, nor between PS2 and PS3 locos.  The same foibles are there, and reaction times don't noticeably differ.  I look forward to reading what you say about PS2 vs PS3 in the next edition.

 

I just got back to working on this issue, I checked the voltage change from black to white stripes on the tach reader.  it ranges from 3.16 on black stripes to 2.65 on white strips. I may have another tach reader I can try if this might be the problem. 

 

Could my using the wrong chain files have caused the reader to fail? 

 

Should I start over from the beginning by loading the proper chain files and the sound file again?  

Unless your a tech  you can't purchase.  The board can be bench tested by a tech.  This will determine if the board is good or not.  If it work in the bench tester, you know it is the locomotive wiring or hardware.  I can test if you don't have a ASC in your area.

 

One thing you may want to do is remove the board from the bracket.  Reseat the 2 boards and reinstall in the tender.

 

Also, you did not by chance remove any of the jumpers on the board did you?  G

Thanks, I may take you up on the offer to test it. There is not an ASC in my area, we do have a PS2 3 volt test set at work. I am planning on ordering a new tach sensor today, AG-0000058 as someone last night. The tach reader spacing is currently 1.1mm, I was thinking about AG-0000083 which has a .5mm spacer giving me a .6mm gap.

Originally Posted by Papajohn88:

Thanks, I may take you up on the offer to test it. There is not an ASC in my area, we do have a PS2 3 volt test set at work. I am planning on ordering a new tach sensor today, AG-0000058 as someone last night. The tach reader spacing is currently 1.1mm, I was thinking about AG-0000083 which has a .5mm spacer giving me a .6mm gap.

That is the test set to use.  Plug the 3V connectors to the board and test it on the Tester.  See if the motor runs with speed control with chuffing and puffing smoke.  If so the board is good.  G

I have been doing some more checking, with the tach sensor connected properly I get 1.18VDC between the blue and gray wires. If I remove one or both of them from the sensor I get 5.07VDC between the blue and gray wires either in the loco or carefully checking where they are plugged into the PS-32 connectors. I am not sure if this is proper behavior or not.

Yes it was speedy service.

 

I installed the new tach sensor today, still no joy. It still runs away, when I put the boards on the test set I had the same results.  I guess this will be a shelf queen until I can afford another set of boards for it.  Having them reflashed by MTH might solve the problem, I have not checked with them to find out if I can send the boards in or if an ASC must send them in.  I am sure the warranty is null and void since I did the installation. That does not bother me as much as the overall cost will.

 

Thanks to everyone that responded to my questions and provided information.  Your help is very much appreciated.

 

Sincerely

I have not touched the jumpers on either of the boards, I have separated and reseated the daughter board. I have checked the wires to the sensor, the gap is 1.1mm last time I measured it and the flywheel is clean. 

 

I have reloaded the flash file, removed track power, applied track power again and then reloaded the sound file. I used the sound file for 30-1287-1,  http://mthtrains.com/sites/def..._up030221efin_3v.mth

 

 

Originally Posted by Papajohn88:

Yes it was speedy service.

 

I installed the new tach sensor today, still no joy. It still runs away, when I put the boards on the test set I had the same results.  I guess this will be a shelf queen until I can afford another set of boards for it.  Having them reflashed by MTH might solve the problem, I have not checked with them to find out if I can send the boards in or if an ASC must send them in.  I am sure the warranty is null and void since I did the installation. That does not bother me as much as the overall cost will.

 

Thanks to everyone that responded to my questions and provided information.  Your help is very much appreciated.

 

Sincerely

Take a peek at the  motor leads right at the motor. One thin strand of wire touching the motor chassis and you'll have a run away.   Having said that,  I can no longer keep up with all   this stuff.   It's getting tooo confusing.

Originally Posted by Papajohn88:

Gunrunnerjohn,

If that is the case then it is beyond my current capabilities. I do have a friend that has SMD capability at his business I might be able to get him to replace it. I assume that is on the bottom board.

Not to fear, I thought this was the 3V PS/2 board for some reason, so it's a different issue anyway.  AFAIK, repairing this on a PS32 board is not likely in the field.  I know we have no information from MTH about any component repairs on the PS3 boards of any flavor.

 

I just completed checking the entire wiring harness used in this PS-3 upgrade kit, there are no problems with the wiring harness. This was all working correctly until I applied a set of chain files to the PS-3/2 board set.  Obviously I should not have done that because it now does not know about the tach sensor.  I have since applied the chain files that put it back to the original state however it still does not recognize the tach sensor.  I will be putting it on the shelf for display now and devote my time to other projects. If anyone has a set of boards they would sell me I will gladly purchase them so I can get this thing running again.  

 

Thanks for all of your help.

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.
×
×