i have exactly the same problem i read the 2 eproms and need to combine them and just get an print of the ladder in a pdf file for fault finding can anyone help with that
Yes contact [email protected]
I would be happy if someone could combine our OE=>.ex and vice versa. Or any info on scripts/programs to do that by myself (I'm a lot computer savvy, maybe not a programmer with tons of github stuff, but still can sorta things out).
On the other side - has had anyone tried replacing 27C256 EPROMS with 29xxxx EEPROMS ? Even some are not pin-to-pin compatible it should be very easy to make socket-to-socket adaptor, so much easier to play with ladders.
I'm trying to push old Leadwell GMC350 to the limits - found it ditched in some company junkyard and it's slowly going back to life. Need to add G134.x somewhere to the ladder on unused I/O pins to sort out remote program upload - so far there's python webserver sitting on raspberrypi + ft232/max232 combination - but I need to be close to the machine to hit 'upload' just after NC INPUT has been pressed. Also - drip
Looking forward to any tip
Thanks,
Chris
let me reply to myself.
Managed to read the EPROMS and join them into .#EX - following next days I'll compare the output with actual PMC ladder on machine to be sure the script works just fine. And yes, with a bit of luck - I'll be able to convert any PMC-L on 0m-a/b/c
Next step: replace EPROM with EEPROMS - with a bit of hacking since gate A14 & VPP iirc are swapped. So far so good
hello!...do you have the binary files of the master card A16B-1010-0210/16D of the Centrum 3000 punch press...they are OE1, OE2, OC1, and OC2...the executive software version is 0130-11?
Hello everyone,
I have the opposite problem: I have the factory ladder files, and I need a pair of equivalent data files so I can burn them into a pair of 27256 EPROMs as OP1 and OP2.
I would be glad to pay for this service.
I've been trying to do it myself:
- resurrected 486/33 computer
- installed modern floppy emulator
- tried to get FAPT LADDER II and LADDER III working on it
- so far it's beating me.
Got tired and decided to try throwing myself on the mercy of you folks that are already properly equipped. Sorry to bother you. :-(
I'll be glad to pay for the service. I just want a pair of standard-format data files that an EPROM programmer can accept. Any of the popular formats will be fine. Intel and Motorola are my two favourites.
Here follows the text generated from me looking at the set of data files provided by the manufacturer, SuperMAX / YCM out of Taiwan.
--------------
8 files within directory L1R03:
L1R03.#TA - 262 bytes -
L1R03.#C1 - 7902 bytes -
L1R03.#C2 - 4 bytes -
L1R03.#CN - 23 bytes -
L1R03.#EX - 75360 bytes -
L1R03.#LA - 15700 bytes -
L1R03.#PA - 120 bytes -
L1R03.#SY - 10140 bytes -
======================================
Analysis:
-----------
- #TA file: 262 bytes of ASCII text as follows:
"YCM
VMC,65A/85A,24T
PMC-L,0M
ROCK
M52,53, 54, 55
83/31/95
L1 03"
... that describes what this firmware is for, and what it does.
-----------
- #C1 file: 8k of un-punctuated ASCII text. I could believe that it is the Named Aliases used within the ladder to make it more readable.
-----------
- #C2 file: four NUL bytes
-----------
- #CN file: 23 bytes of mostly NULs plus ASCII "FOB N"
-----------
- #EX file: 75k bytes of pure binary data - presumably this is what gets put in a pair of EPROMs
-----------
- #LA file: 16k bytes of slimly populated binary data
-----------
- #PA file: 120 bytes of mostly NULs and spaces
-----------
- #SY file: 10k bytes of ASCII with lots of nulls -- looks like more Named Aliases for the ladder.
======================================
each 27256 EPROM is 32k 8-bit bytes = 32768 bytes
address space is 0000 -7FFF
if 16 bytes/line then 2048 lines.
The two EPROMs are labelled OE1 and OE2.
===================
Assistance would be greatly appreciated.
How to contact me:
- reply here
- e-mail wood{at}dingwallguitars{dot}com
- phone or text to Canada 306-227-5578
Thanks again and so long.
Pm me [email protected]