Warning on the console since update
-
No they are not from my macro, I think they are coming from the internal G31 code.
As I stated, the macro is not using M120 or M121.
I have also checked the macro and all indents are tabs. -
@appjaws said in Warning on the console since update:
No they are not from my macro, I think they are coming from the internal G31 code.
As I stated, the macro is not using M120 or M121.
I have also checked the macro and all indents are tabs.When I get those warnings the line number refers to the line in one of my gcode files where I am using conditional code requiring indentation.
Frederick
-
Post your files as uploads so we can look at them in a text viewer that shows the difference between tab and space characters.
-
Here is the relevant file, thanks for your interest
-
I don't see anything in there. Could it be in the SET_LED macros that get called?
-
No, The called macros are all ok, just tabs.
Has something changed in the beta firmware in the way G31 operates? -
I had a similar problem with that error message finally was the error not in the macro file where the error point me to but at the bed.g file.
-
Hi,
I updated my 6HC to 3.3 beta 2 and I am not getting any warnings like that from invoking G31.
Frederick
-
Warning: both space and tab characters used to indent blocks by line 184
Do you have a macro with a line 184?
-
@Phaedrux
No, all my macros are quite small.
This is really strange, I'll check all my macros again tomorrow . -
@appjaws said in Warning on the console since update:
@Phaedrux
No, all my macros are quite small.
This is really strange, I'll check all my macros again tomorrow .It can be any gcode file in your SYS or MACRO directory.
Frederick
-
@fcwilt
Even if not called?
I'd better check all my files. -
@appjaws said in Warning on the console since update:
@fcwilt
Even if not called?
I'd better check all my files.Well yes they have to called.
Frederick
-
Problem solved, I checked all files and there were a few that had space and tabs. They now have all tabs and the error has been fixed.
Thank you for all who helped
