Advanced Search

Yes. When I try to upgrade,I one part of the error message reads:  raspi-firmware: missing /boot/firmware, did you forget to mount it?.
I cannot post full message because the system clock is wrong so internet is not working.........

I'm using the physical keyboard keys to control jogging.

Checking halui.mode.is-manual = FALSE. I attempted to set it to TRUE but halshow reported that the parameter is not writable.

Is there a way to force this pin to be high?

Regards,

Sometimes a custom component simplifies your hal file. Here is my solution for a similar problem where there are two belts each with 4 positions. But because it's not possible for both belts to use the same position, it comes down to the same problem you have. For the ratios, I just ran the spindle on each belt combination and read the actual rpm with a cheap laser tacho and did some maths. But I did not have levers, and made a panel for qtdragon which Chris "borrowed" for the qtdragon docs.

github.com/rodw-au/vmnmillqt/blob/main/scalebelts.comp

Sean Drummond did a really nice diagram of a 7i96s which you can grab over at plasmaspider plasmaspider.com/viewtopic.php?p=231679#p231679 

If you want a diagram you can't go better. I usually just create a table of all the pins and where that go. Its better to do it in a word document rather than a spreadsheet so you can add more freeform text/

Update: I uninstalled Glade and then reinstalled it. The issue still persists.

The errors thrown during launch not reads:

tool_mmap_user(): tool mmap not available
poll(): continuing without tool mmap data
gtk-builder-error-quark: crosshair_panel.glade:12:34 Invalid property: HAL_Table.n-rows (11)
**** GLADE VCP ERROR: With xml file: crosshair_panel.glade : 'gi.repository.Gtk' object has no attribute 'glade'

when launched from the panel from the command line:

$ gladevcp crosshair_panel.glade

Maybe I need to reinstall linuxcnc?

Regards,

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.