Products > Test Equipment
Flood of new Agilent 82357B GPIB-USB adaptors on eBay the real deal?
<< < (42/83) > >>
Scottjd:
Just a quick update, I had requested the certificate from Keysight and they did provide it.
Their a a few notable differences, so if anyone receives an adapter new and sealed in a box the certificate can tell you if it's fake or not. It took them a few weeks since they had to pull it from the archives.

The certificate number is a real number on the keysight form, the fake one just had 82357B.
The serial number was on the real certificate, the fake one didn't have any serial number listed.
The big one, it looks like it was copied with a cheap copy machine.
And as I mentioned, of you register the serial number with keysight it's probably already registered in the past and the warranty is expired.

Their are other differences, but I won't mention them all since they will try to fix it.
But those are the easiest to figure out if it may be a fake one you received. It's funny, they out the time in listing the serial number on the box that matches the one in the adapter, but didn't bother to list it on the form.

Oh, and your software CD probably has a scratch on it, and it's in a very flimsy CD case. I guess they don't want to bother burning real CDs with the software, so they just print labels and out them on bad CDs. So who knows what data was really on the CD. I should have checked, but to late now.
macboy:

--- Quote from: Macbeth on December 07, 2015, 11:33:17 am ---@nightpanda, fascinating story  :-+ it's a shame your little business has ended. I would also call your device compatible, rather than counterfeit!

--- End quote ---
I agree, it is a compatible, not a counterfeit.  When I replaced the alternator in my car, I used a compatible after market one. It is not counterfeit either, just a less expensive option for the consumer who wishes to choose that.

However, those look-alike 82357B clones are counterfeit. They copied the look, the PCB layout, and presumably the firmware. Because it is identical in every way (except build quality) it works identically too, which is great for users, but it is clear-cut IP theft. I own one of these (see my earlier post), but I didn't get it as cheaply as some here, and I did believe it was authentic. I would not have purchased it had I suspected a counterfeit.
plesa:
Thanks for joining forum and posting story behind it. So the currently discussed adapters
http://www.ebay.com/itm/82357B-GPIB-USB-Interface-Compatible-with-AGILENT-82357B-new-version-/251692772284?hash=item3a9a0eebbc:g:GBgAAOSw8cNUTQ1O

with ID H82357 are based on one of your design?
Based on yesterday test these adapters accept the measat_releaseX1.8.hex firmware uploaded by fxload.
But uploading this firmware the adapter ID is changed to 82357B with SN: US12345678

Maybe this can explain why adapters does not work in Win10 at all and in Win8 they works on random basis.
nightpanda:

--- Quote from: plesa on December 07, 2015, 03:09:00 pm ---Thanks for joining forum and posting story behind it. So the currently discussed adapters
http://www.ebay.com/itm/82357B-GPIB-USB-Interface-Compatible-with-AGILENT-82357B-new-version-/251692772284?hash=item3a9a0eebbc:g:GBgAAOSw8cNUTQ1O

with ID H82357 are based on one of your design?
Based on yesterday test these adapters accept the measat_releaseX1.8.hex firmware uploaded by fxload.
But uploading this firmware the adapter ID is changed to 82357B with SN: US12345678

Maybe this can explain why adapters does not work in Win10 at all and in Win8 they works on random basis.

--- End quote ---

Yes,  that's the one I mentioned in my post. This guy bought two pieces from me, and then start sell his version on ebay. I also bought one unit from him, and compare the firmware file with mine and found only the ID and SN number was changed (you can simply do this by a ASCII file editor). I have also published my schematic on a local forum, so its not difficult to get all the stuffs.

But what he has is a very old firmware version. Basic SCPI send and read function is ok, but not support SICL mode (not able to communicate with old HP instrument like 3458A). Not support secondary GPIB address (like R&S CUM200), no DMA mode, and no Linux support.

Since we have the same hardware before 2014, the firmware file from S82357 could be used with his adapter too. And after that, I change the hardware and added another piece of EEPROM on S82357 with SN number and some other information on it. Before running the code, it compare those message and decide whether to run the code.

So, after 2013, S82357 firmware file is linked with its SN number. You can not simply read firmware from one piece and upload  to another piece. That's why I'm always asking customer to provide SN number for firmware upgrading. I need to generate firmware for each piece of S82357 individually.

I think that explains why H82357 with my firmware not works in Win10 or win8. It just failed at SN check point.
Macbeth:
I found a teardown of the Beiming S82357 on the Sigrok website. I guess we can identify the scratched off IC numbers now  ;)
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod