Connection Errors Repetier FW + Host

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 errorystem.IO.Ports.SerialErrorReceivedEventArgs
15:42:17.416 : Serial com errorystem.IO.Ports.SerialErrorReceivedEventArgs
15:42:17.580 : Serial com errorystem.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
> errorystem.IO.Ports.SerialErrorReceivedEventArgs
>
> 15:42:15.112 : Serial com
> errorystem.IO.Ports.SerialErrorReceivedEventArgs
>
> 15:42:17.416 : Serial com
> errorystem.IO.Ports.SerialErrorReceivedEventArgs
>
> 15:42:17.580 : Serial com
> errorystem.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?{????? ?i0?j@?kP?l?Z??X`??p?????????????n?????? ?m0?n?@?oP?p?Z??X`??p????????????V?j?{????? ?q0?r@?sP?t?Z??X`??p?????????=?#??n?????? ?e0?f@?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 errorystem.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?????? ?e0?f@?gP?h?Z??X`??p?????????????j?{????? ?i0?j@?kP?l?Z??X`??p?????????????n?????? ?m0?n@?oP?p?Z??X`??p????????????V?j?{????? ?q0?r@?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 errorystem.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 errorystem.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