Welcome to the Onshape forum! Ask questions and join in the discussions about everything Onshape.
First time visiting? Here are some places to start:- Looking for a certain topic? Check out the categories filter or use Search (upper right).
- Need support? Ask a question to our Community Support category.
- Please submit support tickets for bugs but you can request improvements in the Product Feedback category.
- Be respectful, on topic and if you see a problem, Flag it.
If you would like to contact our Community Manager personally, feel free to send a private message or an email.
Options
Strange value for no max axial limitation of a mate
C_Justin
Member Posts: 16 ✭
I have this block of json returned by the api. It's really strange since the mate is a revolute mate and I didn't set any limitation on Z axis rotation, but the json seems says the value is not null. Also, the value is 0 deg for maximum but in the document, the mate seems to have the freedom to rotate 360 degrees. I'm confused about the default value of each limitation.
{
"type" : 807,
"typeName" : "BTMParameterNullableQuantity",
"message" : {
"isNull" : false,
"nullValue" : "No minimum",
"units" : "",
"value" : 0.0,
"expression" : "0 deg",
"isInteger" : false,
"parameterId" : "limitAxialZMin",
"hasUserCode" : false,
"nodeId" : "nDu/OIODp1wkH+Fl"
}
}, {
"type" : 807,
"typeName" : "BTMParameterNullableQuantity",
"message" : {
"isNull" : false,
"nullValue" : "No maximum",
"units" : "",
"value" : 0.0,
"expression" : "0 deg",
"isInteger" : false,
"parameterId" : "limitAxialZMax",
"hasUserCode" : false,
"nodeId" : "hpo8dGfqMupMcyDl"
}
}
Tagged:
0
Best Answer
-
Options
Ethan_K
Member, Onshape Employees Posts: 57 
Hi @C_Justin,
If you look further up in the json, I'm guessing you'll see:{</code>{"type" : 144,</pre><pre> "typeName" : "BTMParameterBoolean",<br> "message" : {<br> "value" : false,<br> "parameterId" : "limitsEnabled",<br> "hasUserCode" : false,<br> "nodeId" : "tfSEeDEOd+kmV/8Z"<br> }<br>}</pre><br>Indicating that the limits are indeed not enabled. If this is the case, then we don't show the limits as editable and say there are none. Additionally, if there is the relevant message in the nullValue field, that indicates that there isn't a maximum or minimum. For instance, a set zxial min to 0 will look like:<br><br><pre class="CodeBlock"><code>"type" : 807,
"typeName" : "BTMParameterNullableQuantity",
"message" : {
"isNull" : false,
"nullValue" : "",
"units" : "",
"value" : 0.0,
"expression" : "0 deg",
"isInteger" : false,
"parameterId" : "limitAxialZMin",
"hasUserCode" : false,
"nodeId" : "hX1hE2yBXPj2wzH/"
}
}
Whereas an unset minimum would look like: (notice the changed nullValue field){"type" : 807,
"typeName" : "BTMParameterNullableQuantity",
"message" : {
"isNull" : false,
"nullValue" : "No minimum",
"units" : "",
"value" : 0.0,
"expression" : "0.0*deg",
"isInteger" : false,
"parameterId" : "limitAxialZMin",
"hasUserCode" : false,
"nodeId" : "hX1hE2yBXPj2wzH/"
}
}5
Answers
If you look further up in the json, I'm guessing you'll see:
{</code>{"type" : 144,</pre><pre> "typeName" : "BTMParameterBoolean",<br> "message" : {<br> "value" : false,<br> "parameterId" : "limitsEnabled",<br> "hasUserCode" : false,<br> "nodeId" : "tfSEeDEOd+kmV/8Z"<br> }<br>}</pre><br>Indicating that the limits are indeed not enabled. If this is the case, then we don't show the limits as editable and say there are none. Additionally, if there is the relevant message in the nullValue field, that indicates that there isn't a maximum or minimum. For instance, a set zxial min to 0 will look like:<br><br><pre class="CodeBlock"><code>Whereas an unset minimum would look like: (notice the changed nullValue field)
{