- Posts: 22010
- Thank you received: 3
Postprozessor Fusion 360 PlasmaC
- tommylight
-
- Offline
- Administrator
-
As for derrived arcok, i am still using it on my machines, so far there are 4 in daily use, all work properly with default values in QTPlasmaC.
Please Log in to join the conversation.
- MaikTheBike
- Topic Author
- Offline
- New Member
-
- Posts: 14
- Thank you received: 0
PlasmaC works now and I can cut with it. I added a delay for the loss of arc as you described. Very nice.
I cut some pieces and also tried out the "cut xxx mm in x or y direction-button".
When I press this button, in most cases the z-axis goes down and starts the cut in x or y. But sometimes the Z-axis seems to go up when I use this function ? Maybe its looking for an end-switch (I don't have any at the moment) ? But why does it go up sometimes instead of going down and starting the cut ?
thanks for you help
Please Log in to join the conversation.
If you mean this:MaikTheBike wrote: I cut some pieces and also tried out the "cut xxx mm in x or y direction-button".
When I press this button, in most cases the z-axis goes down and starts the cut in x or y. But sometimes the Z-axis seems to go up when I use this function ? Maybe its looking for an end-switch (I don't have any at the moment) ? But why does it go up sometimes instead of going down and starting the cut ?
Attachment not found
then that is odd behavoiur, it should attempt a probe first.
If the Z axis height when you press the Start Cut button was lower than the Probe Height setting in the Run Panel then it would need to move up to get to probe height.
Please Log in to join the conversation.
- MaikTheBike
- Topic Author
- Offline
- New Member
-
- Posts: 14
- Thank you received: 0
Yes. Thats exactly the function I wrote about.
What I do is the following:
I start the PlasmaC-machine, Press F1, then F2, and home all axis.
Then I press the "start cut" button of the function. The machine starts to cut and everything is good.
After cutting the machine moves up and I have to press F1, because there are no limit/homing-switches on the machine. So if I don't press F1, the axis doesn't stop.
Then I press F1, F2 and Start Cut and the machine moves up instead of moving down. Maybe its because the machine doesn't have end-switches and I have to press F1 after the first cut ?
Thanks a lot,
Maik
Please Log in to join the conversation.
- tommylight
-
- Offline
- Administrator
-
- Posts: 22010
- Thank you received: 3
-probe speed to fast
Please Log in to join the conversation.
Homing and limit switches are not mandatory. I don't use limit switches at all. But you must have the all the axes at the position it says HOME is at in the ini file when you home the machine and you must have the MIN_LIMI and MAX_LIMIT sttings correct.MaikTheBike wrote: After cutting the machine moves up and I have to press F1, because there are no limit/homing-switches on the machine. So if I don't press F1, the axis doesn't stop.
Please Log in to join the conversation.
- MaikTheBike
- Topic Author
- Offline
- New Member
-
- Posts: 14
- Thank you received: 0
I have to make sure that these settings are correct.
Until now I have only cut simple shapes like rectangles or circles and I wanted to cut a part from a DXF-file (a cat).
I imported the file into Fusion 360, generated the G-Code with the PlasmaC-PP and then there is an error in LinuxCNC:
"Radius to end of arc differs from radius to start" (in line 78)...
Maybe you have an Idea, what I'm doing wrong here ? The NGC-File and Fusion 360(F3d) are attached.
Thanks a lot,
Maik
Please Log in to join the conversation.
forum.linuxcnc.org/38-general-linuxcnc-q...o-start-error#116469
Please Log in to join the conversation.
- MaikTheBike
- Topic Author
- Offline
- New Member
-
- Posts: 14
- Thank you received: 0
I was able to solve the problem and PlasmaC seems to work now.
Today I tried spotting with the Fusion 360 Postprocessor as described in the PDF-manual of the PP
with Multiple-Tools set to 1 in the hal-file.
I created the G-Code and the machine did the centerpunch very well. Thats awesome.
But after punching the Z-Axis went up and down again to do a second punch at the same spot. Then it went up and down and did a third punch at the same spot. Then I stopped the program.
I looked at the GCode and linuxcnc stayed at line N105 X3.5, while the z-axis went up and down multiple times and did the punches.
Threshold was set to 120V and timeOn was 10ms. I don't know if these are good values for punching, but the "holes" punched looked nicely.
Thanks a lot,
Maik
Please Log in to join the conversation.
This line is not required:
Nor are these:
Although having said that, they shouldn't cause any problem apart from the error message caused by line N50.
EDIT: The issue is caused by this line:
It should be:
Please Log in to join the conversation.
