Advanced Search

Thanks, I'll give it a try.

The ethercat thread and linuxcnc thread should be the same, On startup, the 2 thread synchronise. If you use the ethercat drivers on the linuxcnc-ethercat github page, this has been improved with changes to linuxcnc and the ethercat master to improve this sync. You probably need master to get these changes.

rubes wrote:

that is what everyone gas been telling me (the part about home_ignore_limits). that other line i dont understand because i am not a HAL programmer. but there is probly several ways to accomplish this. if your one line per axis accomplishes the same thing, it is certainly more elegant and efficient.
 

Personally, I like writing statements on separate lines. I find its easier to understand and maintain

Is it a Pi5 or 4b? the 4b was always a bit marginal but some say the 5 is flawless for them.

You could try the Respberry way perhaps. Once you get the RT kernel sorted, just compile linuxcnc

forums.raspberrypi.com/viewtopic.php?t=396623

new driver plugin: TMC5160 via SPI:

www.youtube.com/shorts/DlIHY1Iy-ZQ

I don’t really like AI, but I do give it a go every now and then.
But this time I have to admit that gpt-5.6-sol-xhigh
did a pretty good job of it; it understood how a Rio plugin is structured and also generated the Verilog code quite neatly.
So this is the first plugin I’ve created with the help of AI.
I’d had the drivers for a while, but I was always too lazy

The tricky bit here was realising that, although the drivers use SPI (for configuration), they can’t be controlled via SPI.
To do that, you have to re-solder a tiny resistor on the back – not much fun.
So if you’re going to do this, get a board with the right jumpers for SD mode and SPI mode.

Wow, ambitious, looking forward to seeing your results.

Thankyou for your contributions.

New TP2 shall have 9 axis look ahead, we are working on a different base source, i can't share a work in progress, I will be porting later, still working out feed override spikes at the moment, and thinking about remaking the TP base completely.

For multiaxis, I started also on porting and improving G12.1 (switchkins from rushabhGH), and I'm juggling with an idea to have tool length be something adjacent to a virtual axis, and if those are in place, have the proper axis limits be derived from joints + current kins + current tool

Time will tell...

sounds like graphics drivers likely loaded just fine

Have you made any edits to the file /etc/lightdm/lightdm.conf yet?

Something I think to try, before running startx:
sudo systemctl status display-manager --no-pager -l
and
systemctl status lightdm --no-pager -l
If you can, snap a good photo of each command's result and post here that will save you lots of typing.

right .... oops

5280 wrote:

Kernel driver in use 1915
Kernel modules: 1915

I think got it all typed right.

Almost, it is i915.

The 2nd reply from the program in terminal is the same.

the reply is :

00:02:0 VGA compatible controller (0300): Intel Corporation Haswell-ULT Integrated Graphics Controller (8086:0a16) (rev 09)
Subsystem: Dell Device (1028:05ec)
Kernel driver in use 1915
Kernel modules: 1915

I think got it all typed right.

Again THANK YOU for all the help.

My GladeVCP panel fails to launch intermittently. The only errors that are found in the report are:
GladeVCP.QTVCP.QT_ISTAT][^[[33mWARNING^[[0m]  INI Parsing Error, No MIN_SPINDLE_0_OVERRIDE Entry in DISPLAY, Using: 0.5 (qt_istat.py:532)
**** GLADE VCP ERROR:    With xml file: crosshair_panel.glade : 'gi.repository.Gtk' object has no attribute 'glade'

and:

crosshair_panel.hal:7: Pin 'crosshair_panel.crosshair-ctl-active' does not exist

The second error is thrown because the panel fails to launch.  The reference to the pin is in my postgui_hal file.

How do I diagnose and repair this issue.

Regards,

Ok, graphical.target is correct. This tells me it is configured to start to graphical, but apparently something is breaking it.

Lets try:
(run this before startx, then let me know what it answered:)
sudo lspci -nnk | grep -A 3 -i vga

maybe also run it again in a terminal after you ran startx and see if anything changed.

  I'm automating a parallel lathe with a 9-speed gearbox selected manually using two levers, each with 3 positions: lever 1 has positions A, B, and C, and lever 2 has positions D, E, and F. The possible combinations are as follows:   Direction changes are achieved by activating two electromagnetic clutches.This gives me the following truth table: I'm using the gearchange component for up to 32 speeds created by Andy Pugh, which can be used in this case. The first problem I encountered was creating the logic to detect these combinations, as I needed to detect the positions of the 6 switches I'm going to install to control the lever positions. Of the 6 bits, two will always be true. The component I found and was able to use was LUT5, but the problem is that it's only valid for 5 bits, and there are 3 combinations where bit 5 is one. Therefore, for these 3 combinations, in addition to LUT5, I had to use an additional AND2 gate to detect them.I read on the forum that for some automatic gear shifters, like the Maho MH400E, they created a component with an array that detects each gear by the switch positions.I also used the generic mux component to identify which gear was selected using a number between 1 and 9. Since it's 9 bits, it gave me a combination of 512, of which I only used 9 so that the mux output was a number between 1 and 9.I don't know if there's another way to detect the switch combination for the two levers.I've attached my HAL file to detect each lever position so I can send the correct speed to the VFD.