Hi all,
I have a problem with the attached post-processor.
In Italian W10 the decimal separator is set as ',' but g-code uses '.' char as decimal separator.
At 90% of times, the SheetCAM post engine works fine and uses '.' for decimals.
The remaining 10% of times, in the same PC, some ',' enter in numbers so I can have some lines with G04 P1.3 and some lines with G04 P1,3
which creates an invalid char error in the G-Code compiler.
There is a way to define what is the decimal char in LUA post-processor language?
I use the 6.1.74 version but our customers, with the same issue, uses the latest 6.9.7.
Best regards
Silverio
Decimal separator char
-
- Posts: 15
- Joined: Tue Nov 13, 2018 8:30 am
Decimal separator char
- Attachments
-
- RosettaCNC 3 Axis Plasma.scpost
- (15.91 KiB) Downloaded 54 times
- Les Newell
- Site Admin
- Posts: 3665
- Joined: Thu May 11, 2006 8:12 pm
Re: Decimal separator char
Give this version a try. There were a number of decimal separator issues.
I didn't find an issue with G04 though.
I didn't find an issue with G04 though.
- Attachments
-
- RosettaCNC 3 Axis Plasma.scpost
- (15.88 KiB) Downloaded 51 times
-
- Posts: 15
- Joined: Tue Nov 13, 2018 8:30 am
Re: Decimal separator char
Thank you very much, Les!
Your help has been very useful to me, rarely I've to write post-processors, so I'm a newbie in this matter.
Tomorrow I will send it to the customer for the final test.
Your help has been very useful to me, rarely I've to write post-processors, so I'm a newbie in this matter.
Tomorrow I will send it to the customer for the final test.
-
- Posts: 9
- Joined: Tue Oct 13, 2020 8:12 pm
Re: Decimal separator char
I solved this issue for a different post-processor in a generic way, code is here:
https://github.com/DenkBrettl/plasmac_s ... 00aea59718
https://github.com/DenkBrettl/plasmac_s ... 00aea59718
- Les Newell
- Site Admin
- Posts: 3665
- Joined: Thu May 11, 2006 8:12 pm
Re: Decimal separator char
Forcing a C locale is a very bad idea. This affects the whole application, not just the post processor. Looking quickly at the post I can't see why you would need to do this anyway.
I see you are using a pre-set feed rate instead of using the feed rate supplied by SheetCam. This will disable feed rate overrides from path rules so things like slowing down for corners or small holes will not work.
I see you are using a pre-set feed rate instead of using the feed rate supplied by SheetCam. This will disable feed rate overrides from path rules so things like slowing down for corners or small holes will not work.