Hi, Struggling with post processing posts from fusion 360 to a duet controlled workbee Every time I post and attempt to run the program it looses connection I’m confident the duet has no problems as a file supplied to me by workbee runs ok any help appreciated Mark See picture
Are you getting any error messages when post processing in Fusion, and what post processor are you using for the Duet. Fusion have made some changes recently which are apparently causing issues with post processing but I haven't had time to explore any issues with the Duet post processors. Please upload your Fusion file and your g-code file here so I can have a look at them both. Alex. PS, do you have a WiFi or ethernet Duet? PPS, was on my phone when I first posted - have now seen the header of your g-code file. While I don't see anything in that that would cause a disconnection, I do see that you are not using Ooznest's post processor for Fusion (or my development of it that gives you back most of the rapid moves that Autodesk took away from hobby users and allows the use of multiple wcs's within one job). Your feedrate does seem VERY high at 4500 mm/min - are you seeing any signs of motors stalling, any low voltage reports from the Duet or other error reports? Is this an Ooznest machine running Ooznest's firmware. If not could you please tell me more about it's origin and set up.
you will need to remove all references to the alert() method call and if you used 'power' as a local variable, you have to change the name since postprocessor.power is now a readonly property. I have not found any documentation of these changes at Autodesk CAM Post Processor Documentation, yet....
Thanks David. Haven't had time yet to look at post processors for the Duet, I don't think "power" is used as a variable in any of my post processors or in Ooznest's (which is quite basic). I'll have to boot up the PC in my attic to check other issues. Speaking of other issues, someone in my Facebook group for Workbee users reported problems if coolant method wasn't selected (I thought one was always selected as a default but I may have set up a default setting years ago without really noticing). Holiday weekend so I'll try to boot up my design PC tomorrow, update Fusion and see what happens. Alex.
Hi, No luck with the google search. This is where I picked up the post processor. I selected the V1.0.1- WorkBee Firmware Releases No errors showing in Fusion for setup ,cutting or post processing I have slowed the cutting speeds right down, made sure coolant was selected still no joy used this to setup for the Duet in Fusion - How do I get fusion 360 to post process As soon as you go to run the programme the duet looses connection and the error message occurs. you then have to swich re-start the machine to clear the error Ooznest workbee machine running Ooznest software wifi connected NC file uploaded Regards, Mark
I don't see how a Post Processor/GCODE can cause your browser to lose connection to the controller (Websocket or HTTP?) Might just be coincidence - when exactly does it lose connection? When you run the job and it reaches what line? Just after turning on spindle? (EMI or controller PSU plugged into spindle's IoT Relay's Normally On socket - if used) or just after homing? (Hits a shorted limit switches) etc? Something else is surely the root cause. Does it start moving and then stop? Take a video
Have to agree with @Peter Van Der Walt - as I said above, there is nothing in the header of your g-code that could cause a disconnection. I did wonder if the high feedrate was causing a motor stall, possibly causing a voltage drop as a result. The Duet Web Control interface has a console tab - show us a screenshot of that immediately after the disconnection and include the whole screen in your screenshots - sometimes there's a clue in the bit you don't show. Have you set up the Duet to connect via your LAN or as an access point? Alex. PS, please confirm if you are using the RepRap V3.3 based firmware from Ooznest - from your screenshot it looks as though you are but the info that would confirm it is just out of view.
Hi after homing the machine then going to its starting 0,0,0 position I upload the NC file and the run the programme at this point I get the disconnect immediately and error file every time ( machine does not move) and have to cycle power to clear the error. The Duet is connected by LAN over wifi running RepRap v3.3 firmware which is running ok and tested with a programme from workbee I've slowed the feed speeds down to 200 but still the same
coolant should just default to none if the user has not selected an actual option (ie no coolant codes are output). Usual option is Flood, Duet may support Mist as well, Blackbox does not have an output pin for Mist so Flood is the only option there. I don't know how far down the rabbit hole you want to go...... Fusions laser and plasma operations do not allow the selection of a coolant mode so the OB post allows a coolant override in the post settings so the user can activate coolant even for laser/plasma (for that 1 person on the planet that needs it
That is a problem with Ooznest's adoption of the RepRap V3.3 firmware (which expects an output pin to be defined for spindle control) and the fact that they have not updated their post processor to deal with it. The Duet normally ignores that error and runs the job anyway. If not using g-code to control a spindle the simplest solution if it is causing issues is to not output the spindle control g-code. I've already created a Vectric post processor to do that, but I see that Ooznest's Fusion post processor isn't outputting those codes anyway. I'll contact some people in my Facebook group who are more into that version of the RepRap V3.3 firmware for advice, but, as I said, the Duet normally ignores that error - it certainly wouldn't cause a WiFi disconnection. My feeling is that the focus on the Fusion post processing is leading us away from the true issue. Alex.
coolant should just default to none if the user has not selected an actual option (ie no coolant codes are output). Usual option is Flood, Duet may support Mist as well, Blackbox does not have an output pin for Mist so Flood is the only option there. I don't know how far down the rabbit hole you want to go...... Fusions laser and plasma operations do not allow the selection of a coolant mode so the OB post allows a coolant override in the post settings so the user can activate coolant even for laser/plasma (for that 1 person on the planet that needs it
Hi This file runs fine on the workbee. would you be able to compare to the file I supplied earlier to stot if there is an error
Try adding its header T1 G17 G21 ; or G20 (mm or inch depending on what the other file was CAD as) G90 M3 S15000 (I still am suspect of the Spindle error even though Alex says its normal, adding a spindle command should at least remove that particular error popup)
It's the other way round with the Duet firmware version Mark is using Peter - if the Duet sees a spindle g-code it will look for a definition of that tool - which output pin is to be used to send signals to it for example. Vectric users have found that, if it does cause issues, NOT sending a spindle command solves the issue. This is the first time I've come across a problem with Fusion. I don't use that version of the firmware, so I'm waiting for feedback from some of my Facebook group members who are much more familiar with it. I still don't see anything in the g-code that would cause a WiFi disconnect. @Mark Goodacre, the first file you you posted was post processed using the Autodesk "generic 3 axis" post processor - NOT a Duet specific post processor. Try using Ooznest's post processor or my development of it. If you upload your Fusion file as I requested I can run it through an appropriate post processor to see what happens. In the meantime, can you tell me what you see in the tab circled in red in the pic below immediately after losing connection? Thanks, Alex.
Hmm, going back to Peters' point about spindle commands I do see that the file Ooznest gave you DOES have spindle commands, so do use the correct post processor, although I still don't see how that could cause a WiFi connection problem. Alex.
Hi, Yes, did the same I'm sorry to say also clicked on console just before upload and run - connected to workbee local LAN . the page freezes on running the programme so no access after Regards, Mark PS. very appreciative of all your help
Then I am out of ideas (apart from jokingly suggesting an Upgrade to BlackBox X32?) Might want to check in with the vendor
I notice that you have flood coolant specified for the toolpath that outputs an M8 command when I post process it using the generic grbl POST. Does your machine support flood coolant? Might be worth trying without, since most other ideas seem be exhausted.
Hi my machine doesn't support flood coolant as its a basic machine router that you have to power separately along with any coolant you require separately. everything worked fine before the duet upgrade leaving flood coolant and router speed set at a realistic speed for the router , but as I said these two are controlled manually during operation not by the duet. So is coolant and spindle speeds an issue??
This is the first time I've seen any mention of a "Duet upgrade". Do you mean the firmware? If so that is likely your problem - you most likely missed a step in the rather long upgrade process and you now have some elements of the old firmware trying to interact with the new. It's fixable but I'll have to dig through some old posts in my Facebook group to find the info and links you will need. Make sure you have all the details for your WiFi login saved somewhere safe Alex.
Hi Yes I mean software upgrade How To Update WorkBee Firmware V1.0.7 > V3.3.0-1.2 I have a file that Ooznest sent me to check the machine operation when seeking help from them - but its not generated from Fusion 360. this runs the machine fine so I can only guess it's my Fusion 360 setup?? file attached
M8 is not a valid RepRap code - if the Duet firmware did encounter the M8 command it would look for a macro with that name. There is no M8 in the g-code though.
Highly unlikely that it is a problem with Fusion - that post processor dates from 2019 and has been working fine for hundreds/thousands of users. I'm still upgrading my Fusion install so that I can open your file - then I'll post process it using Ooznest's and my, rather more complex, post processors. There is nothing in your g-code though that could possibly cause a WiFi disconnect as far as I can see. Alex. PS I've messaged you.
