search

winder / Universal-G-Code-Sender

A cross-platform G-Code sender for GRBL, Smoothieware, TinyG and G2core.
http://winder.github.io/ugs_website/
GNU General Public License v3.0
1.9k stars 765 forks source link

Freezing up #1143

Closed waltoncnc closed 4 years ago

waltoncnc commented 5 years ago

Feature request

Problem description

Expected Behavior

Actual Behavior

Steps to Reproduce the Problem

1. 1. 1.

Specifications

Version

Operating system

Platform

Other

AbySet commented 5 years ago

Can you please put some text about your problem so we try to help ? thanks.

waltoncnc commented 5 years ago

Freezes up during carving. Have to shut everything down and start over. Have cancelled,router and computer on their own dedicated breaker. Have tried it on 3 computers. Get it cutting again and within a few seconds it does it again. On Oct 26, 2018 1:50 PM, AbySet notifications@github.com wrote:

Can you please put some text about your problem se we try to help ? thanks.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/winder/Universal-G-Code-Sender/issues/1143#issuecomment-433490649, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlR8fX9IS_opHliCMCCX7iie0w5H9TDuks5uo0tzgaJpZM4X6ro1.

AbySet commented 5 years ago

Is it software freeze or machine freeze ? We also would like to know:

waltoncnc commented 5 years ago

Software freezes up. Windows 10 and Windows 7 Grbl 1.1f It is a stock Shapeoko 3xxl. Tried three computers and everything is on its own dedicated breaker. On Oct 26, 2018 2:23 PM, AbySet notifications@github.com wrote:

Is it software freeze or machine freeze ? We also would like to know:

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/winder/Universal-G-Code-Sender/issues/1143#issuecomment-433499902, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AlR8fblhdOqehx_tt5GH2HPjY9E33NKNks5uo1MFgaJpZM4X6ro1.

AbySet commented 5 years ago

If you tried with the same usb cable into all 3 PCs then try with some other usb cable. If you tried with different usb cables and still doing the same issue, then you may call service for controler replacement, hope you still have the waranty for that.

This assume that:

Please let me know when you fix it and how. Good luck.

BarrettLowe commented 5 years ago

I am using the nightly build on a shapeoko 3xxl using Windows 7 home SP1 and the nightly build from December 18. All seems fine to me. I've got merely 4 gigs of RAM. Maybe some of this can help you?

AbySet commented 5 years ago

If it does freeze always with the same file and only with that file and according to your previour posts i suspect:

Can you post you gcode files ? Does different gcode file the same issue ?

(All this assuming that the machine is freezing not the software).

carneeki commented 5 years ago

A HOWTO for @AbySet 's suggestion that step frequency could be too fast, let's confirm or rule it out by getting the following information:

  1. The last 5 or 10 lines of code that cause the failure (or possibly further up if the F word is set earlier).
  2. Output of the Grbl config, this can be copy+pasted from typing '$$' into the command box and pasting the output back here.

Background reading (optional) & Explanation: There's a value configured inside of Grbl called the "step rate". It has a maximum limit based on a bunch of complicated maths and how the Arduino inside the Shapeoko works, but essentially, this step rate cannot exceed 30k steps per second (30khz). The stepper motors take a step pulse from the drivers (which are kind of like amplifiers for the Arduino microcontroller), and move forward a small "click" or step. If you try to make the gantry move too fast, Grbl tries to step faster and faster. Eventually it may exceed this 30khz figure, and the controller resets.

Shapeoko should have configured $110, $111 and $112 appropriately so that this wouldn't happen, or maybe the CAM software you use should prevent feed rates (F word) from exceeding the maximum rate.

Further reading (though not necessary, but might be of interest) - https://github.com/grbl/grbl/issues/194 and https://github.com/gnea/grbl/issues/41.

This all assumes that the step rate is being exceeded. We cannot tell until you give us the info in (1) and (2). Thanks!

breiler commented 5 years ago

Could you check which connection driver you are using, try switching to the other:

image

AbySet commented 5 years ago

Thank you carneeki, i also suggest to follow breiler recomandation. And please let us know if you fixed it and how.

breiler commented 4 years ago

Closing as there wasn't any feedback on suggested workarounds.