I am totally new in this field and forum. So perhaps my question might seem stupid, but:
Did anyone make any experience on connecting the MKR WIFI 1010 with the AWS IoT Cloud using MQTT? Is there a library on the board, which can be used?
is it possible to connect a normal position sensitive detector to the MKR 1010 or do one need adjustments etc.?
My Goal is to link the board with the AWS IoT Cloud (which I want to use as a MQTT Broker) and send the sensor output from the board over the cloud to a PLC. Apparently a Beckhoff PLC (with TwinCat 3) can be used for MQTT with the AWS IoT Cloud.
Is the MKR 1010 the right choice? Do you have any suggestions?
Have you tried MKR 1010 on AWS? I also want to know the answer. I found a paragraph in the article (MKR1010 | Hackaday)
"
But a new 8-bit microcontroller doesn’t make a WiFi-enabled Arduino. The wireless power behind the new Arduino comes from a custom ESP-32 based module from u-blox. There’s also a tiny crypto chip (Microchip’s ATECC508A) so the Uno WiFi will work with AWS.
"
MKR 1010 with AWS IoT is a perfect solution for my project as I am looking for a combination of most updated hardware with MQTT platform I can trust a 100% to be there 10 years.
However, having to create a unique certificate per board and register it on AWS eliminate the ability to simply reproduce boards for production and I wonder if anyone has an idea how to deal with this issue the day we need to distribute thousands of boards.
You could consider loading the provisioning sketch on the board at the time of production and having a desktop app that connects to the AWS API's directly to register the device directly.
Also, instead of storing the certificate and wifi credentials in the sketch. You could partition some of the flash on each board and use it for configuration, another option is to use the MKR MEM shield and it's on board flash for this.
You could consider loading the provisioning sketch on the board at the time of production and having a desktop app that connects to the AWS API's directly to register the device directly.
I will defiantly give that a try.
Also, instead of storing the certificate and wifi credentials in the sketch. You could partition some of the flash on each board and use it for configuration, another option is to use the MKR MEM shield and it's on board flash for this.
The Cryptochip stores the certificates so I dont think there should be an issue with that and obviously I will use the EEPROM for credentials and other parameters that may be modified by the user.
