I am trying to do a threading operation but there is no feedrate for threading tools and no feedratet output in gcode.
Trying to get work done and would appreciate solutions ASAP.
Thanks
No feedrate for turning threading tools
The only place that a feedrate can be input for a Threading toolpath is in the "Pitch" tab, which would be found on the Passes tab (4th one from left). If it's still not outputting a feedrate, it sounds like a post processor error. What post are you using?
Seth Madore
Customer Advocacy Manager - Manufacturing
Ok. I've pinged one of the post developers, hopefully we can get you sorted out. Sorry for the trouble you've been thru
Seth Madore
Customer Advocacy Manager - Manufacturing
This whole Autodesk ignoring paying customers for 9 months and trying to get them to volunteer their time or pay third party companies to fix Autodesk's broken software is getting out of hand. I pay for software because it is supposed to make my life easier, allow me to focus on my job, and give me support with the product.
If I wanted to look to a volunteer community for support, volunteer my time to software and product development, and spend a bunch of time on DIY solutions I would still be using FOSS software.
You can't charge people for a product then default them to the FOSS pipeline any time there are issues with the products.
This is a defect that needs to be fixed. Just producing an error notification is not a solution.
Threading is a core functionality to machining and CAM, not an "enhancement".
This is so ridiculous. I pay Autodesk because that is supposed to give me functional solutions and support to quickly be able to do my work.
If I wanted to do my own coding or pay to have custom software made I would still be using Open Source Software and supporting that community with my efforts.
Autodesk adopting this model of charging its customers then insisting they go elsewhere for support is absolutely unacceptable. This is why I pay for Autodesk products. Because it is supposed to make my life easier and allow me to focus on my work.
" In regards to disabling canned cycles only affecting drilling cycles, are you available for a remote session this afternoon or sometime this week to go over the behavior? I'll need to gather more details to investigate properly. "
Again this is something you should be able to test and confirm on your own with both the Heidenhain and Fanuc post processors yet you are asking me to volunteer my time to help you fix Autodesk's product.
If you want my help fixing your buggy and broken products I can start billing $100/hr because that is what my time is worth.
Hello @yoshimitsuspeed ,
Sorry for the inconvenience!
I've found and fixed the problem with the feedrate output in the Heidenhain turning post and attached the updated version to my reply here. Another problem was that the post did not output G33 for threading, this is fixed now as well.
Could you please try it and give me feedback?
Thanks in advance!
Achim.N
Principal Technology Consultant
It's almost like autodesk could have spent about a third the paid hours and probably a tenth of my time if they had just put me directly in touch with you to try to improve their products instead of bouncing me through 3 days of "customer service" trying to convince me I should fix it myself or pay someone else to lol.
It also looks like after at least three separate times of me spending hours to compile, document, and show all my issues in extreme detail they must not have passed it on to you lol. I don't mean this as anything against you. I am glad someone is finally here who actually knows what they are talking about. I just probably have about 40 hours of my time invested to get to this point.
So first directly relating to threading. I get this error as soon as it starts the op.
I tried playing with different values in 208 and it seems to cause either path too short, or path longer than traverse path.
I think values B and P override the default and would probably be better for F360 to output but in a couple tries still couldn't find a happy middle value that didn't throw an error.
Then I disabled Fade thread end in the threading op and was able to get it to cut threads. This is progress but also a bummer because I really wanted to use that fade thread feature. But it is adding a canned cycle move that doesn't get along with what the machine wants to see.
So now with fade thread disabled I have successfully cut NPT tapered threads with acceptable success.
No onto other issues.
It seems they didn't pass on this issue either but it is still not outputting feedrates for G94 or G95 moves so I need to go input those manually every single time.
@yoshimitsuspeed wrote:
So now with fade thread disabled I have successfully cut NPT tapered threads with acceptable success.
Thats good! Not sure why the control errors when fade is enabled, cannot reproduce that here on the simulator. Which version is your control? DataPilot 620 / 4110 or older?
Regarding the G95/G94 feedrates, the feedrate output itself looks correct to me, so i assume the issue is that the feedrate must be output with the G94/G95 directly in the same line?
Achim.N
Principal Technology Consultant
Can you fix the G94 and 95 not outputting feedrates issue?
Now onto the older issues in my previous threads.
The tool numbers aren't outputting correctly and are especially an issue for drills.
Our machine expects the tool list tool number first, then the turret position second.
So if I have my drill in #50 in our tool list with tool details, offsets, etc, and that tool in the #4 slot in our turret I need to call 5004 in the machine interface or Gcode.
For most cutting tools if in the post processor section of the tool in the tool library I enter 4 for tool, and 50 for compensation offset it will output 450.
If I enter 50 for tool and 4 for compensation offset it will output 5004 which is what I need but I don't know if this will cause issues elsewhere as it seems backwards to me.
The bigger issue though is for drills it calls completely wrong either way.
If I do this
It outputs 400
If I enter
50
4
4
It outputs 5000
I need it to output 5004 for turret position number four and tool list number 50
Also I am back to trying to drill which is the first issue I posted about here 9 months ago and it looks like the canned drill cycles are also still not correct.
First error Q cannot be assigned to any function
I am thinking this is supposed to be P as that is what I have for pecking depth.
It also isn't calling out all the other data I entered in the chip breaking cycle like depth reduction, min pecking depth, or accumulated pecking depth which I am wondering if maybe that is the A value in the manual? Guess I'll try it lol.
@yoshimitsuspeed wrote:
Ugh okay turns out I didn't even need any of that but got mistaken because the boring bar is visualized in a way you can't tell top or bottom and it seemed backwards.
We've done some work (that's not yet in the Production build) to rectify this. The tool is more properly displayed as you would see it in the machine. Stay tuned for a future update (or you can join the Insider program to access it today).
@yoshimitsuspeed wrote:
Do people actually professionally use F360 CAM?
Many thousands of people do with excellent success. The issue (it appears) is that, to-date, there have been only 23 unique users who've tried the post you are working with, and you're the first that have offered feedback (good, bad or otherwise). You have an uncommon machine control, it seems, so we need to spend some time in getting the post sorted out.
Seth Madore
Customer Advocacy Manager - Manufacturing
Ok lets do this bit by bit.
In the attached post i´ve updated the following:
- Always output a feedrate with the G94/G95 command, that seems to be required for the control?
- The tool call is now 4 digits always and uses this format: Txxyy (tool number followed by the turret number)
- Added property "use Cycles" which allows you to disable drill cycle output. That should help you to move forward for now. We would need a manual of your control to be able to fix the drill cycle output, anything you can share there?
Achim.N
Principal Technology Consultant
