Hello johntmitchell, The Y-type USB cable is only necessary on older PC/laptops without USB 3.0 standard ports. If you have USB 3.0 ports on your system then you only need to connect the thicker of the two cables which carries power and data. It sounds like the USB driver did not install correctly, ...

Hello rteali0001, > The 'new' device shows all 'X's when read and no errors when blank checking. This "new" device has likely been programmed and protected. As this is not an erasable part there is not much that you can do. Do you have any more chips that you can try or chips from a differ...

Hello brian12345,

Unfortunately, our PG4UW software is created for manual operations and the remote control is focused on the device programming process. We do not plan to implement special features in the command line of the remote control system.

Hello Ryan@loreal, Based on the information we provide in the "Device info" section of our software for this device it is only possible to remove the protection by fully erasing the device: General Info: Code memory array is located in buffer from 0h to FFFFh. Work with 'User Signature Arr...

Hello KYPeter-Lee, > 1. What is the difference between "Registers" checked or not checked? It is the same as the "Flash" checkbox or the other checkboxes. Checked = program this area, unchecked = don't program this area. > 2. Understood, if the QE is enabled, !WP and !HOLD functi...

Hello PhilArqiva,

After READing a protected device the buffer content will usually be all FFh or 00h.

Hello Amani,

I believe this product is actually made by the company Cognex, not Dataman:

Hello iftikhar2000, Dataman support some of these manufacturers, for example we have supported 1900 of the GigaDevice GD32 chips. Some of these devices/manufacturers are not supported mainly due to a lack of samples and/or very low demand from our customers. If you have any specific devices in mind ...

Hello PhilArqiva,

Both of these chips have a security fuse, therefore if set, the read procedure will only get invalid data from the chip.

Are you sure these devices are not read-protected?

Hello radeonrelive, Our engineers have said that frankly speaking we don't understand this situation. Here in our lab the programming works (several chips tested), next solo verify also OK. It looks like the problem is related to the PIC17C44 chips themselves. Can you provide one for testing here in...