Advanced Search

I’m aware of how it’s _supposed_ to work, my question is what I’m doing wrong in my configs that make halui not expose mdi-command-00 etc pins despite the presence of MDI_COMMAND entries in the [HALUI] INI section, and HALUI=halui in the [HAL] section?

Hello all,

I'm a basic user of LCNC - I know it reasonably well, but don't use a tool changer, only have a basic through tool Z probe which gets occasional use - you get the idea: my set-up is pretty rudimentary but I get good results and productive use out of the software.

When I need to find the centre of a circular feature I've been touching a dowel off at three points around a circumference (fag paper or multimeter method) and feeding three sets of X,Y coordinates into a spreadsheet which then works out the centre for me, like so:





Here's the sheet in OpenOffice format.

It works, but I was wondering if there was a way to incorporate a simple centre finder tab into the interface, something that would look a little like this:

 

The first three buttons to touch off the three positions on the circumference and the 'FIND CENTRE' button to perform four ops:

Calculate the X,Y centre coordinates
Lift the Z axis to its G53 0
Move to the calculated X,Y centre
Set G54 (or current WCS) X,Y to 0,0

So I guess there would need to be six variables that get written using date from 'current position' numbered parameters #5420 & #5421

POSA_X
POSA_Y
POSB_X
POSB_Y
POSC_X
POSC_Y

And then the two calculated variables that are used in a subroutine to lift and move the spindle to the centre and zero out X,Y at the new position

CNTR_X
CNTR_Y

I get that this is still clunkier than using a probe, but I honestly have little need for one!  If I have to keep punching the numbers into the spreadsheet then that's fine, but to have this in a tab would be cool.  Am I thinking about this in the right way?

How would you tackle it?

Many thanks.

Wal.

If anyone stumbles on this looking for a solution I was able to work it out in hal using wcomp and some and, or, not components. Basically I used the wcomp to check the startup position from the last_position.txt file, then using a bit of funny logic I made it so after the joints hits the home switch in the positive direction, the wcomp keeps the home switch closed for the remainder of the positive direction travel, then in the negative direction I used the min wcomp output to disable the home switch input for the remainder of the negative travel. So the home switch only properly works in a narrow joint position range. With this setup the normal homing routine does exactly what I need. When the joint is in the positive direction it backs off until it's in the proper range and in the negative direction it ignores the physical switch until it's in the proper range. There's some silly logic with some and/or/not comps which I'm sure could be made more elegant, but it does work.

An MDI command can be executed by using halui.mdi-command-00
Here is an example showing how it 's done:

linuxcnc.org/docs/html/gui/halui.html
 

I found a few lpf files.. like the one litex generates, and the one here:
github.com/ZeroMips/Colorlight-5A-75B-gp.../master/gpiotest.lpf

However, when I program the bitstream, it doesn't seem to be doing anything. Even a simple led blink. 

Opening the lpf in Lattice Diamond, I notice that these lpf files show errors in the spreadsheet view.. so I think Lattice is ignoring the pin assignments all together?

 

W8 must be down

To see the 5ABOB specific pinout:

mesaflash --device 7i96 --addr 10.10.10.10 --dbname3 5abob --readhmid

For posterity, I have managed to solve this by writing a little HAL component  that works by switching between OR and AND depending on whether the machine is over the tool setter with the touch probe loaded in the spindle. Feels a bit like redneck engineering, but hey, if it works it works.

There's also a simplistic probe crash protection, I was actually surprised when I wasn't able to find this feature elsewhere.

thank you for the help, I did a fresh install using the latest image and got mesaflash to work, the proper firmware is now on the board.

I have a few more questions before I fry my card

when connecting the bob o the 7i96 in what position should W8 be?

what is the correct adress for the P1/PWM pin on the bob?

Thanks!!! Not sure how I could have missed that one. I posted something right after it, but my focus back then was on Trixie, not on EtherCAT. I feel so stupid now Anyway, I'm sure I will get it fixed with that info. Again, thanks!

Hoping someone can point out the probably obvious error in my configs that is causing halui.mdi-command-NN pins not to be created.  The halui component loads and the rest of halui's normal pins show up in the HAL Configuration tree; in the [HAL] section I have the HALUI = halui line; I've made sure the [HALUI] section in the INI file exists and that there are MDI_COMMAND entries under that heading, but still no joy.  Can someone see what I've missed? 



Thanks.


 

Hi everyone. I know this topic has been covered before, but I would like a bit of advice specific to my machine as I'm not that well versed in LinuxCNC.

I've built a 5 axis rotating nutating (head-head) type CNC and it's been running well for the past 1.5-2 years. However, I'm getting quite slow feedrates on certain multi axis operations and it's becoming increasingly frustrating.

As an example, this image shows a test file where the X and Y axes barely move, the Z and A axes don't move, and it basically just rotates the C axis. At a specified feedrate of 4000mm/min, it's only cutting at about 600mm/min. My max velocity for linear axes is 25,000mm/min, and angular is 4500deg/min. Acceleration is relatively high, and 4000mm/min should be achievable.

 

I'm using Fusion for the CAM, and the above test file is using swarf machining. This can only be output as a bunch of small lines, so I've gone as coarse as possible with the tolerance and that's set at 0.1mm, and I'm using P0.1 Q0.1 for smoothing. And I'm using TCP.

Correct me if I'm wrong, but is the slowdown in the feedrate due to the 1 line lookahead in multi axis?

I have a separate LinuxCNC config setup to run my machine as a simulation, and it uses a different ini file to my machines so I can test files prior to running them. With this ini file I've bumped up the max velocity a bit, and really bumped up the acceleration, and I've been able to get the required 4000mm/min. However, these velocity and acceleration speeds are very unrealistic for my physical machine.

So my question is, is this just how LinuxCNC is? Or am I doing something wrong? Or is there a workaround for this issue? I've also tried using inverse time, but it gives me the same outcome as programmed feedrate. Let me know if there are any files I should post (ini, etc). Thanks.

Here's a couple of photos of my machine.

 

 

HP Z600 WorkStation
forum.linuxcnc.org/18-computer/57073-hp-...or-use-with-linuxcnc

OK more tests done, and frankly way to much for a day and a half, but sparing you of the long whinny road so here is a lowdown in no particular order:
-uses about 80W of power at idle with Linux Mint 22.1 running the 6.13 RT kernel, should use less with the normal kernel
-uses 350W of power while running FurMark and Blender Benchmark at the same time with GTX1060/6GB graphic card, so fully loaded
-plays 4K@60FPS youtube videos at 1.5X speed without dropping frames, BUT, hardware acceleration must be turned OFF in FireFox. This is also something i do on every new install as FireFox has dropped the ball badly there.
-6.13 RT kernel works with the included Nvidia cards with NO proprietary drivers installed, fails with black screen when drivers installed.
-6.13 RT kernel will not work (well it will, once, then black screen) with AMD RX580/8GB graphic card, normal kernel works perfectly. Not tested with proprietary ADM drivers, just the included Mesa drivers (not our Mesa/PCW )
-6.13 RT kernel works nicely with PCI to parallel port adapter, LinuxCNC finds the port and works perfectly, 50000 base period might cause latency warnings, did not test tuning of any kind.
-PC has only USB2.0, so an addon USB3.0 card should be the first thing to get
-PC has 2 of full X16 PCI-E slots, so perfect for "Home Lab" cramming in two graphic cards for media server, or NAS with a fast SAS controller although not much space for 3.5" HDD drives it might be possible to cram 16 of 2.5" SSD just in the DVD-ROM space
-has enough power supply to run all of the above at the same time
-does about 54 points in Blender Benchmark (pitiful as my R7 7700 does 322 points with temperature limited to 75 degrees C in BIOS !!!)
-Replacing CPU's might just be a good idea as they should be pretty cheap, like 10-20$ probably even less on aliexpress, have not checked, Xeon 5570 are 3.3GHz parts while the included Xeon 5530 are 2.4GHz parts, that is nearly 8 GHZ of difference in total, worth the money if i could find them here for one or two of them, so 2 or 4 CPU's ...
- ... i am out, it is 2:53AM here, need sleep...

Why are there 2 topics for the same machine by two different users located in the same country?
Are you two competing who fixes the machine first?

Why are there 2 topics for the same machine by two different users located in the same country?
Are you two competing who fixes the machine first?