[lucamark]

On units: we do support metadata in the model, but I wouldn’t position it today as a full unit-aware workflow with automatic Imperial/SI conversion across the whole tool. If that part is important for your use case, I’m happy to understand more of it

[gus_massa]

If microcontroler a important for your project, I recommend to put a photo (or a graphic) of a microcontroler near the top of the front page. Otherwise it may be missed.

Hi from Argentina! 100% metric here, except for the water pipes and faucets. I still have nightmares about metric vs imperial screws when I was in a lab a few years ago. Anyway, I expect USA to be a big market for your project and they expect to see everything using the imperial system.

[lucamark]

Good point! Today Modeloop mostly treats signals as numeric values with optional metadata.

I probably wouldn’t want Modeloop to automatically convert between SI and Imperial units inside the model, because that can make the behavior less explicit.

What I do think is useful is documenting that a certain signal represents speed in mph, temperature in degC, pressure in psi, etc. So the value stays exactly what the model defines, but the user and generated artifacts have clearer semantics about what each signal represents.