Advanced Search

So now I need to figure out the hardware side. I do have a dividing table with a chuck on it. Unfortunately it seems the gearing is not suitable 1:90 4 degrees per turn. 
so I guess I will be better off removing tha chuck and make a way to fit it on a shaft with bearings. The cam belt gears have a ratio of 1:4 which seems a bit small to me. 
will it work with a 100mm chuck and pipes up to 150mm 


 

Is that your chanel on youtube with the ESP MPG?
I'll be bothering you about that soon as i have a 3D printed MPG with a screen that Mesa7i73 does not use.
RMT will have to wait, limited time, but lately i am stuck at home/shops so maybe...

Hello All,
I am new to linuxcnc and i have been working through installation and getting etherCAT set up.
So far I have / had been sucessful with the basic install and getting Beckhoff units to function. and driving inputs / outputs.I purchased leadshine EL8 servo drives for a 2 axis project i am working on.
Creating my own .xml and .hal i was able to get by beckhoff units into "operational" and the EL8 Drives into "pre-operational," but that was as far as i could get.in the past days i have lost my way (probably with a lack of understanding of fundamentals), and I caved into trying other online .xml examples and got everything in a total mess and couldn't even get back to LinuxCNC to open.I have got my files back to the basic situation of LinuxCNC opening and everything working, but the drives are not going into operational state. i belive its my .hal file. but if i add any cia402 links everything stops working.Is it wrong for me to expect I can make one drive work in LinuxCNC first  ? (say the x axis) then add the y axis later ? i was thinking the homing was stopping the drives from going into operational for a time.this is my situation:~$ ethercat slaves
0  0:0  OP     +  EK1100 EtherCAT-Koppler (2A E-Bus)
1  0:1  OP     +  EL1008 8Ch. Dig. Input 24V, 3ms
2  0:2  OP     +  EL1008 8Ch. Dig. Input 24V, 3ms
3  0:3  OP     +  EL2004 4K. Dig. Ausgang 24V, 0.5A
4  0:4  PREOP  +  L8EC(COE)I have attched 3 files1)axis_mm-try2.ini
  2)TRY.hal
  3)ethercat-config.xml
 

@Kworm,

I think the current code is able to setup connections for input's and output's for all kind of ethercat devices.
Not all data type's are integrated yet. 1,8,16,64 bit data type is integrated. But there are more types.

It's just following a digital "ethercat xml" structure. From there it creates pdo's. The actual xml structure in
the core code is a complexer struct :

~/realtime_app/src/vendor/ethercat_master/tool/common.h

It setup's 1 bit, 8 bit, 16 bit, 64 bit value's and start adress for input and outputs.
There is no typical driver code for a certain servo drive.

If code is expanded, it can match a xml product code to use a certain servo driver setup.  This is
like linuxcnc-ethercat

If i had a servo here, i certainly would test it out.

My goal so far was to be able to interact with ethercat-master using a auto configurator.
This was quite a bit off work to get that done.
In that process i got some insights how automate this process for linuxcnc.


 

As far as the slug dropping or crossing the kerf, the arc voltage can spike, but it will never pass the limitiations of the plasma it self. The plasma has a maximum power it can output . Example the a maxpro200 can output 33kW, if you cut with 200A, the voltage can go only so high before the plasma hits its limit.

Umm no.

That assumes that the plasma output has no series inductance or parallel capacitance. This is far from the case. The problem is that the arc starts and stops at nanosecond rates, generating voltage and current spikes far in excess of the plasma power supply ratings.

Thank you, I had indeed forgotten to do this.

Even stranger, when I run the script by hand, the log file fills up, but this isn't really interesting because in this situation everything works correctly. But when it's run automatically, the log file remains empty.

I have built them form the source withbut it has behaviour same same... after
but when I change toand didit immediately works

it looks like it does not have disabled generic driver and still using it

regards

All things both of you said are true. But if you use the already divided voltage the requirements are much smaller.

For the ohmic sensing its even worse than electrode to work. I have scoped about +/- 3kV in one plasma during HF (this being in the MHz range).

I have seen multiple plasmas around the world having just a normal beckhoff analog input taken from the already divided arc voltage.

As far as the slug dropping or crossing the kerf, the arc voltage can spike, but it will never pass the limitiations of the plasma it self. The plasma has a maximum power it can output . Example the a maxpro200 can output 33kW, if you cut with 200A, the voltage can go only so high before the plasma hits its limit.
Its ok to put safety measures but if you compare reading the direct raw arc voltage or the divided one, these are 2 different things.
I would assume an OP amp used as a buffer rated example +/- 36V is more than enough for example divider ratio 30.

Does the included simulation config work?
'configs/sim/touchy/touchy.ini'

S3 cores ran on the 240meg and compiled -o2 is pleeeenty sufficient (my fav silicon of them all in fact). The P4 is very much overkill here, but hey, who doesn't like overkill anything lol ps.150hz is nothing for a S3. That makes both the S3 and P4 overkill in that sense

On the MCU Motion Control rant; and If I'd be any of you MCU experts, I'd get a RMT based driver working on 1 (one) motor to begin with, and before doing/coding anything else, have that comm and feedback 110% reliably with the Lcnc comm driver **mutex'ed**.

Once that's sold and a certainty, move to the next step (channel array!)

maybe writing the terminal output to a file could provide some clues

GTK warnings, probably due to new versions using GTK3 instead of GTK2.

I like my linuxcnc machine to be ready automatically. The session opens automatically and launches a little script that waits a few seconds, launches my linuxcnc config and offers to shut down the system when I leave the linuxcnc interface.

This script works very well, even on another machine at work. But I'm having a little problem with a custom embedded tab in place of the cooling buttons I use to control my dust collector.

When I run my config by hand, it usually displays correctly, but with autostart, my button is missing. Even without using my little script or extending the delay.

It's a LinuxCNC ISO that's a bit old (maybe two years) but updated, so maybe that's the problem, because at work, on a machine where I've used a more recent ISO, I don't have any problems.

My current LinuxCNC version: 2.9.3
GMOCCAPY: 3.4.8

I've attached my script, my ini file and two screenshots

It's quite strange. But it doesn't matter.
I'm curious to know what could be the problem.
Thanks

P4 was not found on amazon.de so S3 it was.
Had a play with this earlier today, Wez's version fails to set networking for some reason on ESP32wroom module, the other version someone linked here does work but suffers from random reboot loops, a lot.
I am after something else here, use an ESP32 as it has 12 bit ADC to measure the arc voltage and turn the torch on, mounted on the plasma source, and another module connected to PC to translate those voltage values to pulses with variable frequency.
Should be doable and have good enough latency for about 50-150 updates per second. It they survive the EMI

Hello CNC'ersGreat forum all, many many questions already answered !Many thanks..however....Am trying to configure Linxcnc using Touchy UI.I keep hitting the same error, see attached report.If I switch the UI to Axis in the ini file, it starts no problem.I've searched on the forum but there is surprisingly little on Touchy and seemingly nothing for the warning the report gives.I'm using a stock OS Linuxcnc image for the RPI 4B with a Mesa7i96s, nothing convoluted. Debian 12/Linuxcnc2.9.1All advice welcome !!