Module vs developer kit

Autonomous Machines Jetson & Embedded Systems Jetson Xavier NX
#1

Im building an application intended to run in producion at a museum on jetson nano. My idea was to run it on the developer kit. it works fine but I wounder what are the downsides of doing this instead of running it on the module? The module comes without carrier board so in the case I am using that one I need to build something myself or buy some addon for connecting usb hdmi etc. So that makes the developer kit more convenient.

But are there other downsides that i might not be aware of. In the specs it says “non-production specification” but what does this really mean? For example that it cant handle be up and running longer periods of time etc. I dont know. Otherwise I rather stick to the developer kit but would be great to hear an opinion …

Has anyone experience of running jetson developer kit on an everydaybasis as on a museum? Did you experience any problems?

#2

Hi acro,

The devkit can’t be used on production, the developer kit is used to develop and test software in a pre-production environment. Jetson modules are designed for deployment in a production environment throughout their operating lifetime.
Please refer to https://developer.nvidia.com/embedded/faq%20#jetson-devkit-not-for-production

BTW, you issue is similar as below thread, also can be a reference How to take a jetson nano project to production

#3

The devkit can’t be used on production,

okej thanks. they will not survive? or why? just curious. :)
I have actually some difficulties to find the module version in sweden where I am located. as well as carrier board

#4

Warranty is the concern, the devkit is only one year, and will be expired automatically if it’s used as end product.

#5

thanks. But is it likely to break if used in an everyday situation? It is pretty convinient since it has GPIOs for there are no GPIOs in the module version right?

#6

For just a unit or two, the devkit should be fine for your purposes. You probably just want to get a case or enclosure for it to protect from dust and such. Typically, ‘production’ means deploying lots of units in volume. The commercial module has additional environmental qualifications that you can find in the datasheet, but you are just running it in a normal ambient environment (indoors).

The commercial module has all the same I/O as the module on the devkit. In fact, you can take one of the commercial modules and put it on the devkit and it will act the same. In both cases, there is additional I/O available that isn’t broken out by the standard devkit carrier board (which can be accessed via a custom carrier board or third-party carrier board)

#7

For just a unit or two, the devkit should be fine for your purposes.

You mean as long i wont put them in a cluster or maximum connectiting two nanos together there woudnt be any problem? And in that case the developer version of the nano will be a stable solution for everyday use in a museum environment. That sounds good. No I just need one. Maybe maybe two but likely not.

#8

I mean as long as you aren’t taking these into volume production and deploying lots of units - like a real product. Making a small-ish personal cluster is fine with the devkit too.