Closed GoogleCodeExporter closed 9 years ago
Can you please provide a picture of the circles, you may refer to the lead in
circles.
Original comment by chrisko....@googlemail.com
on 2 Feb 2015 at 5:24
Chrisko, I'm sure those are NOT lead in circles (i don't use G41/42). Here's a
screenshot of linuxCNC AXIS with this file open.
I think it might be due to some issues with tolerances... looks like those were
suppose to be tiny arcs but for some reason became huge arcs on the other side
(+/- errors?)
Thanks in advance,
Bushman
Original comment by inner.bushman
on 2 Feb 2015 at 10:05
Attachments:
Hello Bushman,
i think your right, this may be a tolerance issue or a issue with the NURBS
Parameters itself. What doés DXF2GCODE Show you?
I just updated the files on the Server to my newest issue, can you please try
that issue, i think i did Change some Parameters of the spline Import. I
attached my Picture of dxf2gcode.
My Import Parameters are (You can try to Play with those in order to get a
better result):
[Import_Parameters]
point_tolerance = 0.001
spline_check = 3
fitting_tolerance = 0.001
regards
Christian
Original comment by christian.kohloeffel
on 4 Feb 2015 at 1:18
Attachments:
Original comment by christian.kohloeffel
on 4 Feb 2015 at 1:20
Hi Christian, thank you for your reply.
The issue is not on the import side but rather on export side.
I've downloaded your new version and run the file through it again but the
resulting g-code is still producing the same random circles in LinuxCNC AXIS.
The imported image is looking great! exactly like in your screenshot.
Everything looks good in your program window. Problems start when i export
g-code and open it in AXIS.
I didn't add new screenshots cause the old ones (yours and mine) still apply.
regards,
Bushman
PS: the program is no longer verbose in terminal window, is that intended?
There were some error messages that let me know if the tolerance was to great
to process the file, now they're gone.
Original comment by inner.bushman
on 5 Feb 2015 at 12:00
I needed to Change something with the logger etc. in order to make it work for
EMC2 Integration correctly, maybe thats the reason why it is no longer verbose.
Did you try to increas/decrease the tolerance, maybe that helps to solve the
issue? Since DXF2GCODE itself is getting it right, this might be also a Problem
with the Export tolerance to EMC2, which Digits Count do you use for Export?
Try to increase that?
Try the following:
- Increase Digits in Postprocessor e.g 4-6 digits
- Decrease Fitting Tolerance of Splines e.g 0.1
- Increase Fitting Tolerance of Splines eg. 0.0001
Original comment by christian.kohloeffel
on 6 Feb 2015 at 1:54
Thanks for suggestions, it worked!
After your last post I've started to read the config files (I've only used the
GUI before that). I've started to tweak some values...
The thing that helped was to increase postprocessor post_decimals to 5! Now it
works with default 0.001 import tolerance! :D
It seems that postprocessor has some discrepancies in G3 rounding down and AXIS
interpreted it wrong. I bet that's the same reason why AXIS was spitting out
bad arcs in the past and didn't let me use the code at all. I bet the other
code will work now too!
Thanks for all the help!
Bushman
PS: Owl in attachment ;]
btw reading the config i've figured out the verbosity ;] changed it to my
preferred setting for window_loglevel instead of console, now i can run it from
launcher without console ;]
Original comment by inner.bushman
on 7 Feb 2015 at 12:26
Attachments:
I'm glad to hear that everything is fixed. You produced a really geat looking
owl for decoration i guess?
best regards
Christian
Original comment by christian.kohloeffel
on 7 Feb 2015 at 11:21
Yes, it's a decoration piece. My friend is one of those "everything 'owl' must
be mine!" persons :D
BTW, is there a chance you could add this parameter into your GUI and make all
3, tolerances and number of digits a non volatile settings? I'd do it myself
but i suck at coding, wouldn't know where to start XD (should i open a new
ticket for that as feature request or something?) :P
Thanks again,
Bushman ;]
Original comment by inner.bushman
on 7 Feb 2015 at 11:29
Original issue reported on code.google.com by
inner.bushman
on 2 Feb 2015 at 4:36Attachments: