Multiple units were up for sale as recently as a couple months ago. Locky told me that new hardware is currently being developed, but no timeline was given.
BK
BK
Hi,
are there any news regarding a new curve tracer from Locky_Z?
I think, this time I wouldn´t wait till too long for an order.
jauu
Calvin
are there any news regarding a new curve tracer from Locky_Z?
I think, this time I wouldn´t wait till too long for an order.
jauu
Calvin
Subscribed.
Interested to buy a curve tracer from Locky_Z.
Let me know when the new model is out for sale.
Thanks
Interested to buy a curve tracer from Locky_Z.
Let me know when the new model is out for sale.
Thanks
I am a bit late to the party...
Is this curve tracer still available? If yes: how and where?
Is the software interface documented so that I could cobble up my own software?
Is this curve tracer still available? If yes: how and where?
Is the software interface documented so that I could cobble up my own software?
Software Version 3.5
Hi Murdoc
I try to find the software version 3.5 in the yahoo group. Registered but cannot find. Any hints?
Thanks in advice!
Markus
Hi Murdoc
I try to find the software version 3.5 in the yahoo group. Registered but cannot find. Any hints?
Thanks in advice!
Markus
Is this curve tracer still available? Ready to buy.
If not, is there any manufacturing documentation?
If not, is there any manufacturing documentation?
Does the Yahoo group still exist? When I call up the address
given in the readme file of my Locky-Z, I get "server not found".
Maybe they moved to groups.io like most everybody else.
I think, I've got V 3.5 of the software.
The .doc files are partly electronically unreadable and the
rest is not really understandable. I managed to produce
some Id over Vgs plots for some JFETs. BJTs did not work
for me at all. My locky-z is sitting on the shelf collecting dust.
Gerhard
given in the readme file of my Locky-Z, I get "server not found".
Maybe they moved to groups.io like most everybody else.
I think, I've got V 3.5 of the software.
The .doc files are partly electronically unreadable and the
rest is not really understandable. I managed to produce
some Id over Vgs plots for some JFETs. BJTs did not work
for me at all. My locky-z is sitting on the shelf collecting dust.
Gerhard
Oh, Markus, you were searching the software 3.5
Try < www.hoffmann-hochfrequenz.de/downloads/ENG.zip >
It won't stay there forever, tell me if it works.
Or send me your email address. 3.1 MB
Try < www.hoffmann-hochfrequenz.de/downloads/ENG.zip >
It won't stay there forever, tell me if it works.
Or send me your email address. 3.1 MB
I have used this curve tracer very happily on a Windows7 PC since the original launch of the group buy.
But now that the move to Windows10 is imposed for the workshop PC which I want to be online as well, as I feared, the USB-to-Serial driver doesn't work (regardless of the original driver provided on CD with the curve tracer). I keep an offline Windows7 installation as well (for many other obsolete test devices/interfaces), but it would be nicer if the Win10 PC would allow the curve tracer to be used.
Having installed a 64-bits Windows10 Pro, with all possible updates to date, the curve tracer will not be able the obtain 'parameter from device', with the following screen shots from Win10 device manager:
With the following properties:
"This device is working properly" .... yeah, right.... not really thus
In other Windows versions (7, 8) it might also state "error code 10"
So, hereby a simple fix for how to FIX the "Prolific USB-to-Serial" driver issue, for anyone else encountering this problem.
Main cause of this issue is because the curve tracer contains a counterfeit (i.e. clone) Prolific chip. To solve this intellectual infringement, the original Prolific companies modified their newest drivers to render the counterfeit adapters unusable. Unfortunately this decision also renders all earlier adapters inoperative.
The Prolific drivers that Microsoft supplies via Windows Update, Versions 3.4.67.325, 3.4.25.218, 2.1.51.238 and 3.4.62.293 - will not work with most adapters and therefore shows the above or generic "Code 10" error. Or you may get no error at all, but the curve tracer will still not work.
As Windows 8, 8.1 and Window 10 are set by default to automatically update your drivers without your permission (or notifying you of the update) no matter how many times you remove the driver files and reboot - the next time you insert the USB-To-Serial adapter, Windows installs the newest non-working version again.
After some searching da mighty web, the only driver that works with all the "Prolific" adapters is Version 3.3.2.102.
32-bit here
64-bit here
The installer program will remove all of the incompatible drivers — make a change so that Windows can never update the driver without your approval — and install the Version 3.3.2.102 compatible drivers. Disconnect any USB-to-Serial device prior to installation, and connect the (powered-up) curve tracer during the installation process only when prompted to do so.
After installing the driver patch, the device manager screen and driver properties should look like this.
xx
With the following properties screens:
and
and
And when running the curve tracer start-up procedure, the very wanted screen:
Happy days again
Credits to the website providing this solution here.
But now that the move to Windows10 is imposed for the workshop PC which I want to be online as well, as I feared, the USB-to-Serial driver doesn't work (regardless of the original driver provided on CD with the curve tracer). I keep an offline Windows7 installation as well (for many other obsolete test devices/interfaces), but it would be nicer if the Win10 PC would allow the curve tracer to be used.
Having installed a 64-bits Windows10 Pro, with all possible updates to date, the curve tracer will not be able the obtain 'parameter from device', with the following screen shots from Win10 device manager:
With the following properties:
"This device is working properly" .... yeah, right.... not really thus
In other Windows versions (7, 8) it might also state "error code 10"
So, hereby a simple fix for how to FIX the "Prolific USB-to-Serial" driver issue, for anyone else encountering this problem.
Main cause of this issue is because the curve tracer contains a counterfeit (i.e. clone) Prolific chip. To solve this intellectual infringement, the original Prolific companies modified their newest drivers to render the counterfeit adapters unusable. Unfortunately this decision also renders all earlier adapters inoperative.
The Prolific drivers that Microsoft supplies via Windows Update, Versions 3.4.67.325, 3.4.25.218, 2.1.51.238 and 3.4.62.293 - will not work with most adapters and therefore shows the above or generic "Code 10" error. Or you may get no error at all, but the curve tracer will still not work.
As Windows 8, 8.1 and Window 10 are set by default to automatically update your drivers without your permission (or notifying you of the update) no matter how many times you remove the driver files and reboot - the next time you insert the USB-To-Serial adapter, Windows installs the newest non-working version again.
After some searching da mighty web, the only driver that works with all the "Prolific" adapters is Version 3.3.2.102.
32-bit here
64-bit here
The installer program will remove all of the incompatible drivers — make a change so that Windows can never update the driver without your approval — and install the Version 3.3.2.102 compatible drivers. Disconnect any USB-to-Serial device prior to installation, and connect the (powered-up) curve tracer during the installation process only when prompted to do so.
After installing the driver patch, the device manager screen and driver properties should look like this.
With the following properties screens:
and
and
And when running the curve tracer start-up procedure, the very wanted screen:
Happy days again
Credits to the website providing this solution here.
Last edited:
More platforms than just windoze need to be cared for. Linux, OSX at the very least.
And the real goal shouldn't be just to display curves. The data should be used for more than just plotting curves, it can be used to match devices.
And the real goal shouldn't be just to display curves. The data should be used for more than just plotting curves, it can be used to match devices.
What will you do while you wait?
Until someone builds and sells the exact test instrument you desire, including all of the functions and features you think are important ... what do you do before then?
Until someone builds and sells the exact test instrument you desire, including all of the functions and features you think are important ... what do you do before then?
I run it on Win7, on a virtual machine provided by VMware player on Linux Mint.
If Prolific had the slightest interest in selling their chips, they would probably
have a distributor one could find in 10 minutes.
If I could get hold of one good chip, I would probably buy it and replace the
pirate chip. This is DIY, after all.
And then I'll never buy anything with Prolific inside.
Gerhard
If Prolific had the slightest interest in selling their chips, they would probably
have a distributor one could find in 10 minutes.
If I could get hold of one good chip, I would probably buy it and replace the
pirate chip. This is DIY, after all.
And then I'll never buy anything with Prolific inside.
Gerhard