Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
This is a really good idea - and - essential, because there may be some geometries the CAM doesn't support (yet), or some tooling that is very specialized. I think it could be just a two tab setup, eg, "Tool" and "Gcode". Tool would be normal setup, providing speeds, feeds, coolant, etc. The 'Gcode' window could just be a plain text edit box becuase by the time you need somthing like this code gen would be hard, if not impossible, to parameterize. What would be really cool is if the toolpath engine could read/parse the gcode and render a whatver tool path it could understand or some error info for things like arc center points.
I ran into a use-case this summer when I was making some aircraft induction parts that had a dovetail o-ring groove on a forward 45 degree face. No way to get CAM on this; it had to be hand coded. A feature like the above would at least allow you to keep hand coded stuff in the work flow as you made changes to other parts of the model/CAM. Otherwise it had to copied and pasted into the final gcode, which leaves the door open for human error.
This something that should not only be simulated, but also create a toolpath on the CAM view, and machining time, like any 'native' operation. It's not rocket science to implement. This is a feature I've implemented in the post processor ( Tormach SlantPRO ) , and have used several times. One blatant example is face grooving, which isn't supported very well yet in Fusion, but is easy to hand code. It would solve the entire class of issues with unsupported cutting as a universal work around.
We don't want to bother the Fusion team with true CAM idea's.
Also if we want to have the Inventor HSM and HSMWorks users voting, and keeping an eye on the Idea's don't put it in the special seperate Fusion 360 forum.
So if you ask me the best way would be to move the CAM Ideastation form Fusion into the "CAM" forum.
People that use CAM in fusion will visit that forum more often than the Inventor HSM user will visit the Fusion 360 forum.
So one seems like a solid plan for me, just not where it is now.
But my point is that the CAM idea's should be in a meeting with You, René, Mark.
And not in the Fusion 360 meetings. Since I rather have a developer give his view on the idea, and immediately have a view on how easy it is to implement instead of people that might get annoyed by all those weird CAM users that want new things everyday.
Except that CAM is also a part of Fusion, so what happens on the CAM side may still affect what happens in Fusion.
Overall though I do think it would be best to have a separate CAM ideastation, since the same CAM system is used across 3 different platforms. It's distinct enough from general 3D modelling that it should have its own space.
Fusion is its own bird and I wouldn't go there to give an idea cause well "I DO NOT USE IT!" So why would I search there?
ideas for CAM should be just in a CAM IDEASTATION because not in a singular CAD one.
there a lot of us who are die hard SW USERS that never touch fusion or inventor, sorry, that's why when Lauren's asked me to make an IDEASTATION I didn't because it was in the fusion one, so I'll keep complaining on the CAM forum and asking for enhancements there.
i added a code in my post so i can use PASS THROUGH.
add to line 124 to 132 after statement // collected state VER
/** Writes "Pass-Through" <-- Added, not part of generic haas post. */ function onPassThrough(text) { var commands = String(text).split(","); for (text in commands) { writeBlock(commands[text]); } }
in manual NC click on pass-through then add your code each line of code has to be a separate pass through line.
Charlie, does your serial number increment? If so I could help you with creating a macro to handle changing it on a part by part basis.
The operator would change the part number in the controller or you have have it change when the program number changes.
I wrote one for us that is scaleable, rotates, steps the depths, and increments. Example: Our serial is MXXXXXX-001, MXXXXXX-002, MXXXXXX-003, MXXXXXX-004...MXXXXXX-XXX.
I had a hard time finding help with this myself so I'd be glad to help if it sounds like something you are interested in.