Home › Repetier-Firmware
serial com error system io ports
Доброго времени суток.
Заказал 3D-принтер MC2. Всё благополучно приехало. После сборки принтера и прошивки микроконтроллера установил и настроил Repetier-Host 1.6.2. Подсоединение к принтеру проходит успешно. Вентилятор работает, хот-энд греется, путь по осям отображается, но шаговые двигатели не реагируют на управление.

Сразу после подсоединения к принтеру появляется сообщение об ошибке:
Ошибка com-порта:System.IO.Ports.SerialErrorReceivedEventArgs
Далее в журнале появляется строка:
echo:???????????????? ??????????????????: 0
Что это может значить и как исправить?
Пробовал переустанавливать Repetier-Host, устанавливать Pronterface. Не помогает.
Первоначально заметил, что ШД, которые были в комплекте, по названию на корпусе (PL42H48-D5) не соответствуют указанным в перечне (17HS8401J4PW550_MC5). По техническим характеристикам PL42H48-D5 его рабочий ток равен 2,4А. У используемых мной драйверов MP4988 (были в комплекте) максимальный входной ток 2А. Возможно ли, что двигатели не реагируют из-за этого несоответствия характеристик?
Заранее спасибо.
-
01-14-2014, 04:26 PM
#1

Student
Error in Repetier Host : System.IO.Ports.SerialErrorReceivedEventArgs [Gen 3]
Hi, I have a solidoodle 3rd gen and I get this error every time I hit «connect» in repetier host:
14:21:47.503 : Serial com error:System.IO.Ports.SerialErrorReceivedEventArgs
I saw this on the installing drivers page on the solidoodle website, and i followed the steps and
it didn’t fix it, however I saw something odd, in device manager it just says «USB Serial Port (Com 4)» where
the solidoodle website says it should say something like «USB Serial (Communication Class, Abstract Control Model) (Com 4)» so I don’t know if that has something to do with it.
Thanks!
Tags for this Thread

Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
- BB code is On
- Smilies are On
- [IMG] code is On
- [VIDEO] code is On
- HTML code is Off
Forum Rules
- Remove From My Forums
-
Question
-
I am getting Exceptions while trying to Connect/Reconnect from the port using Microsoft Dot Net 2.0 Serial Port Component.
The Following Settings are used:
1.Parity-None
2.Stop Bits-One
3.Baud Rate-9600
4.Handshake-None
When i said Connect/Reconnect I literally mean connect and Disconnect serial port (plug in and plug out).
I am getting the System.IO.Ports.SerialErrorReceivedEventArgs exception
with following properties
base: {System.IO.Ports.SerialErrorReceivedEventArgs}
EventType : FrameCode Example:
SerialPort serialPort = new SerialPort();
serialPort.ErrorReceived += HabndleError;
serialPort.DataReceived += HandleDataReceived;serialPort.PortName = «COM1»
serialPort.Parity = Parity.None;
serialPort.StopBits = StopBits.One;
serialPort.DataBits = 8;
serialPort.BaudRate = 9600;serialPort.Open();
private void HandleDataReceived(object sender, SerialDataReceivedEventArgs e)
{
//Do Something
}private void HabndleError(object sender, SerialErrorReceivedEventArgs e)
{
MessageBox.Show(e.ToString());
}Thanks in advance
Answers
-
There is always a start bit to indicate a byte is coming down the line. You’ll have one or two stop bits, it’s a setting. If the stop bit isn’t detected, you get a framing error. StopBits.None is not supported by any real hardware.
Hans Passant.
-
Marked as answer by
Tuesday, August 12, 2008 3:20 AM
-
Marked as answer by
-
The bottom line is that you have received invalid data and this has to be handled. The event is how the SerialPort (and the UART) tells you that.
If you are receiving streaming data (from a GPS for example) just discard the current message. If you are receiving data in response to a command or question (AT command for a modem for example), you can try to retransmitt the command. But how you handle it is really up to you and how the connected device works — there is no standard way.
Some more info about start and stop bits: The serial port is asynchronous which in this case means that it doesn’t need a separate clock signal. Instead the serial stream is synchronized with start and stop bits and the bits inbetween (the transmitted character) is sampled with a free running clock in the receiver (based on the baud rate). You can say that this clock is resynched for every new start bit.
The voltage on the serial port pins can have one of two valid levels — High or low. When there is no transmitting the voltage is low and the receiver is waiting for a start bit, which is a high voltage level. When the receiver now sees a high voltage (for a minimum amount of time, depending on the baudrate) it interprets this as a start bit. After this it samples the voltage on the serial line 8 times (or rather the number of databits the uart is set for) with time intervals that is depending on the baud rate. These 8 bits is the received character (one byte). If parity is used, one more bit, the parity bit, is also sampled. At the next bit position the receiver expects to see a stop bit, which is a low level voltage. If at this time, there instead is a high voltage level, the receiver knows that something is wrong and this is called a framing error since the frame in which one character should have been received is invalid.
A framing error can occur if the serial port connector is connected in the middle of a character. The first high voltage level is then interpreted as a start bit (which it isn’t) and if the sampling where the expected stop bit is supposed to be isn’t low (which it very likely can be), you get a framing error.
/Ruben
RJJournal-
Marked as answer by
jack 321
Tuesday, August 12, 2008 3:20 AM
-
Marked as answer by
Hello RepRap Community!
i have built my first RepRap Prusa with Sanguinololu Electronics and installed the Repetier Firmware onto it.
My problem is, that sometimes i am able to move my axes for some seconds but i can’t get it stable. I always get errors after time, or it won’t connect at all.
Heres my log from the host:
12:59:32.361 : start
12:59:32.391 : N0 M110 *3
12:59:32.391 : N1 M115 *7
12:59:32.393 : N3 M111 S6 *68
12:59:32.393 : N4 M80 *63
12:59:32.441 : FIRMWARE_NAME:Repetier_ PROTOCOL_VERSION:1.0 MACHINE_TYPE:Mendel EXTRstart
12:59:32.443 : N6 M220 S100 *71
12:59:32.443 : N7 M221 S100 *71
12:59:32.456 : Error: expected line 1 got 6
12:59:32.456 : Resend:1
12:59:32.461 : Resend: N1 M115 *7
12:59:32.463 : skip 7
12:59:32.463 : Resend: N3 M111 S6 *68
12:59:32.463 : Resend: N4 M80 *63
12:59:32.466 : Resend: N6 M220 S100 *71
12:59:32.466 : Resend: N7 M221 S100 *71
12:59:32.486 : N8 M111 S6 *79
12:59:32.486 : FIRMWARE_NAME:Repetier_0.71 FIRMWARE_URL:[github.com] PROTOCOL_VERSION:1.0 MACHINE_TYPE:Mendel EXTRUDER_COUNT:1 REPETIER_PROTOCOL:1
12:59:32.488 : N9 M220 S100 *72
12:59:32.498 : N10 M221 S100 *113
12:59:32.501 : N11 M111 S6 *119
12:59:32.506 : start
12:59:32.506 : Unknown command:
12:59:32.710 : Resend:1
12:59:32.710 : Receiving only error messages. Stopped communication.
13:00:34.012 : start
13:00:34.015 : N0 M110 *3
13:00:34.015 : N1 M115 *7
13:00:34.017 : N3 M111 S6 *68
13:00:34.030 : start
13:00:34.030 : Error:Binary cmd wrong checksum.
13:00:34.030 : Resend:1
13:00:34.030 : Receiving only error messages. Stopped communication.
I am using repetier host 0.82b. I don’t know what to do
I checked my cable and my connection, firmware uploads fine everytime so there should be no problem with the connection.
I am using Windows.
Any ideas that could help?
Thanks in Advance
kugel
Your log shows clearly that your sanguino gets reset every now and then. You see this at the «start» messages which are always printed at the start of the firmware.
So your plan must be identifying the reason for the reset. Start with a naked sanguino and no hardware attached. There are many reasons for a reset like brown out, wrong pin configuration, no enough memory, …
Start also with a firmware without user interface, sd card and eeprom support. If you have a 644 processor it doesn’t fit into the controller the same time and sd card uses much ram, so not using it makes sure it is no ram issue.
Repetier-Software — the home of Repetier-Host (Windows, Linux and Mac OS X) and Repetier-Firmware.
Repetier-Server — the solution to control your printer from everywhere.
Visit us on Facebook and Twitter!
Hi repetier,
thank you for your answer. I compiled the firmware without SD and EEPROM support and it connected immediately. But there are still errors:
14:11:37.604 : N1 T0 *27
14:11:37.604 : N0 M110 *3
14:11:37.604 : N1 M115 *7
14:11:37.604 : N3 M111 S6 *68
14:11:37.620 : N4 M80 *63
14:11:37.635 : FIRMWARE_NAME:Repetier_0.71 FIRMWARE_URL:[github.com] PROTOCOL_VERSION:1.0 MACHINE_TYPE:Mendel EXTRUDER_COUNT:1 REPETIER_PROTOCOL:1
14:11:37.635 : N5 M220 S100 *68
14:11:37.635 : N6 M221 S100 *70
14:11:37.635 : N7 M111 S6 *64
14:11:37.651 : Resend:5
14:11:37.666 : Resend: N5 M220 S100 *68
14:11:37.666 : Resend: N6 M221 S100 *70
14:11:37.666 : Resend: N7 M111 S6 *64
14:11:38.207 : Resend:8
14:11:38.410 : Resend:8
14:11:38.612 : Resend:8
I also detached the Steppers. How can i remove the user interface support?
Thank you
ui support is by default off if you didn’t enable it in uiconfig.h.
You log looks a bit like you have used Arduino 1.0 and have set receive cache size in host > 63. If you do this, the host will send more commands then allowed at once and you get such frequent resend errors. Older sanguino had 127 byte buffers, but perhaps this changed with the latest update.
Repetier-Software — the home of Repetier-Host (Windows, Linux and Mac OS X) and Repetier-Firmware.
Repetier-Server — the solution to control your printer from everywhere.
Visit us on Facebook and Twitter!
Hi again,
i really had the buffer set to 64! I set it back to 63 and now there are no more resends.
But now i have the problem that the commands are waiting. First it did not send the first 4 commands at all, on the second or third try this happened:
14:50:37.505 : N0 M110 *3
14:50:37.505 : N1 M115 *7
14:50:37.505 : N3 M111 S6 *68
14:50:37.520 : FIRMWARE_NAME:Repetier_0.71 FIRMWARE_URL:[github.com] PROTOCOL_VERSION:1.0 MACHINE_TYPE:Mendel EXTRUDER_COUNT:1 REPETIER_PROTOCOL:1
14:50:37.520 : N4 M220 S100 *69
14:50:37.520 : N5 M221 S100 *69
14:50:37.536 : N6 M111 S6 *65
14:50:37.551 : N7 M80 *60
14:50:45.850 : N11 G91 *1
14:50:45.850 : N12 G1 X-100 F4800 *53
14:50:45.850 : N13 G90 *2
14:50:46.750 : start
14:50:48.863 : SD init fail
14:50:52.350 : N2 G91 *51
14:50:52.350 : N3 G1 X-100 F4800 *5
14:50:52.350 : N4 G90 *52
14:50:57.108 : N7 G91 *54
14:50:57.108 : N8 G1 X10 F4800 *19
14:50:57.108 : N9 G90 *57
14:51:02.171 : N12 G91 *2
I moved the x-achsis around a bit and then the commands started to be queued again. What could the reason for this behavior be?
Okay now the resends happened again:
14:56:45.715 : N0 M110 *3
14:56:45.715 : N1 M115 *7
14:56:45.725 : N3 M111 S6 *68
14:56:45.745 : N4 M220 S100 *69
14:56:45.745 : N5 M221 S100 *69
14:56:45.745 : FIRMWARE_NAME:Repetier_0.71 FIRMWARE_URL:[github.com] PROTOCOL_VERSION:1.0 MACHINE_TYPE:Mendel EXTRUDER_COUNT:1 REPETIER_PROTOCOL:1
14:56:45.748 : N6 M111 S6 *65
14:56:49.878 : N9 G91 *56
14:56:49.878 : N10 G1 X-10 F4800 *7
14:56:49.878 : N11 G90 *0
14:56:49.961 : Error: expected line 12 got 7
14:56:49.961 : Resend:12
14:56:50.170 : Resend:12
14:56:50.361 : Resend:12
14:56:50.570 : Resend:12
14:56:50.777 : Resend:12
14:56:50.970 : Resend:12
14:56:51.179 : Resend:12
14:56:51.370 : Resend:12
14:56:51.577 : Resend:12
14:56:51.786 : Resend:12
14:56:52.090 : Resend:12
14:56:52.375 : N13 G91 *3
14:56:52.375 : N14 G1 X10 F4800 *46
14:56:52.377 : N15 G90 *4
14:56:53.390 : N16 G91 *6
14:56:53.390 : N17 G1 X10 F4800 *45
14:56:53.390 : N18 G90 *9
14:56:54.647 : N19 G91 *9
14:56:54.647 : N20 G1 X10 F4800 *41
14:56:54.649 : N21 G90 *3
14:56:54.665 : start
14:56:56.761 : SD init fail
14:56:56.968 : Resend:1
14:57:01.255 : Resend:3
14:57:02.918 : N4 G91 *53
14:57:02.918 : N5 G1 X10 F4800 *30
14:57:02.920 : N6 G90 *54
14:57:04.695 : N8 G91 *57
14:57:04.695 : Resend:8
14:57:04.712 : start
14:57:04.712 : N1 G1 X10 F4800 *26
14:57:04.712 : N2 G90 *50
14:57:06.822 : SD init fail
14:57:06.822 : Error:Binary cmd wrong checksum.
14:57:06.822 : Resend:1
14:57:06.824 : Resend: N1 G1 X10 F4800 *26
14:57:06.827 : Resend: N2 G90 *50
14:57:06.839 : Error:Binary cmd wrog checksum.
14:57:06.839 : Resend:1
14:57:06.842 : Resend: N1 G1 X10 F4800 *26
14:57:06.842 : Resend: N2 G90 *50
14:57:06.854 : Resend:3
14:57:07.046 : Resend:3
14:57:07.384 : Resend:3
I hope this can help you identify my problem.
For some implentation reasons, the serial buffer is always 1 less then set, so 63 for 64 byte buffer is necessary.
Your log shows that you have sd card support (intention), which fails but takes eventually some seconds to do so. There are also some initalizations after a restart (which the host forces on connections). So normally the x commands waiting disappear after a few seconds of wait if connection is successfull.
I saw
14:50:46.750 : start
which indicates a reset. Was that you with the emergency stop button or the printer? If it was the printer your resets are still there. and you still need to find the reason. One reson might be the stepper driver. Some are delivered with faults that cause different kinds of trouble. Try also with them removed and if it works for some moves (which you now cant see 🙂 you can start adding them back one by one to see if one of them causes the troubles.
Repetier-Software — the home of Repetier-Host (Windows, Linux and Mac OS X) and Repetier-Firmware.
Repetier-Server — the solution to control your printer from everywhere.
Visit us on Facebook and Twitter!
If you see lines like
14:56:54.665 : start
your board has restarted, which is a second source for resend errors. After a reset line counter starts at 1 again mismatching lines from before the start.
Repetier-Software — the home of Repetier-Host (Windows, Linux and Mac OS X) and Repetier-Firmware.
Repetier-Server — the solution to control your printer from everywhere.
Visit us on Facebook and Twitter!
Now it looks like this:
15:38:21.234 : Serial com errorystem.IO.Ports.SerialErrorReceivedEventArgs 15:42:15.112 : Serial com error
ystem.IO.Ports.SerialErrorReceivedEventArgs 15:42:17.416 : Serial com error
ystem.IO.Ports.SerialErrorReceivedEventArgs 15:42:17.580 : Serial com error
ystem.IO.Ports.SerialErrorReceivedEventArgs 15:42:17.598 : Resend:1 15:42:17.598 : Receiving only error messages. Stopped communication.
what do they mean?
I read another thread where you helped another user. I modded my atx psu so that the 12V output is stabilized rather than the 5V like normal, it is quite stable. Nevertheless now I tried without my atx supply now — only usb. Still does not work like you can see 
kugel Wrote:
——————————————————-
> Now it looks like this:
>
>
> 15:38:21.234 : Serial com
> error
ystem.IO.Ports.SerialErrorReceivedEventArgs
>
> 15:42:15.112 : Serial com
> error
ystem.IO.Ports.SerialErrorReceivedEventArgs
>
> 15:42:17.416 : Serial com
> error
ystem.IO.Ports.SerialErrorReceivedEventArgs
>
> 15:42:17.580 : Serial com
> error
ystem.IO.Ports.SerialErrorReceivedEventArgs
>
> 15:42:17.598 : Resend:1
> 15:42:17.598 : Receiving only error messages.
> Stopped communication.
>
> what do they mean?
>
I think you are giving me not enough informations. What did you do to get this, how did the log start, what have you tried. If the com gets to much resend errors, the host will clos et he connection, which is what I see.
> I read another thread where you helped another
> user. I modded my atx psu so that the 12V output
> is stabilized rather than the 5V like normal, it
> is quite stable. Nevertheless now I tried without
> my atx supply now — only usb. Still does not work
> like you can see 
PC PSU are always a good source for instabilities, yes. But have you removed the stepper or what else have you done?
Repetier-Software — the home of Repetier-Host (Windows, Linux and Mac OS X) and Repetier-Firmware.
Repetier-Server — the solution to control your printer from everywhere.
Visit us on Facebook and Twitter!
Sorry for not giving you enough information 
The errors in my last post show up after clicking «connect» in the host interface. Nothing else was clicked. I have disconnected everything except the usb cable and removed the pololus.
I could connect the printer to a LiPo battery, that would be the most stable power source i can imagine. The PSU is quite stable when i charge my LiPo batterys with it, meaning the voltage is regulated pretty good (ca 12.23V at 20-300W).
Edited 2 time(s). Last edit at 12/15/2012 10:18AM by kugel.
Testing the naked board with usb only should be enough. That way I already tested many boards with success.
I misread the latest log entry. This message comes from windows serial driver, meaning it had troubles with the connection it self. You could try reconnecting the usb cable to reinitialize the usb connection it self.
I hope you always disconnect power/usb before changing hardware?
I got this error also some times, but reinitializing usb connection worked most of the times. Sometimes I needed to reboot to get it working again. With all my testing it no wonder that I get sometimes such errors. Hope something of this works for you, too.
Repetier-Software — the home of Repetier-Host (Windows, Linux and Mac OS X) and Repetier-Firmware.
Repetier-Server — the solution to control your printer from everywhere.
Visit us on Facebook and Twitter!
Okay i restarted windows, still the same. Then i plugged it into another usb port on another controller and still the same. I will try to get a shorter usb-cable and try it again when i get one. I am using a 3m cable i got with my electronics kit, maybe this is the problem. The cable works fine with my normal printer though.
I don’t think it is the cable if it worked before. You could look into the hardware manager if the serial device shows up without errors.
Repetier-Software — the home of Repetier-Host (Windows, Linux and Mac OS X) and Repetier-Firmware.
Repetier-Server — the solution to control your printer from everywhere.
Visit us on Facebook and Twitter!
Hmm, yes it shows up and does not give any errors. It’s always on COM3 no matter where i attach it to, so this is not the problem either. Most of the time the commands are just waiting, even those which are sent when clicking connect.
I just managed to get it to do just something but nothing good. Here’s my complete log from the Workdirectory:
< 16:58:01.983 : OpenGL version:4.3.0
< 16:58:01.983 : OpenGL extensions:GL_AMD_multi_draw_indirect GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_blend_func_extended GL_ARB_clear_buffer_object GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_conservative_depth GL_ARB_compute_shader GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_draw_buffers GL_ARB_draw_buffers_blend GL_ARB_draw_indirect GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_ES2_compatibility GL_ARB_ES3_compatibility GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_no_attachments GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_gpu_shader5 GL_ARB_gpu_shader_fp64 GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_internalformat_query2 GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment GL_ARB_map_buffer_range GL_ARB_multi_draw_indirect GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_program_interface_query GL_ARB_provoking_vertex GL_ARB_robust_buffer_access_behavior GL_ARB_robustness GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_separate_shader_objects GL_ARB_shader_atomic_counters GL_ARB_shader_bit_encoding GL_ARB_shader_image_load_store GL_ARB_shader_image_size GL_ARB_shader_objects GL_ARB_shader_precision GL_ARB_shader_storage_buffer_object GL_ARB_shader_subroutine GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shading_language_420pack GL_ARB_shading_language_include GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_stencil_texturing GL_ARB_sync GL_ARB_tessellation_shader GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_buffer_range GL_ARB_texture_compression GL_ARB_texture_compression_bptc GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_cube_map_array GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_gather GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_levels GL_ARB_texture_query_lod GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_storage GL_ARB_texture_storage_multisample GL_ARB_texture_swizzle GL_ARB_texture_view GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_transform_feedback_instanced GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_attrib_64bit GL_ARB_vertex_attrib_binding GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_texture_float GL_ATI_texture_mirror_once GL_S3_s3tc GL_EXT_texture_env_add GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_Cg_shader GL_EXT_depth_bounds_test GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXTX_framebuffer_mixed_formats GL_EXT_framebuffer_multisample_blit_scaled GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_shader_objects GL_EXT_separate_specular_color GL_EXT_shader_image_load_store GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA8888 GL_EXT_texture_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_texture_type_2_10_10_10_REV GL_EXT_timer_query GL_EXT_transform_feedback2 GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_EXT_vertex_attrib_64bit GL_EXT_import_sync_object GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_KHR_debug GL_KTX_buffer_region GL_NV_alpha_test GL_NV_blend_minmax GL_NV_blend_square GL_NV_complex_primitives GL_NV_compute_program5 GL_NV_conditional_render GL_NV_copy_depth_to_color GL_NV_copy_image GL_NV_depth_buffer_float GL_NV_depth_clamp GL_NV_draw_texture GL_NV_ES1_1_compatibility GL_NV_explicit_multisample GL_NV_fbo_color_attachments GL_NV_fence GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragdepth GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_framebuffer_multisample_coverage GL_NV_geometry_shader4 GL_NV_gpu_program4 GL_NV_gpu_program4_1 GL_NV_gpu_program5 GL_NV_gpu_program_fp64 GL_NV_gpu_shader5 GL_NV_half_float GL_NV_light_max_exponent GL_NV_multisample_coverage GL_NV_multisample_filter_hint GL_NV_occlusion_query GL_NV_packed_depth_stencil GL_NV_parameter_buffer_object GL_NV_parameter_buffer_object2 GL_NV_path_rendering GL_NV_pixel_data_range GL_NV_point_sprite GL_NV_primitive_restart GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_shader_atomic_counters GL_NV_shader_atomic_float GL_NV_shader_buffer_load GL_NV_shader_storage_buffer_object GL_NV_texgen_reflection GL_NV_texture_barrier GL_NV_texture_compression_vtc GL_NV_texture_env_combine4 GL_NV_texture_expand_normal GL_NV_texture_lod_clamp GL_NV_texture_multisample GL_NV_texture_rectangle GL_NV_texture_shader GL_NV_texture_shader2 GL_NV_texture_shader3 GL_NV_transform_feedback GL_NV_transform_feedback2 GL_NV_vertex_array_range GL_NV_vertex_array_range2 GL_NV_vertex_attrib_integer_64bit GL_NV_vertex_buffer_unified_memory GL_NV_vertex_program GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_NV_vertex_program3 GL_NVX_conditional_render GL_NVX_gpu_memory_info GL_OES_compressed_paletted_texture GL_OES_depth24 GL_OES_depth32 GL_OES_depth_texture GL_OES_element_index_uint GL_OES_fbo_render_mipmap GL_OES_get_program_binary GL_OES_mapbuffer GL_OES_packed_depth_stencil GL_OES_point_size_array GL_OES_point_sprite GL_OES_rgb8_rgba8 GL_OES_read_format GL_OES_standard_derivatives GL_OES_texture_3D GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_array_object GL_OES_vertex_half_float GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture GL_SGIX_shadow GL_SUN_slice_accum GL_WIN_swap_hint WGL_EXT_swap_control
< 16:58:01.983 : OpenGL renderer:GeForce GTX 580/PCIe/SSE2
< 16:58:01.998 : Using fast VBOs for rendering is possible
> 16:58:13.893 : omstart
< 16:58:13.940 : N1 T0 *27
< 16:58:13.940 : N0 M110 *3
< 16:58:13.940 : N1 M115 *7
< 16:58:13.940 : N3 M111 S6 *68
< 16:58:13.940 : N4 M80 *63
> 16:58:16.139 : SD init fail
> 16:58:16.155 : Error:Binary cmd wrong che?????????j?{????? [email protected]?kP?l?Z??X`??p?????????????n?????? [email protected]?oP?p?Z??X`??p????????????V?j?{????? [email protected]?sP?t?Z??X`??p?????????=?#??n?????? [email protected]?gP?h?Z??X`??p???????
> 16:58:16.155 : Resend:1
> 16:58:16.170 : ok
> 16:58:16.170 : ok 0
< 16:58:16.170 : Resend: N1 M115 *7
> 16:58:16.170 : Unknown command:
> 16:58:16.170 : error writing to file
> 16:58:16.170 : Unknown command:
> 16:58:16.170 : Unknown command:
> 16:58:16.170 : Unknown command:
> 16:58:16.170 : Unknown command:
> 16:58:16.170 : Unknown command:
> 16:58:16.170 : Unknown command:
> 16:58:16.170 : Unknown command:
> 16:58:16.170 : Unknown command:
> 16:58:16.170 : Unknown command:
> 16:58:16.170 : Unknown command:
> 16:58:16.170 : Unknown command:
> 16:58:16.170 : Unknown command:
< 16:58:16.170 : Resend: N3 M111 S6 *68
< 16:58:16.170 : Resend: N4 M80 *63
> 16:58:16.170 : Unknown command:
> 16:58:16.170 : Unstart
> 16:58:18.370 : SD init fail
> 16:58:18.370 : Error:Binary cmd wrong checksum.
> 16:58:18.573 : Resend:1Resend:1
> 16:58:18.588 : ok
< 16:58:18.588 : Resend: N0 M110 *3
< 16:58:18.588 : Resend: N1 M115 *7
< 16:58:18.588 : Resend: N3 M111 S6 *68
< 16:58:18.588 : Resend: N4 M80 *63
> 16:58:18.588 : ok
> 16:58:18.588 : ok 1
< 16:58:18.604 : Serial com error
ystem.IO.Ports.SerialErrorReceivedEventArgs
> 16:58:18.620 : FIRMWARE_NAME:Repetier_0.71 FIRMWARE_URL:[github.com] P?????????????????`?????????h?q?j??Y???n????a?q??H???8S?+?k?q??n?q??????H????d?q??H???8S?+?n?q??a?q??????H????g?q??H???8S?+?a?q??d?q??????H??#??n?????? [email protected]?gP?h?Z??X`??p?????????????j?{????? [email protected]?kP?l?Z??X`??p?????????????n?????? [email protected]?oP?p?Z??X`??p????????????V?j?{????? [email protected]?sP?t?Z??X`??p???????start
< 16:58:18.620 : N7 M220 S100 *70
< 16:58:18.620 : N8 M221 S100 *72
> 16:58:20.804 : SD init fail
> 16:58:20.850 : Done saving file.
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Un?nown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
> 16:58:20.850 : Unknown command:
< 16:58:20.850 : Serial com error
ystem.IO.Ports.SerialErrorReceivedEventArgs
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknow? command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
> 16:58:20.882 : Unknown command:
< 16:58:20.882 : Serial com error
ystem.IO.Ports.SerialErrorReceivedEventArgs
> 16:58:20.897 : Unknown command:
> 16:58:20.897 : Unknown command:
> 16:58:20.897 : Unknown command:
> 16:58:20.897 : Unknown command:
> 16:58:20.897 : Unknown command:
> 16:58:20.897 : Unknown command:
> 16:58:20.897 : Unknown command:
> 16:58:20.897 : Unknown command:
> 16:58:20.897 : Unknown command:
> 16:58:20.897 : Unknown command:
> 16:58:20.897 : Unknown command:
> 16:58:20.897 : Unknown command:
> 16:58:20.897 : Unknown command:
> 16:58:20.897 : Unknown command:
> 16:58:20.913 : Unknown command:
> 16:58:20.913 : Unknown command:
> 16:58:20.913 : Unknown command:
> 16:58:20.913 : Unknown command:
> 16:58:20.913 : Unknown command:
> 16:58:20.913 : Unknown command:
> 16:58:20.913 : Unknown command:
> 16:58:20.913 : Unknown command:
> 16:58:20.913 : Unknown command:
> 16:58:25.780 : Unknown command:
> 16:58:25.780 : Unknown command:
> 16:58:25.780 : Unknown command:
> 16:58:25.780 : Unknown command:
Edited 1 time(s). Last edit at 12/15/2012 11:10AM by kugel.
Doesn’t look to good.
Why do I see
> 16:58:16.170 : error writing to file or > 16:58:20.850 : Done saving file.
That indicates you are uploading a gcode to the firmware. I didn’t see commands starting upload nor should it work with sd card not inserted.
The many errors especially the output seem like the baudrates don’t match. What baudrate are you using?
Also what sanguino firmware version did you use from www.sanguino.cc and which board type did you select? If you have selected the 20MHz Sanguino board that could perhaps explain the problems.
Repetier-Software — the home of Repetier-Host (Windows, Linux and Mac OS X) and Repetier-Firmware.
Repetier-Server — the solution to control your printer from everywhere.
Visit us on Facebook and Twitter!
Hi repetier,
i have selected 250000 baud in the firmware and in the host. I used the «Gen7 Arduino IDE Support 2.0» because i read that they were more up to date and selected a «Gen7 with ATMEGA 644P and 16Mhz».
Is this the problem perhaps? I will try the ones from www.sanguino.cc and report back.
Thank you very very much!
Edited 1 time(s). Last edit at 12/17/2012 06:08AM by kugel.
still the same with Sanguino 0101r1 and it tries to write to a file again 
Edited 1 time(s). Last edit at 12/17/2012 06:09AM by kugel.
You really should disable sd card for testing. I mean compiling without sd support!
I have the feeling that you are using more ram then you have. This would also get rid of the writing messages.
Repetier-Software — the home of Repetier-Host (Windows, Linux and Mac OS X) and Repetier-Firmware.
Repetier-Server — the solution to control your printer from everywhere.
Visit us on Facebook and Twitter!
Hi!
I meant to compile it without SD support, thought that this was necessary to achieve this:
*/ #define EEPROM_MODE 0 /** Comment out (using // at the start of the line) to disable SD support: */ #define SDSUPPORT 0
I did not mean to ignore your suggestions! Just thought that the above statements disabled EEPROM and SD support 
I found that the source and drain of the hotend mosfet where shorted and removed the bridge that the solder had built — could it be that i damaged something by shorting those pins?
EDIT:
okay i found the option to show the free RAM and uploaded the firmware with it enabled. The Log:
17:46:22.501 : start 17:46:22.533 : N0 M110 *3 17:46:22.533 : N1 M115 *7 17:46:22.533 : N3 M111 S6 *68 17:46:22.533 : N4 M80 *63 17:46:22.548 : start 17:46:24.732 : SD init fail 17:46:24.732 : Free RAM:768 17:46:24.732 : Free RAM:747 17:46:24.763 : error writinstart 17:46:26.963 : Serial com errorystem.IO.Ports.SerialErrorReceivedEventArgs 17:46:26.979 : SD init fail 17:46:26.979 : Free RAM:719 17:46:26.979 : error writistart 17:46:29.178 : SD init fail 17:46:29.178 : Free RAM:717 17:46:29.178 : error writingstart 17:46:31.370 : SD init fail 17:46:31.370 : Free RAM:717 17:46:31.370 : error writstart
Maybe this could help….
Edited 2 time(s). Last edit at 12/17/2012 12:03PM by kugel.
You need to do
//#define SDSUPPORT 0
to disable sd support
Repetier-Software — the home of Repetier-Host (Windows, Linux and Mac OS X) and Repetier-Firmware.
Repetier-Server — the solution to control your printer from everywhere.
Visit us on Facebook and Twitter!
Hi again,
i am so sorry for misreading the comment line for disabling SD card support…
Uploaded firmware again and still not working:
18:32:23.752 : Free RAM:1373 18:32:23.767 : N0 M110 *3 18:32:23.767 : N1 M115 *7 18:32:23.767 : N3 M111 S6 *68 18:32:23.783 : FIRMWARE_NAME:Repetier_0.71 FIRMWARE_URL:[github.com] PROTOCOL_VERSION:1.0 MACHINE_TYPE:Mendel EXTRUDER_COUNT:1 REPETIER_PROTOCOL:1 18:32:23.783 : Free RAM:1372 18:32:23.783 : N4 M220 S100 *69 18:32:23.783 : N5 M221 S100 *69 18:32:23.799 : N6 M111 S6 *65 18:32:23.814 : N8 M80 *51 18:32:25.374 : Resend:9 18:32:25.561 : Resend:9 18:32:25.764 : Resend:9 18:32:25.983 : Resend:9 18:32:26.170 : Resend:9 18:32:26.373 : Resend:9 18:32:26.622 : Resend:9 18:32:26.825 : Resend:9 18:32:27.075 : Resend:9 18:32:27.168 : start 18:32:27.168 : Free RAM:1381 18:32:27.215 : Free RAM:1375 18:32:32.972 : Free RAM:1366
It seems that i am only able to connect to the board if i have just uploaded the firmware. After some minutes the commands are only queued — is that possible?
A friend of mine will visit later and i will test his board, which i also built.
Maybe theres something wrong with my atmega 
Ok, now we see you have enough ram. You have to disable memory check for production run, it can cause crashes etc as the memory check interferes normal operation in some cases.
In a other thread (german) was a similar problem. The reason there was a wrong coil with 100uH for the temp. sensor. That caused a brown out that nobody could explain. Replacing it with a 10uH coil helped. That guy could also only connect after a firmware upload.
Having made the board yourself, did you do the same?
The problem that communication stops in your case are the frequent resets I guess. If they are not recogniced, communication hangs.
Repetier-Software — the home of Repetier-Host (Windows, Linux and Mac OS X) and Repetier-Firmware.
Repetier-Server — the solution to control your printer from everywhere.
Visit us on Facebook and Twitter!
Okay i’m pretty sure that would be a problem. I bought a kit from xyzprinters.com i hope that all parts are the right ones. But it does not seem like sanguinololu has any coils (RepRap.org assemby instructions). I just cleaned the PCB from the remaining flux but this also did not help.
Now i am again not able to connect to the board — very strange.
I also speak german (and write) if you prefer it, you’re definitely the only one helping.
EDIT: Now i am even not able to upload firmware anymore 
Edited 1 time(s). Last edit at 12/17/2012 02:54PM by kugel.
It looks more and more like a hardware issue. If uploading fails i guess resets continue during upload and now even more frequent. So your cleaning worsened the problem. If you find the bridge or defect part it will probably start working again.
Perhaps the sanguino of your friend gives more informations.
Repetier-Software — the home of Repetier-Host (Windows, Linux and Mac OS X) and Repetier-Firmware.
Repetier-Server — the solution to control your printer from everywhere.
Visit us on Facebook and Twitter!
Hi again,
yes the board works! But only after i cleaned it, too. But there are no errors and i did not change anything in the firmware configuration!
Now i just have to find the problem on the other board.
But one of the Polulus on his board is not working, its overheating the 5V Regulator. Is that possible to fix?
kugel Wrote:
——————————————————-
> Hi again,
>
> yes the board works! But only after i cleaned it,
> too. But there are no errors and i did not change
> anything in the firmware configuration!
Ok, that is good.!
> Now i just have to find the problem on the other
> board.
>
> But one of the Polulus on his board is not
> working, its overheating the 5V Regulator. Is that
> possible to fix?
I’m no electronics expert. I would replace it before risking permanent damage on the board. If it is defect you should still have warranty on it!
Repetier-Software — the home of Repetier-Host (Windows, Linux and Mac OS X) and Repetier-Firmware.
Repetier-Server — the solution to control your printer from everywhere.
Visit us on Facebook and Twitter!
Okay i will contact my supplier!
Now i have another problem: the x-axis won’t home. When i click home, the axis stays where it is and the x-coordinate in the host shows xmax (200) as current coordinate.
I tried various inverting of endstops settings and inverting the x-achsis homing direction in the FW but they did not help. My x-endstop is at x-max
What should i do ?
Edited 1 time(s). Last edit at 12/18/2012 05:29AM by kugel.
Use M119 to test if the endstop works as expected. It shows the endstop state. So test open and closed and see if the signal changes. If it doesn’t change you have your reason, why the motor does not home. Endstop setting depend on type (pullup, invert). From your description I guess it is interpreted always closed. Might also be the wrong pin number. In pins.h you have normally xmax pins -1 set, which is none. Give it the pin number of xmin and set xmin to -1 in this case. Best is to copy the 2 defines in you configuration.h after the pins.h is included.
Repetier-Software — the home of Repetier-Host (Windows, Linux and Mac OS X) and Repetier-Firmware.
Repetier-Server — the solution to control your printer from everywhere.
Visit us on Facebook and Twitter!
Thank you very much now it works 
Contents
- 1 Introduction
- 2 Main improvements and features
- 2.1 Specifications
- 2.2 Safety Instructions
- 2.3 Assembly
- 2.4 Install the drivers and software
- 2.4.1 Install the drivers
- 2.4.2 Install Software
- 2.5 How To set up
- 2.6 Leveling The Print Bed
- 2.6.1 Leveling the bed with a piece of paper
- 2.6.2 Leveling the bed with a dial indicator
- 2.7 Belt Tensioning
- 2.8 How to control on LCD
- 2.9 How to print off-line with GEEETECH I3
- 2.10 Slic3r Manual
- 2.11 FAQs & SOLUTIONs
- 2.12 where to get
Introduction
![]()
This acrylic frame Prusa Mendel I3 3D printer is designed and manufactured by Shenzhen Getech Co., Ltd based on Reprap pursa I3, Geeetech I3 features simple assembly, easy debugging and more stable performance. The acrylic structure makes the printer less complex and easy to operate.As you can see from the above pictures, we provide two Acrylic I3, black one and tranparant one.
Main improvements and features
1.Further simplified structure means fast assembly and easy adjustment, which saves you both time and energy as well as speeds up the molding of your innovative products and ideas. It usually takes up to 3 days for a DIYer to assemble the previous I3, not to mention the post-adjustment and debugging work. As to this I3 of Acrylic Frame, however, you can save 70% of time.
2.Enhanced stability and reliability. Geeetech I3 adopts 8 mm-thick acyclic plates, also you can choose the piano-black one and the transparent one, and both colors look good.
3.The PSU (power supply unit) is assembled together with the printer; which saves you a lot of space and can avoid unnecessary electrical trouble.
4.All the cables and wires are well arranged to make it more neat and easy to operate.
5.MK8 extruder ensures smaller layers and higher resolution, make models and objects.
Specifications
Printing specifications:
Print technology: Fused Filament Fabrication.
Build volume: 200 x200x180mm
Layer resolution: 0.1-0.3mm
Positioning Precision: 0.1-0.3mm
Filament diameter: 1.75mm, 3mm
Nozzle diameter: 0.3mm, 0.35mm, 0.4 mm, 0.5mm
Filament type: ABS/ PLA
Software:
Operating system: Windows/Mac/Linux
Control software: Repetier-Host, Printrun
File format: .STL
Temperature:
Max heated bed temperature: about 110°C
Max extruder temperature: about 240°C
Electrical:
Power supply:
input: 115V/1.5A 230V/0.75A
Output:DC12V/0-15A
Connectivity: USB, SD card (support off-line printing)
Mechanical:
Body: Acrylic plate of 8 mm thickness (black/ transparent)
Build Platform: Borosilicate glass + MK2A heatbed
XYZ Rods: Wear-resistant, stainless steel
Stepper Motors: 1.8° step angle with 1/16 micro-stepping
Physical structure: Reprap
Safety Instructions
We recommend the following practice instructions for the safe and effective use of our printers. Failure to follow these practice instructions may
(i) degrade your printer’s performance;
(ii) cause injury and/or damage;
(iii) disqualify you from customer support. Please ensure that you have read and understand all practice instructions before using your Prusa I3 printer for the first time.
You can contact the Prusa I3 Customer Support Team with any questions about the practice instructions at our [forum].
Operation
- Never reach inside your Prusa I3 printer when it is turned on. Moving parts can cut or pinch you, and several parts reach high temperatures that can cause burns and other injuries.
- Always allow your Prusa I3 printer to cool down for at least 5 minutes before you touch any internal part or remove a printed object.
- Never leave your Prusa I3 printer unattended while printing or powered on.
- Always turn off your Prusa I3 printer and disconnect it from your computer when not in use.
- Never attempt to print using any materials that have not been approved by Prusa I3.
- Keep the nozzle tip at least two inches away from the heated build platform anytime you are not running a print job.
- Never operate your Prusa I3 printer if it appears damaged.
- In case of an emergency or malfunction, immediately disconnect your Prusa I3 printer from the power outlet and computer.
Placement
- Always operate your Prusa I3 printer in an open, well-ventilated area to allow potentially irritating fumes to dissipate.
- Never operate your Prusa I3 printer outdoors, near open windows, or anywhere where it may be exposed to water or moisture.
- Always place your Prusa I3 printer on a flat and sturdy surface to avoid power interruptions and deformities in your prints.
- Never place objects on or above your Prusa I3 printer or power supply.
- Always have a working fire and smoke alarm in the same room as your Prusa I3 printer.
- Never place your Prusa I3 printer near open flames, heat sources, or flammable materials.
Connectivity
To avoid printing interruptions, disable your screensaver, sleep, and hibernate functions on your computer.
- Make sure the heating plate and extruder are not heated when starting software.
Power
- Plug your computer and Prusa I3 printer into the same power outlet for best performance.
- We recommend plugging your Prusa I3 printer into a surge protector with a circuit breaker.
Never attempt to open or fix your power supply. If you believe your power supply is not working properly, contact us asap.
- Only use the power supply that was provided with your Prusa I3 printer.
- Do not plug your Prusa I3 printer into the same outlet as power hungry devices such as air conditioners, space heaters, or other large appliances.
Modifications
Prusa I3 printers are tested for performance and safety before they leave the factory. Prusa I3 cannot guarantee the performance or safety of printers that have been modified by users.
Warnings
- THERE IS A RISK OF ELECTRICAL SHOCK. UNIT IS NOT USER SERVICEABLE.
- Prusa I3 PRINTERS CONTAIN HEATED MOVING PARTS. NEVER REACH INSIDE THE PRINTER WHILE IT IS IN OPERATION OR BEFORE IT HAS COOLED DOWN.
- NEVER LEAVE YOUR Prusa I3 PRINTER UNATTENDED WHILE POWERED ON OR PRINTING.
- DISCONNECT YOUR Prusa I3 PRINTER FROM THE POWER SUPPLY AND COMPUTER WHEN NOT IN USE.
- DO NOT ATTEMPT TO PRINT MATERIALS NOT APPROVED BY Prusa I3.
- ONLY OPERATE YOUR Prusa I3 PRINTER IN A WELL-VENTILATED SPACE AWAY FROM MOISTURE AND HEAT SOURCES WITH A WORKING SMOKE/FIRE ALARM.
Assembly
assembly manual for the new 5mm one
assembly manual for the new 8mm one
Install the drivers and software
Install the drivers
Installing Drivers
Before printing, you’ll need to install drivers. The kind of driver that a Prusa I3 requires in order to operate properly is called a USB Serial Driver. A USB Serial Driver is software that establishes a COM port.
Plug the USB into a USB port on your computer. Windows Update should automatically find and install the drivers. You’re done with installing the drivers!
Windows 8
When you attempt to install the unsigned 3rd party driver on Windows 8, you will most likely not be able to install because the file is not digitally signed. To get around this restriction, you must temporarily remove this restriction by following the instructions here .
Once you have followed the directions to disable driver signature enforcement, download the driver and click to install. This is only a temporary change, however, and restarting your computer after you have installed the driver will return your computer to its normal state.
Note that this involves restarting your computer, so make sure to close out all other windows. You may want to print out these instructions so you can refer to them while your computer is restarting.
Windows Manual Install
Note: In some cases the drivers will not install on their own. The drivers for Windows can be found in the following link:
drivers for GT2560 and Sanguinololu
Drivers for rapms 1.4
If the driver was not automatically installed, you may see this screen:
In this case,
a. Click “Change Settings…”
b. Select “Install driver software from Windows Update”.
c. Click “Save Changes”. The FTDI drivers should now install successfully.
Attention: For those having difficulty selecting your COM port
If you have installed the USB serial driver successfully and you are still not able to connenct to your printer in Repetier Host, then windows has not recognized the newly installed driver.
In Repetier Host, you may even notice an error message that is similar to this one:
Serial com error:System.IO.Ports.SerialErrorReceivedEventArgs
In some situations, a computer running windows will not automatically recognize a newly installed Serial driver. This means that you will have to update your newly installed driver manually.
To manually update the driver, you will first need to plug the USB cable into your printer and attache the other end directly to one of your computer’s USB ports. Now, enter the ‘Device Manager’ in Windows and navigate to the hardware category called Ports (COM & LPT) and then left click on it once. You should notice the Ports category expand to reveal a Sub-Category called USB Serial (Communication Class, Abstract Control Model) (COM X); where X is the COM port number. You should be looking for that COM port number in Repetier Host after this procedure is completed; which can be found in “Printer Settings.”
You will need to right click on the USB Serial Sub-class and select proprties. In the drivers tab you will find a selection to update drivers, click on Update Drivers to access the next menu.
Now that you have selected which driver to update, you will have to tell Windows where the “updated” driver can be found. You should be presented with two options. Select “Browse my computer for driver software” to locate and install the driver software manually.
Next, you will be greeted by a menu that allows you to “Browse for driver software on your computer” You will be presented with two choices, select “Let me pick from a list of device drivers on my computer.” Now select the Serial port device and proceed with the installation.
That is pretty much all there is to it. You will then see an installation indicator bar.
Once the installation is complete you will be notified that “Windows has successfully updated your driver software.” You will be prompted to restart your computer; you should do so.
Macbook (OS X) Manual Install
Download link of driver: http://www.ftdichip.com/Drivers/VCP.htm
Download the driver that is compatible with system version.
Open the downloaded file, you will see a .pkg file, Open «FTDIUSBSerial.pkg»
Click «Continue» in Instruction.
Click «Continue» in Read me.
Click «Continue» in License.
Click «Agree» to continue installation.
Select the installing destination and click «Continue».
Click «Install» in Installatin Type.
Mac will start to install the driver:

Once your computer restarts, try selecting the appropriate COM port and baud rate in Repetier Host and then connect.
Install Software
we will take windows OS as an example.
To install all required software by Prusa I3, please follow the steps provided below.
1) Download and install: RepetierGEtechSetup.exe
step 1,start the installer,choose the display language.
step 2,click next to continue
step3,select the destination where you would like to install the RepetierGEtechSetup.
step4,select start menu folder and create a shortcut, click next to continue.
step 5,get ready to install. Click install.
step 6,wait about half a minute while installing. The green bar will show you the rate.
step 7,set up has finished the installing, you can choose to launch it immediately or exit out.
2) Plug the power cord into a wall outlet and the USB cable into a USB port on your computer. Windows should detect your motherboard and assign the appropriate driver.
3) Open Repetier Host and Connect to your Prusa I3!
Click on the Manual Controls Tab and click in a direction X or Y to test your connection.
If you are having difficulty connecting, please review the following supportive documentation: Installing Drivers and How to connect.
Please note that if you have difficulty connecting, there might have been an issue with the installation process. Ensure that the following have been installed:
Download and install the Serial Driver.
Download and install Microsoft .netFrameWork 3.5
In Mac, you can download Repetier for Mac» at:
-
- http://www.repetier.com/w/?wpdmdl=1777
After downloading, open «Repetier-Host-Mac_56.dmg»,then you will see the icon of «Repetier Host», open it.
How To set up
How to Connect
1. Plug the USB into your Prusa I3 and the other end into your computer.
Do not be alarmed if the standard messages do not appear. Because of the Prusa I3’s drivers, it may show up as a generic USB device.
2. Power on the Prusa I3. You can see the LED lights and fan come to life! You may be able to hear the motors idling.
3. Open Repetier Host and ensure that you have a valid port selected for communications. To do this simply, click “Printer Settings” in the upper right-hand corner to bring up the printer settings menu.
4, Select GEEEtech PI3A in “Printer”
5. Select the corresponding COM port, click OK to continue.
If you can not fond the COM port, click “refresh ports” and see if it appears. (It is usually the last one; you can check the device manager to see which port it is). PS: if you still cannot find the port, please reinstall your USB driver.
In Mac, you should finish step 5 in «Printer>Printer settings», step 4 is unnecessary
6. Hit «connect» in the upper left-hand corner, select GEEEtech PI3A. You should see the details of the connection in the console window in the bottom section of the screen. if your pronter is other models, you can select it, if you are not sure, you can skip it and connect directly.
If it turned green, it is connected.
7. On the right panel, click the «Manual Control» tab. Scroll down and click both heat extruder and heat print bed buttons to activate your heaters. You will know they are on if they turn a bright blue.
The heat will gradually rise, as you will see from the status bar on the bottom of the window. The extruder should be set to 195° and the bed should be set to 95°.
8. At the same time, you can click the arrows on the above panel to move the motors to check if they work well.
9. Click “load” to load the STL. File you need to print.
You can see now the model in the cubic box and on the right of the panel, you can see the loading bar.
10. After loading, choose “slicer” > “configure” to set the printing configurations. You may need to wait for a minute.
11. First, you need to set the layers and perimeters. As you can see in the following picture, all you need to set is the layer height and the first layer height. Leave the rest as default. (For each setting, you can get a prompt to refer)
12. Set the printing infill density and pattern. Refer to the prompt.
13. Set the printing speed. Again, refer to the prompt.
14. Filament setting. You just need to fill in the correct filament diameter.
15. After setting, do not forget to save the settings and name each setting.
16. Select the settings you save on the right panel. Then click the “Slice with slice3r”to generate G- code. You may have to wait for a while.
17 click slicer button and slice with Slic3r.
You can see the small window on the screen, the duration for the generation of G-code depends on the size of your file. It may take 1-2 minutes.
After that, you can see the code in G-code editor.
There are two parameters deserves your attention.
One is the bed temperature, another is the extruder temperature.
- Here is a temp reference.
Filament Type Bed temp Extruder temp PLA 50-100 190-210 ABS 70-110 220-240
if you are not familiar with Slic3r, you can read this Manual to start.
Leveling The Print Bed
Getting the bed level in relation to the X and Y axis is very important for getting prints to stick well and is one of the first steps you should do when receiving your Delta . The first layer might have the right amount of squish in one area, but if another part of the bed is too low, that part of the print is more likely to come unstuck and begin to warp. The level is adjusted with the spring loaded screws, two at the front and one at the back. If you are using the standard kapton tape on the build platform and not a sheet of glass, you will need to poke holes in the tape in order to turn the leveling screws or print some thumbscrews and use a little super glue to screw them onto the bottom of the leveling screws. We suggest using the thumbscrew route so that you do not have to damage your kapton tape.
Leveling the bed with a piece of paper
You can check the level of the heated platform by using a piece of paper to check the gap under the nozzle. It’s best to do this with the platform heated to account for any change due to expansion.
Put the paper under the nozzle near one of the front screws and raise the bed .1mm at a time using the manual controls in the software interface while sliding the paper back and forth. Stop when you feel the nozzle start to grab a little bit.
Move the nozzle to the other front screw and adjust the screw until you get the same amount of friction as you felt with the first one. Then adjust the back screw the same way. Once you have adjusted each of the three screws, go back and check each one again, since adjusting one screw can affect another. You shouldn’t need to go around the bed more than twice.
Leveling the bed with a dial indicator
The best way to level the bed is with a dial indicator. This uses a spring loaded plunger to detect changes in distance. You can mount one the the front of the extruder, and zero the reading at one corner of the bed. The watch for the readout to change as you move it around the bed and adjust the screws accordingly. If the fit is too loose for the tab on your gauge, you can use a few pieces of tape to thicken it up.
Belt Tensioning
There are 3 belts to be adjusted on your Prusa I3. These steps will guide you through adjusted them.
Tools:
2.5 mm hex driver
1.5 mm hex driver
Steps
1. As always, before trying to work on any part of your Prusa I3, make sure that both the bed and extruder are turned off to prevent burns. Lowering the bed will also keep it out of the way so that you can access all the necessary parts more easily.
2. To test the belts, you need to be able to move the belts. This requires the motors to be turned off. Go to the Manual Control tab in Repetier Host and click the stop motors button. You should now be able to move the extruder around without much resistance.
3. Pull the extruder forward and out of your way.
4. Using the 2.5 mm hex driver, loosen the four 4 screws on the left side of your printer. This will allow the Y motor to move up and down. Note that you do not need to completely remove these screws as there is no need to remove this motor from the printer.
5. Using your hand, lift the Y motor enough to take the short loop of belt off the pulley attached to the motor. This belt is the source of most trouble with printing circles. If this is the only belt you wish to adjust, you can skip to step 11.
6. Loosen the screws on the inside of the pulleys on the left and right end of the back horizontal rod using your 1.5 mm hex driver.
Make sure the back horizontal rod is centered by feeling the bearings that hold it on either side of the printer. You want to make sure it is even.
7. Push the extruder back and forwards. This movement should naturally align the belts, so that the back rod should not be moving side to side.
8. Once the belts are aligned, you can tighten the pulleys again with the 1.5 mm hex driver. The screws should be tight enough to hold on to the rod, but be careful not to strip the screws.
9. Put the short loop of belt back on the Y motor pulley by again lifting the motor up.
10. Make sure the two pulleys that the short loop of belt is on are aligned. If they are not, you can loosen the screw on the pulley on the back rod and carefully nudge it into place. Once it is aligned with the pulley on the y motor, tighten the screw.
11. Push the Y motor down firmly to draw the belt taut, and tighten the screws on the left side of the printer one-by-one to hold the motor in place.
12. Check that you can move the extruder back and forth. It may be a little resistant.
13. Slide the extruder forward so you can check the tension of the bottom belts behind the y carriages. These belts should be not too tight but not too loose. The most important thing is that they are of roughly equal tension.
14. You can tighten or loosen the bottom belts by adjusting the screw on the back of the y carriages with a 2.5 mm hex driver.
15. Now slide the extruder back to check the tension of the bottom belts in front of the y carriages. Again, these belts should be not too tight and not too loose. Using a 2.5 mm hex driver on the screws on the front of the y carriages, adjust the belts so that they are of roughly equal tension.
16. If the belts are still not moving smoothly, there may be a problem with the pulley alignment on the back horizontal rod. Using your 1.5 mm hex driver, loosen the screw on the pulleys so that you can move them into alignment, then tighten to hold them in place. This step can take some trial and error until you get everything properly aligned.
How to control on LCD
1.How to print from LCD
Note:
- 1)If you do not set the temperature of extruder and hot bed in g-code, you should manually heat up extruder and hotbed to proper temperature before printing.
- 2)If you do not set letting all the axes auto home in g-code, you should manually let all the axes auto home first.
- Press the button>»Print from SD»>Choose the file you want to print and press button.
![]()
2.How to let all the axes auto home
- Press button on LCD> “Prepare”>“Auto home”
3.How to move the axis and extruder motor separately
- Press the button>”Prepare”>”Move axis”>”Move 10mm/1mm/0.1mm”>”Move X/Y/Z/extruder”>Rotate the button> Press button
Note: The extruder motor can not move unless the temperature is more than 180 degrees.
![]()
![]()
![]()
4.What if you can not move the axis with you hand
Press the button>“Prepare”>”Disable steppers”
![]()
5.How to set the temperature of extruder
Press the button>“Control”>”Temperature”>”Nozzle”>Rotate the button>Press the button
![]()
![]()
![]()
6.How to set the temperature of hot bed
“Control”>”Temperature”>”Bed”>Rotate the button
![]()
![]()
![]()
How to print off-line with GEEETECH I3
After leveling, you can print now, with an SD card, you are allowed to do off-line printing, here is a step by step instruction on how to set up for off-line printing:
Tip: It is recommended to use an SD card with the memory size less than 1G.
1.Open the software, and load the STL file to the slicer software, as shown below:
2. Click “Slice with Slic3r” under “Slicer” tab, as shown below:
3. The time for generating code depends on the size of model:
4. After generating the code of G-code, it will automatically skip to “G-code editor”, as shown the figure below:
5. Click “save job” to save G-code file into your SD card (Note: Do not put it into any folder)

6 Plug the SD card into the slot on the back of the LCD panel.
7 turn on your printer; wait for about 30 seconds you can hear the LCD panel light up and the fan and motors are activated.
8. After about 30 seconds, you can see the “Geeetech I3B is ready” on the LCD panel.
9. Now you can choose “ print from SD card”
10. Choose the G-code file you have saved in the card.
11, now you can see the heatbed is heating, the temperature is rising very quickly.
After the heatbed is heated to the rated temperature, the extruder will begin heating.
12. When you see “heating done”, the printer will begin printing immediately.
Slic3r Manual
This manual was written by Gary Hodgson.
Slic3r is a tool which translates digital 3D models into instructions that are understood by a 3D printer. It slices the model into horizontal layers and generates suitable paths to fill them.
Slic3r is already bundled with the many of the most well-known host software packages: Pronterface, Repetier-Host, ReplicatorG, and can be used as a standalone program.
This manual will provide guidance on how to install, configure and utilise Slic3r in order to produce excellent prints.
FAQs & SOLUTIONs
1.Fixing Extruder Jams and Flow Problems
2.How to unblock a nozzle
3.FAQs OF 3D printing
where to get
1. geeetech official oline store
I do not have eeprom activated… perhaps this is part of the problem??? Here is my configuration.h file:
/*
This file is part of Repetier-Firmware.
Repetier-Firmware is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
Foobar is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with Repetier-Firmware. If not, see <http://www.gnu.org/licenses/>.
*/
#ifndef CONFIGURATION_H
#define CONFIGURATION_H
// BASIC SETTINGS: select your board type, thermistor type, axis scaling, and endstop configuration
//// The following define selects which electronics board you have. Please choose the one that matches your setup
// MEGA/RAMPS up to 1.2 = 3,
// RAMPS 1.3/RAMPS 1.4 = 33
// Gen6 = 5,
// Sanguinololu up to 1.1 = 6
// Sanguinololu 1.2 and above = 62
// Gen7 1.1 and above = 7
// Teensylu (at90usb) = 8 // requires Teensyduino
// Printrboard (at90usb) = 9 // requires Teensyduino
#define MOTHERBOARD 5
#include <avr/io.h>
#include «pins.h»
// ##########################################################################################
// ## IMPORTANT ##
// ##########################################################################################
// For easy configuration, the default settings enable parameter storage in EEPROM.
// This means, after the first upload many variables can only be changed using the special
// M commands as described in the documentation. Changing these value sin the configuration.h
// has no effect. Parameters overriden by EEPROM settings are calibartion values, extruder
// values except thermistor tables and some other parameter likely to change during usage
// like advance steps or ops mode.
// To override EEPROM settings with config settings, set EEPROM_MODE 0
// ##########################################################################################
// ## Calibration ##
// ##########################################################################################
/* brief Number of steps for a 1mm move in x direction. Overridden if EEPROM activated. /
#define XAXIS_STEPS_PER_MM 33.33333333
/* brief Number of steps for a 1mm move in y direction Overridden if EEPROM activated./
#define YAXIS_STEPS_PER_MM 33.33333333
/* brief Number of steps for a 1mm move in z direction Overridden if EEPROM activated./
#define ZAXIS_STEPS_PER_MM 1280
// ##########################################################################################
// ## Extruder configuration ##
// ##########################################################################################
/** Number of extruders. Maximum 2 extruder. */
#define NUM_EXTRUDER 1
#define EXT0_X_OFFSET 0
#define EXT0_Y_OFFSET 0
// for skeinforge 40 and later, steps to pull the plasic 1 mm inside the extruder, not out. Overridden if EEPROM activated.
#define EXT0_STEPS_PER_MM 279
// What type of sensor is used?
// 1 is 100k thermistor (Epcos B57560G0107F000 — RepRap-Fab.org and many other)
// 2 is 200k thermistor
// 3 is mendel-parts thermistor (EPCOS G550)
// 4 is 10k thermistor
// 5 is userdefined thermistor table 0
// 6 is userdefined thermistor table 1
// 7 is userdefined thermistor table 2
// 50 is userdefined thermistor table 0 for PTC thermistors
// 51 is userdefined thermistor table 0 for PTC thermistors
// 52 is userdefined thermistor table 0 for PTC thermistors
// 99 Generic thermistor table
// 100 is AD595
// 101 is MAX6675
#define EXT0_TEMPSENSOR_TYPE 5
// Position in analog input table below for reading temperatures or pin enabling SS for MAX6675
#define EXT0_TEMPSENSOR_PIN 0
// WHich pin enables the heater
#define EXT0_HEATER_PIN HEATER_0_PIN
#define EXT0_STEP_PIN E_STEP_PIN
#define EXT0_DIR_PIN E_DIR_PIN
// set to false/true for normal / inverse direction
#define EXT0_INVERSE false
#define EXT0_ENABLE_PIN E_ENABLE_PIN
// For Inverting Stepper Enable Pins (Active Low) use 0, Non Inverting (Active High) use 1
#define EXT0_ENABLE_ON false
// The following speed settings are for skeinforge 40+ where e is the
// length of filament pulled inside the heater. For repsnap or older
// skeinforge use hiher values.
// Overridden if EEPROM activated.
#define EXT0_MAX_FEEDRATE 1200
// Feedrate from halted extruder in mm/s
// Overridden if EEPROM activated.
#define EXT0_MAX_START_FEEDRATE 10
// Acceleration in mm/s^2
// Overridden if EEPROM activated.
#define EXT0_MAX_ACCELERATION 10000
/** Type of heat manager for this extruder.
- 0 = Simply switch on/off if temperature is reached. Works always.
- 1 = PID Temperature control. Is better but needs good PID values. Defaults are a good start for most extruder.
Overridden if EEPROM activated.
/
#define EXT0_HEAT_MANAGER 1
/* Wait x seconds, after reaching target temperature. Only used for M109. Overridden if EEPROM activated. */
#define EXT0_WATCHPERIOD 20
/** brief The maximum value, I-gain can contribute to the output.
A good value is slightly higher then the output needed for your temperature.
Values for starts:
130 => PLA for temperatures from 170-180°C
180 => ABS for temperatures around 240°C
The precise values may differ for different nozzle/resistor combination.
Overridden if EEPROM activated.
/
#define EXT0_PID_INTEGRAL_DRIVE_MAX 180
/* brief lower value for integral part
The I state should converge to the exact heater output needed for the target temperature.
To prevent a long deviation from the target zone, this value limits the lower value.
A good start is 30 lower then the optimal value. You need to leave room for cooling.
Overridden if EEPROM activated.
/
#define EXT0_PID_INTEGRAL_DRIVE_MIN 50
/* P-gain in 0,01 units. Overridden if EEPROM activated. /
#define EXT0_PID_PGAIN 500
/* I-gain in 0,001 units
WATCH OUT: This value was in 0,01 units in earlier versions!
Overridden if EEPROM activated.
/
#define EXT0_PID_IGAIN 1
/* Dgain in 0,01 units. Overridden if EEPROM activated./
#define EXT0_PID_DGAIN 3000
// maximum time the heater is can be switched on. Max = 255. Overridden if EEPROM activated.
#define EXT0_PID_MAX 255
/* brief Faktor for the advance algorithm. 0 disables the algorithm. Overridden if EEPROM activated.
K is the factor for the quadratic term, which is normally disabled in newer versions. If you want to use
the quadratic factor make sure ENABLE_QUADRATIC_ADVANCE is defined.
L is the linear factor and seems to be working better then the quadratic dependency.
*/
#define EXT0_ADVANCE_K 0.0f
#define EXT0_ADVANCE_L 0.0f
// =========================== Configuration for second extruder ========================
#define EXT1_X_OFFSET 0
#define EXT1_Y_OFFSET 0
// for skeinforge 40 and later, steps to pull the plasic 1 mm inside the extruder, not out. Overridden if EEPROM activated.
#define EXT1_STEPS_PER_MM 373
// What type of sensor is used?
// 1 is 100k thermistor (Epcos B57560G0107F000 — RepRap-Fab.org and many other)
// 2 is 200k thermistor
// 3 is mendel-parts thermistor (EPCOS G550)
// 4 is 10k thermistor
// 5 is userdefined thermistor table 0
// 6 is userdefined thermistor table 1
// 7 is userdefined thermistor table 2
// 50 is userdefined thermistor table 0 for PTC thermistors
// 51 is userdefined thermistor table 0 for PTC thermistors
// 52 is userdefined thermistor table 0 for PTC thermistors
// 99 Generic thermistor table
// 100 is AD595
// 101 is MAX6675
#define EXT1_TEMPSENSOR_TYPE 1
// Position in analog input table below for reading temperatures or pin enabling SS for MAX6675
#define EXT1_TEMPSENSOR_PIN 1
// WHich pin enables the heater
#define EXT1_HEATER_PIN -1
#define EXT1_STEP_PIN E_STEP_PIN
#define EXT1_DIR_PIN E_DIR_PIN
// set to 0/1 for normal / inverse direction
#define EXT1_INVERSE false
#define EXT1_ENABLE_PIN E_ENABLE_PIN
// For Inverting Stepper Enable Pins (Active Low) use 0, Non Inverting (Active High) use 1
#define EXT1_ENABLE_ON false
// The following speed settings are for skeinforge 40+ where e is the
// length of filament pulled inside the heater. For repsnap or older
// skeinforge use hiher values.
// Overridden if EEPROM activated.
#define EXT1_MAX_FEEDRATE 1500
// Feedrate from halted extruder in mm/s
// Overridden if EEPROM activated.
#define EXT1_MAX_START_FEEDRATE 18
// Acceleration in mm/s^2
// Overridden if EEPROM activated.
#define EXT1_MAX_ACCELERATION 6000
/** Type of heat manager for this extruder.
- 0 = Simply switch on/off if temperature is reached. Works always.
- 1 = PID Temperature control. Is better but needs good PID values. Defaults are a good start for most extruder.
Overridden if EEPROM activated.
/
#define EXT1_HEAT_MANAGER 1
/* Wait x seconds, after reaching target temperature. Only used for M109. Overridden if EEPROM activated. */
#define EXT1_WATCHPERIOD 20
/** brief The maximum value, I-gain can contribute to the output.
A good value is slightly higher then the output needed for your temperature.
Values for starts:
130 => PLA for temperatures from 170-180°C
180 => ABS for temperatures around 240°C
The precise values may differ for different nozzle/resistor combination.
Overridden if EEPROM activated.
/
#define EXT1_PID_INTEGRAL_DRIVE_MAX 130
/* brief lower value for integral part
The I state should converge to the exact heater output needed for the target temperature.
To prevent a long deviation from the target zone, this value limits the lower value.
A good start is 30 lower then the optimal value. You need to leave room for cooling.
Overridden if EEPROM activated.
/
#define EXT1_PID_INTEGRAL_DRIVE_MIN 50
/* P-gain in 0,01 units. Overridden if EEPROM activated. /
#define EXT1_PID_PGAIN 500
/* I-gain in 0,001 units
WATCH OUT: This value was in 0,01 units in earlier versions!
Overridden if EEPROM activated.
/
#define EXT1_PID_IGAIN 1
/* Dgain in 0,01 units. Overridden if EEPROM activated./
#define EXT1_PID_DGAIN 3000
// maximum time the heater is can be switched on. Max = 255. Overridden if EEPROM activated.
#define EXT1_PID_MAX 255
/* brief Faktor for the advance algorithm. 0 disables the algorithm. Overridden if EEPROM activated.
K is the factor for the quadratic term, which is normally disabled in newer versions. If you want to use
the quadratic factor make sure ENABLE_QUADRATIC_ADVANCE is defined.
L is the linear factor and seems to be working better then the quadratic dependency.
*/
#define EXT1_ADVANCE_K 0.0f
#define EXT1_ADVANCE_L 0.0f
/** PID control only works target temperature +/- PID_CONTROL_RANGE.
If you get much overshoot at the first temperature set, because the heater is going full power to long, you
need to increase this value. For one 6.8 Ohm heater 10 is ok. With two 6.8 Ohm heater use 15.
*/
#define PID_CONTROL_RANGE 15
/** Number of entries in the user thermistortable 0. Set to 0 to disable it. /
#define NUM_TEMPS_USERTHERMISTOR0 28
/* Number of entries in the user thermistortable 1. Set to 0 to disable it. /
#define NUM_TEMPS_USERTHERMISTOR1 0
/* Number of entries in the user thermistortable 2. Set to 0 to disable it. /
#define NUM_TEMPS_USERTHERMISTOR2 0
/* brief Set PID scaling
PID values assume a usable range from 0-255. This can be further limited to EXT0_PID_MAX by to methods.
Set the value to 0: Normal computation, just clip output to EXT0_PID_MAX if computed value is too high.
Set value to 1: Scale PID by EXT0_PID_MAX/256 and then clip to EXT0_PID_MAX.
If your EXT0_PID_MAX is low, you should prefer the second method.
*/
#define SCALE_PID_TO_MAX 0
/** Temperature range for target temperature to hold in M109 command. 5 means +/-5°C
Uncomment define to use force the temperature into the range for given watchperiod.
*/
//#define TEMP_HYSTERESIS 5
/** brief Simulate PWM
If your extruder uses a pin without pwm or with a pwm already in use for other functions, you
can enable the PWM simulator instead. Only with PWM you can use PID control.
For Sanguino boards (6 and 62) this is enabled by default. To force simulated PWM uncomment
the define.
*/
//#define SIMULATE_PWM
/** Userdefined thermistor table
There are many different thermistors, which can be combined with different resistors. This result
in unpredictable number of tables. As a resolution, the user can define one table here, that can
be used as type 5 for thermister type in extruder/heated bed definition. Make sure, the number of entries
matches the value in NUM_TEMPS_USERTHERMISTOR0. If you span definition over multiple lines, make sure to end
each line, except the last, with a backslash. The table format is {{adc1,temp1},{adc2,temp2}…} with
increasing adc values. For more informations, read
http://hydraraptor.blogspot.com/2007/10/measuring-temperature-easy-way.html
If you have a sprinter temperature table, you have to multiply the first value with 4 and the second with 8.
This firmware works with increased precision, so the value read goes from 0 to 4095 and the temperature is
temperature*8.
If you have a PTC thermistor instead of a NTC thermistor, keep the adc values increasing and use themistor types 50-52 instead of 5-7!
_/
#define USER_THERMISTORTABLE0 {
{1_4,864_8},{21_4,300_8},{25_4,290_8},{29_4,280_8},{33_4,270_8},{39_4,260_8},{46_4,250_8},{54_4,240_8},{64_4,230_8},{75_4,220_8},
{90_4,210_8},{107_4,200_8},{128_4,190_8},{154_4,180_8},{184_4,170_8},{221_4,160_8},{265_4,150_8},{316_4,140_8},{375_4,130_8},
{441_4,120_8},{513_4,110_8},{588_4,100_8},{734_4,80_8},{856_4,60_8},{938_4,40_8},{986_4,20_8},{1008_4,0_8},{1018_4,-20*8} }
#define USER_THERMISTORTABLE1 {}
#define USER_THERMISTORTABLE2 {}
/** If defined, creates a thermistortable at startup.
If you dont feel like computing the table on your own, you can use this generic method. It is
a simple approximation which may be not as accurate as a good table computed from the reference
values in the datasheet. You can increase precision if you use a temperature/resistance for
R0/T0, which is near your operating temperature. This will reduce precision for lower temperatures,
which are not realy important. The resistors must fit the following schematic:
@code
VREF —- R2 —+— Termistor —+— GND
| |
+—— R1 ——-+
| |
+—- Capacitor —+
|
V measured
@Endcode
If you don’t have R1, set it to 0.
The capacitor is for reducing noise from long thermistor cable. If you don’t have have one, it’s OK.
If you don’t need the generic table, uncomment the following define.
/
//#define USE_GENERIC_THERMISTORTABLE
/* Reference resistance /
#define GENERIC_THERM_R0 1042.7
/* Temperature at reference resistance /
#define GENERIC_THERM_T0 170
/* Beta value of thermistor
You can use the beta from the datasheet or compute it yourself. See
http://reprap.org/wiki/MeasuringThermistorBeta
for more details.
/
#define GENERIC_THERM_BETA 4036
#define GENERIC_THERM_R1 0
#define GENERIC_THERM_R2 4700
#define GENERIC_THERM_VREF 5
/* Supply voltage to ADC, can be changed be setting ANALOG_REF below to different value. /
#define GENERIC_THERM_VADC 5
/* Number of entries in generated table. One entry takes 4 bytes. Higher number of entries increase computation time too. */
#define GENERIC_THERM_NUM_ENTRIES 40
// uncomment the following line for MAX6675 support.
//#define SUPPORT_MAX6675
// ############# Heated bed configuration ########################
/** brief Switches fast between config for heated bed and non heated bed. Default setting is autodetect
assuming only 2 heater outputs are available. */
#if HEATER_1_PIN>-1 && NUM_EXTRUDER==1
#define HAVE_HEATED_BED true
#else
#define HAVE_HEATED_BED false
#endif
//#define HAVE_HEATED_BED false // Override autodetected value
#if HAVE_HEATED_BED==true
// Select type of your heated bed. It’s the same as for EXT0_TEMPSENSOR_TYPE
// set to 0 if you don’t have a heated bed
#define HEATED_BED_SENSOR_TYPE 1
/** Index of analog sensor to read temperature of heated bed.
THIS IS NOT A PIN NUMBER — IT’S A REFERENCE TO A TABLE WITH PIN NUMBERS!!!
Look at ANALOG_INPUT_CHANNELS for the position
or to add the Arduino pin id there. /
#define HEATED_BED_SENSOR_PIN 1
/* brief Pin to enable heater for bed. */
#define HEATED_BED_HEATER_PIN HEATER_1_PIN
// How often the temperature of the heated bed is set (msec)
#define HEATED_BED_SET_INTERVAL 5000
#else
#define HEATED_BED_SENSOR_TYPE 0
#define HEATED_BED_SENSOR_PIN -1
#define HEATED_BED_HEATER_PIN -1
#endif
// uncomment to use AREF for reference voltage
// on a GEN6 you want AVCC
#define USE_AVCC_FOR_TEMP
// how many samples do we want per reading. 1 sample takes 1/125000 seconds.
// more samples get more reliable values, but take more time.
#define ANALOG_SUPERSAMPLE 10
/** The number of analog sensors, we need to read out. These are the thermistors used for temperature
reading of the extruder and heated bed. /
#if HAVE_HEATED_BED==true
#define NUM_ANALOG_SENSORS 2
#else
#define NUM_ANALOG_SENSORS 1
#endif
/* Number of digital temp. sensors like MAX6675 */
#define NUM_DIGITAL_SENSORS 0
#define TEMP_PID true
//// Experimental watchdog and minimal temp
// The watchdog waits for the watchperiod in milliseconds whenever an M104 or M109 increases the target temperature
// If the temperature has not increased at the end of that period, the target temperature is set to zero. It can be reset with another M104/M109
//#define WATCHPERIOD 5000 //5 seconds
//// The minimal temperature defines the temperature below which the heater will not be enabled
#define MINTEMP 5
//// Experimental max temp
// When temperature exceeds max temp, your heater will be switched off.
// This feature exists to protect your hotend from overheating accidentally, but NOT from thermistor short/failure!
// You should use MINTEMP for thermistor short/failure protection.
#define MAXTEMP 275
/**
Normally you need a PWM controlable output, to define different fan speeds. If you
don’t have one, you can only turn your fan on or off.
As a sulution, you can simulate PWM for your pin. This works for all pins, even non-PWM pins!
If your fan is connected to a PWM output that is used by the firmware internally, you must
activate PWM simulation.
To active fan PWM simulation uncomment the next define.
*/
//#define SIMULATE_FAN_PWM
/** brief number of analog input signals. Normally 1 for each temperature sensor /
#define ANALOG_INPUTS NUM_ANALOG_SENSORS
#if ANALOG_INPUTS>0
/* Channels are the MUX-part of ADMUX register
Put all the pin numbers for the analog sensors (temp. sensor for extruder and heated bed) in here.
In the configs of the sensor, use the index in this array. For the typical combination of
one extruder with heated bed, write:
#define ANALOG_INPUT_CHANNELS {TEMP_0_PIN,TEMP_1_PIN}
_/
#if HAVE_HEATED_BED==true
#define ANALOG_INPUT_CHANNELS {TEMP_0_PIN,TEMP_1_PIN}
#else
#define ANALOG_INPUT_CHANNELS {TEMP_0_PIN}
#endif
// Bits of the ADC converter
#define ANALOG_INPUT_BITS 10
// Build median from 2^ANALOG_INPUT_SAMPLE samples
#define ANALOG_INPUT_SAMPLE 5
#define ANALOG_REF_AREF 0
#define ANALOG_REF_AVCC _BV(REFS0)
#define ANALOG_REF_INT_1_1 _BV(REFS1)
#define ANALOG_REF_INT_2_56 _BV(REFS0) | BV(REFS1)
/* brief Used reference, normally ANALOG_REF_AVCC or ANALOG_REF_AREF */
#define ANALOG_REF ANALOG_REF_AVCC
#define ANALOG_PRESCALER _BV(ADPS0)|_BV(ADPS1)|_BV(ADPS2)
#endif
// ##########################################################################################
// ## Endstop configuration ##
// ##########################################################################################
/* By default all endstops are pulled up to high. You need a pullup if you
use a mechanical endstop connected with gnd. Set value to false for no pullup
on this endstop.
*/
#define ENDSTOP_PULLUP_X_MIN true
#define ENDSTOP_PULLUP_Y_MIN true
#define ENDSTOP_PULLUP_Z_MIN true
#define ENDSTOP_PULLUP_X_MAX true
#define ENDSTOP_PULLUP_Y_MAX true
#define ENDSTOP_PULLUP_Z_MAX true
//set to true to invert the logic of the endstops
#define ENDSTOP_X_MIN_INVERTING false
#define ENDSTOP_Y_MIN_INVERTING false
#define ENDSTOP_Z_MIN_INVERTING false
#define ENDSTOP_X_MAX_INVERTING false
#define ENDSTOP_Y_MAX_INVERTING false
#define ENDSTOP_Z_MAX_INVERTING false
//If your axes are only moving in one direction, make sure the endstops are connected properly.
//If your axes move in one direction ONLY when the endstops are triggered, set ENDSTOPS_INVERTING to true here
//// ADVANCED SETTINGS — to tweak parameters
// For Inverting Stepper Enable Pins (Active Low) use 0, Non Inverting (Active High) use 1
#define X_ENABLE_ON 0
#define Y_ENABLE_ON 0
#define Z_ENABLE_ON 0
// Disables axis when it’s not being used.
#define DISABLE_X false
#define DISABLE_Y false
#define DISABLE_Z false
#define DISABLE_E false
// Inverting axis direction
#define INVERT_X_DIR false
#define INVERT_Y_DIR true
#define INVERT_Z_DIR false
//// ENDSTOP SETTINGS:
// Sets direction of endstops when homing; 1=MAX, -1=MIN
#define X_HOME_DIR -1
#define Y_HOME_DIR -1
#define Z_HOME_DIR -1
//If true, axis won’t move to coordinates less than zero.
#define min_software_endstop_x false
#define min_software_endstop_y false
#define min_software_endstop_z false
//If true, axis won’t move to coordinates greater than the defined lengths below.
#define max_software_endstop_x true
#define max_software_endstop_y true
#define max_software_endstop_z true
// If during homing the endstop is reached, ho many mm should the printer move back for the second try
#define ENDSTOP_X_BACK_MOVE 5
#define ENDSTOP_Y_BACK_MOVE 5
#define ENDSTOP_Z_BACK_MOVE 2
// For higher precision you can reduce the speed for the second test on the endstop
// during homing operation. The homing speed is divided by the value. 1 = same speed, 2 = half speed
#define ENDSTOP_X_RETEST_REDUCTION_FACTOR 2
#define ENDSTOP_Y_RETEST_REDUCTION_FACTOR 2
#define ENDSTOP_Z_RETEST_REDUCTION_FACTOR 2
// When you have several endstops in one circuit you need to disable it after homing by moving a
// small amount back. This is also the case with H-belt systems.
#define ENDSTOP_X_BACK_ON_HOME 0
#define ENDSTOP_Y_BACK_ON_HOME 0
#define ENDSTOP_Z_BACK_ON_HOME 0
// You can disable endstop checking for print moves. This is needed, if you get sometimes
// false signals from your endstops. If your endstops don’t give false signals, you
// can set it on for safety.
#define ALWAYS_CHECK_ENDSTOPS true
// maximum positions in mm — only fixed numbers!
#define X_MAX_LENGTH 200
#define Y_MAX_LENGTH 230
#define Z_MAX_LENGTH 112
// ##########################################################################################
// ## Movement settings ##
// ##########################################################################################
/** After x seconds of inactivity, the stepper motors are disabled.
Set to 0 to leave them enabled.
This helps cooling the Stepper motors between two print jobs.
Overridden if EEPROM activated.
/
#define STEPPER_INACTIVE_TIME 120L
/* After x seconds of inactivity, the system will go down as far it can.
It will at least disable all stepper motors and heaters. If the board has
a power pin, it will be disabled, too.
Set value to 0 for disabled.
Overridden if EEPROM activated.
/
#define MAX_INACTIVE_TIME 0L
/* Maximum feedrate, the system allows. Higher feedrates are reduced to these values.
The axis order in all axis related arrays is X, Y, Z
Overridden if EEPROM activated.
/
#define MAX_FEEDRATE {15000, 15000, 100}
/* Speed in mm/min for finding the home position. Overridden if EEPROM activated. */
#define HOMING_FEEDRATE {2400,2400,100}
/* If you have a backslash in both z-directions, you can use this. For most printer, the bed will be pushed down by it’s
own weight, so this is nearly never needed. */
//#define Z_BACKSLASH 0.1
/** Comment this to disable ramp acceleration */
#define RAMP_ACCELERATION 1
/** If your stepper needs a longer high signal then given, you can add a delay here.
The delay is realized as a simple loop wasting time, which is not available for other
computations. So make it as low as possible. For the most common drivers no delay is needed, as the
included delay is already enough.
*/
#define STEPPER_HIGH_DELAY 0
/** The firmware can only handle 16000Hz interrupt frequency cleanly. If you need higher speeds
a faster solution is needed, and this is to double/quadruple the steps in one interrupt call.
This is like reducing your 1/16th microstepping to 1/8 or 1/4. It is much cheaper then 1 or 3
additional stepper interrupts with all it’s overhead. As a result you can go as high as
40000Hz.
/
#define STEP_DOUBLER_FREQUENCY 10000
/* If you need frequencies off more then 30000 you definitely need to enable this. If you have only 1/8 stepping
enabling this may cause to stall your moves when 20000Hz is reached.
/
#define ALLOW_QUADSTEPPING true
/* If you reach STEP_DOUBLER_FREQUENCY the firmware will do 2 or 4 steps with nearly no delay. That can be too fast
for some printers causing an early stall.
*/
#define DOUBLE_STEP_DELAY 1 // time in us
/* The firmware supports trajectory smoothing. To acieve this, it divides the stepsize by 2, resulting in
the double computation cost. For slow movements this is not an issue, but for really fast moves this is
too much. The value specified here is the number of clock cycles between a step on the driving axis.
If the interval at full speed is below this value, smoothing is disabled for that line./
#define MAX_HALFSTEP_INTERVAL 1999
//// Acceleration settings
/* brief Use RAMP acceleration for faster printing speed. /
#ifdef RAMP_ACCELERATION
/* brief X, Y, Z max acceleration in mm/s^2 for printing moves or retracts. Make sure your printer can go that high!
Overridden if EEPROM activated.
/
#define MAX_ACCELERATION_UNITS_PER_SQ_SECOND {2500,2500,100}
/* brief X, Y, Z max acceleration in mm/s^2 for travel moves. Overridden if EEPROM activated./
#define MAX_TRAVEL_ACCELERATION_UNITS_PER_SQ_SECOND {1500,1500,100}
#endif
/** brief Maximum allowable jerk.
Caution: This is no real jerk in a physical meaning.
The jerk determines your start speed and the maximum speed at the join of two segments.
It’s unit is mm/s. If the printer is standing still, the start speed is jerk/2. At the
join of two segments, the speed difference is limited to the jerk value.
Examples:
For all examples jerk is assumed as 40.
Segment 1: vx = 50, vy = 0
Segment 2: vx = 0, vy = 50
v_diff = sqrt((50-0)^2+(0-50)^2) = 70.71
v_diff > jerk => vx_1 = vy_2 = jerk/v_diff_vx_1 = 40/70.71_50 = 28.3 mm/s at the join
Segment 1: vx = 50, vy = 0
Segment 2: vx = 35.36, vy = 35.36
v_diff = sqrt((50-35.36)^2+(0-35.36)^2) = 38.27 < jerk
Corner can be printed with full speed of 50 mm/s
Overridden if EEPROM activated.
*/
#define MAX_JERK 20.0
#define MAX_ZJERK 0.3
/* Define the type of axis movements needed for your printer. The typical case
is a full cartesian system where x, y and z moves are handled by seperate motors.
0 = full cartesian system, xyz have seperate motors.
1 = z axis + xy H-gantry (x_motor = x+y, y_motor = x-y)
2 = z axis + xy H-gantry (x_motor = x+y, y_motor = y-x)
Cases 1 and 2 cover all needed xy H gantry systems. If you get results mirrored etc. you can swap motor connections for x and y. If a motor turns in
the wrong direction change INVERT_X_DIR or INVERT_Y_DIR.
*/
#define DRIVE_SYSTEM 0
/** brief Number of moves we can cache in advance.
This number of moves can be cached in advance. If you wan’t to cache more, increase this. Especially on
many very short moves the cache may go empty. The minimum value is 5.
/
#define MOVE_CACHE_SIZE 16
/ How many line segments can the path planner use for path optimization. The maximum possible
value is MOVE_CACHE_SIZE-2. Higher values need more computation time, which can cause blocking for many
short subsequent moves. If this happens you will see BLK messages in your log and then you now the
value is to high for your printer settings.
/
#define PATH_PLANNER_CHECK_SEGMENTS 12
/* brief Low filled cache size.
If the cache contains less then MOVE_CACHE_LOW segments, the time per segment is limited to LOW_TICKS_PER_MOVE clock cycles.
If a move would be shorter, the feedrate will be reduced. This should prevent buffer underflows. Set this to 0 if you
don’t care about empty buffers during print.
/
#define MOVE_CACHE_LOW 12
/* brief Cycles per move, if move cache is low.
This value must be high enough, that the buffer has time to fill up. The problem only occurs at the beginning of a print or
if you are printing many very short segments at high speed. Higher delays here allow higher values in PATH_PLANNER_CHECK_SEGMENTS.
*/
#define LOW_TICKS_PER_MOVE 400000
// ##########################################################################################
// ## Extruder control ##
// ##########################################################################################
/** brief Prescale factor, timer0 runs at.
All known arduino boards use 64. This value is needed for the extruder timing. */
#define TIMER0_PRESCALE 64
/* brief Minimum temperature for extruder operation
This is a saftey value. If your extruder temperature is below this temperature, no
extruder steps are executed. This is to prevent your extruder to move unless the fiament
is at least molten. After havong some complains that the extruder does not work, I leave
it 0 as default.
*/
#define MIN_EXTRUDER_TEMP 175
/** brief Activate ooze prevention system
The ooze prevention system tries to prevent ooze, by a fast retract of the filament every time
printing stops. Most slicing software have already an option to do this. Using OPS_MODE=1 will
in fact mimic this. This works good, but can increase printing time. To reduce the additional
waiting time, the OPS has a fast mode, which performs the retraction during the travelling move.
The only reason, your slicer doesn’t do it, is because it can’t tell. There is simple no
G-Code command telling the firmware to do that.
You can always compile including OPS. Then you can disable/enable it anytime you want. To disable it
set USE_OPS 0
Caution: Don’t enable anti-ooze in your slicer if you are using this.
*/
#define USE_OPS 0
/** brief Sets the ops operation mode
0: Off
1: Classic mode. Stop head, retract move to target, push filament back.
2: Fast mode. Retract during move, start pushing back the filament during move. For safty, we start
at with a low speed and wait for the push back, before the pintmove starts. Normally there is some
time needed to wait for the filament.
Overridden if EEPROM activated.
*/
#define OPS_MODE 0
/** brief Minimum distance for retraction.
If a travel move is shorter than this distance, no retraction will occur. This is to prevent
retraction with infill, where the angle to the perimeter needs a short stop. Unit is mm.
Overridden if EEPROM activated.
*/
#define OPS_MIN_DISTANCE 1
/** brief Move printhead only after x% of retract distance have been retracted.
Overridden if EEPROM activated./
#define OPS_MOVE_AFTER 50.0
/* brief Retraction distance in mm. If you want to enable OPS only sometimes, compile with
OPS support and set retraction distance to 0. If you set it to e.g. 3 in your eeprom settings it is enabled.
Overridden if EEPROM activated.*/
#define OPS_RETRACT_DISTANCE 3.0
/** brief Backslash produced by extruder reversal
If you are using a bowden extruder, you may need some extra distance to push the filament back into the
original place. This is the value you enter here. Unit is mm.
Overridden if EEPROM activated.
*/
#define OPS_RETRACT_BACKSLASH 0.0
/** brief Enable advance algorithm.
Without a correct adjusted advance algorithm, you get blobs at points, where acceleration changes. The
effect increases with speed and acceleration difference. Using the advance method decreases this effect.
For more informations, read the wiki.
*/
#define USE_ADVANCE
/** brief enables quadratic component.
Uncomment to allow a quadratic advance dependency. Linear is the dominant value, so no real need
to activate the quadratic term. Only adds lots of computations and storage usage. */
//#define ENABLE_QUADRATIC_ADVANCE
// ##########################################################################################
// ## Communication configuration ##
// ##########################################################################################
//// AD595 THERMOCOUPLE SUPPORT UNTESTED… USE WITH CAUTION!!!!
/** brief Communication speed.
-
250000 : Fastes with errorrate of 0% with 16 or 32 MHz — update wiring_serial.c in your board files. See boards/readme.txt
-
115200 : Fast, but may produce communication errors on quite regular basis, Error rate -3,5%
-
76800 : Best setting for Arduino with 16 MHz, Error rate 0,2% page 198 AVR1284 Manual. Result: Faster communication then 115200
-
57600 : Should produce nearly no errors, on my gen 6 it’s faster than 115200 because there are no errors slowing down the connection
-
38600
Overridden if EEPROM activated.
/
//#define BAUDRATE 76800
//#define BAUDRATE 57600
#define BAUDRATE 250000
/* brief Size in byte of the output buffer /
#define OUTPUT_BUFFER_SIZE 64
/* brief Activates buffered output.
The Arduino libraries have a buffered input for serial connections. Write operations are
always unbuffered, which means the controller will wait with execution, until the data
is send. To solve this handicap, all write operations have to use out insted of Serial.
If you uncomment this, you still have to use out, but it will use no buffers, so you
keep with your slow communication version.
*/
/**
Some boards like Gen7 have a power on pin, to enable the atx power supply. If this is defined,
the power will be turned on without the need to call M80 if initially started.
*/
#define ENABLE_POWER_ON_STARTUP
/** What shall the printer do, when it receives an M112 emergency stop signal?
0 = Disable heaters/motors, wait for ever until someone presses reset.
1 = restart by resetting the AVR controller. The USB connection will not reset if managed by a different chip!
*/
#define KILL_METHOD 1
#if !defined(AVR_AT90USB1286) && !defined(AVR_AT90USB1287) // not needed for USB serial
#define USE_BUFFERED_OUTPUT
#endif
/** brief Cache size for incoming commands.
There should be no reason to increase this cache. Commands are nearly immediately send to
execution.
/
#define GCODE_BUFFER_SIZE 2
/* Appends the linenumber after ever ok send, to acknowledge the received command. Uncomment for plain ok ACK if your host has problems with this /
#define ACK_WITH_LINENUMBER
/* Communication errors can swollow part of the ok, which tells the host software to send
the next command. Not receiving it will cause your printer to stop. Sending this string every
second, if our queue is empty should prevent this. Uncomment if you don’t wan’t this feature. */
#define WAITING_IDENTIFIER «wait»
/** brief Sets time for echo debug
You can set M111 1 which enables ECHO of commands send. This define specifies the position,
when it will be executed. In the original FiveD software, echo is done after receiving the
command. With checksum you know, how it looks from the sending string. With this define
uncommented, you will see the last command executed. To be more specific: It is written after
execution. This helps tracking errors, because there may be 8 or more commands in the queue
and it is elsewise difficult to know, what your reprap is currently doing.
*/
#define ECHO_ON_EXECUTE
/** brief EEPROM storage mode
Set the EEPROM_MODE to 0 if you always wan’t to use the settings in this configuration file. If not,
set it to a value not stored in the first EEPROM-byte used. If you later want to overwrite your current
eeprom settings with configuration defaults, just select an other value. On the first call to epr_init()
it will detect a mismatch of the first byte and copys default values into EEPROM. If the first byte
matches, the stored values are used to overwrite the settings.
IMPORTANT: With mode <>0 some changes in configuration.h are not set any more, as they are
taken from the EEPROM.
/
#define EEPROM_MODE 0
/* Comment out (using // at the start of the line) to disable SD support: /
//#define SDSUPPORT 0
/* Show extended directory including file length. Don’t use this with pronterface! */
#define SD_EXTENDED_DIR
// ##########################################################################################
// ## Debug configuration ##
// ##########################################################################################
/** Uncomment, to see detailed data for every move. Only for debugging purposes! /
//#define DEBUG_QUEUE_MOVE
/* Allows M111 to set bit 5 (16) which disables all commands except M111. This can be used
to test your data througput or search for communication problems. /
#define INCLUDE_DEBUG_COMMUNICATION
/* Allows M111 so set bit 6 (32) which disables moves, at the first tried step. In combination
with a dry run, you can test the speed of path computations, which are still performed. /
//#define INCLUDE_DEBUG_NO_MOVE
/* Writes the free RAM to output, if it is less then at the last test. Should always return
values >500 for safety, since it doesn’t catch every function call. Nice to tweak cache
usage or for seraching for memory induced errors. Switch it off for production, it costs execution time. /
//#define DEBUG_FREE_MEMORY
//#define DEBUG_ADVANCE
/* brief print ops related debug info. /
//#define DEBUG_OPS
/* If enabled, writes the created generic table to serial port at startup. /
//#define DEBUG_GENERIC
/* If enabled, steps to move and moved steps are compared. */
//#define DEBUG_STEPCOUNT
// Uncomment the following line to enable debugging. You can better control debugging below the following line
//#define DEBUG
#endif