Advanced Search

Had a look again, in the sim. When enter the first number or decimal point, 'file not open apears' in the dialog box.
When i delete all content of the input field, another message:

 

You might have some luck in remapping an unallocated gcode, but I'm unsure how this would integrate with your cam software.
linuxcnc.org/docs/html/remap/remap.html

Best bet guys, since this an official release is to go to GitHub and raise an issue.
As it is there should be no "kinks".
Just out of interest does inputting 0.0 or some other variation work ? Just a guess .

MaHa wrote:

That was not helpful. Now it's off the no reply list without solution.
As mentioned, any input but zero greys out the ok button. The real machine and sim in Virtualbox have the same issue.
In the dialogbox it says:  file not open
A gcode file is loaded, so this could point to an internal fault

 

To be fair, you never said "anything other than zero causes it to be greyed out", you said that 0 works.

Probably a bug.

Keep using 2.9.4 'till the kinks are worked out.

You never stated the outcome of values other than -1 and 0.

Sorry for the miscommunication.

Perhaps magnets are a solution?

If you have a magnet in the home location or something, the spindle could move there and deposit its strings fter each drill.

Unless your spindle motor and spindle driver are capable of instant reversing, you will have to wait for the motor to stop, then reverse, stop again, and restart, which could be a lengthy procedure, not to mention being potentially detrimental to the spindle and/or driver in the long term.

The same her with 2.9.5 on my real machine and simulation. I went back to 2.9.4.

Second line does not look correct, see my previous post.
You have a # in the wrong place behind a < , it should be in front of it.

Ok, I got some help and realized the mesa 7i76e was in mode 0, now it is in mode 2 and I can see the counts on hm2_7i76e.0.7i76.0.0.enc0.count

I am still lost about how the following works (as for the logic)

I would love to have one button that enables the jog for x axis for example, and then the mpg makes it move (while the button is pressed)

 

Don't know why file didn't come through, but I'm pasting it here:

o<auto-xy-zero> sub
<#factor> = 1 (Adjust for metric)
o100 if [#<_metric> EQ 1]
#<factor> = 25.4
o100 endif

#<X-move> = [#<_ini[LASER]laser-offset-x> * #<factor>]
#<Y-move> = [#<_ini[LASER]laser-offset-y> * #<factor>]
#<feedrate> = [20 * #<factor>]

; (Move table to program start)
G91 G0 X#<X-move> Y#<Y-move> F#<feedrate>
G10 L20 P0 X0 Y0 A0 ( Set X/Y DROs to zero )

o<auto-xy-zero> endsub

m2

Looks to me that all of the references are correctly formatted.

Regards,

Hi,
Is there any way to easily add spindle reversal each hole during drilling? I drill a lot and the my steel is too stringy regardless of speed and feed. i came across HASS video of it. this is the link .
is there any way I can modify G83 like that? or even better spindle reversal between pecks

That was not helpful. Now it's off the no reply list without solution.
As mentioned, any input but zero greys out the ok button. The real machine and sim in Virtualbox have the same issue.
In the dialogbox it says:  file not open
A gcode file is loaded, so this could point to an internal fault
 

Are you using PNCconf?

Weird.

Does positive 1 work?

Aciera wrote:

I've replaced the standard kinematic file with your modified version, added extra joints and changed the config to inches to test in the simulation but I cannot reproduce your jogging issue in TWP mode.
I'm afraid I'm a bit at a loss as to how to troubleshoot this further.
 

Hi,
I was able to test this out a bit today and I've figured out it wasn't working because after setting the TWP, the G59 offset made the axis positions outside my soft limits,  I made my soft limits massive and it worked as expected.  If I have G54 zeroed out, then I don't get any values in G59, but my axis position are still outside the soft limits. 

I've been digging through the remap.py trying to figure out where the G59 offsets are coming from and I can see where it sets them around line 863, but I'm not sure how it's getting it's value.  It looks like it's passing the G54 offset value to to the twp-helper-comp.twp-ox-in correctly, but after that I'm not sure what to check.  Any idea what I should be looking for?

Some Testest with the Mesa 7c81 and 400W Servos:

www.youtube.com/shorts/KLijHrYiQXw

Board: eusurplus.com/index.php?route=product/product&product_id=131 + 5Axis-BOB
Servos: www.amazon.de/dp/B0DM5V6BZ2
Spindle: Huanyang VFD via Modbus