JourdanWithaU

USB had no error. Keyspan always had error. But it's ok... I FIGURED IT OUT!!! Short answer: The USB Printer Support Driver was too new. I had to force install an older driver. Driver Version: 6.1.7600.16385 works. I found it here: https://www.driverscape.com/download/usb-printing-support (https://www.driverscape.com/files/inbox/win764/usbprint.inf_amd64_neutral_54948be2bc4bcdd1.zip) Long answer: I happened to have an old drive that still had my old Win7 Install on it. Booted from that. Cutter worked. Went through the settings. Noted the driver version for the USB Printer Support. Rebooted into 10. Checked settings, Win10 Driver was different (newer probably). Found Win7 driver. Win10 didn't want to install it. Reboot with driver signature disabled. Forced the Win7 Driver down this MF's throat. Tested it. It works. It F-in' works... Again, Skeeter and slice&dice, I sincerely appreciate you guys popping in here and spending time helping people out. Digging through all this mess, your names kept coming up again and again. The world needs more people like you.

I can stick with the 6.0.21 as that has a more correct device option and known to work (Worked before). The CDM driver, I had initially loaded the 20828 until I found the updated 21228. Tried 4800 and 9600 rates. Moved the Bluetooth thing and set the Keyspan to COM3. Both rates, still initialization error.

[This post got long. But I want to get as much info out here in the hopes that it may help someone else who is having problems.] No love from Com2. Here are what the Com settings look like. This will net an the error initializing cutter. FYI, I have two instances of SignBlazer. Release 6.0.21 (Refine) that I have been using and Release 7.0.0 (RedSail) that I found on one of slice&dice's posts. Two completely separate installations. I'm trying to see if one will work. So far, they are both behaving the same way. I found an updated FTDI driver, (21228) and gave that a shot. Here are the USB settings. No love this way either. But it seems to be closer. There isn't the initialization error. And the job will flash in the print queue. But that's it. It flashes and the cutter itself just continues to sit idle. I found a PDF (attached) for Windows 7 setup which is exactly the process that I am doing how. But with the Win8 driver that I found here: https://www.uscuttersupport.com/mh-series-vinyl-cutter-setup.html (https://www.uscuttersupport.com/downloads/Drivers/MH_MK2_Driver_Win8_10.zip) Although I am not experiencing Step 13 where Windows Security comes in about not being able to verify the publisher of the driver. I had a similar issue when I first got this thing 8 years ago. I posted about it here and the FTDI driver got me out of the pickle. But it doesn't have the spice this time around. I am seeing some bits about driver security. But I'm not getting any pop-ups about any of these drivers being unsigned. Would Win10 throw a fit about an unsigned driver or just do nothing? I appreciate you guys helping out with this. It's kind of a shame that USCutter doesn't seem to be lifting a finger here. In fact a lot of their links that I have been digging through are dead. I get excited when I find something that seems new and I download it only to find that I already have that piece of the puzzle. MH_USB_WIN7.pdf

I'll try 2. 3-17 are listed as "in use". Bauds are 4800 on both com port and Sign Blazer. I don't think I have any of the original cables that came with the cutter. I might have used the original USB cable when I got it 8 years ago. I got a longer USB cable when I moved 6 years ago. This is the Keyspan I got, https://www.amazon.com/gp/product/B0000VYJRY/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1 This is the Null Modem cable I got, https://www.amazon.com/gp/product/B00CEMGMMM/ref=ppx_yo_dt_b_asin_title_o01_s01?ie=UTF8&psc=1

Got a Keyspan adapter today. Now SignBlazer has the error initializing cutter. I got the latest driver from Tripp Lite. The adapter initially came in as COM18 I adjusted it to COM1. Set the baud in SB to 4800. In my old version of SB, there is an option for Refine MH721, I'm using that. In the newer version, I was able to find RedSail RS800C. Neither are getting through. I also no longer have USCutter listed as a printer. Without the Keyspan, there wasn't a comport associated.

It acted like a printer for me in the past. It's listed as a printer in devices and printers. The video you sent me is almost a decade old and a Win7 install. I likely used that when I initially installed this printer 8 years ago. When I setup SignBlazer yesterday, it didn't take me through the Cutter setup and driver install. I had installed the drivers separately. But my cutter is not listed under the com ports. It is listed as a Printer and within the Print Queues. Is there a different driver I need to be using?

I'm running towards my wit's end on this. I have a similar issue. I have an MH MK2, Win10, and SignBlazer. This is a computer that was upgraded to Win10. Was working and running with Win7. Figured out that I had SignBlazer 6. Downloaded and installed 7. I also installed the chipset drivers and the MH_MK2_Driver_Win8_10 driver. Printer properties shows my printer on USB002. I have that selected in SignBlazer. When I go to cut, the job flashes in the print queue and nothing happens. I feel like I'm really close. But just not getting there.

Got it working! Found a more up to date driver. http://support.uscutter.com/index.php?/Knowledgebase/Article/View/72/23/ftdi-driver-executable-xpvista7 Works great! Thank you for the help, cowboy_1_831.

Could it be possible that the problem is the lack of flow control options as a USB Printer?

Thank you for the quick reply! I have that selected. When I send a job to cut, nothing happens. No error messages and nothing comes up on the machine.

So I am pretty sure I have everything set up right. I have Sign Blazer installed and working. I have my cutter set up and working. This is all on a computer running Windows 7. However, my cutter isn't connecting through a COM port. It's showing up under "USB Printer Support". How can I get it to come in as a COM, or how can I get SB to work with it being USB? - Jourdan