$25 Windows 10 x64 OEM mode 1314 and DIY Cable

[yanuk]

Originally Posted by jakehanl

So I wish to clarify the entire procedure from start to finish; before I actually get started on doing anything.

1) Make cable as prescribed.
2) Install Curtis software (ie. 1314-4401 Version 3.12 build 33 Update Patch 2 - except I can only find build 35 - Patch 4 hopefully this is okay?)
3) Reprogram FTDI chip as prescribed and use template & other instructions.
4) If the drivers didn't install, manually install them and point Windows to "C:\Program Files (x86)\Curtis Instruments\1314-4402 PC Programming Station\1309 USB Driver" (BTW - these drivers are part of the later software version 4402 - A bit confused by this as I would also then need to install the 4402 software correct?)
5) Once FTDI cable is connected to controller, Bring up Regedit. Go into HKEY CURRENT USER/Software/Curtis Instruments/1314 CV4/Settings
**Under Name, look for the entry IAL and right click on the name IAL, select Modify Binary Data - For the line 0000, you want to input the values 76 00 31 00 EC 00 44 00 - For the line 0008, it remains 00 00 00
**Do the same for SAL.

If I install the Curtis 1314-4401 software beforehand; I do not see the registry values for SAL v1ìD at all. Are these registry fields created when I first plug in the FTDI cable alone or does the cable also need to be plugged into the controller as well? OR am I completely incorrect about such? OR Do I have to create the actual registry entries SAL & v1ìD manually? If I do, what exactly do I need to enter manually as far as the exact registry entries please?

Did I get anything wrong here or is there anything that I have missed?

Also, can either the 1314-4401 OR the 1314-4402 software be used with the FTDI cable? If so, do I only need to invert Rx and TXT signals with the earlier version 1314-4401 OR?

I sincerely appreciate the assistance :)

I was equally confused after reading resources here and from another different thread.

If you're using 4401 version, you only need a standard USB - Serial cable without Tx/Rx inversion, VID/PID will be standard FTDI factory default. Try both serial and enhanced serial. (Enhanced worked for me, but not serial)

Use a low comm port number because apparently higher numbers don't work.

If you're using 4402, then the cable in the first post with Tx/Rx inverted signal is for you. It didn't work for me even after entering the IAL and SAL registry values. It recognised the cable, I could enter OEM mode but couldn't detect the curtis controller target.