G-Code Ambiguity January 20, 2016 02:45PM |
Registered: 8 years ago Posts: 9 |
Re: G-Code Ambiguity January 20, 2016 06:08PM |
Registered: 10 years ago Posts: 14,672 |
Re: G-Code Ambiguity January 20, 2016 06:21PM |
Registered: 10 years ago Posts: 580 |
Re: G-Code Ambiguity January 20, 2016 06:47PM |
Registered: 8 years ago Posts: 9 |
Re: G-Code Ambiguity January 20, 2016 06:56PM |
Registered: 8 years ago Posts: 9 |
Re: G-Code Ambiguity January 21, 2016 07:37AM |
Registered: 8 years ago Posts: 9 |
Re: G-Code Ambiguity January 21, 2016 02:47PM |
Registered: 10 years ago Posts: 580 |
Re: G-Code Ambiguity January 21, 2016 07:26PM |
Registered: 8 years ago Posts: 9 |
Re: G-Code Ambiguity January 21, 2016 08:01PM |
Admin Registered: 13 years ago Posts: 6,995 |
Re: G-Code Ambiguity January 21, 2016 08:43PM |
Registered: 8 years ago Posts: 9 |
Re: G-Code Ambiguity January 21, 2016 09:15PM |
Registered: 8 years ago Posts: 9 |
Re: G-Code Ambiguity January 21, 2016 10:01PM |
Registered: 10 years ago Posts: 580 |
Re: G-Code Ambiguity January 21, 2016 10:15PM |
Registered: 8 years ago Posts: 9 |
Re: G-Code Ambiguity January 22, 2016 08:16AM |
Registered: 13 years ago Posts: 7,616 |
Quote
SE
I'm writing firrnware to process commands sent to my code, and I'm trying to make it compatible with as many slicers and printer hosts as possible. So it looks like I'll need to support multiple representations of the same command ie. (G1, G01, g001, etc)
Generation 7 Electronics | Teacup Firmware | RepRap DIY |
Re: G-Code Ambiguity January 22, 2016 12:23PM |
Registered: 8 years ago Posts: 9 |
Quote
Traumflug
Such a wheel was invented long time ago already. At 30 to 50 CPU clocks per character, Teacup's parser is blazingly fast. Faster than characters coming in over a 115200 baud serial line even on a 16 MHz ATmega. It parses each character immediately, so no processing phase when a line is completed. And it handles G1, G01, g001 just fine.