well just a short test importing your sat-file in solid edge + moi3d gave 1000 x 1000 x 1000 mm
best regards

Also looks OK in Fusion.
Larry

Both MOI3D and Alibre Design bring it in at 1m square. There is usually a bug with scaling, happens with the stp in v12 and many other issues relating to the imperial to metric conversion. It could be that shark sees it the 1meter as 1unit, and since it's made in imperial units displays 1inch? I don't know but that would be my guess, either way doesn't help with the import!

Hi,

I asked the question and got a response back. I then looked for more info on how to interpret SAT file data strings and found this link https://paulbourke.net/dataformats/sat/sat.pdf

The header string contains various sub strings to identify the file aka

Save File Header
Topic: *SAT Save and Restore
The first record of the ACIS save file is a header, such as:

712 0 4 0 11 Scheme AIDE 11 ACIS 7.0 NT 24 Mon Apr 09 16:44:18 2001 -1 9.9999999999999995e-007 1e-010

SAT Format D 7.0
...... An encoded version number. In the example, this is “712”, which means the release is major release 7, minor release 1, and point release 2.
...... The total number of saved data records, or zero. If zero, then an end mark is required.
...... A count of the number of entities in the original entity list that were saved to the part file.
...... The least significant bit of this number is used to indicate whether or not history has been saved in this save file.
...... String length for the product string: “11”.
...... ID for the product which produced the file: “Scheme AIDE”. ...... String length for the ACIS version string: “11”.
...... ACIS version which produced the file: “ACIS 7.0 NT”. This may be different from the file version and can include the major release number, the minor release number, and the point release number. It also includes the platform on which it was produced.
...... String length for the date string: “24”.
...... Date file produced (in C ctime format): “Mon Apr 09 16:44:18 2001”.
...... Number of millimeters represented by each unit in the model: “-1”.
...... Value of resabs when the file was produced: “9.9999999999999995e-007”. Real . . .
...... Value of resnor when the file was produced: “1e-10”.

so if you look at the header file from damhave's file aka

10 Techsoft3D 15 ACIS 5.0 Darwin 25 Wed May 8 16:39:50 2024_ 1000 9.999999999999999547e-07 1.000000000000000036e-10

so it was produced by Techsoft 3D. and is an ACIS 5 format and the units are "1000", which is a little odd.

What it does suggest however and the response is not mine, is that maybe the other folks have made a mistake and nobody has picked up on it yet.

Mike

Hi Danny

I'm not sure that "-1" is unitless, by default ACIS files from what I've read recently were historically unitless, but then later the units become millimetres by default... and the user saving the file was given options later to apply a unit designation that becomes part of the header file string and can be parsed out when imported etc.

http://www-isl.ece.arizo.../ACIS/FCG/08TOL/0006.HTM

Maybe "-1" just means millimetres

Mike

PS I tried entering -1 in your header file and importing it the TCAD I'm using and I had to force quit, as the spinning beachball was looking at me, however when I changed the units to "1" vs "1000" I saw a 1mm cube, and a 25.4mm cube

Hi 24c,
Thanks a lot!
I think the hint is in the last paragraph in the link you send. It is up to the application to do the scaling.
maybe "unitless" is not the right word for -1. it should probably be "no scaling" (default mm units) but unitless was the word I found in the autodesk link.

I just tried to set SharkCAD pro to meter units and export the ACIS SAT file for a 1mx1mx1m cube made in Shark. then it correctly writes a scaling factor of 1000 (fiie attached)
But when importing this SharkCAD generated ACIS SAT file the cube becomes 25.4mm x 25.4mm x 25.4mm in SharkCAD. Both when Shark units is set to mm and meter units)

It means that SharkCAD cannot read its OWN file. Something is wrong in the SharkCAD v14 ACIS SAT import.

(the SharkCAD generated ACIS SAT imports with correct size in Plasticity).
kind regards
Danny

Edited by user Friday, May 10, 2024 2:48:37 AM(UTC)  | Reason: added info mm

ok not always a bug just when the scaling factor is 1000 SharkCAD cannot read its own SAT files (and other SAT files) , but anyway I think that not working in SI units (meters) is something that should be fixed very fast ;-)
kind regards
Danny

Edited by user Friday, May 10, 2024 4:56:30 AM(UTC)  | Reason: Not specified

Hi 24c
Have you tested the TCAD export with both with mm and meter units in the preferences?
(I am asking just to be sure that we are testing the same)
When setting the units to meter (see attachement- I guess it is more or less the same in TCAD) the scaling factor in the SAT file becomes 1000 in SharkCAD export (ACIS SAT v26) when I export the 1x1x1 (meter units) cube.
kind regards
Danny

Edited by user Friday, May 10, 2024 9:26:23 AM(UTC)  | Reason: Not specified

@24c Thank you very much for your help.