Angle between Features.

[[os...]]

Hello,

I want to find the angle between two circles using angle between feature.
As seen in the results,


it gives different results only when I go to the report section. How can I fix this?

(I'm a rookie cmm user, sorry in advance for the question)

[[Ju...]]

The lower tolerances (Lower Allowances) should be negative. See if that fixes it.

[[os...]]

Please sign in to view this quote.

Actually, my exact problem is this, I want to see it as degrees and minutes in the report, but as you can see, an expression like "0.5240..." appears.

[[Ju...]]

Under the Measurement Plan tab, click Measurement Plan Editor Features. From here, you can set the Angle units.

AngleUnit.jpg

[[os...]]

I also checked there by degrees, minutes, seconds. so the values I want to see in the report, but I can't see.

[[Ün...]]

Osman merhaba, Bunu dener misin

[[os...]]

Selamlar Ünal Hocam,

Bunu kontrol ettim, olması gerektiği gibi benim sorun raporda çok alakasız değerler çıkıyor. 30 derece görmek istiyorum ancak desimal ifadeler geliyor.

[[Ma...]]

Problem here is wrong usage of angle between features.
Try using 3d line by recalling small and main circle ( just recall to get 2 points ). There is no way to report 30° as shown.

If it would be cylinders instead of circles, then it would not work.

[[os...]]

If you're talking about this, I've tried, the result is the same again.


Is what you're talking about that the report can't come up with a value like 30 degrees 5 minutes 14 seconds ?

[[Ma...]]

I see you have difference in Z axis - this should add inaccuracy - i tried two 3D lines, where both in X/Y were 10° apart and set 2° and 5° on Z/Y - report was ~10.4°

Even your nominals are wierd. 30° is 30 in number - unless you have RADIANS - 30°deg is 0,5236° rad - so check again.
Check Enviroment -> system settings where you setup langage of protocol

[[os...]]

I paid attention to the topic you said, it was similar in my settings.

there's no problem with my calypso values, it's already turning into radiation in the report.


What I'm trying to fix is actually the value in the report.

[[Ma...]]

So one last check.
When you go to edit PiWeb Designer and edit your selected protocol, what you find on settings?
Tools -> Settings ( Ctrl+Shift+O )

[[os...]]

I think the solution to the problem is right this time. however, there is no "output unit angle" section on my page, which is correct this time. however, the "output unit angle" section on my page 😕 😕

[[Ma...]]

I ran out of ideas. Let's summon Jeffrey Penrod

Please sign in to view this quote.

[[os...]]

Please sign in to view this quote.

I have a question,

[[Ün...]]

Osman, bu ayarları yaptıktan sonra bilgisayarı aç/kapat yaptın mı?
Bu ayarlardan sonra raporda doğru şekilde görebilmen gerekir.

[[os...]]

Yaptım hocam ancak sonuç değişmiyor. tüm sistemi açıp kapatmayı deneyeyim bir de.

[[Je...]]

What version of CALYPSO are you running? This looks like a units conversion issue that was a bug in several older versions that was corrected by Service Packs. Please look at your CALYPSO version #.#.#### in the "?" heading in CALYPSO and I will review . I would also suggest going to the DOWNLOAD CENTER on the PORTAL and verifying you are on the most recent SP (and using something > 7.#)

[[os...]]

My CALYPSO version is "Version 6.2.2808(10.07.2018)". other details "CALYPSO 2016 , ServicePack 9"

" I would also suggest going to the DOWNLOAD CENTER on the PORTAL and verifying you are on the most recent SP (and using something > 7.#)"

I will try this suggestion of yours, something I have not done before, I will do by following the steps you mentioned.

[[Je...]]

There were issues with conversion in early versions of PiWeb from CALYPSO. I would suggest a few different things to try.
1st and foremost - Upgrade to a newer version of CALYPSO + PiWeb (these errors have been addressed in newer versions)
2nd - Change tolerance type to Decimal degrees instead of DMS (if the error is from DMS conversion - this is my first suspicion)
3rd - Change tolerance type to Radians instead of DMS (if the error is from DMS conversion) - See if a change is noticed.
4th - Use a Result Element and "getActual()" to report the value from a Result Element (if the error exists within the "Angle Between Features" characteristic)


The values look to be converting from DMS to Radians into PiWeb and then not making it back to DMS in PiWeb. My first suggestion is Decimal degrees as a trial.