Advanced Search

My project is slowly progressing. I've put together a few things using examples and AI. The interface starts, but I'm stuck in the ESTOP. The statuses in HALSHOW aren't changing either. So there seems to be no connection to the board, even though pinging 10.10.10.10 is successful. Is there a way I can test the communication?         

Thanks,
yes, theoretically this also works with large servos, but this also requires large power amplifiers.
it is better to run something like this separately on real servo drivers.

it must run on the same computer as linuxcnc, to find the python libs.

BUT, it's only a proof of concept, do not use it for production systems

You need to change the home search direction for that.

Yes, because whenever I flip it the bed homes in the opposite direction, maybe I'm doing something wrong, but that was the solution i found until now

OK, check what tool it is outputing, several years back i had such an issue with it but on windoze, it would ONLY output tool 6 instead of 1, no matter what i did or change or how many times i reinstalled it...so i installed LinuxCNC.

Hello everyone,

I have a problem where, after changing the diameter or Z offset in the tool table for an active and loaded tool, the values ​​aren't immediately applied. Even if I click the "Apply" button.

I have to explicitly unload the tool and reload it with M6.

Unfortunately, I can't figure out how the Apply button works.



Maybe someone here can help me. Thank you very much.

Andy wants to replace 32 bit  pins with 64 bit pins in 2.10. Some people don't agree with this as it could result in unexpected consequenses (me included). for example I can see it breaking the Ethercat driver.

Re memory storage, its really defined by the CPU byte and register size so there is not any benefit in storing 8 bits. eg. the CPU will load 64 bits at a time into its registers so 8, 16, 32 or 64 bits will all probably take the same amount of storage on a 64 bit system.

thanks Tommy,

Using the same linuxcnc post in sheetcam that i have been using for ages.

grijalvap wrote:

yes it works if you use 2 tools one with piercing delay and one with 0 delay.
I'm using the tool from sheetcam (tempoary tool created from file). so i need 2 files or edit the file after pierce and reload.
what I'm thinking is just press a button and make the Pircing delay 0,

In the Sheetcam processor, there are some variables at the top of the file to select between Sheetcam and qtplasmac tools. Sorry about that but had to humor Les at Sheetcam seeing its distributed with his software (and he wrote the post.)!

There is also a script that lets you import a Sheetcam  toolset into qtplasmac

snowgoer540 wrote:

Temporary materials were meant to be temporary, QtPlasmaC and PlasmaC before were not built with a temporary materials workflow in mind.

Nothing more permanent than a temporary solution! Quote from someone on the internet...he/she was bloody right!
-
I absolutely and strictly use the materials in PlasmaC/QtPlasmaC, using anything else is asking for trouble.
I have modified the Inkscape gcodetools to output the required plasmac-feed-rate in gcode, and that was it.

The thing is, a round 20mm tube is roughly 63mm in perimeter (or in this case the distance the machine must move) while a 100 round tube is 314.15mm in perimeter, so if you have the same rotation speed, the 100mm will travel much faster under the spindle.
The easy way to avoid any of this is to have multiple normal configurations for each diameter, and use Y as rotary but in hal it remains linear. Not using A.
I have several rotary plasma machine in use with this type of configuration, so normal 2D CAM (Inkscape with gcoodetools), and just run the configuration for the diameter being cut.

spincycle wrote:

Ah using Linux to entirely tune the feedback loop?

Yes, the position loop is in LinuxCNC.
Velocity loop is usually on the drives when motors also use tacho generators.

spincycle wrote:

Am I right in thinking that if you run analog signal and rely on linuxcnc to close the loop, all tuning happens within Linux, as per your link?

No auto tuning through the drives etc?

Yes, again only the position loop is handled in LinuxCNC, velocity and torque loops are handled usually in the drives, although LinuxCNC can also handle all of the above on it's own.
The tutorial is for using older existing drives, whenever possible i try to use them as they are very good quality and rarely fail, and most of the tuning is already done in the drive as they were in use and working perfectly fine.

You could just stop using temporary materials and let the materials in QtPlasmaC be your master.

Then you only have to perfect settings in one place. Furthermore for your situation you’d go to another tab, change the delay,  do your pieces go back to the tab change the delay again and run the program. No editing gcode files necessary.

Temporary materials were meant to be temporary, QtPlasmaC and PlasmaC before were not built with a temporary materials workflow in mind.

Might not be the issue, but you should really avoid using Mach3 post processors for LinuxCNC, if you use any for plasma, it will shows each consecutive cut on screen lower and lower. Try something with 200 cuts!
If you must, use the plainest post processor, mill should do probably, again with no gcode for tool changes n'stuff.