I just upgraded to a new PC,

I just upgraded to a new PC, from Windows 7 32 bit to Windows 10 64 bit (dell XPS 8910 w Win 10 pro). I installed LaserWeb and mirrored the settings that I was using under Windows 7. When I run a job I get “Server error: Writing to COM port (WriteFile): Unknown error code 22” after a few lines of the job. I had it working under Windows 7 after updating my Smoothie firmware. It’s a K40 with a Cohesion3D Mini board. I suspect I may be I need some driver or need to change some setting but I am not sure what. I was sure to use one of the USB 2.0 ports.

I also get the error “Server error: Writing to COM port (GetOverlappedResult): Unknown error code 121” and then the laser just freezes up

You do not need to install any Smoothie drivers for windows 10.

I didn’t think so but I’m thinking there had to be some driver or setting for something since it’s dropping. I’m tinkering with the serial driver settings with no luck. As a side note seems when it disconnects the Cohesion3D mini board freezes up (though I ran the small raster job off the SD card with no issue)

Board keeps freezing up… not so sure it’s a LaserWeb issue as I thought at first but probably something from switching to a new machine. I tried manually installing the windows 8.1 drivers with no change.

As a note, I was sure to use one of designated USB 2.0 ports. I am going to turn off all that USB power saving features, I think I got them all, but I’ll take another double check. I plugged the laser back into the Win 7 Dell PC, and the connection remained stable. I took note of what settings were at in the device manager in the smoothie serial port in my Win 7 and I am going to be sure to replicate that in Win 10 tonight and see what that does.

I’m starting to suspect the mbed USB driver running on the 1769. We noticed horrid mbed driver behavior with non-USB stuff porting grbl so switched to more conventional libraries before even attempting to use mbed’s USB support. There’s a lot of flexibility on the USB host side and maybe the mbed driver just can’t handle all the variation that’s out there. My take on mbed: good idea, horrid implementation. I’ll never try it on an embedded device again.

So far no luck…still just keeps disconnecting within 5 mins tops with the overlap error. Based on the links seems it just might not work on my new PC
… which is a shame since I upgraded just for the laser. Maybe it will work eventually one way or another.

I have my old and new pc in the same room and on a KVM so it’s not that bad to switch the USB back and forth should other ideas need to be tried.