Advanced Search

It turned out there *was* a G52/G92 offset, with a Z value of -4.038x when I looked at it. And at that point touching off with my 4" master tool in the spindle resulted in a tool length of 8.038x. I edited my vars file and manually zeroed out the G52 offset, and then things started behaving. Offsets are new to me and I wasn't familiar with those or how they are stored in the file.

So, my tool setter now appears to work, repeating to +/-0.0001 or so. Time to break everything by upgrading... 

Thanks for your help andypugh and Lcvette!

Well I attached the histogram..I really donot understand it..is it acceptable for linuxcnc?

And one new issue arises. The computer getting restarted automatically while LCNC is running. I have noticed the monitor goes blank first and then system shuts down/ restarts. Any clue, why?

last thing I printed was a mounting thing to use a linear scale for adjusting the Z-Offset when moving the column



with printing you can make it big to get it rigid

Thinking more about it...
If your gladevcp panel does not have gremlin object in it, you will not get gcode properties generated in that pythons context.

I would lean to ethercat as well. Delta ethercat options are only nominally more expensive than step/dir models. Likewise lichuan (although they seem to have some setup quirks to get around).

Z on these machines is the ram, it is a horizontal axis.

thinking about how to solve the problem to conveniently adjust the Z offset when moving the column, just using linear scales als I always wanted was the easiest solution in the end.
So i skipped the manual part. Bought some scales and printed which did fit in the ode mounts for the pointer. Just added a third boost spaced with water for stiffness.



I can set the encoder position by M_code which I only need when I move the column without linucnc active. Which will almost never happen. Cause unlocking the column without the hydraulic as a real pain. The position is made persistent by ustoring it in a parameter.

youtube.com/shorts/wv0c47Jk_JA

I also can now move the column to a fixed or relative position.
While the lowest preset position can't be traveled over. This way I can prevent collisions when using big setups.
Same for the highest.

the preset heights are now set by the scale and stored and loaded in the VCP parameters hals analog outs als Hal lcd widgets. Only downside they are not updated until used once.
but that's fine.

From hal_glib.py:

Specifically ignores loading with the same filename (reloading)
I'll have to dig a bit to comment about gcode-properties - just off to work

Chris

What version of linuxcnc are you running?

I cannot reproduce this on my side. Do you get this behavior using a simulation or only on real hardware?

sorry but I'm not very capable so I ask. I installed mesaflash, copied the script into the folder renaming the text file with "stepgend.txt",
From the terminal I entered mesaflash and typed "sudo mesaflash" to then call the script. I have no apparent result, if I measure the voltages on the pins they are fixed and nothing changes. the ip address of my card from linuxcnc file is 10.10.10.10. what am I doing wrong?


andrea@debian:~$ cd mesaflash
andrea@debian:~/mesaflash$ sudo mesaflash
[sudo] password di andrea: 
Mesaflash version 3.5.9
Configuration and diagnostic tool for Mesa Electronics PCI(E)/ETH/EPP/USB/SPI boards
Try 'mesaflash --help' for more information
andrea@debian:~/mesaflash$ chmod +x stepgens.txt
andrea@debian:~/mesaflash$ chmod +x stepgens.txt

Here's a video showing the safety features of Flex GUI when probing is enabled.


JT

I am working on a 5-axis cnc machine and when playing around in the kinematics I encountered a strange issue where when I am working in the TCP and go from MDI to manual control the joint position changes example:
MDI :-
X=150 Y=0 Z=-75 A=0 B=10 degrees
switch to manual
MANUAL:-
X=152.353 Y=0 Z=-76.232 A=0 B=10 degrees

I initially chalked it up to it being an error in my kinematics but when I tried to do a similar maneuver with the '5-axis table dual rotary' machine that comes preinstalled with linuxcnc I faced the same problem.

is there anyone experiencing this issue as well? any help is highly appreciated

Here's a short video showing how probing is setup and used  and the example is in the Flex GUI examples.


The documents page for probe are here .

JT

bentiggin wrote:

I just went through and changed all the joint 0 to joint 1 and joint 1 to joint 0.
That seems to make it work. I don't think qtplasmac is ok with y being joint 0 and x being joint 1.

This is OK in theory, but is likely to cause confusion. 

It is possible that the behaviour you see is because you are jogging before homing. (In so-called "joint mode"). This bypasses kinematics. Depending on how you are jogging this may map X to joint 0 and Y to joint 1. Keyboard jogging in the GUIs will tend to do this, but if you are button-jogging through HAL this would just suggest that the HAL connections are wrongly allocated. 

If this is what is happening you will see the XY swap before homing then it will do what you expect after homing. Which is probably a situation worth avoiding. 

For a new servo setup, I would go ethercat servos.
Sell the Mesa board (there is plenty of demand for Mesa).

I would only buy servos with software available for setting parameters and tuning.
Setting multiple parameters with the few buttons on the drive is awful.