RoadTest: Enroll to Review the Infineon AIROC™ Cloud Connectivity Manager Eval Kit
Author: rsc
Creation date:
Evaluation Type: Evaluation Boards
Did you receive all parts the manufacturer stated would be included in the package?: True
What other parts do you consider comparable to this product?: Avnet Azure Sphere MT3260 Starter Kit
What were the biggest problems encountered?: Connecting to the cloud, WiFi credentials issues.
Detailed Review:
Infineon AIROC
Cloud Connectivity Manager Eval Kit
Unboxing:
The IFW956810 Infineon AIROC Cloud Connectivity Manager Eval Kit arrived in a nice large foam filled plastic box.
The CCM was overly protected on all sides with foam, and came with a USB-C adapter cord and a small getting started card under the foam.
Initial Connection to PC
The CCM connected to the PC without any issue and ends up under the device manager as two serial ports.
Running the Demo:
Connecting TerraTerm to the CCM kit was quick and easy. To run the demo program on AWS, a list of AT+ modem commands is required to be executed.
The issue I ran into was connecting to the WiFi.
The Quick startup guide says to use these two commands:
AT+CONF SSID = <SSID>
AT+CONF Passphrase = <Passphrase>
This is fine if that's how your router security is configured. At work, however, our security is different
We have two choices, 1) SSID and no Passphrase, or 2) SSID, USERID, Passphrase
I could not figure out how to get either of these methods to work with the AT+ commands, so I instead took the part home to work on.
At this point I was able to get the WiFi connected, however, the AWS demo would connect then crash giving me an MQTT error:
>> UNABLE TO CONNECT MQTT device authentication failure.
AT+CONNECT
ERR14 5 UNABLE TO CONNECT MQTT device authentication failure
AT+DIAG PING 8.8.8.8
OK Received ping response in 32ms
AT+DIAG PING a5x45cxzf4ozn-ats.iot.us-east-1.amazonaws.com
ERR43 PING FAILED Invalid IP
AT+DIAG PING 8.8.8.8
OK Received ping response in 32ms
AT+CONF Endpoint= a5x45cxzf4ozn-ats.iot.us-east-1.amazonaws.com
OK
AT+CONNECT
ERR14 5 UNABLE TO CONNECT MQTT device authentication failure
AT+DIAG PING a5x45cxzf4ozn-ats.iot.us-east-1.amazonaws.com
ERR43 PING FAILED Invalid IP
Then I found another Quick connect guide on the Infineon web site called :QuickConnect_infineon_v1.0_windows.x64 and tried that.
It would connect to the web and AWS, but would still not run the data visualization part of the demo.
After several hours of trying different things, I deleted all my AWS "Things" and registered a new account on AWS then the Infineon demo would run.
This is part of the automated script that ran OK. The random numbers are different than the screen capture shows above.
19:54:43 - Provisioning complete. Retrieving thing name from the device.
19:54:43 - Fetching ThingName from the device
19:54:43 - Sending serial command: AT+CONF? ThingName to the device
19:54:43 - Device thingName is Infineon_0100048f3033323293fb38520597d37b
19:54:43 - ---------------------------------------------------------------------
19:54:43 - Starting AWS Session
19:54:44 - AWS Session Initialized
19:54:59 - ---------------------------------------------------------------------
19:54:59 - The file CLICK_ME.html was created in the Expresslink folder.
CLICK_ME.html will open the visualizer in a browser and display board
data when it is connected to AWS.
19:54:59 - Would you like to open the visualizer website?
19:54:59 - [Y/N]: y
19:55:02 - Connect to IoT Endpoint by sending AT+CONNECT command to the device.
19:55:02 - Connected to the Cloud.
19:55:06 - Configuring MQTT topic name by sending AT+CONF Topic1= ****** to
device.
19:55:06 - Sending Command to device: AT+SEND1 [{"label": "Random Values",
"display_type": "line_graph", "values": [{"unit": "C", "value": 10,
"label": ""}]}]
19:55:08 - Sending Command to device: AT+SEND1 [{"label": "Random Values",
"display_type": "line_graph", "values": [{"unit": "C", "value": 10,
"label": ""}]}]
19:55:09 - Sending Command to device: AT+SEND1 [{"label": "Random Values",
"display_type": "line_graph", "values": [{"unit": "C", "value": 3,
"label": ""}]}]
I sent some random JSON messages and it seemed to be working also
I tried to Subscribe/Publish topic messages to and from my new AWS account with some success, although some messages bounced back to the "Thing"
At least I think I managed to do what the road test required and run the demo connecting to AWS and passing some messages back and forth to the device.
I spent many more hours on this road test than I planned to do, and I now remember why I haven't used Azure/AWS in a few years.
The AWS dashboard can get very complicated very quickly.
Next Steps:
What I would like to do next with this board is to connect a few real sensors and send the data to AWS.
There is no information I have found yet that describes how to recompile the source code, add GPIO data or serial data to the board and send it to AWS.
Using AT+ modem commands is a 40 year old technology. https://en.wikipedia.org/wiki/Hayes_AT_command_set
