KNK with windows 10 issue

gup

Gday all its been a while since ive needed help but im back now
The old KNK has been in the cupboard for a while and I have updated to windows 10.
When I plugged it all in I got this error message and I cant work out how to fix it. I have updated MTC and all the drivers and plug ins and still cant get it to work...any ideas would be great. 

Crazy_Mr_Zing

I have no experience with the KNK
Here is a Old discussion does it offer a solution
http://forum.make-the-cut.com/discussion/16814/overlapped-i-o-operation-error-when-cutting-to-a-knk

gup

thanx but i read that one and tried all that.

Crazy_Mr_Zing

I not 100% if you need it but maybe installing the latest FTDI driver
http://www.ftdichip.com/Drivers/D2XX.htm

Liz_A

@gup - which KNK do you have? I found this in regards to connecting the KNK Element:

"Do you have the serial cable as well? You need TWO SEPARATE cables... a serial and then an adaptor that has a serial end and a USB end. ONLY using the serial-to-USB adaptor will not work."

SandyMcC

@Liz_A is most likely correct. The fact your window shows CH341 next to the COM Port number indicates that it probably won't work. I have an early Element model that requires using the serial cable plus converter if I want to use MTC instead of KNK Studio for cutting.  Andy, the developer of MTC, explained it once but it was all Greek to me. Chad at KNK USA confirmed that the early Element models had a different kind of USB module whereby the boards were actually serial and not USB but had this converter on them.  Again... mostly Greek to me. I just knew that because my Element used a CH341 driver, I could only use MTC via a serial cable plus converter cable.  

My only question to you is if you know with 100% certainty, that you were able to use direct USB with your Element AND MTC at some point?  Again, it's not an issue with KNK Studio, only with MTC.   If you were, then maybe just following Paul's recommendation and installing  the latest FTDI driver might make the difference. 

gup

thanx for all the help everyone. I have ordered a new serial cable to try and see if that works. it did all work on MTC with the usb but this is the 1st time i have used it after updating to windows 10....curse you windows 10!!
downloaded the new driver Paul recommended now.   
oh its a "elements" machine I think.big white one with a green origin button and some blue triangle ones  

gup

still no joy it shows up with a com port when i connect via usb but nothing with the serial cable. still getting the same overlap message and cant connect.

gup

ok so joined 2 serial leads together and it comes up as com port 9 but there is nothing with com port 9 in the MTC drop down?

SandyMcC

Can you explain what you're using in more detail?  For example, here's what I have to use. On the right side is an RS232 serial cable. It is then connected to an RS232-USB converter cable.  The end of the white cable (on the right) plugs into the serial port on the Element. And then the end of the black cable  (on the left) plugs into a USB port on my computer:   

gup

im using exactly the same set up as pictured.

SandyMcC

What is the new listing under Serial Port in the MTC window... exact words?  Also, are you positive that both the serial cable and converter are RS232? 

Crazy_Mr_Zing

Could it be the the converter cable needs a different driver ?
Only going what I read off the net
There appear to be 2 major chip providers FTDI and Prolific

There quite some discussion Microsoft Update did seem to cause quite a few issue with these devices

The other thought was is the USB port you using a USB 3  as I have some older equipment that won't work on USB 3 ports not sure why
I just swapped to a usb 2 port and they work

gup

gup

no idea whats going on with it.... you only get 1 go to test connection and then it is gone from the drop down and you have to unplug it and start again,but still with the error message.

SandyMcC

These cables are not all the same. That's why I always recommended specific sources for both the serial and the converters so that they would work.  When mine is connected, the menu option would be something like COM9 (USB-to-Serial) and that's all. I've never seen anyone use Prolific before.  Sorry.    

Crazy_Mr_Zing

I would assume if this was a driver issue there would be a little yellow escamation mark next to the device in device manager
found think link not sure if it will help
https://www.campbellsci.com.au/blog/usb-rs-232-adapter-cable-issues

Liz_A

@Crazy_Mr_Zing - not always the case. Windows may install a generic Windows driver which may make the device work as far as Windows is concerned, but the software or something else doesn't like it. No yellow explanation marks...those are usually indicative of missing drivers all together, a resource conflict, or other stuff.

Crazy_Mr_Zing

I guess i assumed incorrectly Liz

I have been reading about both FTDI and Prolific that measures to prevent devices contain non genuine copy of their chips working with new driver releases  ?

Liz_A

@Crazy_Mr_Zing - well it's a KNK and I doubt they would have counterfeit chip in it. Heck all of our cutters would have come to a grinding halt, likely!

Liz_A

@Crazy_Mr_Zing - I would think that a solution would be to roll back to an older driver version.

Crazy_Mr_Zing

OK wasn't sure if it was a knk supplied convertor cable
I was assuming KNK cable would be ftdi chipped  where as the image seem to show it being prolific
wondering if in the short term rolling back the windows update would resolve the issue

SandyMcC

Later today, I will pull down my original Element, hook up my two cables that are the brands/types that DO work with the Element and I will again test that the Element works fine under Windows 10. I have the Fall Creator's release installed.   

SandyMcC

Okay, using recommended serial and converter combination, my Element communicates just fine with my Windows 10 computer that has the Fall Creator's Edition installed.  When I go to Device Manager and look up the driver that is working with my Element, this is what I see:  

MeFlick

SandyMcC said:

These cables are not all the same. That's why I always recommended specific sources for both the serial and the converters so that they would work.  When mine is connected, the menu option would be something like COM9 (USB-to-Serial) and that's all. I've never seen anyone use Prolific before.  Sorry.    

Though it wasn't a  windows 10 issue at the time - I found the same thing.  Not all USB to serial cables are created the same.  I had a similar issue back with a Black Cat Cougar and had ordered one USB to serial converter cable and it simply would not work and had to get a different one.  I have found this is not an uncommon problem with those converter cables unfortunately.

Since Sandy notes just above this hers works with the cables KNK previously knew to work with the Element, this is probably the same issue and you will need to get those specific cables.