Possible upgrade  - Agilent 34410A to 34411A - Page 1
Forum section: electronics / testgear

author: plesa
author_rank: Frequent Contributor
timestamp: December 03, 2015, 10:50:04 pm
content: To one member here I make a promise to check the internals of 34410A and 34411A.After removing covers there was small surprise - boards seems to be identical!!On both is marking 34410A and also sticker on 64 MBit Flash inside 34411A meter has marking 34410A:)In brief the main difference is reading speed - for more checkhttp://literature.cdn.keysight.com/litweb/pdf/5989-4039EN.pdf?id=744074This automatically triggered next step - check firmware, but unfortunately meters seems to be based on VxWorks.Schematic is available, no information about 34411A in it, maybe JM1102 and JM1103 position needs to be found.http://www.keysight.com/owc_discussions/thread.jspa?threadID=36971&tstart=-1In attachment is high resolution picture of main board from internet.Stay tunned.

author: HighVoltage
author_rank: Super Contributor
timestamp: December 05, 2015, 08:04:17 pm
content: Thanks for sharing this.I just bought a broken 34410A and this schematic will help a lot.Do you also have a parts list of all components, as we know it from the 34401A?

author: nukie
author_rank: Frequent Contributor
timestamp: December 06, 2015, 10:48:46 am
content: Very nice looking forward to your further investigation

author: plesa
author_rank: Frequent Contributor
timestamp: December 13, 2015, 04:06:40 pm
content: Unfortunaltelly units which I can afford to brick do not have J1003 and U1101 (75LV4737) populated. So I decided to start with L4411A which I can brick.Debug terminal output (9600 baud rate if someone is going to follow)Code:Attaching interface lo0...doneAdding 26466 symbols for standalone.AMDFLASH-> rhapsodyInit: programInguard0x13f87b8 (tOxf): FPGA readyrhapsodyInit: initInstrumentEngineKOM_gpib_configKOM_int_cfgn0x1206bb0 (tUsb): Config EBIU USB Asynchronous Timings0x1206bb0 (tUsb): Previous USB EBIU_DCR_BR: 101883980x1206bb0 (tUsb): NEW USB EBIU_DCR_BR: 101883680x1206bb0 (tUsb): Config EBIU USB Synchronous Timings0x1206bb0 (tUsb): Previous USB EBIU_DCR_BR: 101883680x1206bb0 (tUsb): NEW USB EBIU_DCR_BR: 101881620x11d4cb8 (tPollVbus): USB connectPullUp = 0IP address = 192.168.0.5+------------------------------------------------------------| GPIB is enabled| USB is enabled| Sockets Server is running on port 5025| Telnet Server is running on port 5024| VXI-11 Server is running| WEB Sockets Server is running on port 5042| AllegroTaskInit successful| Web Server is running+-------------------------------------------------------------> helphelp Print this listioHelp Print I/O utilities help infodbgHelp Print debugger help infonfsHelp Print nfs help infonetHelp Print network help infospyHelp Print task histogrammer help infotimexHelp Print execution timer help infoh  Print (or set) shell historyi  Summary of tasks' TCBsti task Complete info on TCB for tasksp adr,args... Spawn a task, pri=100, opt=0x19, stk=20000taskSpawn name,pri,opt,stk,adr,args... Spawn a tasktd task Delete a taskts task Suspend a tasktr task Resume a taskd [adr[,nunits[,width]]] Display memorym adr[,width] Modify memorymRegs [reg[,task]] Modify a task's registers interactivelypc  Return task's program counterType <CR> to continue, Q<CR> to stop:iam "user"[,"passwd"] Set user name and passwdwhoami Print user namedevs List devicesld [syms[,noAbort][,"name"]] Load stdin, or file, into memory(syms = add symbols to table:-1 = none, 0 = globals, 1 = all)lkup ["substr"] List symbols in system symbol tablelkAddr address List symbol table entries near addresscheckStack  List task stack sizes and usageprintErrno value Print the name of a status valueperiod secs,adr,args... Spawn task to call function periodicallyrepeat n,adr,args... Spawn task to call function n times (0=forever)version Print VxWorks version info, and boot lineNOTE: Arguments specifying 'task' can be either task ID or name.value = 1 = 0x1-> versionVxWorks (for Agilent KOM PPC405, SA27E rev1) version 5.5.1.Kernel: WIND version 2.6.Made on May 22 2015, 14:33:34.Boot line:emac(0,0)host:vxWorks h=10.1.1.2 e=169.254.9.80 u=demo pw=demo tn=value = 78 = 0x4e = 'N'->

author: plesa
author_rank: Frequent Contributor
timestamp: December 13, 2015, 06:01:30 pm
content: Partial success.L4411A is now 34411A for this change only header of file needs to be changed.In file agt34411_instrument_rev241.xschange row "%model=34411A" to "%model=L4411A"Meter boot up correctly and in LXI it is 34411A nowIt is also possible to downgrade L4411A to 34410A without any issue.Only the front panel will be off.After this upgrade L4411A is working in BenchVueSimilar attempt with 34410A:Firmware upload by Firmware Update utility finished correctly. But after restart there is message on display : "Please load 34410A firmware"Further investigation needed, so stay tuned.

author: nukie
author_rank: Frequent Contributor
timestamp: December 15, 2015, 05:16:13 am
content: I have 4x 34410 candidates

author: HighVoltage
author_rank: Super Contributor
timestamp: December 15, 2015, 09:52:11 am
content: You are making progress, great.Are you really sure the hardware is the same between the 34410A and the 34411A instruments?I would expect a at least a small difference.But then, may be this was the beginning at Agilent to introduce software downgrading.

author: plesa
author_rank: Frequent Contributor
timestamp: December 15, 2015, 08:04:57 pm
content: Quote from: HighVoltage on December 15, 2015, 09:52:11 amSure, the partnumber and stickers are the same. According to test above there is some check of meter ID. This should be in one of another firmware or in bootloader.Any other thoughts? I needs to install IDA /pro dissassembler to chce the VxWorks firmware:)

author: asp
author_rank: Regular Contributor
timestamp: February 01, 2016, 03:09:35 pm
content: Quote from: plesa on December 03, 2015, 10:50:04 pmDon't bother with JM1102 and JM1103 as they are for calibration purposes. I have the unpacked firmware somewhere if you need it. The only notable difference seems between 01 and 1x is the check for frmware... for sure there are others

author: plesa
author_rank: Frequent Contributor
timestamp: February 01, 2016, 09:13:11 pm
content: Quote from: asp on February 01, 2016, 03:09:35 pmCurrently I am looking for 34410A unit with populated serial interface. 34411A/L4411A can be downgraded. So it seems to be in the bootloader or boot parameters.

author: HighVoltage
author_rank: Super Contributor
timestamp: August 28, 2016, 08:31:15 am
content: Did you make any progress?I just bought a broken 34411A that is on its way.Once I have it, I will make a good comparison to one of my 34410A

author: plesa
author_rank: Frequent Contributor
timestamp: August 28, 2016, 02:45:26 pm
content: Unfortunately no progress at all. What's wrong with 34411A?

author: bitseeker
author_rank: Super Contributor
timestamp: August 28, 2016, 11:32:00 pm
content: @HighVoltage: That comparison will be very interesting indeed.(Hmm, were your other DMMs getting lonely -- pining for a new team member?)

author: HighVoltage
author_rank: Super Contributor
timestamp: August 29, 2016, 07:18:59 am
content: Quote from: bitseeker on August 28, 2016, 11:32:00 pmI never owned a 34411A and got it for Euro 100 incl. shippingSymptoms: Does not turn ONI still don't have it, may be an easy repair, may be beyond repair, I don't know.The 34411A rarely become available at a reasonable price.May be we really can find out the differences between the 34410A and the 34411A

author: bitseeker
author_rank: Super Contributor
timestamp: August 29, 2016, 07:25:23 pm
content: Woahthat was a score! Well, I certainly hope it's just the power supply.My 34410A and I eagerly await your next update.

author: plesa
author_rank: Frequent Contributor
timestamp: August 30, 2016, 03:54:29 am
content: Quote from: HighVoltage on August 29, 2016, 07:18:59 amThe board / hardware is identical. the only difference in in software and probably calibration. If I have unit for 100 EUR I will invest more into experiments with programmer. You can easily downgrade 34411A to 34410A by changing model number in firmware file header (%model=34410A).

author: bitseeker
author_rank: Super Contributor
timestamp: September 11, 2016, 09:53:15 pm
content: Quote from: HighVoltage on August 29, 2016, 07:18:59 amCongrats on the "no fix" fix, as you put it. Way to score. We anxiously await your revelations as to the potential of upgrading a 34410A to a 34411A. For curiosity, of course. Most of the time, I'm running my 34410A with integration at 10 or 100 PLC.

author: zrq
author_rank: Frequent Contributor
timestamp: October 09, 2022, 12:58:06 am
content: Sorry to revive this old thread. I'm seeking for a 6 1/2 digits DMM for the home lab and got interested in second hand 34410As, which seems available on ebay for a reasonable price (other suggestions welcome). For obvious reason, the meter will be of better value if it's hackable. I downloaded the firmware (agt34411_instrument_rev243.zip) from Keysight website and start digging into it.Basically, the xs file is a Motorola S file for the hex content, with tools like 010Editor, we can easily convert to the actual bytes in rom. binwalk indicates there is a Zlib compressed section, use -e to extract, and we get a vxworks image. With -a it turns out in the Agilent ASIC, the firmware runs on a big endian 32bits PowerPC core. Googling shows there is a toolhttps://github.com/PAGalaxyLab/vxhuntercan help me load the memory image in GHIDRA, and I noticed the image comes with a symbol table. Searching the "Please load" quickly led to the _checkModelNumber__5IEIfcF routineCode:*************************************************************** FUNCTION ***************************************************************undefined _checkModelNumber__5IEIfcFv()undefined r3:1 <RETURN>undefined4 Stack:4 local_res4 XREF: 004d4adc(W),004d4b40(R)undefined4 Stack[-0x10]:4 local_10 XREF: 004d4acc(W)_checkModelNumber__5IEIfcFv XREF: initInstrumentEngine__5IEIfcFv:000a4d690(*)004d4acc 94 21 ff f0 stwu r1,local_10(r1)004d4ad0 7c 08 02 a6 mfspr r0,LR004d4ad4 3d 80 90 00 lis r12,-0x7000004d4ad8 a0 8c 00 0a lhz r4,offset DAT_9000000a(r12) <- UNKNOWN ADDRESS004d4adc 90 01 00 14 stw r0,local_res4(r1)004d4ae0 2c 04 23 5a cmpwi r4,0x235a004d4ae4 40 82 00 3c bne LAB_004d4b20004d4ae8 3c 60 00 96 lis r3,0x96004d4aec 38 63 2c fc addi r3=>s_34410_FIRMWARE_00962cfc,r3,0x2cfc = "34410 FIRMWARE"004d4af0 3c 80 00 96 lis r4,0x96004d4af4 38 84 2d 0c addi r4=>s_PLEASE_LOAD_00962d0c,r4,0x2d0c = "PLEASE LOAD"004d4af8 4b bc f7 29 bl updateVfdNow__FPCcT1 undefined updateVfdNow__FPCcT1()004d4afc 48 0c 96 89 bl theMgr__19GandalfStateManagerSFv undefined theMgr__19GandalfState004d4b00 38 80 00 00 li r4,0x0004d4b04 48 0c 90 e5 bl enablePorRecall__19GandalfStateManagerFb undefined enablePorRecall__19Gan004d4b08 3c 60 00 1e lis r3,0x1e004d4b0c 60 63 84 80 ori r3,r3,0x8480004d4b10 4b d6 e2 c9 bl spin__9SpinTimerSFi undefined spin__9SpinTimerSFi()004d4b14 38 60 40 00 li r3,0x4000004d4b18 4b ca 96 15 bl reboot int reboot(int __howto)004d4b1c 48 00 00 24 b LAB_004d4b40LAB_004d4b20 XREF: 004d4ae4(j)004d4b20 28 04 b6 43 cmplwi r4,0xb643004d4b24 41 82 00 1c beq LAB_004d4b40Although still not sure what the code is checking, as I hadn't got to figure out the memory mapping. I guess there is a 0x235a value in the calibration rom which is checked against, and it's possible the value can be changed in the vxWorks shell by the debug commands. But apparently, as there seems to be no secure booting, a trivial solution is to nop out the only code reference to this function in initInstrumentEngine__5IEIfcFv.Code:*************************************************************** FUNCTION ***************************************************************undefined initInstrumentEngine__5IEIfcFv()undefined r3:1 <RETURN>undefined4 Stack:4 local_res4 XREF: 004d4f30(W),004d4ff4(R)undefined4 Stack[-0x4]:4 local_4 XREF: 004d4f2c(W),004d5004(R)undefined4 Stack[-0x8]:4 local_8 XREF: 004d4f28(W),004d5000(R)undefined4 Stack[-0x10]:4 local_10 XREF: 004d4f20(W)initInstrumentEngine__5IEIfcFv XREF: vxmain__FiPPc:0005c034(c),00a661f0(*)004d4f20 94 21 ff f0 stwu r1,local_10(r1)004d4f24 7c 08 02 a6 mfspr r0,LR004d4f28 93 c1 00 08 stw r30,local_8(r1)004d4f2c 93 e1 00 0c stw r31,local_4(r1)004d4f30 90 01 00 14 stw r0,local_res4(r1)004d4f34 4b be 34 8d bl instance__10SoftRebootSFv undefined instance__10SoftReboot004d4f38 4b b8 ca 6d bl subscribeEventBootHandlers undefined subscribeEventBootHand004d4f3c 4b ff fb 91 bl _checkModelNumber__5IEIfcFv undefined _checkModelNumber__5IE004d4f40 4b ff fb 0d bl _checkFlashType__5IEIfcFv undefined _checkFlashType__5IEIf <------------HERE004d4f44 3f c0 00 c8 lis r30,0xc8004d4f48 3b de 7c c0 addi r30,r30,0x7cc0004d4f4c 48 08 9e 15 bl newScanController__Fv undefined newScanController__Fv()I don't (yet) have the 34410A to verify this is feasible, but it looks promising.BTW: who is Gandalf?

author: TheSteve
author_rank: Unknown
timestamp: October 09, 2022, 05:29:16 am
content: Going 34410 to 34411 is pretty easy. In the past you just needed swap the names of the bin files so the upgrade package would install the 34411 firmware into your 34410. When it boots it will be unhappy so the other thing required is to edit the model # in the eeprom that is in the back left corner of the unit(8 pin SOIC). You can get an SOIC clip onto it without even removing the PCB. Just edit the instances of 34410 to 34411.

author: coromonadalix
author_rank: Super Contributor
timestamp: November 06, 2022, 02:59:33 pm
content: im playing with an l4411Apoking into the serial debug port ...in my case i have only one user with loginUserShow() commandannnnnd itsgandalfvalue = 0 = 0x0Is it possible to find the user password ??, i've read they must be encrypted with vxencrypt.exe and be typed encryptedis there a way to get this file ?Tried to create other user with some i've found out on the webUpon reset the added user(s) are cleared up, onlygandalfremain loll

author: coromonadalix
author_rank: Super Contributor
timestamp: November 18, 2022, 10:32:28 pm
content: Edit sold the L4411A and got an 34410a with the populated debug port (ic+ plug) old fw 2.21 .... gonna do a normal upgrade and see the plug pinouts with the known schematic

author: coromonadalix
author_rank: Super Contributor
timestamp: November 19, 2022, 12:16:32 am
content: Was hard to find a way to solder a thin wire on the jtag connector to hold the cpu in reset while reading the eeprom in SPIChanged the 34410 occurrence to 34411 and it still complained about the model versionattached is the original non modded AT24C16 eepromif someone has ideas lollThe wp pin is tied to ground maybe its a problem, my programmer seem able to bypass this ?? i've tried some read an writes ... and seems to work ?Or someone has an defective 34411a board ?

author: TheSteve
author_rank: Unknown
timestamp: November 19, 2022, 01:20:32 am
content: You have to mod the eeprom and program the 34411A firmware.

author: coromonadalix
author_rank: Super Contributor
timestamp: November 19, 2022, 05:41:38 pm
content: While i have pmed TheSteveStill no luck with info's given here or TheSteve info'sThe Firmware updater seems to check something who's not related to the eeprom model found in it ??Tried many combinations eeprom vs the fw files, no avail, the meter will request to have proper 34410 fw .....TheSteve did apparently manage to convert 2 meters, no success for meOn the Keysight Connection Manager, even with the 34411 model put in the eeprom, it will still identify as a 34410AThe populated debug port on my meter doesn't seems to react at all, checked many times against the schematicI was maybe or surely too fast to upgrade my version 2.21

author: coromonadalix
author_rank: Super Contributor
timestamp: November 20, 2022, 04:08:06 pm
content: thecpu resetis located on theses pads (pictures attached) i was not connected properly, i was on the jtag reset pin ...One side is DCOM digital ground / metal casing of the meterI connected the pin 14 of the lm339 u902 to the ground via an 100 ohms resistorStill no success, the info is elsewhere ... not in the eeprom it seems

author: coromonadalix
author_rank: Super Contributor
timestamp: December 25, 2022, 02:17:34 am
content: An eevblog member tried a few hacks on the 34411a firmwarethe XS file with an + at the end is patched and the FW updater tooNever worked for me and did not brick the meterTry at you own risk and not liable for any problemsThe XS file was compressed again, but the compression ratio is not the same, they are less bigger, my meter failed in the last FW portion, and if one worked fine it would ask for the 34410a fw on the screenIf you flashback the original keysight software it will function correctly againhttps://www.sendspace.com/file/f5qj0dadded the 34410a eeprom dump

author: zrq
author_rank: Frequent Contributor
timestamp: May 21, 2023, 01:19:38 am
content: Quote from: TheSteve on October 09, 2022, 05:29:16 amHave you tried this or saw evidence that this worked? I had another look into the 34410A flash dump on another post (https://www.eevblog.com/forum/repair/agilent-34410a-u1001-flash-dump/msg3786704/#msg3786704), and it appears to me that the magic number being checked is just in the flash rather than the eeprom. The value checked against in _checkModelNumber() is hardcoded in the boot rom.Code:006022cc 3c 20 01 c0 lis r1,0x1c0006022d0 38 21 00 00 addi r1,r1,0x0006022d4 28 08 40 00 cmplwi r8,0x4000006022d8 40 82 00 10 bne LAB_006022e8006022dc 39 00 00 00 li r8,0x0006022e0 38 60 00 02 li r3,0x2006022e4 48 00 00 0c b LAB_006022f0LAB_006022e8 XREF: 006022d8(j)006022e8 38 60 00 01 li r3,0x1006022ec 48 00 08 95 bl FUN_00602b80 undefined FUN_00602b80()LAB_006022f0 XREF: 006022e4(j)006022f0 3c 80 90 00 lis r4,-0x7000006022f4 38 84 00 08 addi r4,r4,0x8006022f8 98 64 00 00 stb r3,0x0(r4)=>DAT_90000008006022fc 38 60 01 00 li r3,0x10000602300 3c 80 00 1f lis r4,0x1f00602304 38 84 84 80 subi r4=>DAT_001e8480,r4,0x7b80 = E5h00602308 48 00 09 15 bl FUN_00602c1c undefined FUN_00602c1c()0060230c 38 60 23 5a li r3,0x235a <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<BINGO00602310 3c 80 90 00 lis r4,-0x700000602314 38 84 00 0a addi r4,r4,0xa00602318 b0 64 00 00 sth r3,0x0(r4)=>DAT_9000000a0060231c 3c 80 ff e0 lis r4,-0x2000602320 38 84 2d e4 addi r4,r4,0x2de4

author: coromonadalix
author_rank: Super Contributor
timestamp: May 21, 2023, 10:49:51 am
content: In my case nothing worked, some patched xs files, patched firmware updaters ... a mix of them, nada nietthe only thing is : the meter will spit a FW warning saying it need the 34410a FWAnd was not able to receive any data from the internal serial console, all parts and connector is there ?? maybe i have not wired it correctly ?

author: HighVoltage
author_rank: Super Contributor
timestamp: May 21, 2023, 12:46:32 pm
content: This hack also did not work for me.Once I got a real 34411A, I did not try anymore.

author: coromonadalix
author_rank: Super Contributor
timestamp: May 21, 2023, 03:38:08 pm
content: but it seems "easy" since the only notable difference is the sampling rate from the L4411a, 34410a to the 34411aor not loll

author: zrq
author_rank: Frequent Contributor
timestamp: May 21, 2023, 03:40:31 pm
content: Now I believe the only reason that the 34411A firmware will refuse to run on 34410A is: the 34410A bootloader at physical address 0x0060230c on the flash (loaded address 0xFFE0230E) is writing a magical word 0x235a to RAM 0x9000000A. This address is then checked by the main firmware (store compressed on the flash too, in two copies) and expecting 0xB643. If it reads 0x235A, the meter will hang with the Load 34410A Firmware message.One can see the evil instruction (38 60 23 5a li r3,0x235a) in the bootloader by querying DIAG:PEEK? 4292879116 and DIAG:PEEK? 4292879118,(4292879118=0xFFE0230E). If someone is willing to remove the flash from the main board and change the 23 5A at offset 0x0060230E to B6 43 with a programmer, then the meter should accept 34411A firmware as well. Someone brave enough can also try DIAG:POKE 0xB643 into 0xFFE0230E. I'm not sure if DIAG:POKE can write to flash, as the implementation is just a memory assignment, so it may not do anything. Alternatively, instead of crafting a firmware update package with the checkModelNumber patched, one can try to craft a file that overwrites the bootloader and modify the 0x235A to 0xB643. I'm not sure how the firmware update works (yet?) but it doesn't sound easy.I have only a L4411A so have little motivation (and capability) of looking into this deeper, but if anyone interested want a GHIDRA project to play with, I may send it.Bonus:Code:L4411A> DIAG:PEEK:FIRM? 24,0,0Elapsed Time Hours: 266.822This seems to return the total powered on hours of the meter.OT: I was looking all around in the code to find a backdoor to allow backup of the cal rom, but couldn't. Most accesses are done by a call to iiceeprom and I couldn't find if the memory is mapped somewhere so I can fish out data by DIAG:PEEK?. If someone does find one, please let me know.

author: coromonadalix
author_rank: Super Contributor
timestamp: May 21, 2023, 05:13:32 pm
content: i'll try any commands latergoing outNOT lollbut removing the flash for now is a no can't doi dont have a socket for it and for the programmer i have .... they sell it pretty darn high loll but i would ...i'm trying to understand you diag poke commands loll in RSVisaTester 5.12....DIAG:PEEK? 4292879116gave me this ? +14432DIAG:PEEK? 4292879118gave me +9050DIAG:POKE 0xB643 gave a beeep ? and received an VI Error TMOand your bonusDIAG:PEEK:FIRM? 24,0,0gaveElapsed Time Hours: 9.77694

author: zrq
author_rank: Frequent Contributor
timestamp: May 21, 2023, 05:18:25 pm
content: Ahhh, I'd not recommend trying without a proper backup. Even you have a cal rom backup, recovering from corrupt firmware may need soldering and the flash programmer.I think DIAG:POKE will only accept decimal input. And I'd suggest first trying out with a few safer addresses (checked by DIAG:PEEK? to be non-essential data), figure out the syntax (likely DIAG:POKE <decimal address>, <decimal number of thetwobytes, big endian>) and then try the real thing.Also:+14432 = 38 60+9050 = 23 5AThese are the expected values.

author: coromonadalix
author_rank: Super Contributor
timestamp: May 21, 2023, 05:24:13 pm
content: DIAG:PEEK? doesn't work VI Error IO ?sorry noob in this world of commands lolland the dangerous command would be loll ........ DIAG:POKE uh oh endians ??ok ill try to find some progammer loll and or a socket .......

author: TheSteve
author_rank: Unknown
timestamp: May 21, 2023, 05:32:09 pm
content: 100% for certain I did change two 34410's to 34411's. This was a number of years ago and I don't have them anymore to compare/verify or repeat the process.

author: zrq
author_rank: Frequent Contributor
timestamp: May 21, 2023, 05:36:26 pm
content: Hmm, then that's weird. Maybe I missed something?

author: coromonadalix
author_rank: Super Contributor
timestamp: May 21, 2023, 05:39:12 pm
content: Maybe on the older FWi was to speedy to upgrade my meter damn it was very old

author: TheSteve
author_rank: Unknown
timestamp: May 21, 2023, 05:52:59 pm
content: I know the only thing I did was trick the firmware update util to program the 34411 firmware into the 34410, I then made changes to the eeprom.

author: coromonadalix
author_rank: Super Contributor
timestamp: May 22, 2023, 10:31:59 am
content: oh found out some solderless clip test for tsop 56 ... 68$ cadi hope my programmer will take it, if not a new one will come too

author: MegaVolt
author_rank: Frequent Contributor
timestamp: May 22, 2023, 11:58:44 am
content: Quote from: coromonadalix on May 22, 2023, 10:31:59 amWhere is it sold?

author: coromonadalix
author_rank: Super Contributor
timestamp: May 22, 2023, 01:43:18 pm
content: aliexpress searched for this and they appearedUni-clip 56pin Universal CLIP ...........Examplehttps://vi.aliexpress.com/item/32814634915.html?