Lfx Tool Custom Mod Apk

0 views
Skip to first unread message

Gabby Dreher

unread,
Aug 5, 2024, 7:43:00 AM8/5/24
to acstanemun
Wehave operated continuously since 1976, and many of our customers have been with us for more than ten years. Our expertise is broad and deep, with skills that include CNC grinding, medical tool grinding, OD and ID grinding, and Wire EDM.

I have a custom profile that I use for creating holes in CLT-panels. I would like to use the opening tool instead to create these holes rather than a beam with a custom profile.

In plan view and on a slab I can paste the custom shape and use the magic wand with opening tool to acheive this, but I cannot save the shape as afavorite and thus not use it on walls.

I have tried a work around and use "Connect/Create opening from selection" however the shape of the custom profile is translated in to the nearest circular or rectangular opening (in this case a rectangle).



Has anyone been able to save a custom shape for the opening tool so that it can be used on walls?



Thanks!


i am using the service now input tool to connect directly to SN tables to fetch data in alteryx workflows. However, one of the tables contains over 20M records and i need to figure out a way to filter the records before the input tool fetches all the records.


I sincerely hope you have figured this out, but for those who are also searching for the answer to this, I spent most of this afternoon trying a ridiculous number of variations. May I point out that the Information text does NOT really help:


I tried so many variations with "sysparm_query=" at the beginning, which apparently you should NOT do. I tried the display value, as the Information text shows, with and without double-quotes, to no avail. I tried the sys_id value with and without quotes. I finally got the expected results from this:


I've created a custom script tool. And I want to be able to describe what to do for each parameter. I would think you could edit the little info box that appears when you hover over it. Right now it's blank.


The columns names are not the same on both side of the output tool, so I understand this is the cause of the issue.

It somehow doesn't make sense because I'd use the manual mapping option specifically when the name are different (if they are identical the 'Map by name' option is sufficient). Or am I missing the point?



Thanks again!


I would suggest you try installing the ODBC driver again or try pushing the data into another table. This error can also occur due to an older version of Alteryx. You can also try installing the newer version.


In order to do the custom mapping enabled, please make sure the table you want to map with (I mean output table) should be created in the database first and once done then you will be able to see the table structure to map it manually! Hope it helps.


I am trying to create a custom tool profile for a small single-point thread mill. I've managed to do this several times in the past, but when I select the file with the profile, I get a warning message that says "Problems with custom tool file or data". I've checked the chain for gaps and different Z levels and all the usual stuff, but Mastercam (X3) won't let me use it. I've even tried it with and without the centerline. Makes no difference. Any ideas here? File is attached.


Okay... I finally got this to work. How? I dont know. First off I had the step drill drawn up like it was a lathe part. Only half of it. Then I mirrored the geometry about 2 points to get the full tool. I then joined the two lines that made up the end of the opposite the drill point. I then added a center line. Saved the file. Then I removed the centerline and deleted half of the tool again. Now the message has gone away and the tool displays in the backplot properly. I did use "Undefined" as well from the outset of all of this. Why is this such as hassle?


you got it to work and it sounds correct. You don't or shouldn't have to draw the whole diameter of the tool, only half of it. Sometimes it just takes redoing it the same way and it will work. I dunno. It does become easier the more you do it, though. Glad you got it.


I just posted this on another thread but for someone who searches this and comes across this thread instead of the other one I'll post it here too. I would make a link to the other thread however I think these links get broken over time.


Save the file as a DXF and load the DXF file and voila! There is a reason to doing it from the Tool Manager and not the Mastercam Interface which would take a while to explain. If anyone wants me to explain it let me know.


Ok...I'm hesitating to post the reason due to my lack of knowledge in Mastercam, but here it goes...I could be wrong about this...but the real reason to create the tool in the Tool Manager program is because of the holder not the tool. However creating the holder in the Tool Manager Program follows the same process as creating the tool other than the fact that you place the holder on the NOCUT layer.


I BELIEVE (based on limited experience) When you create a holder within the Mastercam interface the only way to get that holder into your library is to marry it up with a tool upon the creation of a toolpath and then export or "save" that "tool assembly" into the library by selecting the tool within the tool manager and right clicking the tool and selecting "Save to Library".


Here is the issue with this....when you open that tool library in the Tool Manager program you will find the tool assembled with the holder in tool "Assemblies" I cant figure out a way to get the Holder into the "Holders Section" So that I can use the holder on different tools. Basically the holder is locked to that tool.


It can be done, I personally manage my holders and tools in separate tool dbs just for this. Then, I join them into machine specific dbs. It seems to be a little smoother to use holders and tools when maintained separately. Keep in mind I've only been using Mastercam for 5 years and am biased by existing perception of how it "should" work coming from 11 years of other softwares.


It can be done, I personally manage my holders and tools in separate tool dbs just for this. Then, I join them into machine specific dbs. It seems to be a little smoother to use holders and tools when maintained separately. Keep in mind I've only been using Mastercam for 5 years and am biased by existing perception of how it "should" work coming from 11 years of other softwares.


This is a good idea to some extent. How did you build your holders? Did you build them within the Tool Manager Program or did you build them within Mastercam and then export them somehow to your ToolDatabase. "Somehow" is the key word. I don't know how to build a holder within Mastercam and save just the holder to a tool database that when opened with the Tool Manager Program it recognizes it as a Tool Holder. The only way I know how to do this is just to build the holder within the Tool Manager Program by importing a DXF file or by using the tool holder builder.


The reasoning behind this is that I'm trying to standardize projection lengths so that operators and programmers don't use random projection lengths when building tools. If your using a 3/8 Endmill with a 1.00" flute length then the standard projection length would be either 1.500" or 1.375". It's all about automation. Automation works better when things are standardized.


I build them in both. If I only need to build one, I usually do it on the fly inside of Mastercam. If I have for example bought a new batch of holders or have a new customer I will use the Tool Manager to create them - it flows better when creating multiple tools.


Hi Jlw. Thanks for your feedback. You are correct, the only question I have is how to export just the holder which I have created in Mastercam to a Tool Database so that it can be assembled with other tools within the Tool Manager Program. I am running Mastercam Version 2019. If you have that answer I would like to know and I appreciate your efforts on this. It's no biggie however because I now know the prerequisites for the DXF file so I can do it within the Tool Manager Program


Thank-you jlw! That's exactly what I was missing. I didn't realize there was a contextual menu at the holder section which allowed the creation and saving of Tool Holders as well as libraries. Thats pretty decent of you. Thanks for your efforts. Perfect.


Hey guys, has anyone else come across this? No matter what I do, if there is a radius at the end of the holder, I get a concave cone on the end of the holder. This causes tools to not assemble in Tool Manager. Chamfers on the end of holders are not a problem. This is what my .dxf looks like. Level 1 is "CUT" with 0 entities, level 2 is "NOCUT" with all of the entities.


You can create custom lenses with your own pillars, questions, best practices, and improvement plan. You apply custom lenses to a workload in the same way that you apply AWS provided lenses. You can also share custom lenses that you create with other AWS accounts, and custom lenses owned by others can be shared with you.

3a8082e126
Reply all
Reply to author
Forward
0 new messages