To upload your Arduino sketches to the Omzlo One, you simply follow these steps:Write your Arduino sketch in the Arduino IDE In the Sketch menu, click on "Export Compiled Binary"Go to the NoCan web interface, select the node and upload the binary.
To upload your Arduino sketches to the Omzlo One, you simply follow these steps:Write your Arduino sketch in the Arduino IDESelect "Arduino/Genuino Uno" from the Tools > Board menuIn the Sketch menu, click on "Export Compiled Binary"Go to the NoCan web interface, select the node and upload the binary.
What sense could it possibly make to use a 48 MHz ARM Cortex M0 merely as the interface to "the real workhorse", a 16 MHz ATMega328?
And on a slow CAN bus to boot, which is of interest to no one outside the automotive industry.
See my reply above. For an advanced user who doesn't care about software support there is no sense but for the typical Arduino user who values ease of use over performance it makes good sense (assuming the use of the ATmega328PB doesn't introduce significant complications, which I believe is not an issue here).Having no experience with CAN, I can't comment on that criticism, hopefully @l1l1 will do so.
Whenever I see a new dev board the first question to my mind is how well will this be supported by the Arduino ecosystem? We see people create nice hardware with fancy modern chips but often they don't make the extra effort on the software side of things. This even happens with official Arduino certified boards, which I think has led many potential customers to be wary of trying new hardware. If I understand correctly, this is not an issue for the Omzlo because it's binary compatible with ATmega328P and thus can take advantage of the excellent support for that chip that already exists. There will be no need to install an Omzlo hardware package and hope that out favorite libraries will happen to be compatible, you just treat it as an Uno with a superpower. Although you have mentioned this several times in your Kickstarter, I think that the sort of customer who would be concerned about this will not understand the term "binary compatible". One thing I think would help to make this clear would be to change:to something like: