Advanced Search

Hi, everyone.

I have a trouble getting LinuxCNC work about homing  with Lichuan LC10E Servo drive.

My LinuxCNC System can move XYZ GCode with CSP Mode.
But I could not use homeing function.
I believe I should use cia402_homecomp.
I tried configurate my ini, hal, xml to use cia402_homecomp manually, using LC10E-driver's homing function,  but I failed to work it so far.

I hope, I can find any configuration about this library as a example.
Are there any LinuxCNC configuration files about it ? 

Thanks.


 

i am sorry, it was some time ago. I believe that you can customize PDOs as you need.

A grounded steel enclosure is not the best place to be emitting radio signals from.

Nowadays just about any wifi dongle will work, but it will need an external antennae.

Should a good starting point for usable wifi adapters, anything that works with Debian Bookworm will work.
github.com/morrownr/USB-WiFi

If you need extra help I'm located in Sydney as well.

Currently, this GPU is quite out of stock. In China, the price is approximately $40.

Hi all,

I'm just starting out with EtherCAT, and I'm trying to configure my Servo drives. Looking at some example configs, I often see dcconf and/or watchdog tags with varying parameters.

Would somebody be so kind to explain in simple words what those lines do? Are they mandatory or just for optimization? Where do I find the correct parameters for my drives (Hiwin ED1 400W)?

A link to a good documentation of those tags would probably also be fine, I didn't find good info yet...

Cheers,
Matthias

Steel, 400 x 600 x 190.
See attached (poor) photo showing RPi hanging in space:
Row 1: stepper drivers,
Row 2: RPi stacked on Mesa, I/O PSU,
Row 3: 12 Vdc relays, Mesa core PSU,
Row 4: Terminals,
Side: stepper sockets, hole for monitor+keyboard+mouse cables, GPO for monitor + RPi.
Terminals and cables as appropriate, much neater generally.

I have a virtually identical cubicle with some electrical equipment in it.
Stripping and testing should begin next week.

The RPi 4GB and L2.9.2 need to go back to their day job of cutting metal.
John.

(SOLVED)

I compared V1.04 and V1.11 EEPROM Files.
And tried to understand configuration files.
I found my cnc configurations were mixed for V1.04 and V1.11.

Lichuan sales person said, we should use V1.11 with LinuxCNC for some reason.

Now servo lock is working by pressing PowerOn button.

Have a look at 'extra joints':
linuxcnc.org/docs/html/man/man9/motion.9.html

The maximum number of joints is 16.

Alrighty!

Drives and motors arrived. Setup a bench test rig. 

I've made it as far as getting the encoders to read in LCNC (scale seems right). Unfortunately I'm getting following errors when I try enabling the drive. I can hear the drive enable relay latch very briefly. 

I've followed Tommylights guide, but can't get too far when it errors straight out of the gate. Im also getting a "could not switch machine on, is limit switch activated". I currently have no IO assigned. 

I suspect my wiring is at fault or I'm really missing the mark with my initial PID numbers - I've tried a bunch so far, even with giant max f errors.
Schematic below. Any thoughts would be greatly appreciated!

Thanks,

J



 
 

So we have the 9 normal ones.....problem is I need 16axis total.
 

Found a machine that needs a new controller and peaked my interest on how would I do it..... It has 20ish stepper motors on it

It's a machining version of a progressive stamping die. Where 4 drills and a tap station are positioned into place via steppers than ran pneumatically after that. Thus most of the axis are used at the start of the program... after that they aren't used. These do have working homing switches. 


A saw, bar feeder, bar magazine, and prob the tap station are the things that need live axis/gcode control..... But none of the axis needs to be coordinated As everything fires (drill, tap, saw) then the bar feeder advances one station. 


The lame way would be to have 8 solenoids (3PDT) connect the step, direction, and home switch pins for each of those 4 drills (2 axis each), then home and position it. So all 8 axis could be "one axis" in software..... Seems complex.

Surely a software solution exists. Custom M code? 

Will use gcode for as much as possible but not opposed to Python or hal scripts. 


Thanks








 

Thanks, and to confirm both tool setting and probing use "probe-input"?

If so, then I am considering using mux2 and utilizing M64 and M65 to select which digital input the tool setter and digital probe are connected to.

INCREMENTS = 1 mm, .5 in, ... - Defines the increments available for incremental jogs. The INCREMENTS can be used to override the default. The values can be decimal numbers (e.g., 0.1000) or fractional numbers (e.g., 1/16), optionally followed by a unit (cm, mm, um, inch, in or mil). If a unit is not specified the machine unit is assumed. Metric and imperial distances may be mixed: INCREMENTS = 1 inch, 1 mil, 1 cm, 1 mm, 1 um is a valid entry.

From the docs. I don't think you can change on the fly since it in the initialization file. I could be wrong, but you can mix and match to suit your needs. I rarely use any besides the fine feed. Could probably get away with 4 units, jog, mm, mm, in, in

Thanks.

I want to jog in inch increments when in G20, and have it change to mm increments when using G21. Similar to the DRO when it changes.

Yes you can have either in or mm to specify what is displayed.

the internal wifi card sits on the same pci bus as hard-drive and ethernet, so its driver can easily throw a wrench into the latency. I could probably just blacklist its driver in grub from loading, but i chose to completely remove it.

yes, sudo apt install r8168-dkms will work fine if you have your controller connected to the internet. I did not, so i used that command to build realtek 8168 driver on a virtual machine connected to the internet. (which in fact is just one file called r8168.ko) then i copied this file over to the controller using usb stick and manually replaced the default driver.

I don't plan to upgrade the kernel any time soon, so this approach works for me.