About Thingy52: 3D simulation file

[leejh]

Hello, Nordic.

I am working on an iOS App that uses a MPU9250 sensor to display a 3D simulation screen in my app. (It is same as motion control in Thingy52 App).

I have completed the firmware, but before that I leave a question as to whether the SCN file of the product I created is working properly in the Thingy app.

(Using H/W : Thingy52 , App : in Nordic Github)

My worked step is 

1. Exported .stl file from 3D image of my product (in Solidworks).

2. Imported the stl file in MeshLab and then Exported .obj file in MeshLab.

3. Imported the obj file in X-Code (Thingy project file), and converted to .scn file.

4. Deleted the existing scn file(thingy_obj.scn) and changed my scn file to thingy_obj.scn.

5. Created camera same position as original thingy app

The app run normally and receive sensor values, but the 3D image does not move.

This is the first time I have used 3D images. I think there is a problem when creating an SCN file or exporting a 3D image.

How did Thingy create 3D file? and What am I doing wrong?

I'll wait for your reply.

Thanks.

Regards,

James Lee

[Joakim Jakobsen]

Hi.

I haven't been able to reach our mobile developer that did this 3D image on the Thingy app. 

However, I talked to one of our other mobile developers and he asked if you can see if the values are applied to the 3D object correctly?

Best regards, 
Joakim

[leejh]

Yeah, for now I solved that my production 3D image(SCL) is not moving. The 3D file(SCL) object name and the childnode name should be set the same. 

Now I'm just wondering how the thingy created the 3D image.

Thank you for your reply

[Joakim Jakobsen]

Hi.

It seems that the developer who made the 3D image part of the nRF Thingy app is no longer working for Nordic.

I'll see if any of the other mobile developers have any knowledge about this.

Best regards,
Joakim