Advanced Search

I'm not feeling authoritive here but Debian Bookworm split the earlier non-free  into non-free (not in the default) and non-free-firmware (included in the default). We include non-free in our apt sources but I don't know if the installer refers to that as it runs.

When I faced this earlier with the Odroid H3+, I had to install Debian without  a network driver and install it after installation and run the NIC installer. This will set your /etc/apt/sources.list to only use a CDROM so it will need editing to be something like this
 

This is Summer from Facebook.
I am still reading and researching everything I need to know to get my ATC and rack toolchanger setup.
I installed PB but the instructions suggest having your machine as set up as possible before converting over to PB. I have basically everything I want set up on the machine aside from ATC and that is all set up on the hardware and electrical side so the only things left to do are to get automatic toolchanges set up and my tool setter doing what I want to set tool offsets for the racked tools.

I am stoked to see this all being developed right now and I like that there are some things like being able to set up tool positions in the UI and things like that.
So I'm thinking maybe I should just do the switchover.

In a previous post you said the parameters are saved in the .var file. I am still learning all this but I assume this means they are stored per typical standards in a way where any typical or other UI documentation, examples, etc, will apply, and or is UI independent correct? This just kind of gives a parameter box in the UI to enter information that I would otherwise be entering in the .var file directly yeah?

Well now I'm stuck. its asking for non free intel drivers. I put them on a usb stick but linuxcnc installer cant find them. I'm sure ive done something simple wrong here, but i dont see it.

Samba (SMB) is pretty easy to install. Just set it up to share your home folder. Plenty of online tutorials
The sneaky bit is by default Windows disables access and you have to change a policy to enable it.
I like to map a share to my Linuxcnc home folder on a windows box so you can save gcode straight to the ~/linuxcnc/gcode folder from Fusion360 and Sheetcam.

Lcvette wrote:

@rodw, I haven't checked recently, but the iso had an old qtpyvcp source listed that causes some issues and requires removed to resolve. We updated the instructions to use the lockdown deb on the forum page as it doesn't have the outdated source.

If we are not told or an issue raised, it won't have changed.
You can send your pull request with changes to the qtpyvcp files in this folder in the installer
github.com/LinuxCNC/linuxcnc-live-build/...worm/config/archives

 

I am using Octopus Pro board with remora-spi. Can you help me with working TMC5160 (stepsticks) drivers. Previously I used TMC5160 with tinybee board flashed with FluidNC in daisy chain config, they were working fine.

Gui related pins (ie gmoccapy and pyvcp related pins) do not exist until the gui has loaded. So you need to put those hal connections into the postgui halfile.

Ah cool thanks.
my screen res is 1680x1050 right now (old cinema display) and my panel screen is 2k, 4:3. I'd rather not buy a new screen for any of this.

I'm installing linuxcnc 2.9.4 now.

I got mine set up using axis and then moved to TTS repeatable tooling and  went to QT Dragon because I could not get probe basic working on my hardware. Then I found none of the QTdragon screens worked for my 16" monitor so upgraded to a 16"  1080p monitor. It has probing and ATC. The manual tool change works well.
Don't Google, Its all well documented in the Linuxcnc docs.