I have Itemcode (:MESC1 :MESC2 :MESC3 and etc. based on the bolt legth. Please have a look below for details. In isometric it is coming ok.
How to extract this in Isodraft boltreport ?. I hope this expert advice.
My opion, you list MESC in 1 line (:MESC1) sequently for 9 no in the Blength
i.e: 80mm -> x
90mm -> 81.38.15.075.1
100mm -> 81.38.15.077.1
....
then, MESC for bolting will come out in Isome
(with your settings for Bolt/Nut in Isome-Option-File refer to UDA)
If you are getting correct item code in isometrics, then you should be getting them in Bolt report also. Make sure that you have same options settings for bolt reporting.
It is rather obvious, the bolt length selected (165.1) is longer than the avaliable length (152.4). Suggestion - on DTAB, set a range of BLEN (152.4 170, 190). And :ABBCODE will have 3 other values (66666666 66666667 66666668) example. It will refere to the sequencial length in the same order. Please try that and respond please.
hi nerby. Thank you for you answer. Before I do an example can you clarify for me please:
1. we have a SPCO with a ref to SBOL element, where we put diameter and reference to NSTD array with available lenghts for this diameter. Coorect or not?
2. when PDMS calculates lenght of bolt, it compares with avalibable lenght form NSTD and takes nearest bigger. (Am I right or not ?)
3. If so, why we put by hand in element SBOL attrib [COLOR=#333333]Length 165.1mm?[/COLOR]
reply 1. You may set SBOL LENGTH to 0 and BDIA to 0
reply 2. It will take which ever is larger
reply 3. you have to set it and try it to see the result.
nerby, really works. Big thanks! I just found description why we have to add lenght in BLEN of SBOL element.
That was OLD boltin method. I will have to ubderstand how NEW bolting methid works also:) Bolts will drive me crazy.
UDA string is limited. If UDA is used to get the ITEM CODE for different length, you need to populate them in a sequential fashion of the UDA, in your example:
