Another plasma component...

More
7 years 6 months ago #132434 by PCW
Replied by PCW on topic Another plasma component...
As far as following errors go, You might try removing all the

"setp pid.N.maxerror .0005"

statements. These will cause following errors on Metric machines
(machines units set to metric in the INI file)

Do you gcode files have a G20/G21 in the beginning?
if not, metric or imperial mode will be determined by the last file that included a
G20/G21
The following user(s) said Thank You: rodw

Please Log in or Create an account to join the conversation.

More
7 years 6 months ago - 7 years 6 months ago #132435 by rodw
Replied by rodw on topic Another plasma component...

PCW wrote: As far as following errors go, You might try removing all the

"setp pid.N.maxerror .0005"

statements. These will cause following errors on Metric machines
(machines units set to metric in the INI file)

Do you gcode files have a G20/G21 in the beginning?
if not, metric or imperial mode will be determined by the last file that included a
G20/G21


Peter, thanks, I just checked my hal files and that maxerror setting has been there since day dot!
It looks like my Sheetcam postprocessor inserts the G21 for my metric config. But Phill is also loading a different startup .ngc file for metric and imperial so G20/G21 is set on startup with plasmac.
Last edit: 7 years 6 months ago by rodw.

Please Log in or Create an account to join the conversation.

More
7 years 6 months ago #132436 by Dee436
Replied by Dee436 on topic Another plasma component...
Hi PCW

Thanks for that, I will comment them out and try it again.

I do use G21 at the beginning of my gcode although I have not had any g-code files loaded in plasmac as yet

Darren

Please Log in or Create an account to join the conversation.

More
7 years 5 months ago - 7 years 5 months ago #132470 by phillc54
Replied by phillc54 on topic Another plasma component...

Dee436 wrote:
I noticed the terminal output had quite a few errors on it so I have uploaded that and my config files,

In your ini file, you need to have the five settings at the top of the following code snippet in the [AXIS_Z] section:
MIN_LIMIT and MAX_LIMIT are correct
MAX_VELOCITY and MAX_ACCELLERATION values need to be changed in the [AXIS_Z] section to 200 and 1500 respectively. You may need to adjust STEPGEN_MAXVEL and STEPGEN_MAXACCEL as well.
OFFSET_AV_RATIO is not in the[AXIS_Z] section, is does need to be there. This is giving you the following error:
Code:
File "./plasmac_config.py", line 241, in __init__ float(self.i.find('AXIS_Z', 'OFFSET_AV_RATIO'))) * 60 TypeError: float() argument must be a string or a number
The bit above the [AXIS_Z] section should then be deleted. (from #******************** to OFFSET_AV_RATIO = 0.5 inclusively)


Cheers, Phill.
Code:
#******************** # Axis Z #******************** # this should be the top of your slats MIN_LIMIT = -77.0 MAX_LIMIT = 0.01 # required, set to double the value in the corresponding joint MAX_VELOCITY = 200 # required, set to double the value in the corresponding joint MAX_ACCELERATION = 1500 # required, shares the above two equally between the axis/joint and the offset OFFSET_AV_RATIO = 0.5 [AXIS_Z] TYPE = LINEAR HOME = 0.0 FERROR = 10.0 MIN_FERROR = 1.0 MAX_VELOCITY = 100 MAX_ACCELERATION = 750 # The values below should be 25% larger than MAX_VELOCITY and MAX_ACCELERATION # If using BACKLASH compensation STEPGEN_MAXACCEL should be 100% larger. STEPGEN_MAXVEL = 125 STEPGEN_MAXACCEL = 937.50 P = 1000.0 I = 0.0 D = 0.0 FF0 = 0.0 FF1 = 1.0 FF2 = 0.0 BIAS = 0.0 DEADBAND = 0.0 MAX_OUTPUT = 0.0 # these are in nanoseconds DIRSETUP = 5000 DIRHOLD = 5000 STEPLEN = 2500 STEPSPACE = 5000 STEP_SCALE = -80.0 MIN_LIMIT = -77.0 MAX_LIMIT = 0.01
Last edit: 7 years 5 months ago by phillc54.

Please Log in or Create an account to join the conversation.

More
7 years 5 months ago #132495 by phillc54
Replied by phillc54 on topic Another plasma component...
Guys,
I have a mostly working concept for tool handling in the configs.
As far as a user is concerned it works like:
The materials file holds tip values;
Code:
# TORCH_TIPS # the tips will be parsed and a new LinuxCNC tool table will be written # the number after TIP_ will be the tool number in the LinuxCNC tool table # the format is TIP_n = DIAMETER ; DESCRIPTION TIP_1 = 0.5 ;Fine Cut TIP_2 = 1 ;GP Tip TIP_3 = 3 ;Big Mother
And each material in addition to the original cut parameters holds a tool number which must be unique to each material and a tip number relating to any one of the tips above;
Code:
[Mild Steel 2mm] TOOL_NUMBER = 1 TORCH_TIP = 1 . [Mild Steel 2mm] TOOL_NUMBER = 2 TORCH_TIP = 2 . [Mild Steel 3mm] TOOL_NUMBER = 3 TORCH_TIP = 1 . [Mild Steel 3mm] TOOL_NUMBER = 4 TORCH_TIP = 2
Multiple materials may point to any tip.

On startup the materials file is parsed for the tips and then a new LinuxCNC internal tool table is created from these values and then loaded. So a tool table from the above would look like;
Code:
T1 P1 D0.500 ;fine cut T2 P2 D1.000 ;GP tip T3 P3 D3.000 ;Big Mother
There is no need to edit the LinuxCNC tool table, it will be handled by the config.

So:
if you want to cut 2mm Steel with a 0.5mm tip select tool 1 (M6T1)
if you want to cut 2mm Steel with a 1.0mm tip select tool 2 (M6T2)
if you want to cut 3mm Steel with a 0.5mm tip select tool 3 (M6T3)
if you want to cut 3mm Steel with a 1.0mm tip select tool 4 (M6T4)
The config will map the correct LinuxCNC tool number to the material tool number.

Clear as mud...

BTW. Do we like tip or nozzle?

Cheers, Phill.

Please Log in or Create an account to join the conversation.

More
7 years 5 months ago #132497 by Dee436
Replied by Dee436 on topic Another plasma component...
Thanks Phill

I have a fresh build of Stretch and a fresh clone of Plasmac, I have made the changes to my ini and will be testing in the next couple of hours

Darren

Please Log in or Create an account to join the conversation.

Moderators: snowgoer540
Time to create page: 1.614 seconds
Powered by Kunena Forum