Sharp 90* turn in gcode becomes a large sweeping turn

More
6 years 7 months ago #159729 by BobsGotCnc
G64 P0.0005 resolved the sweeping 90* turn.

So I am still a CNC newb. When I am in the CAM phase, how would I detect such an issue in the future as to reduce the likelihood that I destroy valuable material when running the gcode? At this point in my learning (about 4 months in), I feel like every other new design I take to the CNC destroys a piece of material. Each time I learn something new, but it is getting a bit discouraging that it feel rare to generate gcode, execute it, and have the piece I designed. Maybe this is part of the hobby cnc router process?

Please Log in or Create an account to join the conversation.

More
6 years 7 months ago #159738 by PCW
Probably best way is to have your CAM program insert a gcode preamble that includes
important modal gcodes like G64 Pxxx.

Also with new code and expensive material, take time to study the preview,
or run it in simulation to see if its doing what you expect or perhaps
do an run on scrap material
The following user(s) said Thank You: BobsGotCnc

Please Log in or Create an account to join the conversation.

More
6 years 7 months ago #159740 by PCW

lumberjack_jeff wrote: Thank you for the troubleshooting help.

Can you please advise me about debouncing pin 10?

I think I need to replace this wscnc.hal code

Code:
... net estop-ext <= parport.0.pin-10-in ... #limits debounce to stop false triggers loadrt debounce cfg=2 #change to the number you want setp debounce.0.delay 100 #this sets the delay 100 iterations of the base thread addf debounce.0 base-thread net deb-probe-in debounce.0.0.in <= parport.0.pin-12-in-not net probe-in debounce.0.0.out
with
Code:
... loadrt debounce cfg=2 #I think I only need two setp debounce.0.delay 100 setp debounce.1.delay 100 addf debounce.0 base-thread addf debounce.1 base-thread net deb-probe-in debounce.0.0.in <= parport.0.pin-12-in-not net deb-estop-ext debounce.1.0.in <= parport.0.pin-10-in net probe-in debounce.0.0.out net estop-ext debounce.1.0.out


If you loadrt debounce cfg=2
you get a 2 channel instance of debounce.0
which may be OK if both channels can use the
same delay, for example:

loadrt debounce cfg=2 #I think I only need two
setp debounce.0.delay 100
addf debounce.0 base-thread
net deb-probe-in debounce.0.0.in <= parport.0.pin-12-in-not
net deb-estop-ext debounce.0.1.in <= parport.0.pin-10-in
net probe-in debounce.0.0.out
net estop-ext debounce.0.1.out
The following user(s) said Thank You: lumberjack_jeff

Please Log in or Create an account to join the conversation.

Time to create page: 0.052 seconds
Powered by Kunena Forum