Large G-code File importing

[david]

I seem to be confusing the Masso with large files generated by the 2D and 3D adaptive clearing methods in Fusion.

The Masso is becoming unresponsive when attempting to load the file from USB, the mouse stops responding (using the alpha release) and the machine requires a restart.

Produced in Fusion using the Fanuc Post Processor.

Attached is one of the offending files.

Please, could you load up the file at your end and let me know if its a dodgy Gcode in the file, incorrect post-processor, to large a file, or some other issue.

All files produced from fusion that are not using adaptive clearing have worked so far.

Cheers

 

[masso-support]

1. If the gcode file is very big then it can take a long time to display the file on the screen. While the file is being drawn on the screen you can press escape to skip the preview generation bu the gcode file will still run all the way to the end of the file.
   
2. Sorry but there is no file attached, can you please reload.
   
3. Please also mention the exact version of the MASSO software.
   

 

[david]

Thanks, for us, escape does not return mouse or other control.

Its been left for 1/2 an hour to load g-code preview.


Software Version: Mill Gen 11 V3.28.23A,

The file is zipped and attached, it failed due to size


Thanks

 

[masso-support]

Yes the file is long and does take a lot of time to generate the preview but we were able to press escape and stop the preview while it was being generated on the screen.



attached is the print-screen of the file loaded to about 10% and then we pressed escape key on the keyboard it stopped the preview. It should work the same way at your end too.

 

[david]

Yes, can confirm that hitting escape fairly quickly in the process does return mouse and other functionality.

However, a test where it was left to get 34% into the load then escaped did return 'file loaded' however the masso remained unresponsive to the mouse after this point.

 

[masso-support]

David, we have logged an issue as on our side we were able to replicate the issue and are working to find and fix the problem.