Advanced Search

A lot has changed in LatheEasyStep over the past few weeks. Much of the work has focused on further improving the existing machining functions and making the generated toolpaths more reliable.In particular, internal machining has been significantly revised. Internal contours can now be processed regardless of the Z direction in which the contour was originally defined. Roughing and finishing have been corrected accordingly, and the approach and retract movements for internal machining have also been revised.There have also been several improvements to contour machining. G1/G2/G3 geometry is now preserved more consistently, so arcs are no longer unnecessarily converted into straight-line segments. Relief grooves have also been further improved, including the automatic positioning of DIN 76 thread reliefs at the actual end of the thread.The handling of tool changes, retracts and safety movements has been revised in several areas. The same applies to switching between G96 and G97, as well as various plausibility checks intended to detect invalid or unreasonable inputs before G-code is generated.The preview has also received further work. The side view, front view and cross-sectional view have been revised, and the representation of the different machining operations has been made more consistent.Another improvement that is clearly noticeable in everyday use is the panel startup time. At one point, startup took more than 20 seconds. The initialization process has since been revised, and tasks that are not immediately required are now performed only when needed. As a result, the panel now starts significantly faster.The user interface and language system have also been further revised. In addition to German and English, Spanish is now fully available. All visible text is managed through external language files, allowing additional languages to be added without modifying the program code.The current development branch is now 0.8.0-dev. For the 0.8.0 release, only a few targeted acceptance checks remain, including facing with a radius and final checks for internal machining and the DIN 76 thread relief.After that, 0.8.0 is intended to provide a defined state of the existing machining functions before development continues towards 0.9.0.

MeetAgree.com
Choose your companion for the evening

<a href=https://MeetAgree.com> She's ready to have a good time

Not a LinuxCNC install. Same class of box as the earlier J1900 eglfs vs Xorg thread.Posting because the useful knob was not another kernel cmdline flag.
Intel Celeron J1900 has 2 MiB L2 as two 1 MiB slices:
CPUs 0-1 share one L2
CPUs 2-3 share the other L2
We already isolated the EtherCAT loop on CPU3 (SCHED_FIFO 80, 1 kHz).
That is not enough if the fullscreen Qt/eglfs HMI is still allowed on CPU2.
The UI then sits on the L2 sibling of the RT core and contends for the same 1 MiB.
Change (HMI only, not a whole-system cgroup):
before: Qt main / touch / QML / render / GPU worker allowed on CPUs 0-2
after: those threads allowed on CPUs 0-1 only
RT thread stayed on CPU3 both times
Same binary, same recipe, same 1 ms period, 20 automatic press cycles each side.
Jitter = wake-to-wake CLOCK_MONOTONIC minus 1 ms, integer microseconds.
0 us means |error| < 1 us. This is period error, not latency-test / cyclictest.
All numbers below are the full captures (approach + press + retract), not a PID subset.
Absolute jitter, nearest-rank, all samples
UI on 0-2 (20 runs) UI on 0-1 (20 runs)
n 119159 119254
P50 0 us 0 us
P95 6 us 1 us
P99 13 us 1 us
P99.9 21 us 2 us
signed min/max -42 / +46 us -13 / +14 us
|j| >= 10 us 2983 8
|j| >= 20 us 198 0
|j| >= 30 us 22 0
|j|
Per-run P50 / P95 / P99 / P99.9 (|jitter|, us)
# UI 0-2 UI 0-1
1 1 / 9 / 14 / 23 0 / 1 / 1 / 2
2 0 / 2 / 9 / 19 0 / 1 / 1 / 2
3 0 / 5 / 12 / 21 0 / 1 / 1 / 2
4 0 / 6 / 15 / 20 0 / 1 / 1 / 2
5 0 / 7 / 15 / 20 0 / 1 / 1 / 2
6 0 / 1 / 1 / 2 0 / 1 / 1 / 2
7 0 / 6 / 14 / 20 0 / 1 / 1 / 2
8 0 / 7 / 15 / 20 0 / 1 / 1 / 2
9 0 / 4 / 13 / 19 0 / 1 / 1 / 2
10 0 / 6 / 16 / 26 0 / 1 / 1 / 2
11 0 / 3 / 11 / 22 0 / 1 / 1 / 3
12 1 / 9 / 15 / 23 0 / 1 / 1 / 2
13 1 / 9 / 14 / 26 0 / 1 / 1 / 2
14 1 / 9 / 15 / 32 0 / 1 / 1 / 2
15 0 / 8 / 14 / 19 0 / 1 / 1 / 2
16 1 / 9 / 14 / 26 0 / 1 / 1 / 2
17 0 / 1 / 6 / 13 0 / 1 / 1 / 2
18 0 / 6 / 13 / 19 0 / 1 / 1 / 2
19 0 / 1 / 5 / 15 0 / 1 / 1 / 2
20 0 / 1 / 1 / 2 0 / 1 / 1 / 2
After the pin, every run has P99 = 1 us. 15/20 runs have max |j|
The 8 remaining >=10 us samples are two ticks each in runs 1, 8, 15, 16.
Point of the numbers
- P50 was already 0 us. The HMI was not ruining the median.
- The L2 sibling shows up in the tail: P95 6->1, P99 13->1, P99.9 21->2.
- Moving i915 IRQ off CPU2 was not sufficient by itself. User-space Qt
render can still land on CPU2 and thrash the RT core's L2.
- Do not set a cgroup AllowedCPUs=0-1 on the whole process: the FIFO
thread must still be able to bind to CPU3.
- Do not park every system thread on 0-1. This was only the HMI/render path.
Box (for context, not the variable under test)
- Debian 13 PREEMPT_RT 6.12, Qt eglfs_kms, no X
- IgH EtherCAT, 1 kHz, Lost frames = 0
- isolcpus / rcu_nocbs on CPU3, i915 IRQ on CPU0
Happy to hear if anyone running a GL HMI on Bay Trail saw the same
CPU2/CPU3 L2 pairing.

I just updated to the latest probe basic (Probe Basic APT Stable Install Bookworm 12).  I do not use an ATC.  Everything is working as it was before the update except I get this error (Error Named parameter #<number_of_pockets> not defined ) when trying to load a tool utilizing the Tool Change Panel (load tool).If I load a tool from the main screen it works fine.  I can even use the Tool change panel to unload the tool.  I have looked through my ini file and cannot see anything out of place.  Any suggestions on where to start looking would be appreciated.

I've encountered this bug many times. Thanks for posting.

Will do

A better solution should be to submit your changes to LinuxCNC as a PR.

I would upgrade to 2.9.10 and see if it persists.
If it does, learn how to do a run in place install of master branch 2.10pre and try there.
Then, post as an issue on GitHub where it will be reviewed but the devs. 

If the G540 is connected to the 7I96S parallel expansion connector, you should use
7i96s_g540d.bin firmware, that configures the 7I96S's P2 expansion connector the G540
pinout, Then basic setup can be done with pncconf. No need for AI, that just a time sink here.

You're welcome.

Once you are setup, it relatively easy to make a new configuration in a few minutes.

Спасибо за помощь. Всё получилось, сначала залил вашу прошивку, потом решил для пробы изменить пару пинов и скомпилировать новый bit - успешно, загрузил и запустил LinuxCNC - работает. Ещё раз спасибо!!!

How is the Mesa wired to G540?

I made a diff with the latest hal.cc from Github and got a 43 kB patch...
Can you make a patch from your sources?
 

Hello Folks Newbe here.

I mistakenly though I could easily convert my Shark SD120 to a Linuxcnc setup using a Mesa 7i96s to a Gecko g540. After hours of fooling with it and being misled by AI I now realize there is no easy way to setup the HAL and INI configs. I purchased the hardware and would like to make it work so any help would be greatly appreciated.

Thanks,
Doug
 

That's basically correct:

1. Add new pinout file to project (seveni98.xise in this case)
2. Select proper card and desired pinout file in top level file (TopEthernet16HostMot2.vhd in this case)
3. Recompile
4. Rename created bit file (TopEthernetHostMot2.bit in this case)  to desired final name.