Advanced Search

I would probably get a working xyz Ethercat config with axis.
Then I would use pncconf to build a qtplasmac config then merge them together by hand

You will need to work out how to sense torch voltage. I would look for an Ethercat module that sensed analog voltage.
This has been done in the past but it was before QTplasmac.

The mode can be automatically selected based on voltage sensed. You know at startup its not cutting, start in hypersensing mode but if the voltage exceeds 24 volts, calibrate to THC range and stay there until it falls to say < 5 volts, go back to hypersensing mode.

Yes will need 2 factors one for the arc voltage and one for the Hypersensing, also the QtplasmaC need to change from THC to Hypersensing Mode.
 

Aciera would you like to be a moderator?

JT

Do you happen to have any PC, even 10 or 15 year old will do?
Sorry i am no help, but i really do not like RPI, it is way to much trouble for nothing.

I had bad experience with capital letters in naming of subroutines.
try a lovercase 'o'

O<safe-go-home> sub

Well unfortunately, I have not been able to reproduce this.

Using your maho_vfd.mod example either with a running
LinuxCNC instance or your hal script I get all stepgens fb positions
= 0 and stable (or running as expected under LinuxCNC)

This is with LinuxCNC 2.9.3, but I don't think the have been any
mesa modbus changes between 2.92 and 2.93 (last mesa modbus
change was in Sept 2023, and 2.92 was released in Dec 2023)

Edit: There's definitely a loose wire in mesa modbus because if I change your script

to: 

#loadrt hm2_eth board_ip="10.10.10.10" config="num_stepgens=5" # This causes jumps in hm2_7i95.0.stepgen.00.position-fb
loadrt hm2_eth board_ip="10.10.10.10" # This appears to work without issues

I get a segv!


 

Help.
I'm no linux guru and I'm having trouble finding an installation path the gives me a working system with connection Pi to the Mesa card.
By background I'm a retired electronic engineer turned C++ programmer doing large models and I actually worked for Hitachi Seiki years back until they died.
I have added steppers to a bench top milling machine and I really hoped to get LinuxCNC running on it.
I bought a Pi-5 with an NVMe hat which runs fast and a Mesa 7i95T to do the heavy lifting,
I tried the Pi-5 system image from this site but I can't get it to Ethernet into the Mesa.
I can't get a lot of the Pi commands to work to control the NVMe or the networking although they work on the 'standard' image.
I'm confused as can be and google gives me contradictory sites that often give me command that don't run or generic instructions that I can't trace to concrete things to try.

Is there an ELI5 guide somewhere, or do I have to give up on my current hardware and do it another way? If so what?

Yes I have had done it ... I will post them tomorrow ... Take an inspiration from them there will be a ET200B from siemens, keb f5 vfd and kollmorgen s343... But... I am out of shop today .. family stuff

Regards

forum.linuxcnc.org/18-computer/44828-rem...board?start=0#231852

Hi endian, Thanks for your answers. I'll try to follow your advices. Another question: How do I setup the SDOs. Do you have some hints for me?
BR Franz

Hello!
I'll try to flash remora firmware for my new board, but how do you know which pins are the SWCLK, SWDIO? I suppose the bottom one is the GND.

Bari wrote:

linuxgizmos.com/updated-wiznet-reveals-n...ernet-functionality/

Raspberry Pi RP2350 and the fully hardwired TCP/IP controller W5500 enhancing the capabilities of the traditional Raspberry Pi Pico2 board with additional Ethernet functionality via W5500

Thanks, just ordered one with GoFundMe contributions.

meister wrote:

if i have overlooked any open questions, please ask again, i was a bit busy at the weekend and lost the thread

---

here is my excuse:mitsubishi rv-e2 

 

without controller and one harmonic drive is broken
 

I approve of this excuse!

Quick question about the iceshield config:

Should the pi be emitting 18mHz, rather than 5mhz via pin 7 instead, since the oscillator is configured as 18mhz on pin 35 on the up5k? I wonder if this is the source of my following error at higher speeds?

I don't think the contractor is required as the hypersensing circuit is impervious to high voltage.
Currently when the voltage exceeds 24 volts, the component is seeing an arc voltage and it never breaks now. The thcad always sees a bit past the full scale and the 390k resistor sets full scale to 23.5 volts anyway.

So what if you mux the  THCAD calibration instead? once it is > 24 volts, recalibrate it to be fullscale 200 or 300 volts?