- Posts: 83
- Thank you received: 0
Another plasma component...
I noticed the terminal output had quite a few errors on it so I have uploaded that and my config files,
As a last ditch attempt I am going to try a complete re-build of the pc.
What version of Linux would any of you suggest I install to give me the best chance of getting this working, wheezy seems very old to be messing about with but is what is still supplied on the Live/Install and the recommended method.
Please Log in to join the conversation.
- islander261
- Offline
- Platinum Member
-
- Posts: 757
- Thank you received: 0
I have not tried the latest plasmac yet. Yesterday and today are wild to the mainland delivery days. It was supposed to be only one day but thanks to the ferries and a big multi car wreck on the rural freeway which blocked it for 7 hours we couldn't get everything done. I will get things ready and try and cut tomorrow. I will need to fix my PP first and maybe one of my .hal files. On my system right now motion.digital-out-01 is my THC enable bit. Motion .digital-out-00 is my test probe enable bit. No rhyme or reason here, I just needed the test probe bit first.
John
Please Log in to join the conversation.
"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
Please Log in to join the conversation.
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.
Please Log in to join the conversation.
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 to join the conversation.
In your ini file, you need to have the five settings at the top of the following code snippet in the [AXIS_Z] section:Dee436 wrote:
I noticed the terminal output had quite a few errors on it so I have uploaded that and my config files,
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:
Cheers, Phill.
Please Log in to join the conversation.
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;
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;
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 to join the conversation.
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 to join the conversation.
phillc54 wrote: Guys,
I have a mostly working concept for tool handling in the configs.
I'm actually struggling with this. I have about 6 different tips for my machine. (30A, 40A, 60A, 80A, 100A, 120A) Here is the metric cut chart for my machine with a 9-8211 (80 amp) tip
Attachment not found
The key parameter we want is the Tool Diameter or kerf width
There are 10 different kerf widths for this tip alone.
The kerf widths for mild steel for my machine range from 1.4mm to 4.4 mm. I think I'd have to create a series of 30 odd tips 0.1mm apart that don't really relate to anything.
I'm not thinking the tip definitions add anything other than complexity.
I personally think unless you moved to a fully relational database, what we need would be met by simply adding a unique ToolID and a kerf width to the existing materials table records.
Please Log in to join the conversation.
JT
Please Log in to join the conversation.
