Advanced Search

Nice nice nice... This document is tasty and it is a new galactic space for everyone from us... 

Sinamics are widely used for everything and they are very powerfull.. 

every shared picture is are helpfull i think if you will need help I am here for everyone.. i will create a dry project in the twincat3 to check configuration ...

 

You have a servo period of 2000000 (2 million) but failed to set the correct P value for it at 500, not 666.
Max_velocity is 125 but stepgen_max_velocity is 150 despite just above it being clearly stated it must be 25% above max_velocity, so absolute minimum is 156.25, or rounded 160
And, why do you have anything but 0 for FF2 on a stepper system? It should be 0.
All of those contribute to your issues.

Hey guys, after several delays I got my machine running and I made my first part with it. First part, first problems. The locknut from my driven ball screw came loosened and I got a lot of backlash. I fixed that, then I had problems with my VFD (Hitachi WJ200), and had to send it to the service. Meanwhile, I used a chinese VFD (with filter unit in the line) , that worked fine, but last week I got the known problems with "motor-0-errors. Mostly if the x-axis stopped, turned around, then comes the error. Sometimes it runs several paths, then stopped again. That drives me crazy.
My latency is as good as before, I don't have lost packages, I don't know what to do with it.
Do you have any hints for me to change this problem? I put my actual HAL and INI here.

BTW - I don't understand that kind of error. What makes LCNC to give this error out? There's no connection to the motor's encoders, no feedback nothing what makes sense for me...

Tanks for any help!
Kind regards, Hanno
   

Try this:

unknown wrote:

I don't know where this idea comes from that you need any coding skills to setup Linuxcnc. This is one of the biggest lies ...

 

Sorry if it wasn't clear, my english skills must be just as poor as my coding; I'm coding a component to use TMC5160 drivers over SPI without any step/dir signal. What I wanted to say is that I'm sure I would have a working LinuxCNC configuration by now if I would just have bought a Mesa card. To me LinuxCNC is a bit more complicated to set up, even if you definitively don't need more coding skills than for FluidNC, which also have a config file.

I don't know why you would want to send a gcode file line by line to linuxcnc when it can open and read the file directly.

Maybe because I want to use the power of LinuxCNC for something that is not a mill. Like a pick & place machine that would adapt the position according to a vision result, or for a PUMA arm or any other automation machine in which a "master" would send g-code to a LinuxCNC slave to move the axis. OpenPNP is a good example and there already is an interface .

One thing that is very intriguing, you admit to poor coding skills, yet propose some major replacement of the Linuxcnc internal workings. 

I don't propose anything; I just have the feeling that if there is one area where FluidNC or any micro controller based G-Code interpreter is better than a computer based solution, it is for step/dir generation. There is no Latency-test in FluidNC, just hardware interrupts!   (But also, there is no encoder feedback, no routines, no special kinematics and many other no.)

Have a look at the angle jog component:
linuxcnc.org/docs/stable/html/man/man9/anglejog.9.html

ErwinCNC wrote:

Hello
I put my pi 5 into operation yesterday.
Unfortunately I get the locale error with Pconf

I tried to use the same settings as you.
My keyboard is german

Do you have an idea?
 

I *think* you have to set the localle etc from menu-config - mine was not set for me.

Today I started the program with the axis graphical interface. No change, the problem remains. Could someone check the HAW connections?

this problem also exists : " ... I just noticed that when starting LinuxCNC, I need to go into the calibration settings and re-save the PID values for the spindle (I enter test). If I don’t do that, the PID control is soft– under higher spindle load, it triggers a hold .Also, if I leave LinuxCNC running idle (without running a program) for about an hour, and then start program execution again, the axis movement speed during a G1 command is once again higher than what was set."

Hello,

I was wondering if it's possible in LinuxCNC to make a virtual compound slide on a lathe?

I'm considering options for a CNC lathe update and I'm thinking about adding a full set of manual controls. (With the screen acting as a DRO)

One such control would be an MPG to change the angle of a virtual compound slide, and another MPG to move that virtual compound slide - allowing tapers to be cut manually.

Hello,

Let me start off with the purpose of this thread. I've never built a plasma CNC and I've never used a THC. The purpose of this thread is partially to confirm some of the research I've done and partially to probe as a bit of a thought experiment, as from what I can see, things seem to be in a transitional state between a few control schemes. I don't know if what I've identified is valid, or if there's a reason behind it. Maybe it doesn't matter, but either way, I thought it might be fun to design a system (At a high level) from scratch and ask "what if?".


Let's take a step back and first talk about closed loop, older analogue controls and the like as that's quite important. (Or at least, my understanding. I'm basing some of this on an old Cincinnati Sabre 500 VMC with Fanuc controls I researched a while ago as I was looking to purchase it - It turns out that a 4t machine is a logistical nightmare, but the control findings were interesting.)

In ye-olde-days, you had motor drives with an analogue velocity signal. The drive didn't know what the position was, nor did it care. The motion control managed the position, and you had a full closed-loop setup. This was, I suspect, because back in those days, sharing digital signals over multiple devices was a pain, so it was easier to keep the digital stuff inside the motion controller and to have a fully analogue motor driver with analogue signals. An interesting part of this was the spindle motor orientation used for the tool changer - The spindle drive had a motor orientation board which was connected to the encoder. This meant that when the motion controller stopped the spindle, the spindle drive would automatically park it in a specific orientation. The motion controller didn't control this, it just told the drive to sort it out and the responsibilities were clear.

Next we have our standard step/direction drives, with stepper motors operating in a fully open loop. The motion controller assumes that when it commands a movement, that the motor and driver will keep up and hopes for the best. We know about the limitations, so let's not dwell.

After this, we have the hybrid closed-loop setups with step/direction signalling controlling either a "closed loop" stepper or an AC servo. (Which is closed-loop by nature) Some would say that these are not true closed-loop systems, but as long as there's a fault signal being fed back into the motion controller, it really is closed-loop by definition. Some servo drives allow a second machine encoder for increased accuracy.

Most of the more expensive Centroid offerings include ways to close the loop right back to the motion controller, but I believe this is more for compatibility with older hardware. (See above) I don't believe there's any benefit in a new setup as long as the motor drive can report a fault back to the motion controller; they are both closed-loop, just with different responsibility splits.


I wanted to take that detour about exactly what closed loop means because I think it applies to THC. There are many approaches, but I think it's also worth considering where the respective responsibilities should live between each component, and I think a good test is whether or not the system could, at least in theory, support buffered motion planning. I know that doesn't apply to LinuxCNC, but I think it's a good benchmark for responsibility splits either way.


As with motor drivers, there are many ways of approaching THC:
- You have "fully" stand-alone systems such as the Proma unit, which intercept the Z-axis motor control and over-ride it mid-cut.
- You have fully closed-loop systems where the THC is implemented within the motion controller in software with a hardware interface such as the Mesa THCAD.

I think most people would say that software solutions are superior as they can look ahead, implementing features such as anti-diving. However, from my research, I'd argue that the stand-alone systems are not actually standalone; there's a lot of confusion regarding responsibility, as both parts in these standalone systems control Z axis position. I'd also argue that a purely software solution isn't ideal when you start getting into Ethercat and certainly doesn't allow for offloading via buffered motion planning. I would propose that there's another way.


Fully stand-alone THC, with "fully" no longer in quotation marks. Consider the following statement: The motion controller does not care about the Z-axis position for a CNC plasma machine at all. It cares about the target arc voltage, it cares about anti-dive, it cares about the initial torch height - But it doesn't directly care about the torch height. What if the motion controller told the torch height controller about the target arc voltage, when to start/stop the torch, what initial torch height and dwell to use when starting, and when anti-dive should be considered? What if the THC handled probing and piercing itself, if it fully and directly controlled the Z axis, including the limit switches? What if the THC told the motion controller when it was good to start the motion, rather than just when the ARC is okay?

This is the step which I think is missing. You could wrap all of this up into an Ethercat device and it's a lot closer to being able to handle buffered motion. (Although it's not perfect, as the X/Y motor drivers would need to wait until the all-clear from the THC before they start their motion.) It could handle all things plasma, including gas and current control (E.g. Hypertherm's RS485 interface), it could report back all of the diagnostics (Such as current arc voltage, current torch height relative to the probe position, information about the torch tip. I think this would also be much closer aligned to the modern Fibre laser setups with how their focus control works.


I'm curious about people's thoughts. Have I made any mistakes or misunderstood anything? Is it nonsense or even just a waste of time? I'm also hoping my explanation on closed loop helped others understand what it really means, as it took quite a lot of research to get my head around what exactly it meant and why "proper" CNC machines used to have velocity control.

Hi
I have developed a method to center punch locations for drilling holes on my PlasmaCNC setup.I use CAD software (Fusion 360) to locate where I want holes drilled in my finished cut parts. I use fusion to show the location and size of the holes and then use the snap function to locate the centers. I do this with the circle sketch function snapped to the center then draw a 0.003” dot there. After saving in DXF format and importing into SheetCam I change the layer of the dots to separate the center punching from the normal cutting operations. I then have a tool in SheetCam that has the perimeter for the center punching operations. This has the pierce and cut height set at the same height and lower the Amps some for this operation. After planning the whole operation I select the center punching functions into on G-code and then the cutting function into another G-code. SheetCam will ID the center punching as a inside cut and you can make one G-code where it will do the 2 operations in the same G-code. QTPlasmaC seems to have a quicker response for this operation then I had with other controller software, but both produce a very nice dimple in the metal.Attached are images of the center punches and a video of the operation.  I have used this method on different thickness metal with thin metal using the fine cut nozzle. I have used it to create a template for hole marking by center punching a thin plate to transfer the locations on another project surface.

drive.google.com/file/d/1EtZ_7zD49-VbqYf...sVL/view?usp=sharing
       

Try omitting that line with scalemax, right now i can not recall i ever used it.
Just add # in front of the line, save, test.

I use Ditron magnetic scales all the time. Installed my first ones in 2019 on my 5 axis machine. Since the I have used installed about 20 of them. Not a single failure yet.

Be sure to specify that you want 1um resolution. Reader head model DMR2000. And also specify that you want the index pulse version (z signal) otherwise you get only A and B.

Yes. They are differential output

Henk

We've got plenty of trees, but the city white fellas cos playing as black fellas wanna stop everyone walking into where the trees are, unless you're a black fella.
The real black fellas are good fellas.

Now before everyone gets their knickas in a knot black fella isn't an insult, it doesn't matter if ya a black fella or white fella what matters is to be a good fella.

There's large swathes of land here that are off limits unless you're Aboriginal.

Hi,
only one 7c81, you tip has done the trick. Thank you!
but the next problem occured
The error changed to:
/intos.hal:88: parameter or pin 'hm2_7c81.0.7i77.0.1.analogout0-scalemax' not found

so checked this line in the old, working hal, without the 7i78, and its exactly the same. What does change here when i use 2 daughterboards?
Any Ideas?

EDIT:
i have also tried to change the channel number to 0:
hm2_7c81.0.7i77.0.0.analogout0-scalemax'
and 2 and 3