Hello new poster here, I built a plasma table a few years ago and have been routinely using the open builds post processor in fusion 360 for it. I have been using V1.0.30 without issue until recently, I then decided to upgrade to V1.0.40 and am still getting the same issue. I am unable to post at all and this is the feedback I am getting from Fusion 360. I have never seen this error before. Any feedback on this issue would be greatly appreciated.
hmmm, looks like they have created a new internal property named 'power' and made it readonly. I will post a new version tonight
Thanks for the update. I just updated to the latest version of Fusion 360 and started getting this problem. I will give it a try as soon as I can.
I have uploaded V1.0.41 that fixes the namespace collision GitHub - OpenBuilds/OpenBuilds-Fusion360-Postprocessor: Post Processor for Fusion 360 for use with OpenBuilds Machines running Grbl 1.1
I downloaded the update (V1.0.41). I am NEW NEW NEW to this and haven't a clue how to do this. Please dumb this down for me. I've had responses which I appreciate but the answers seem to require a stronger understanding of computers and I just don't have it. Computer programming is not my strong suit. I can draw in fusion/ sketchup just fine. Just when I got this thing going there's an update that requires reprogramming or updating and I'm stalled again. I have spent countless hours trying to get this table operating. I've made less than half a dozen cuts. PLEASE HELP!!!!
Same as you installed it initially - just using the latest CPS file docs:software:fusion360 [OpenBuilds Documentation]
Thanks! I suppose I need to work on my computer skills. I managed to get it to work. Took me a while, but it worked. I appreciate your help! Thanks again.
I am getting an error "Hard limit triggered" after using the latest post processor of open builds for fusion 360. Job start -- runs for some time and then I get this error. Error is at random time. My old g-codes are working properly. Today my earlier PP stopper working and it was showing some error, so I downloaded the new one and since then I am getting this issue.
Sounds more like EMI docs:blackbox-x32:faq-emi [OpenBuilds Documentation] that is, unless the machine actually does run into the limit switch?
Well, the Hard limit error specifically means, a limit switch was hit. Thus the question It either does (incorrect options in post but unlikely to be "random" ; Or something mechanic making machine lose position) or its a false trigger caused by EMI. The post cannot "cause" a false alarm
Thanks a lot for your help. Can you please let me know what incorrect options selected in post may cause this error. I will check it, if by mistake there is some incorrect selection in post.
So, by that you are confirming you are actually running into a switch? Not a random error, but an actual Limit hit?
im having the same issue as the original poster. but when i click on the github link to get v1.0.41 it only shows the latest update is v1.0.37
