BUG on RepRap firmware V. 20100628 July 02, 2010 07:39AM |
Registered: 14 years ago Posts: 356 |
// Our interrupt function ISR(TIMER1_COMPA_vect) { (...)This interrupt code does the step signal for stepper drivers, and so it's frequency change accordantly the distance and velocity, on this piece of code:
// wait for next step. // Use milli- or micro-seconds, as appropriate // If the only thing that changed was f keep looping if(real_move) { timestep = t_scale*current_steps.f; timestep = calculate_feedrate_delay((float) timestep); setTimer(timestep); }
11:11:06 Echo >>Echo: N1902 G1 X6.64 Y2.45 Z1.96 F720.0 *51 11:11:06 Send >>SendData: N1904 G1 X6.62 Y2.64 Z1.8 F801.882 *9 11:11:06 Echo >>Echo: command done 11:11:06 Echo >>Echo: N1903 G1 X6.65 Y2.63 Z1.85 F1433.813 *15 11:11:06 Send >>SendData: N1905 G1 F15000.0 *89 11:11:06 Echo >>Echo: command done 11:11:06 Echo >>Echo: N1904 G1 X6.62 Y2.64 Z1.8 F801.882 *9 <--- LONG PAUSE!!! 11:11:50 Send >>SendData: N1906 G1 E20.09 *86 11:11:50 Echo >>Echo: command done 11:11:50 Echo >>Echo: N1905 G1 F15000.0 *89 11:11:50 Send >>SendData: N1907 G1 F801.882 *84 11:11:51 Echo >>Echo: command doneI added another echo string at the end of command when it is executed, on that way I could know the time the firmware/AVR took to execute it -- it begins when it's does echo the gcode line and ends when echoes "command done".
11:11:06 Echo >>Echo: N1903 G1 X6.65 Y2.63 Z1.85 F1433.813 *15 11:11:06 Echo >>Echo: N1904 G1 X6.62 Y2.64 Z1.8 F801.882 *9 <--- LONG PAUSE!!! -0.03 +0.01 -0.05
// find the dominant axis. // NB we ignore the f values here, as it takes no time to take a step in time :-) total_steps = max(delta_steps.x, delta_steps.y); total_steps = max(total_steps, delta_steps.z); total_steps = max(total_steps, delta_steps.e);
Re: BUG on RepRap firmware V. 20100628 July 08, 2010 04:34AM |
Admin Registered: 16 years ago Posts: 476 |
Re: BUG on RepRap firmware V. 20100628 July 08, 2010 04:44AM |
Registered: 14 years ago Posts: 356 |
Re: BUG on RepRap firmware V. 20100628 July 08, 2010 07:09AM |
Registered: 13 years ago Posts: 7,616 |
Quote
jmarsden
As a practical matter, you might want to investigate what is causing your host software to generate such unusual Gcode.
Quote
casainho
That's why I want to go for a OpenSource and DIY fast ARM9 @ 454MHz and with JTAG debug, so I can at least see the variables values and find the problem.
Generation 7 Electronics | Teacup Firmware | RepRap DIY |
Re: BUG on RepRap firmware V. 20100628 July 08, 2010 07:16AM |
Registered: 14 years ago Posts: 356 |
Re: BUG on RepRap firmware V. 20100628 July 08, 2010 07:28AM |
Registered: 13 years ago Posts: 7,616 |
Quote
Here is one video I did recorded while debugging an ARM Cortex M3 LPC1768:
Generation 7 Electronics | Teacup Firmware | RepRap DIY |
Re: BUG on RepRap firmware V. 20100628 July 08, 2010 07:36AM |
Registered: 14 years ago Posts: 356 |
Re: BUG on RepRap firmware V. 20100628 July 08, 2010 08:27AM |
Registered: 13 years ago Posts: 7,616 |
Generation 7 Electronics | Teacup Firmware | RepRap DIY |
Re: BUG on RepRap firmware V. 20100628 July 08, 2010 08:59AM |
Registered: 14 years ago Posts: 356 |
Re: BUG on RepRap firmware V. 20100628 July 08, 2010 09:25AM |
Registered: 13 years ago Posts: 7,616 |
Quote
RepRap uses Makerbot boards
Generation 7 Electronics | Teacup Firmware | RepRap DIY |
Re: BUG on RepRap firmware V. 20100628 July 08, 2010 09:53AM |
Registered: 14 years ago Posts: 356 |
Re: BUG on RepRap firmware V. 20100628 July 08, 2010 03:33PM |
Admin Registered: 17 years ago Posts: 1,791 |
Re: BUG on RepRap firmware V. 20100628 July 08, 2010 05:40PM |
Registered: 13 years ago Posts: 103 |
Re: BUG on RepRap firmware V. 20100628 July 09, 2010 04:57AM |
Registered: 14 years ago Posts: 356 |
Re: BUG on RepRap firmware V. 20100628 July 11, 2010 06:45PM |
Registered: 13 years ago Posts: 103 |