Advanced Search

Yeah this seems like trading one problem for many more problems. haha.

I just need to figure out how to make it read this driver. can you not just stick it onto the installer usb like you do with windows drivers?

You could try installing Trixie CD  which is now in alpha release
www.debian.org/devel/debian-installer/
Once you sort out your network install linuxcnc from their repos
 sudo apt install linuxcnc-uspace linuxcnc-uspace-dev
This should also install PREEMPT_RT
This will get you a very late version of 2.9.3 which is basically the same as 2.9.4

Then to hook up the Ethercat repos, try this script
forum.linuxcnc.org/ethercat/53785-instal...thercat-repositories
and click through to the install instructions in that link

This could be a bit experimental as Trixie is using the 6.12 kernel which was not supported by etherlabmaster. But I raised an issue with them that should have fixed the issue 2 days ago.
gitlab.com/etherlab.org/ethercat/-/issues/160
 

BrysonW wrote:

Hello, this is a reply to beauxnez post from few days ago."hello, is it possible to make an nvem card work with qtplasmac?" The answer is yes, another friend and myself are right at the end of a plasma machine build, were using a ec500 as the controller and it works fantastic with qtplasmac. I will say the THC is the only thing that we don't have working at the moment. On ours the plasma output is just on output 1, torch is either on or off. It goes from the board and turns a relay on and off which is the actual switch. For ours we have a Everlast 82i for the plasma cutter which has a 50:1 voltage divider, that gives us a 0 - 5v output for the torch voltage but from my understanding there aren't any analog inputs on these boards. A analog to digital converter may be a option. I'm not sure what the output of the mesa THCAD boards looks like, there may be a way to use one of those. I'm just getting started on trying to setup a arduino to take the analog voltage, work some magic on it, and send the info to linuxcnc that way using modbus.  The downside I'm seeing to this approach is effectively I'm setting up a second controller to take just one analog input, and I'll have to put a switch inline on the ethernet cables.  The upside is another controller and analog input, so now I can dream up more features to add to this machine (During our build process it started as a basic machine, we now have individual limit switches for every axis, probing, etc. , touchscreen interface, and so on..) I saw that you managed to make a card work under remora with qtplasmacmy card now works with the 3 axes under axisI would now like to pass it under qtplasmac, you can help me because I have an error message 

I saw that you managed to make a card work under remora with qtplasmac
my card now works with the 3 axes under axis
I would now like to pass it under qtplasmac, I need help because I have an error message?

 
 
 
 

From my last go linuxcnc does no install correctly without the network first installed. But last time I got the non free one separate from linuxcnc and not the official one. I was hoping the official one would make this all just work smoothly, but noooo.

What I don't get is why it asks for a usb but then does not recognise it when i put it in.

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.

There was nothing wrong with my THCAD-300, I just switched to a divided voltage source from the new plasma cutter instead of the raw voltage from the older plasma source. By changing the input voltage for the THCAD I would get better resolution with my divided voltage source signal.

If you are ramping the spindle speed you cannot use the PWM enable in the same way.
The PWM enable and 7I78 enable pin need to be driven by something like machine-on
in this case.