Euclid probe update Voron 2.4 v1- Error message " File contains no section headers???"

[SteveS]

I have removed the Inductive probe and installed a Euclid probe. I downloaded Euclid  V3 example from Github.

Using Fluidd interface I uploaded euclid.cfg I then entered all the parameters required. I also updated my printer.cfg file.

I have followed a detailed video from Kapman's Basement Workshop. I have checked the syntax several times.

If anyone can suggest something I would be grateful. I have added the Euclid.cfg and Config.cfg as attachments. 

euclid.cfg printer (3).cfg

[mvdveer]

47 minutes ago, SteveS said:

f anyone can suggest something I would be grateful. I have added the Euclid.cfg

It seems a formatting error. I have reformatted the Euclid.cfg file and uploaded it. Let me know if this solved the problem.

 

euclid.cfg

[SteveS]

Thanks, I will try it out.

[SteveS]

All working! I initially had another line error but once I commented it out all OK.

I would like to understand what you did when you reformatted. Please can you explain what you changed?

The error name is not that helpful.

Really appreciate your help. 

Cheers Steve

[claudermilk]

That "\n" in the error  message suggests to me the file had incorrect line feed coding. Possibly the file was edited in something like Wordpad which makes files Linux does not like as I recall. Notepad or a proper code editor would be better--or of course now just editing directly in Mainsail/Fluidd.

[mvdveer]

9 hours ago, SteveS said:

I would like to understand what you did when you reformatted. Please can you explain what you changed?

Klipper is a programming language and like all coding, it requires a certain format when programming macros. Indentation is the important aspect in all of these. Taking you Euclid.cfg file as an example:

1. Your code started about 20 spaces into the line

2. Your macro's were not indented.

All I did was remove this dead space in front of the code in ALL the lines, then correctly indented the code.

For Example: (your original)

1                                              [gcode_macro M401]
2                                              gcode:
3                                                  G90
4                                                  {action_respond_info("Entering M401")}
5                                                  error_if_probe_deployed    ; check to make sure that the probe is not already attached
6                                                  _M401

should be formatted as: 

1 [gcode_macro M401]
2 gcode:
3   G90
4   {action_respond_info("Entering M401")}
5   error_if_probe_deployed    ; check to make sure that the probe is not already attached
6   _M401
 

For a better explanation see the following link that may explain it better than I can:

https://www.klipper3d.org/Command_Templates.html

 

[SteveS]

Great I will check that in the future. 

Thanks again for your help.

Cheers.

[claudermilk]

Oh! Yes! Klipper (nee, Python/Jinja2) is very specific on indentation. Start macros at the far left, then indent the macro gcode exactly two spaces. 

I'm so used to adhering to indentation standards I didn't even think about that.