Advanced Search

Thank you again.

I struggle with the configuration
If I understand well I need to adapt this line in my Hal file but can't figure what should I put?

net xindex-enable axis.0.index-enable <=> hm2_7i96s ???
I connected my index on i/o 36 (P1)
Thank you for your help

kworm wrote:

@Grotius,

I was suggesting you would need ESI support if you wanted to be able to avoid having to have special code for specific devices like linuxcnc-ethercat does. Ie, if you were wanting it to work something like twincat or other commercial products do.

@Endian,

Have you seen any issues on ethercat with the current position dropping to zero intermittently...noticed on the DRO? I've been attempting to use LCNC on a machine that has G1 acceleration of 1m/s and G0 acceleration of 3m/s (feed is 25-50m/min) and I keep getting following errors.

Which mode U are running? If U run them in the

• CSP - U have to tune your servos for your application ...
• CSV - U have to tune your PIDs and servos too for your appication ...

For ethercat control is lcnc only a trajectory planner such as realtime "position sender" where to go and all control stuff as positioning corrections accel. and deccel. or velocity servo calculates internally ... they are 1st and 2nd derivations of position and ethercat interface of servo has tools to calculate them..

bdw .. I have stuff which has this control loop at 250us but should be faster as siemens DriveCliq S120 drivers which are running at 31.25us

Gentelmen, my bad...

I have 4 ethernet interfaces ... 3 are e1000e and 1 is igb hardware .....

can you guess on which hardware I want to install e1000e driver...

life is life..

Thanks for pushing me

 

probably possible, here are a few rpi/ i2c driver samples i have saved 

github.com/bosston88/LinuxCNCRPi/blob/ma...hive/i2c%20example.c
github.com/bosston88/LinuxCNCRPi/blob/master/mcp3421.c
github.com/bosston88/LinuxCNCRPi/blob/master/si7021.c
github.com/thgerner/hal_mcp23017

yeah 1024x 600 or 768 is not large enough for axis
check out my thing if you want a small screen axis and report any bugs . ive been using it for a while and i havent seen anything unsafe
github.com/cakeslob/regularmac_800

royka wrote:

@rodw Can you confirm that it's the same with the Raspberry or is that kernel source already patched?
 

Sorry, I have no Idea. I don't have a Pi5.
Did you find the code Linuxcnc uses for this check in Git?
 

I also use a table. I always update the table before connecting a new wire.
 
 

From your dump, is there a typo in your MAC address?

Not yet, everything is at default for now, and it works OK (i have a topic about laptops i tested working with LinuxCNC), so a bit more tweaking should push them to being very good, hopefully.
I am using a Lenovo T470 for over a year on a production machine, ocasional latench warning, but usually goes for hours just fine, and never ever shows warnings when servo period is at 2 million, just adding isolcpus should get rid of that warning, but i did not bother as only i use it.
I will be doing more tests with them and report back on the topic
forum.linuxcnc.org/18-computer/54369-use...mesa-ethernet-boards

Sorry, should have set check resistance from the cnc output to work clamp

I would stick to the thcad-2 with a scaling resistor. I can't really see a use case for the thcad-300
Please use a seperate 48v 7-10 amp power supply for motors.  24 v is waaay underpowered
Meanwell MDM-60-24 and  MDM-10-5 would be better choices than the cage power supplies shown.
All motors should have a seperate ground wire back to the star ground so emi does not attempt to pass across linear bearings. Hyrperthem have a good grounding document. Follow it.
I get frustrated when I see suboptimal designs accepted as gospel just because they have used pretty pictures but its a good start
Grab a couple of Mesa COMMX2 bus bars when you get your 7i96s. Also get some of their Din rail mounts.

Also just for me, use a multimeter and check if there is resistance between the torch tip and the work clamp. Most plasmas add a 100k resistor or similar to bring the current on the raw output down to non lethal levels. If so, you can mount the thcad in the control box if you are lazy.

tommylight wrote:

Out of curiosity, how much is a RPI and a good touchscreen these days?
Wondering as i got a Lenovo X1 Carbon Yoga for 120 and a Lenovo Yoga Y370 for 220, bot work for LinuxCNC with Mesa, both have 120Hz touchscreens, very high quality ones, very good keyboards, and both do over 4-6 hours on batteries.

hmmm, thanks for the tip. That might be a good option.

 I seem to recall comments about not using laptops because of the power saving features. Did you have to disable those in BIOS or elsewhere?
 

Looks like a mesact bug.

In the mean time you could just copy/paste/renumber
the stepgen section from another axis to get it working.

issue
github.com/LinuxCNC/linuxcnc/issues/3196
pull
github.com/LinuxCNC/linuxcnc/pull/3197

I home this is correct, if not please let me know.

Can you please try this later version of the linuxcnc image
drive.google.com/file/d/16xQfd_zXuXXKXqO...IY0/view?usp=sharing
I believe the screen issues are solved because the underlying Pi code had some fixes