I selected the surfaces to machine and they are not machined.

[cfisichella]

I might have a video card problem. Solidworks complained about video incompatibility on start up but I ignored it. In HSM, I selected the surfaces to machine. It was a strange exercise because I had to use select other and then always have the desired surface facing away.

Eventually, all the surfaces were selected. I selected a single stay away surface using the same "select other" method. When I view the simulation, HSM excludes two of the surfaces, but does the rest of them. 

It would be great if I could give you the CAD from a secure link. I cannot post it here. 

[kacper.suchomski · Accepted solution]

Hi

It's hard to say anything without the file. No one knows what you clicked, what type of surface you want to machine, or what strategy you chose. We also can't tell where you might have made a mistake, because the descriptions show good intentions, not real actions.

Attach the file and add a screen with the target machining faces marking.

[lenny_1962]

Do you have select thru surfaces selected?

Are you in an an Assemble?

What version of SW\HSMWorks are you using?

What Graphics card? ram on it?

What OS, win 10, 11, home or pro?

[cfisichella]

Hi Lenny_1962,

I tried both assembly and part mode. I tried saving the part as a .SAT file. I am using HSMworks 2025, the rest I cannot disclose only that it complies with Solidworks. You raise an interesting point. I do not know if I am in select thru surfaces mode. I just open Solidworks and accept the defaults. I only have to do that when I am in the model dialog section. The check surfaces works fine. I got it to work by facing the surface away and using select other. HSW did a great job with the tool paths and the GCODE generation.

Best Regards,

Chris

[lenny_1962]

I've been a SW guy since SW97+ so it sounds like you are not that experienced with SW, but I could be wrong.

I've been using SW2024\HSMWorks 2025 for the last years and do not have the this you say., but then I have a dell workstation with pro graphics card.

Give me info on PC, what graphics card and ram for both card and pc along with OS. desktop or laptop?

Are you using SW24 or SW25?

does tis happen on all parts? can you just model something up and replicate then you can upload that so we can see what happening.

is it a native SW part or imported?

lots of unknown this hence my questions.

lenny

[kacper.suchomski]

I do not agree with the thesis that this is a hardware problem.

HSMWorks has several commands for selecting the machined area, some of which are mutually contradictory.
Additionally, different indication possibilities are available for different machining strategies.
Additionally, sometimes indicating the area may require additional modeling work.

All this means that such problems should be solved individually with a dedicated approach.

That is why I think you should attach a file and several screenshots with some information - what is to be machined; what surface cannot be touched in this operation; what strategy you used; what tool you used.
I understand the company secret and NDA.
But this is not a problem. Just create a new file with a fragment of the machined geometry and the surroundings - it is about simulating the situation, not a specific detail.

[cfisichella]

Hi Kacper and Lenny,

I agree with Lenny's idea.  I should be able to make a look-a-like part that does disclose anything. I will work on that. It definitely will not get that done today, but I will try to do it Monday. It would be nice to have normal behavior for the software.

We are using SW2020 with HSW 2025. I read they are compatible, so I went with it. I started SWX and it did not complain about my video card.  This is the first part we have made using HWS. The pretend part will be the second. 

I originally started with a native SWX2017 part. Once I noticed the problems, I saved to ACIS format. The problem persisted, so I reached out the forums. 

I hope you two have a great weekend,

Chris

[lenny_1962 · Accepted solution]

FYI, for SolidWorks use Parasolid "X_T" that is the software kernel not ACIS, that is an DS Native aka CATI Kernel, SW rents from Siemens.

AS for SW2020 and HSMWorks 2025, that usually isn't supported, it's a 3 year rule, so HSMWorks 2022 would be the last.

here:

https://cam.autodesk.com/releases/hsmworks-releases/hsmworks-2025-1-release-notes

[lenny_1962]

FYI I used to be a SW Applications Engineer for the AZ SW VAR, though it was 21 years ago.

[cfisichella]

Here is a model that displays the problem. Thanks for pointing out the software incompatibility. I thought I read compatibility somewhere else. On the 3D contour, I am trying to get the software to do the radii. Selecting those radius surfaces was not working well on my machine. Perhaps it will work well on your machine. But this model displays the problem. You need to find the "Model" section and then try to select surfaces The "Check" section also has you select surfaces, but this one works fine. 

[lenny_1962]

I do not have SW 22 only 23 thru 25 on my machine so you will not be able to see what I did.

From what I see you are thinking way to hard about setups aka XYZ and all the planes. just a simple point or vertex, face to get your zero's.

To cut the radius I use Blend, it will give you a smooth surface, 3D contour is like a topo map, flat areas big steps, more vertical small steps.

To get to Blend in HSMWorks you have to go to Beta Mode: read here: https://forums.autodesk.com/t5/hsm-support-forum/blend-toolpath-not-available-hsmworks/m-p/11134964

[kacper.suchomski]

Here you can see how the individual options affect the behavior of Contour 3D and compare it to Blend.