Advanced Search

It is suport step/dir sir?? Because original stmbl are suported right, if posible open the step/dir interface mate, so we can used for mach3 or grbl, thank u somuch.

I'm running LinuxCNC/Axis 2.9.0-pre1..... on LMDE 6, using software stepping. I have a 3 axis CNC, with two motors on the X. Initial condition has the motherboard parallel port controlling the motors and a second parallel card doing some other details. One X motor works, the second does not.

I was trying to connect my g540 disable to the parallel port and one motor quit working, the 4th axis on the g540 (which is my second X motor, see image). Using an oscilloscope, I can see step/direction for the parallel port pins 2,3 (x) 4,5 (y) and 6,7 (z) when I use the arrow keys. Pins 8,9 have nothing when I use the arrow keys for x. I  figured I had blown up the parallel port, but somehow just those two pins.

Bought a PCI parallel card, changed stepconf to use that card instead of the MB parallel port. Same deal, I can move the X motor but the X2 motor doesn't do anything. I measured the new parallel port pins, same result. I can measure step/direction for pins 2-7, but pins 8 and 9 do nothing.

Somehow the signals on the 4th channel, pins 8-9, is not getting through. I think I have Stepconf set up right, it was a working machine before.

Help will be greatly appreciated!
Steve
 

Hey, i have a question about configuring a 6axis robot arm with lcnc, ive built myself a robot arm and im trying to control it via a puma560 simulation config, ive seen a youtube short of someone doing exactly that but he has no documentation on how he did it, im new to lcnc so i dont really know where to start with configuring physical pins, for context im using a rpi5 and want to use gpio pins for step/dir, ive got some tmc 5160t drivers to work and i get motion from them i just dont know how i would assign physical gpio pins to the already existing config Below ive linked the short where a robot arm is controlled by the puma560 config, if you stop at the right time you can see the tab name: youtube.com/shorts/js6OaVhUN2U?si=68d75rJqwbvCr9V0

tommylight wrote:

Is the void lock disabled?
Old info, but had this happen often on PlasmaC while it was still being developed, does require setting VAD at under 75% and disabling void lock.
Did not happen probably last two years.
-
Also does absolutely require monitoring the voltage, as it can be caused by the plasma source dropping the voltage due to heat or mains voltage going up (transformer plasma) or issues with current control (inverter plasma).

Thanks Tommy. We had not discounted plasma voltage changes and had some ideas to check if that is it.

Stahlwerk
www.stahlwerk-schweissgeraete.de/Plasmaschneider-CUT
Good quality and cheaper than china, vertical machine torch is 40E in Germany, with 5 meter cable is 90E, bought both.
Mind the pilot arc, there are some without it so do not get those, it is easy just look for a red knob on the bottom front and usually it is written in spec info.

Is the void lock disabled?
Old info, but had this happen often on PlasmaC while it was still being developed, does require setting VAD at under 75% and disabling void lock.
Did not happen probably last two years.
-
Also does absolutely require monitoring the voltage, as it can be caused by the plasma source dropping the voltage due to heat or mains voltage going up (transformer plasma) or issues with current control (inverter plasma).

Hm, the issue is that I only have a 12 slot tool rack. I machine wood and metal and have my tool library imported into fusion as well. This means I will be switching tools in and out the tool rack as I need, so it would be great to use the assigned pocket numbers.

Nevertheless for someone not needing to change the tools frequently (or is more flexible in tool numbering) that is a good idea!

You can use tool numbers instead, pocket numbers have to be the same as tool numbers for non random toolchangers

Hello Klopp an ProG.

I'm also in the same situation to retrofit a Weiler 160 CNC. I'm very interested in the LCNC config files and also the classicladder for the turret. Can you help me with these files?

Marc

Hi Chris,
I think this completes this:
You can see another build like ours with the hand adjuster on the top slide and the Kipps handle on the quill clamping assembly
Cheers,
David

If you got an xml file from the manufacturer it is most likely an ESI file. Linuxcnc doesn't use that.
Linuxcnc reads out all necessary info from the drive itself. You can see most of that info yourself with the commands
You do need to connect pdos to hal pins and that is (mostly) what you do in the linuxcnc ethercat-conf.xml file.
A good starting point for that is often the output from the "lcec_configgen" command.
Which happens to use the three commands above and rearranges that info into a workable ethercat-conf.xml that you can then modify if needed and you don't like the naming etc.

I wonder how one can describe the configuration of a linuxcnc ethercat system. There isn't any stepconf or pncconf and it isn't realistic to create one due to the large variety and number of devices. I hope to get proven wrong there.
Starting point is a linuxcnc config from the linuxcnc simulator examples and then substitute pins.
lcec and ethercat-conf.xml, how to create the ethercat-conf.xml
Special on Cia402 drives
Modifications to hal


 

rodw and tommylight thanks for your answers. Although I have to admit I am stil confused.

I bought a cheap pilot arc plasma to play arround. It has an explicit connection between the tip and the workpiece. Ohmic sensing can't be done. Right?

Anyhow, I build a CNC Plasma and I am looking for a suitable frontend (plasma and torch) my wishlist includes:

1 plasma cutter (hopefully < $1000) with a european distributor
2 Ohmic or hypersensing (willing and able to build homemade electronics if I know what)
3 THC with a THCAD-x (best case with an avaibale THCAD-300)

Can someone propose a setup ?

need hal, ini and xml files.
Sounds like something is set wrong

tommylight wrote:

Eventually they gave up and adopted USB-C. (Oh well..., so much for all that work)
nope, they did not "adopt" it, they were forced by Europe.

And I am sure the industry retaliated by strictly enforcing the USBC charging standards so device that used to charge OK on low voltage no longer do.

I never experienced this either But I rarely cut longer than 400mm
Customer says on a long cut, the torch comes down and hits the material and crashes.

I am guessing this has something to do with PID settings but I never used anything other than default settings. Any ideas on how to correct this would be appreciated.

Level flight would be appreciated. I do remember when a light aircraft thought he was flying level but ploughed in well short of the runway with tragic and fatal consequences. Pilot could see the town lights and flew visual instead of by instruments. Seems this is similar,