PiWeb won't accept Nominal input from characteristics editor, plus 2d curve?

[[Ow...]]

This may be a redundant question as I use just the basic version of PiWeb, but has anybody else noticed this? 

Currently running 7.8.08.

Another question regarding curve (sorry not right place to post but, time is limited), every time I bring in a 2D curve feature it says " nominal points are not exactly arranged in a plane"? 

[[Ma...]]

I think i've seen this PiWeb message on forum some years back.

About 2d curve - is your nominals in X ( or correct axis ) same for all points? It can be corrected in modifying nominals last tab.

[[Ow...]]

Please sign in to view this quote.

Regarding PiWeb, I'm going to try and restart the computer and Calypso, that fixes a lot of things.

Curve nominals are in the correct axis but, the Y numbers do differ around 0.10mm. 

The curve points were digitized to create the nominals, which never puts them all the same in plane axis, so I guess this makes sense. I've just never seen Calypso reporting that in past versions. I'll correct them and try again when time is available.

I do appreciate your quick reply Martin Jansky.

[[Ma...]]

Yeah restart do many magic things :-)

If you digitized that curve i would go extra mile to make correct curve with help of model because vectors will be bad too.

For start just correct that nominal axis which was used as cut, then you can try to correct nominals by trying setting as perpendicular to plane or axis of alignment - this should straighten them.

[[An...]]

For the PiWeb message, see :

 

 

[[Ow...]]

Please sign in to view this quote.

Restart didn't fix the PiWeb issue but Andy Block's post fixed that. I'm not sure how it got changed to "amount mode" , but selecting number scale fixed it :-).

Modifying the nominals with the constant value in the coordinate axis direction fixed the " nominal points are not exactly arranged in a plane" error.

I don't have a model, that's why I digitized it. I do have drawing showing the cam nominals and vectors and what I digitized is very close. When digitizing a involute type of curve and other small features, using a very very slow scanning speed of 0.3 or less is critical to getting good results.

When I get back to working in my office, I'll create the cad model, I just didn't have the time for this little one-on, one-off R&D project.

I couldn't edit my original post but, the amount the Y axis nominals differed from each other was less than 0.010 (not 0.1) and again, I don't ever remember Calypso giving that pop-up error and I believe this is the first curve I've digitized since loading Calypso version 2024 back in December. 

[[Ma...]]

Please sign in to view this username.

 I have VastXT - i am scanning 1mm/s - are you telling me, that running slower have a benefit for active head? I sometimes need to scan gears or similar things to make a drawing ( to be machined new part at our facility )

I am having hard time when i offset that curve, so i am leaving that at center of probe, reducing points and rest make in SolidWorks. Points are good, but sometimes vectors are doing such bad job.

Any hints ( that gear mention was just for imagination of part, no licence for gear and no need for that 🙂 )? Thanks

[[Ow...]]

Please sign in to view this quote.

Yes, slower will help, 0.3mm/s is where I'd start and I'm using a Vast Gold head. It does take a long time but, quicker than if you have to do it twice because you got bad results. 

Also it depends on the curvature, but using a point density (points recorded) spaced at least 0.075mm will help. The tighter the points spacing is, the slower you will have to scan to keep the head and probe from searching back and forth for a point. If still having vector issues, taking thousands of single points (instead of scanning) will help but even slower.