PS2 PlayStation 2 MECHACON Adjustment Program (PMAP)

ironsniper1 said:
i didnt prevent it from opening, all i did was type tray close and it tried to close and then opened and showed that error,
Click to expand...

Failure by the MECHACON to detect the tray being retracted, will probably also cause these symptoms. It's why I gave you that analogy about blocking the tray from being retracted - it'll also result in the same behaviour (tray will eject again and you will get this error).

ironsniper1 said:
someone on another forum suggested zeroing out the mechacon to fully reset it but i havent tried that,
Click to expand...

Please don't completely erase the EEPROM, as you'll erase other things like the hardware IDs and some settings (related to the OP block).
I don't think I enabled the functions for initializing the whole EEPROM, as I didn't include the facility to re-enter the hardware IDs. Functions to initialize various individual parts of it, are probably there.

Either way, you might want to back up the EEPROM contents first.
 
Last edited:
Did it still not work for you? I thought you already found the problem.
Click to expand...

I thought I did too but when I returned to those consoles to finish the job it was doing the same thing again, this time updating the eeprom didn't do anything. It seems UK pal F-chassis consoles are incompatible, maybe.
 
sp193 said:
Failure by the MECHACON to detect the tray being retracted, will probably also cause these symptoms. It's why I gave you that analogy about blocking the tray from being retracted - it'll also result in the same behaviour (tray will eject again and you will get this error).



Please don't completely erase the EEPROM, as you'll erase other things like the hardware IDs and some settings (related to the OP block).
I don't think I enabled the functions for initializing the whole EEPROM, as I didn't include the facility to re-enter the hardware IDs. Functions to initialize various individual parts of it, are probably there.

Either way, you might want to back up the EEPROM contents first.
Click to expand...
eeprom backup was one of the first things i did
 
I just thought of something, I may be doing the Jitter wrong.

So a bunch of systems I'm working on right now won't go below 1B00 (256) The lowest I could get one was 1D00. But then I thought that there may be an issue with the spindle speed because the instructions say set it at 1x speed but DVDs travel at 2x at the outer edge and 3x on the inner part of the disc so I did Sled Out and play it at 2x the Jitter 256 went way down to 1300-1700 on all 3 systems that were having jitter issues.

Now I could be completely doing it wrong having it at 2x speed but it shows better results. On one console though I still get a too high jitter error when doing the Electrical Circuit Adjustment even though I got that console at 1500 jitter on 2x speed. Is this correct?
 
Are there any plans of updating the software to fix the few bugs? Specifically the 3000x R DVD-SL adjustment issue. Is there anything I can do to help? I know a little bit about PS2 disc drives and adjustments.
 
  • Like
Reactions: TnA
Hi,
I am a happy user of PMAP, but unfortunately I had no success with scph-50004 systems, and it does not support slim models.
The new mechapwn project that only supports dragon based Mechacon made me wondering, do you think that some day will be a laser calibration tool, that has support for dragon based mechacon? Is it even a reasonable thing to expect without a newer sony mechacon calibration tool leak?
 
AlmightyStokie said:
Are there any plans of updating the software to fix the few bugs? Specifically the 3000x R DVD-SL adjustment issue. Is there anything I can do to help? I know a little bit about PS2 disc drives and adjustments.
Click to expand...

PMAP was based on copied code. I don't think it's something that can be just fixed, if even the Sony tool does not help you.

Either way, I have no plans to make further updates. Sorry.

Freedy said:
Hi,
I am a happy user of PMAP, but unfortunately I had no success with scph-50004 systems, and it does not support slim models.
The new mechapwn project that only supports dragon based Mechacon made me wondering, do you think that some day will be a laser calibration tool, that has support for dragon based mechacon? Is it even a reasonable thing to expect without a newer sony mechacon calibration tool leak?
Click to expand...

PMAP supports up to the H & I-chassis SCPH-50000. That leaves at least 1 SCPH-50000 model that was not covered, since there's the J-chassis SCPH-50000.

We need to understand the protocol and the procedure; even if the commands remained the same, the EEPROM layout got changed with the slim PS2. From the code Sony had, it was like as Sony described: the commands required to correctly adjust each model sometimes differed slightly, for different reasons.

The MechaPwn project seems to have a different goal; even if they managed to dump the firmware, I don't think they have described how the service mode protocol works etc. But who knows what they will do. Anyway, the source code for PMAP is available.
 
sp193 said:
PMAP supports up to the H & I-chassis SCPH-50000. That leaves at least 1 SCPH-50000 model that was not covered since there's the J-chassis SCPH-50000.
Click to expand...
There is also a gap that only Mechacon versions up to 5.04 (5.05 for Dex) are supported. So >=v5.6 (5.06, 5.08, 5.10, 5.12) isn't supported by this app. However, it will be pretty easy to add support for missing v5 mechacons, as only patch sections (area 0x320) seems is affected. Anyway in its current state PMAP isn't working with Dragon models (I can confirm it with my SCPH-50004 with 5.2 mechacon), cause not all offsets were changed to the new EEPROM map.
Also, DESRs have a little different EEPROM map and values, which does not simplify things.
 
i have a v3 ps2 with rs232 max3232 but got santx errpr com port ? any ideas using windows xp i had to use cmd to even try to get the program to work please help
 
raylyd said:
i have a v3 ps2 with rs232 max3232 but got santx errpr com port ? any ideas using windows xp i had to use cmd to even try to get the program to work please help
Click to expand...
Please describe the error (copy the error/post a screenshot if necessary) and perhaps somebody could help you. Windows XP is very old, but so was the compiler (Visual Studio Ultimate 2010) I used to write this program.
 
mistamontiel said:
Is the SCPH-50004 PAL unit still a no-go? My purpose just to boot all region DVD titles
Click to expand...

zastanawia.gif

Could you be more specific?

All region PS2 DVD titles...
All region DVD-Video tiles...

Also this app supports consoles up to the I-chassis (SCPH-50000).

Are you sure that you want this app (MECHACON Adjustment Program) not the MechaPwn?
 
What else to inform you, why movies (!?)

Just to boot every region PS2 game with MechaPwn. Sadly I ordered the SCPH-50004 PAL but I return to seller when I read from the only MechaPwn github release that does not work on these units
 
I have a KHS-400C with a white lens protector. Would that be a T487 or a T609K lens, or do all 400C have the newer T609K lens assembly with no exceptions, regardless of color?
 
niino said:
I have a KHS-400C with a white lens protector. Would that be a T487 or a T609K lens, or do all 400C have the newer T609K lens assembly with no exceptions, regardless of color?
Click to expand...

This is something I've been wondering about too actually. Honestly I don't know the answer??

The only time I've seen white lens 400Cs are when I buy the modern reproductions from Aliexpress. Those specific lasers from my experience are really good but which type they are I have no idea. I've calibrated a PS2 with PMAP to T487 and T609K using those lasers and both settings seemed to work fine with it. My guess is they're T609K?

It's also worth noting that the lens type shows up as "unknown" in PMAP when I use white 400Cs but that just might be a software thing.
 
I have also seen a white lens KHS-400C inside a DESR-7700 PSX that was still sealed, so they definitely have been produced like that by sony. Also, they are very late units, because at that time (mid 2005), sony already produced the slim PS2 and the DESR-*700 PSX was probably the last device to use the KHS-400C. Might try to read the EEPROM of that PSX to see what it's been set to, but neither does PMAP officially support it nor are the UART test point locations known (I could probably trace them out, though). Or are there ps2-side software tools to read information about the laser configuration data from Mechacon?
 
I figured out the UART test points on my PSX. The lens type is shown as unknown by PMAP, however, I have an EEPROM dump which might get analyzed further.

niino said:
Figured out the test points of XPD-005 (PSX DESR-x500 and DESR-x700 mainboard). They are probably identical on XPD-001 (PSX DESR-x00 and DESR-x100), since the section under the mechacon is pretty much identical, with only a few differences on how the ground plane is laid out.

The usefulness of this is limited at the moment, as it mostly only allows showing some console information and dumping/restoring the EEPROM. Adjustment is not possible, since PMAP does not support any PSX chassis at the moment. It might however come in handy with some progress on reverse engineering the Dragon-Mechacon firmware, which has been dumped (last year, I think?).
View attachment 37797
Click to expand...
 
I received a japanase scph-50000 with GH-026 motherboard, I am going to try pmap again, so far I had no success with the 50000 series, 2 out of 2 machines could not make it work, I am curious if this one will work or or not.

EDIT:
Unfortunately no success, the result is the same as with the other 2 ps2 50000 series I tried a few years back.
 
Last edited:
with the big help of @AlmightyStokie and @niino new PMAP release is ready:
v1.12
- Corrected argument parsing for F-chassis and A-chassis
- Corrected EEPROM management for G-chassis
- Corrected some non-escaped menus
- Out-of-range CD/DVD DiscDetect Ratio will be just a warning, not an error
- Enabled verbose logging of all issued serial commands+arguments and mechacon responses into the pmap.log file
- Added argument logging into all cmd messages
- Corrected CD FCS SEARCH CHECK calculation. It was in the range 0..10 cause the value for storing was unsigned, changed to -10..10
- Refactored `cfd` handle logic from uint to char. On Dragons (H-Chassis+) `cfd` returns the Mechacon Renewal date in a different format
- Now all v5 mechacon chips are detected correctly.
https://github.com/ps2homebrew/PMAP/releases/tag/v1.12
 
You must log in or register to reply here.

Similar threads

Back
Top