Connect Tech - NGX004-02 - Quark Carrier + NVIDIA® Jetson Nano™ Module + Active Thermal

[salvi-mattia]

Description	Field
Datasheet component	carrier , heatsink , jetson nano
Project	4k head
Alias Creo	CONNECTTECH_NGX004-02
IIT-Code	[if available]
Applicant	@salvi-mattia
Supervisor	@fiorisi
Maintainer	Marcello Savoldi, @marcellosavoldi
Coworkers	@icub-tech-iit/silo-mech

Attachment:

Notes:

Checklist:

Complete the checklist in order to proceed with the request.

• [x] Created the Alias following the standard convention.
• [ ] Added, if necessary, the source files (STEP, IGS, etc), the links/datasheets/drawings or other information used to create the library part.
• [x] File imported using the Creo start part commercial.
• [x] Checked mass properties.
• [x] Checked if one special case applies to this component.
• [x] Converted the files with the EDU-COM license.
• [x] Created IIT code in WINGST with manufacturer and at least one supplier.

[salvi-mattia]

16446 - Quark Carrier + NVIDIA® Jetson Nano™ Module + Active Thermal NGX004-02

we need to check weight and mounting while the assembly will be here

[pattacini]

Hi @salvi-mattia

For the weights, you could check some values taken by @Mick3Lozzo in https://github.com/icub-tech-iit/study-icub-head/issues/6.

[MrAndrea]

Hi @pattacini, @salvi-mattia, why did you assign only the Wingst code 16446 for this group of 3 components and not 3 different codes?

cc @marcellosavoldi

[pattacini]

For this specific issue, I'll let @salvi-mattia answer. Calling for @fiorisi too, as I remember we talked about this topic in the last board meetings.

[salvi-mattia]

Hi @pattacini, @salvi-mattia, why did you assign only the Wingst code 16446 for this group of 3 components and not 3 different codes?

cc @marcellosavoldi

@fiorisi told me to do so because this is a single code we order as a single part

[fiorisi]

@fiorisi told me to do so because this is a single code we order as a single part

Yes, unfortunately we didn't have any clear specification and we selected the code of the kit.

[MrAndrea]

Thanks. Now we have to replace the Nano board with the Xavier NX as written in this comment, and the Xavier NX has 16487 as code. Do we add a new Wingst code for the new group or do we split the 3 components?

[salvi-mattia]

the day we created this component me and @fiorisi spent a long time checking wich is the code we are coing to order and we found that we are going to order the whole pack and not th single components. as we saw here and here we always spoke about the pack as a pack

as we can see also here

the code is ordered as a single code and created in wingst by @maggia80

this is why me and @fiorisi chosed to create the code this way following the guidelines

furthermore this code has ELTR category, so it doesn.t came out from mechBOM

If any discussion chenged anything I was not informed about.

Please let me know if I'm supposed to change anything and what

[fiorisi]

Thanks @salvi-mattia for the detailed comment.

Probably at this point it would be useful to have a clear list and connection schematics using the dedicated issue template: https://github.com/icub-tech-iit/mechatronics/issues/new/choose

[salvi-mattia]

let's assume from the OP that the whole code weights 46+33+1.4= 80.4g this seems not to be coherent with this at the moment we do not have a physical specimen to be weighed

[salvi-mattia]

talking with @fiorisi fe found out that the correct weight of the here discussed boards pack is 46+33+1.4+18 (https://www.waveshare.com/jetson-nano-module.htm) = 98.4g

[salvi-mattia]

i guess we can close @fiorisi