Recent update blew up post settings
That's not an expected result, by any means. Are you using a Machine Configuration in your file, by chance? Do you have any files to share that will help us to reproduce the error? Please share them here if you do!
Seth Madore
Customer Advocacy Manager - Manufacturing
Hi
Can you provide specifics like, Which post you are using and what error messages you are getting?
Andrew Laas
Senior Machinist, Scott Automation
Hi
There appears to be a problem with the Open builds post, I don't know enough about JavaScript to figure out what the issue is.
being that this is a Third Party post it may pay to contact the post developers for assistance.
in the short term you could use the Fusion supplied grbl post, that one still works fine.
Andrew Laas
Senior Machinist, Scott Automation
@spencerlull do you have the "Optional Feature > Use Upgraded Post Engine" option turned on?
Try turning it off and then using the post you're accustomed to use and see if the issue remains.
Seth Madore
Customer Advocacy Manager - Manufacturing
Hi Seth
I did try that option on and off and it fails the same both ways.
also fails to post in VS code with the extension with a timeout error
This post here:
https://github.com/OpenBuilds/OpenBuilds-Fusion360-Postprocessor/tree/master
Andrew Laas
Senior Machinist, Scott Automation
This post is a machine translation.
Sorry if it's hard to read.
I was using the same post and faced the same issue. I posted it on the Japanese forum,
but it hasn't really solved the problem.
Set the WCS offset in the setup settings.
Posting is now possible by setting the spindle rotation speed to 10,000 ～ 20,000 rpm（Makita router speed）.
Up until now, you could post by simply ignoring the warning dialog when posting, but after the update, this will now fail.
I think there may have been some kind of update to the processing of posts that display dialogs, but I'm a baby so I don't know.
Thank you for the information, it pointed me to the right direction to where the issue appears to come from.
This section:
if (rpm < speeds[1])
{
//alert("Warning", rpm + " rpm is below minimum spindle RPM of " + speeds[1] + " rpm in the " + op + " operation.");
return 1;
}
if (rpm > speeds[speeds.length - 1])
{
//alert("Warning", rpm + " rpm is above maximum spindle RPM of " + speeds[speeds.length - 1] + " rpm in the " + op + " operation.");
return (speeds.length - 1);
}
var i;
for (i = 1; i < (speeds.length - 1); i++)
{
if ((rpm >= speeds[i]) && (rpm <= speeds[i + 1]))
{
return (((rpm - speeds[i]) / (speeds[i + 1] - speeds[i])) + i).toFixed(1);
}
}
//alert("Error", "Error in calculating router speed dial.");
// error("Fatal Error calculating router speed dial.");
return 0;
}
It appears "alert" and "error" are not valid functions and cause the problem
I have commented them out as they appear to have been in the other parts of the post.
Please find the attached version that works, albeit without the error checking for spindle speed.
The alert function is still present in other parts of the post however and may still cause issues, the post developer will need to rectify these in their next release
Andrew Laas
Senior Machinist, Scott Automation
