5 Helpful AE-CLOUD1 Setup Tips

The new AE-CLOUD1 kit comes pre-installed with a Renesas IoT Sandbox Data Intelligence binary that connects to the network with WiFi using a GT202 PMOD module included with the kit.

If you do not already have the kit, please contact Jesse Casman (jcasman@oppkey.com) to receive a coupon good for 50% off your future purchase. This coupon is also good for 50% off the SEGGER J-Link Lite for Renesas Synergy debugger and AE-Wi-Fi1 kit to add WiFi to your S5D9 IoT Fast Prototyping Kit (board only).

The first tutorial to go through is AE-CLOUD1 Diagnostics Intelligence With Synergy SSP 1.3.2 and WiFi.

Here are 5 tips to help you connect your new AE-CLOUD1 to Renesas IoT Sandbox Data Intelligence with WiFi easily.

1. Wait 90 Seconds After Plugging the Board In

When you first plug the board in, nothing happens. Wait 90 seconds.

Keep waiting for LED status lights.


In my tests, the Amber light comes on after 12 seconds. This indicates that the board is waiting for WiFi to be connected.

After 22 seconds since the USB power is plugged in, the board connects to WiFi and successfully connects to Renesas IoT Sandbox Data Intelligence. In my tests, the amber and green LEDs are solid for about 1 second, then the amber LED goes off and the green LED stays on.

When everything is working properly, the LED will be green. This is what you want to see.


Here’s a video of a successful boot sequence and connection to Renesas IoT Sandbox Data Intelligence.


When the board is connected to the Renesas IoT Sandbox, you will see the Board Online Status as “on” in the Last Value Table.

2. Access network.log

When you plug the S5D9 into your computer with a USB cable, it will mount as a USB drive. In the example below, the S5D9 board is USB Drive (E:). The default binary will generate a log file called network.log.

A successful connection will look like this.

3. Access ipconfig.txt


The default binary will also generate ipconfig.txt

4. Solid Green and Amber Indicates Trying to Connect to Data Intelligence

In a good boot sequence, the amber and green LEDs will stay on together briefly, probably less than a second. However, if you see solid green and amber lights stay on and it's stuck at this stage, the board is trying to connect to Data Intelligence. It connected to your WiFi router, but can’t access the Internet or can’t connect to Data Intelligence. The board is still trying to connect.


In your email, you should have received a message about activation.

The email has an attachment.

Make sure that you copied this file to your S5D9 board and ejected the board, then rebooted the board (pull out the USB power and the plug it back in).


5. All Lights Flashing Indicates Connection Failure

The board is no longer trying to connect. Please check your logs.


The AE-CLOUD1 kit provides useful network debugging information both with text logs written to the board’s flash storage as well as LED indicators. Understanding the available logs and LED messages will help in fixing network connectivity problems.

Next Steps

  • Has anyone tried the Medium One tutorial listed under Next Steps here? In Step 6, Noise Detection Workflow, I'm having trouble finding the "processed:last_voice_detected" tag in the Tag Config settings for the Last Value Table widget. Nothing shows up. I've refreshed, restarted, rebooted the board even. I've rebuilt the whole Python workflow. It's just copy and paste code, so I haven't tried to do anything tricky. Has any run into this?
  • In reply to Jesse Casman:

    I created a new topic to improve the tutorial. I provided a few tips for Tag Config settings. Let me know if you still have a problem. Also suggest you follow the tip about reducing the update to 3 minutes. If it's not clear, I'm happy to add more examples to change the update from 15 minutes to 3 minutes. renesasrulz.com/.../improving-ae-cloud1-diagnostics-intelligence-tutorial
  • In reply to codetricity:

    Yes, it's possible reducing the interval between updates would help. I'll try that.
  • I had the same issue that I could not find the processed:last_voice_detected at first. Then in the Tag box search box I typed Last_voice and it showed up. I clicked the check box and everything worked as in Tutorial.
  • In reply to Jesse Casman:

    I had the same issue but then I found out that in the Tag area, in search box, type processed:last_voice_detected and it showed up.