LaserWeb/lw.comm-server

Win10/USB3 bug OverLapped Results

Opened this issue · 32 comments

  1. Connect to Smoothie
  2. Start a Job
  3. Click the Feedrate Overides
    3.1) Get pissed at 1% being too small an increment (make it +10% please - practically speaking i cant see why anyone would do 1% increments during a job. When shit starts chattering you want to adjust the feed FAST! you dont have time for hundreds of clicks. ) )
    3.2) Lose connection to your machine because of the overlapped write, break endmill, ruin material. Realise its last material you had on hand. fuck

You can CTRL-Click to get 10% stepps (help showed on button mouseover).
1% stepps are very usefull to find the sweet spot, especially with laser power.

What do you mean with "create overlapped results"?

"What do you mean with "create overlapped results"?": Total Guesswork: I think it happens when node-serialport is trying to write two streams to the port (queue and realtime)

https://github.com/EmergingTechnologyAdvisors/node-serialport/blob/master/src/serialport_win.cpp#L277

PS: on my faster desktop it doesnt happen often. but on my cheap, slow, https://www.walmart.com/ip/Nextbook-Flexx-10.1-2-in-1-Tablet-32GB-Intel-Atom-Z3735F-Quad-Core-Processor-Windows-10/46664255 windows 10 netbook, it happens almost every time i try using override, but always after a couple clicks, 10+

Or it could be that win7 works better, and win10 doesnt... dont have another win10 to test against

I work with Win10 but never got this error related to overrides or other "real time" commands.
It just happend sometimes mid job with smoothieware, but not anymore with grbl-LPC. Probably has something to do with different USB protocolls.

Okay, still happens on the new Asus laptop, so ruling out slower CPU being the main culprit. Did however notice it happening easier during short segment moves. Mentally i hold off feedrate adjustments till its about to do longer sections.

Error code is 121

We have just had a few reports from users that they are getting the overlapped results error as well.
twoxlje0exs6lnr4rm0baa

Users are running 'Windows 10 home version 1607'
Is there any further development on this?
Is there any information that would be useful fur us to provide to help resolve this?

@domenic-d , also happened when using feed/power overrides?

I checked with them after your feedback and no users reported making any changes to feed/power overrides.

Find out EXACTLY when / why they got the error. It shouldnt happen during normal operations (as during normal operation we run just the single file queue (out, ok, out, ok). Its during overrides that an extra line of commands are dumped onto the port...

(Maybe they dont know the up/down buttons on the DRO are called "feedrate override" and "S override" - so they report they didnt because they dont know what they clicked>?

According to the screenshot, it's not a firmware-cnc version. We need firmware-cnc!
And what are those two Ellapsed lines? Is this a new special smoothie firmware?

@cprezzi This is the current version of Smoothiware we use. There is nothing special about it.
What classifies it as smoothiware-cnc on your system?

Smoothieware should send a second line CNC Build 3 axis after the first line, but probably this is only visible at the server console. I will download and test the latest smoothieware later today.

This is how it should look like when using the right firmware-cnc.bin:

grafik

@domenic-d Can you provide a file and the settings which caused the OverlapedResult error?

I was able to replicate the OverlappedResult error when using a cheap 1.8m USB cable, while it worked flawlessly with a good quality 1.8m cable or a standard blue 0.5m cable (without ferrites)!

All this was tested with the same front panel USB port on a desktop PC with Windows 10 and my C3D Remix.

Then I measured the USB voltage on the board side:

  • Standard blue 0.5m cable: 4.3V
  • Good 1.8m cable: 4.3V
  • Cheap 1.8m cable: 4.0V !

Changed to a rear USB port (onboard) I got 4.16V with the cheap 1.8m cable and the communication was stable.

It seems that not all USB ports provide the correct 5V and bad cables decrease that even more. If the voltage on the board dops below ~ 4.2V, the serial communication (and whatever else) seems to be unstable.

Unfortunately most users with Smoothie or C3D boards do not have a 5V supply.

@cprezzi @openhardwarecoza I am asking for more information. I'll pass it on as soon as I have it.

Ok. I was testing with the Cohesion Remix but without external power connected. If I connect the external 12V supply, the board voltage increases to 4.8V and it works also with the cheap 1.8m cable.

We have been able to replicate 'our' specific problem on our machines in the lab.
It is caused by plugging the smoothieboard into a USB3 or SSUSB port.
After a short period of time, the firmware crashes and these errors are reported.
It is not related to Laserweb.

We will take this up with the Smoothie team.

My PC also hasn't USB3, but one of the ports is combined USB/eSATA, and this port doesn't work with the Remix board.

It is an unusual problem which we have been testing all day. We have tested the latest smoothiware firmware (both cnc and reprap). Both behave the same, with the firmware crash.
This all became apparent with the new laptop we purchased for our QA workstation. None of our other older computers can produce this problem.

Okay. So running on the usb2 port for the last couple days have indeed proven to be more stable. But not eliminated the issue. Now, i still get getOverlapped-121 errors, but, they happen when i have feedrate override over 180% and, then it happens randomly mid job (not only on fro clicks). Looking more and more like usb driver. Might try grbl-lpc to see