Computerized Cutting Systems and Supplies – KLIC-N-KUT › Forums › Cutters & Equipment › KNK MAXX, Groove-e & Eagle › Can't get the Maxx to communicate with PC
February 4, 2018 at 9:47 pm #30465
Hi, I’m having trouble getting my KNK Maxx to communicate with my Windows 10 PC. I followed the instructions I found in some other forum posts, like installing the D2XX drivers and directing software to the correct COM port, but when I send a cut file or even a connection test, nothing happens. Should I see the device listed as a KNK Maxx in my connected devices? Currently it looks like Windows sees it as “FT232R USB UART”. Any advice to help get this set up would be a big help. Thanks!February 5, 2018 at 12:15 am #30469
Seeing it listed as FT232R USB UART should be fine. What model do you own? What software are you using?February 5, 2018 at 12:36 am #30472
Thanks for the quick reply! I’ve got the KNK Maxx, 24-inch model. I have a copy of Make the Cut, which I’d like to use since I’m familiar with it. The person who sold it to me also included a disc with ACS Studio on it, but I’m not interested in using that if I don’t have to.February 5, 2018 at 9:22 am #30474
Three things to check: in MTC, make sure you have the correct Maxx model selected. Secondly, make sure the Com Port selected in MTC matches what is shown in Device Manager under Ports. Thirdly, make sure the Baud Rate on the Maxx itself matches what you’ve selected in MTC.February 5, 2018 at 12:54 pm #30482
Hm, I checked the model (and even tested using the incorrect models), selected the correct Com Port (and even tried changing it to a different one in the advanced Device Manager settings) and confirmed that the Baud Rate is correct (didn’t want to fiddle with that, as I don’t really understand it).
I’m going to see whether it works on a different computer, just to rule out any problems with the machine, but I would ultimately like to get it working with my main computer. Any other suggestions?February 5, 2018 at 3:38 pm #30491
Still trying to get this working, though I found something that may be useful in diagnosing it:
I tried sending some cut data while the machine was in offline mode, and the MTC progress bar said, “Flushing buffers. Waiting for KNK machine”. When I switched the machine back to online mode, the progress bar moved and the coordinates were sent, however the machine still did nothing. I tried using the “repeat” button on the machine, to cut the last data sent, but the screen said “no data”.
So it would seem that the computer is recognizing the machine, but the machine isn’t accepting the data that’s being sent to it?February 5, 2018 at 4:56 pm #30494
Let me think on it some more. Checking on a different computer is definitely a good idea.February 5, 2018 at 5:00 pm #30495
I was only able to get to the same point with the other computer: recognizes that the device is plugged in, MTC points to the correct model, baud, and com port, but nothing happens when the cut data is sent. On both computers MTC can tell whether the machine is in offline mode, but the machine is unresponsive to anything the computer tries to send it (connection test, cut data, or laser alignments).
I’ve also requested support via the KNK site, but still waiting to hear back from them.February 5, 2018 at 5:02 pm #30496
Looks like it’s a similar issue to this thread:
But there was never a solution posted. And my machine is definitely just the Maxx, I checked in the menu and didn’t find any bluetooth.February 5, 2018 at 7:55 pm #30504
Hooray! I figured it out!
There are actually three places to that need to be set to 57,600, not just two. I had the machine “br” set to 57,600 and in Make the Cut I had the Baud Rate set to 57,600, but it turns out the settings of the Com Port itself were only set to 9600. Once I changed that, everything worked great.
For other folks who might be stuck, go into your Device Manager, open your USB Serial Port (COM*) properties and go into Port Settings. Make sure that the Bits Per Second are set to 57,600, or matching whatever your other settings are.
It only took me an entire day, but I am fully operational! And now I know that br, Baud Rate, and Bits Per Second are all related terms.February 5, 2018 at 8:08 pm #30506
That’s fascinating… simply because the software is supposed to ALWAYS override the setting in Device Manager and has always done that (for years) up until now! lol I’m so glad you figured that out. I’ll note this in my tech support database as another thing to check. Thanks for posting back and feel free to post again with any other questions or issues.February 5, 2018 at 11:25 pm #30519
Well, maybe I spoke too soon… I shut things down and when I came back later to show off, it was back to not working. Rrgh. I don’t remember what else I had done that might’ve temporarily fixed it, but I submitted a support ticket with KNK this morning, so hopefully they can help me out soon. At least it was mildly encouraging to see it work for a few minutes.February 6, 2018 at 12:40 am #30520
The fact that it DID work eliminates a lot of possible causes. Hopefully KNK will have the solution but I will also check my tech support notes to see if I might have missed something else.February 6, 2018 at 8:20 pm #30546
Yeah, it’s still frustrating but at least I know it could work eventually! Do you happen to know how quickly KNK typically responds to support tickets? I submitted one yesterday morning, but haven’t heard anything from them yet.February 7, 2018 at 1:33 pm #30561
You must be logged in to reply to this topic.