Hi everybody,

I have a value of 3516.41mm and I want to round it to the nearest whole number.
I have tried to use the round command and it seems to round up to the nearest 10 so 3516.41mm would round up to 3520mm.
So how do I get would I go about rounding to the nearest whole number?

(I don

Internally Inventor does all calcs in cm units. I suspect this is what is causing this. You can get around it by doing the following



IMO this is a bug as we have specified the unit of B to be mm.

_________________
Sean Dotson, PE
RND Automation & Engineering
Free 30 day trial of iPropWiz v5
Follow @seandotson & @mcadforums & @rndautomationon Twitter

Great thanks for the help!

Is there any reason why the parameters B and C show up in red, is this just due to the fact that it

However, the formula
ceil(isolate(a;mm;ul)) results in the number 3617
For it to work, you have to set the units for b to ul. Or you can convert twice from from mm to ul and back as shown in e

Odd that ceil and floor use UL as units. You'd think they would use the units of the argument...

_________________
Sean Dotson, PE
RND Automation & Engineering
Free 30 day trial of iPropWiz v5
Follow @seandotson & @mcadforums & @rndautomationon Twitter

You could use this idea to avoid the formula appearing in red. Red color indicates wrong syntax, since the round function requires a unitless (ul) value.

_________________
Udaya Gunasena
Inventor development

Udaya, I always argued that a red formula should not compute. As you can see I get the "correct" answer but the formula was technically wrong. It should not evaluate if the units do not match.

And why is round unitless anyway? It should take the units of the argument.

_________________
Sean Dotson, PE
RND Automation & Engineering
Free 30 day trial of iPropWiz v5
Follow @seandotson & @mcadforums & @rndautomationon Twitter

and it shouldn't delete the 'red' line if you mistype something. It should give you the opportunity to fix your typing error, or better still, like Excel, it should offer to try to help you fix it.

I was not involved with these decisions so my explanation here is, at best, an educated guess.

Regarding not computing or evaluating when there is an error, it represents one school of thought, which is not without its own issues. Inventor

_________________
Udaya Gunasena
Inventor development

No flames here Udaya, you know that.

OK so if you hole the values internally (regardless of units) then this should work:

I use the round command d=round(a) in units of cm it would take the argument a (say in mm) and then display the result as in cm. So for example if d were in cm then d=round(22.7mm) would be 23cm. Basically d defines the units and the round command takes ANY units.

I realize you were not involved in these very early decisions but it seems like there are a few holes in the workflow.

_________________
Sean Dotson, PE
RND Automation & Engineering
Free 30 day trial of iPropWiz v5
Follow @seandotson & @mcadforums & @rndautomationon Twitter

My point about the 'red' is we know it means something is wrong, but hitting a return on it should not cause the line to be deleted, as more often than not, we were close, but made a typo or error in judgement. When 'red' we should be put back editing the 'red'. We should be prevented from moving away from the edit until it is right, or we explicitly cancel it.

What I would expect if I don't understand what I am doing wrong, is the ability to edit it until I get it right, and hitting F1 (help) will assist me in reaching a correct solution. Now, how do we get out? Hitting Esc, RMB / Cancel or Ctrl Z. Those would all qualify as "As Expected". What is not expected is having my edit work disappear.