probe basic - toolpath/file preview loading error

More
06 Oct 2024 14:20 #311408 by jc2ktr
Hi everyone,

everytime when i try to load a gcode file i get this error. 

Traceback (most recent call last):
  File "<string>", line 1, in <lambda>
  File "<string>", line 1, in <genexpr>
IndexError: tuple index out of range

I use LinuxCNC 2.10 and probe basic screen on Debian12 with linux 6.1.0-25-rt-amd64 kernel

it´s not a big deal i can press on ignore and use the machine to mill. The only problem is that no Toolpath preview is generated at file loading.
At the milling operation it is generated without any issues.
 
Attachments:

Please Log in or Create an account to join the conversation.

More
06 Oct 2024 14:31 #311410 by Lcvette
Check there are no uncommon symbols used in the file, it's likely a language bug 

Please Log in or Create an account to join the conversation.

More
06 Oct 2024 20:13 #311437 by jc2ktr
It seems Probe Basic related. When i load it in a Axis configured machine. There are No Problems. The gcode was generated with Fusion360.

Please Log in or Create an account to join the conversation.

More
06 Oct 2024 21:30 #311445 by Lcvette
It very well may be,  but there have been issues similar in the past that were language related,  need to identify the offending thing to be able to resolve.   

Please Log in or Create an account to join the conversation.

More
06 Oct 2024 21:31 #311446 by Lcvette
Maybe post the file?

Please Log in or Create an account to join the conversation.

More
07 Oct 2024 04:34 - 07 Oct 2024 04:36 #311464 by jc2ktr

Maybe post the file? Sure no problem. i will post it here.   

Sure no problem, i will post it here.

 

File Attachment:

File Name: 2209.ngc
File Size:1,236 KB
Attachments:
Last edit: 07 Oct 2024 04:36 by jc2ktr. Reason: fixed typo :)

Please Log in or Create an account to join the conversation.

More
07 Oct 2024 12:05 - 07 Oct 2024 12:09 #311483 by Lcvette
Error in 2209.ngc line 11
M-code greater than 199: M600

this is the error i get and i have seen this before, @Joco was experiencing this error popping up for some reason, but im not certain why this occurs, i thought he had found a work around for it in the linuxcnc source. as a test i changed the M600 code to M5 and it loaded fine with preview, I will ask him if he recalls how to resolve that issue and see about a fix for it.

I only received the M errror as seen in the image below and not the one you posted so not certain if its the same or if there is something else going on there.  the result with error was the same symptom which was no display of the tool path in the gcode plotter.

Thanks for the heads up!

Chris

 

 
Attachments:
Last edit: 07 Oct 2024 12:09 by Lcvette.
The following user(s) said Thank You: jc2ktr, Unlogic

Please Log in or Create an account to join the conversation.

More
07 Oct 2024 19:21 #311517 by jc2ktr
Thanks Lcvette,

yes the M600 error is a followup from my toolchange remap. I´ve deleted all Comments from Fusion360 in the file, and test ist tomorrow. Maybe there is a problem. 

Thanks for your help and patience 

Please Log in or Create an account to join the conversation.

More
07 Oct 2024 21:09 #311527 by Lcvette
I had to change the M600 to M5 and it loaded without complaint, so there is something i think requiring a fix for M600, you could assign a different M### between 100-199 and it would not complain, unless you've added M600 yo linuxcnc and it sees it and doesnt complain

Please Log in or Create an account to join the conversation.

More
09 Nov 2024 03:18 #314108 by spumco
Adding my two cents here...

I get a similar error message when trying to load a g-code file in PB.  No issues with the backplot but the attached error message pops up when I load the file.

I think I narrowed it down to the tool number being >199.

When I commented out the T407, T823, and T642 it loaded with no complaints.  And when I edited the file it would load fine at T199 (other two commented out) but puked when changed to T200.

I can load the tools in/out of my ATC using the PB interface, and call them up via MDI with no errors.

I can work around this for a short time by renumbering tools, but this is going to be annoying since I imported my F360 library to LCNC and I've got tools up to the 1100-range in the table.
Attachments:

Please Log in or Create an account to join the conversation.

Moderators: KCJLcvette
Time to create page: 0.201 seconds
Powered by Kunena Forum