At the time I dumped the eeprom I had to de-solder the chips from the PCBs, as the CH341 was not recognizing the chip with the clip. Probably because the board pulls too much current on VCC, even with the ribbon cable disconnected, I think it's the other chip that shares its VCC that sinks too much current (or the opto diode more likely).
I've not tried with the new programmer I got (Xgecu T48 et RT809h) since I got them after fixing the balancer...
User Profile
Collapse
-
Hi, thanks.
Unfortunately in the meantime the core proved to be dead so as most of the memories. It ended as a donor, but still thank you.Leave a comment:
-
Here are the eeprom files.
You'll find the following files :
the main one is the "opto patched - 3" which is the most recent one.
It's a file I created after resetting the machine and copying the calibration data from the original.
Note that it's for a 9300 not a 6300, there will be some differences for sure. When you do a factory reset you need to specify which model you have (and I lost a lot of time because I initially thought it was a 6300 and after reset it was throwing some weir errors because I selected the wrong model)....Leave a comment:
-
- Now that I read entirely your message I would say : do not waste any time on this, it will most likely will not help.
I did this because I wanted to ensure the CPU board was "alive" and at least doing something, and wanted to see if any helpfull information could be obtained via a basic terminal.
Turns out in your case you know the CPU board is already starting and doing something, and it will not povide any helpfull information with a basic terminal. I guess that if you had the manufacturer software that can speak with the CPU you might be able to obtain more information
Leave a comment:
- Now that I read entirely your message I would say : do not waste any time on this, it will most likely will not help.
-
Hello Michael,
I'll make a more comprehensive answer later, I've not read everything you wrote yet... And I need to refresh my memory, it has been a while and I already forgot most of the things...
By the way I said my model was a "6300" but is in fact a "9300". But I think it's mostly the same utils with more or less options. At least the base is identical.
Can you describe the process / connections you used to get the printout on your computer from X9 connector? I assume you connected the Rx and GND. I’d like to do this myself but...Leave a comment:
-
Asrock B760M PG RIPTIDE (70-MXBL60-A01)
Looking for Schematic and/or boardview for an Asrock B760M PG RIPTIDE motherboard (70-MXBL60-A01) -
EPILOG Laser - XS002 controller board
Hello gus,
Just have two XS002 controller board for Epilog laser engraver for repair, looking for any schematic or doc on those board. So far I could only find the "Service training manual", but it's for the whole unit, not specific to the controller board and there is very little info on the board itself.
For instance I don't even have the connectors pinout
thx. -
Zotac Gaming Geforce RTX 3060 AMP WHITE ED 12GB, any boardview (or schematic) ?
I'm looking for boardview (or schematic, or even some hi-res board photos of the board) for a Zotac Gaming Geforce RTX 3060 AMP WHITE ED 12GB (P/N 9288-BN617-210Z8).
Trying to fix one, but someone really messed up the board badly already and I don't know what is missing....
... -
I think I made something...
So first, my theory about serial number was wrong, not much surprise here.
But, I did compare the original eeprom content to the eeprom content I get after reseting the machine.
I ignored the first part of the eeprom, there are indeed few different bytes, but I assume that the "header" is where all the options are stored.
then lower (arround @ 0630) I found a section of 144 bytes that is empty on the "reseted state" eeprom vs the orginal eeprom.
I suppose that's enough data to store some calibration...Leave a comment:
-
If I could keep the original eeprom content I think the factory calibration could have survived.
Anyway I tried, copied the original content to the eeprom and the machine is back to the error : 3S-3L beeps, which means communication issue with : KBC/LCD/Motor/BRAKE.
So... either it's looking for the optional brake that is indeed not present (was removed by the previous owner(s))?
or.. I have a new theory : it's looking for the KBD/LCD board which also has his own eeprom, and this eeprom contains only 5 or 6 bytes of data, and (theory intensify) this is the serial number...Leave a comment:
-
I mean... a 6 is an upside down 9.. almost the same...
ok... I did not wait... because I can't see a valid reason why the CPU would be defective on only one of it's A/D input (well... there are reasons, and it could...) but... I need a justification here, because yeah... a few days would not matter but... reasons....
So.... it works. Setting the proper model helps (a lot !) ! funny that with the same board they do not use the same A/D input for V.line...
And finally all that work for nothing... well.. I least I have a pretty good idea of how the electronics...Leave a comment:
-
Ok... I think you can call me stupid. Well, we still need to confirm my new theory, but you still can...
Remember when i said after some poking around the eeprom was corrupted and it started showing an error and asked to reconfigure the model number ?
yes... so.... I selected model 9300 (first option in the list) instead of 6300.
Not sure it can explain the issue, but for sure it would probably not work properly.
Now... should I wait few more days for the new cpu? If it is the cpu at least I will have a(hopefully) fully functional one and won't need...Leave a comment:
-
yes, Vline is on pin 18, but pin 14 (that I tought was the ripped pad) is "Line Freq", which I supposed the absence could be a reason why the firmware would not check VLine and report it as 0V.
My assumption is that the firmware checks line frequency before line voltage, but it was just a guess from my side.
Anyway, not the case as it's definitely pad 13 that is ripped, so no matter how the firmware behaves, that does not explain anything.
I might be trying too hard to find an explanation to the CPU not being able to read VLine while it's definitely present...Leave a comment:
No activity results to display
Show More
Leave a comment: