Bonjour
J'ai rencontré un bug lorsque j'ai voulu générer un cas d'application avec l'interface graphique.
J'ai paramétré ma simulation et lorsque je la lance j'ai ce message qui apparait :
"Elementary swept volume corrupted due to excessive vibration or elementary cutting face too close to the tool axis." et aucun effort n'est enregistré.
J'ai testé un autre outil qui fonctionnait sur une autre simulation, la même erreur est apparue.
Vous trouverez ci-dessous les paramètres que j'ai utilisé pour configurer mon outil et mon tapis de dexel :
Hello,In general, the…
Hello,
In general, the mentioned bug, "Elementary swept volume is corrupted due to excessive vibrations or elementary cutting face too close to the tool axis", is a result of self-intersection of the elementary volumes swept by each elementary cutting face at each increment of the movement (rotation and displacement). In that case, it's impossible to correctly calculate the volume and estimate the amount of removed material. Thus, in general it's recommended to verify the location of the elementary tools or check the vibrations. You can find more details here: Negative swept volume — nessy2m User Guide 2024.1.1 documentation.
However, in the case you presented, the simulation is kinematic (i.e. without vibrations) and the tool is correct. Your request helped us identify a bug in the generation of the dexel carpets that appeared in the version VP2024.1. It appears if the origin of the dexel box basis (R_dbox Origin position in Rp) is different from the origin of the Workpiece basis Rp). This bug was fixed in the version VP2024.1.1