How fast can a Gen 3 Electronics Print?

James,

Thanks. I just tried to compile in Arduino 021 and I got a lot of errors.

Quote

In file included from FiveD_GCode_Interpreter.cpp:9:
extruder.h: In constructor 'extruder::extruder(char, float)':
extruder.h:199: error: 'digitalWriteFast' was not declared in this scope
extruder.h: In member function 'void extruder::setDirection(bool)':
extruder.h:286: error: 'digitalWriteFast' was not declared in this scope
extruder.h:288: error: 'digitalWriteFast' was not declared in this scope
...

Could it be because the macro is expecting constants instead of variables?

I think there maybe something else going on. Can you change the lines with errors back to digitalWrite? see if the rest compiles.

I will take a look at it when i get back home tomorrow. good luck and thanks.

this is the same code, but ran thru the sanguino compiler. I did need to make a few changes.
again let me know if there are any issues.
here is the revised version. once more. FiveD_GCode.zip


I hope this improves your speed. like i said there is still more to be done.

jamesdanielv Wrote:
-------------------------------------------------------
> this is the same code, but ran thru the sanguino
> compiler. I did need to make a few changes.
> again let me know if there are any issues.
> here is the revised version. once more.
>
>
> I hope this improves your speed. like i said there
> is still more to be done.

Initially the writeFast didnt worked for me, so i changed all back to normal digitalWrites and it worked allright, with occasion i noticed this is the first FiveD release i see to fix its own Linenumber error. All other releases were not able to adjust the linenumber when getting a resend which was causing each line of gcode to be sent 3 times (or pause-resume was fixing it manually). Further on the machine was to get stuck at random stages.

I think the writeFast might need pinmodeFast also (i think it didnt had any of those). Havent tested it for speed yet though, just wanted to report that its soooooo..... nice to see it fixing its own resend linenumber errors. I think its actually the first FiveD release i saw to be able to fix this. On the down side i see linenr errors more often now (yet this may be an impression), but at least its able to fix itself - instead turning them into fatal. If others want to test with repsnapper, just so you know it needs "ok " before the "T:" case in process_g_code to get repsnapper interpret the temps correctly (the old reply style).