COM Port not available on Mongoose OS for IoT sensor device TI CC3200 - google-cloud-platform

Just want to build Google IOT core with mongoose OS running for sensing temperature data on google PUBSUB.
I have a problem starting from beginning while not able to the connect via an approved google Core IOT Device - "TI CC3200". Its not able to connect to Mongoose OS. Its getting "access denied" on all COM ports, tried almost all changing COM 1,2,34,5…not working at all…10 times restarted system. Already Installed all required COM Drivers required for Windows 10. Just want to connect Mongoose OS and Sensortag CC3200 and later integrate with GCP Core IOT to push data further.
I am referring this blog post provided by Mongoose OS Team for integration.
https://mongoose-os.com/docs/mongoose-os/cloud/google.md
MOS Screen here for reference
I have tried on other windows 10 and Windows 8 PC, but no success. Same error Access Denied on Mongoose OS screen
Access denied on MOS Screen immediately

Related

Can a STM32 microcontroller board be connected to AWS IoT core without its discovery kit?

I was searching in the net about connection between STM32 microcontroller and AWS IoT core, didnt come across any. I cam across articles where the discovery board of STM32 is used to connect to AWS IoT core. But I want a simple way to connect the STM32 microcontroller to AWS IoT core with the help of WiFi module (since STM32 microcontroller boards dont usually have WiFi modules)
I tried searching as I have already told but didnt come any resources related to what I was searching. I was specifically looking for resources related to STM32F1 series.
You need internet connectivity to be able to connect to aws iot. That could be wireless or ethernet. STM32f4 could work with ethernet.
Or, you move to ESP32.
What I’ve done in the past is to connect a stm32L1 to esp8266 over spi.
AWS provides a tutorial on how to use the IoT Device SDK for Embedded C - https://docs.aws.amazon.com/iot/latest/developerguide/iot-embedded-c-sdk.html
They also provide sample apps specifically ported for STM32 (STM32L4 discovery board - https://www.st.com/en/evaluation-tools/b-l475e-iot01a.html) based on WiFi connectivity.
That can be a good starting point if you build it and review the codebase.
However if you want to use a different STM32 family then you will need to port the project to your specific hardware.
Also if you have a different WiFi module, you will need to rewrite the drivers to fit to your hardware configuration. (You can only use a WiFi module which supports TLS connectivity, as that is mandatory for the AWS IoT Broker connection).
Another approach: in the AWS console under IoT Core > Device Software > FreeRTOS Device Software (https://eu-west-1.console.aws.amazon.com/iot/home?region=eu-west-1#/software/freertos) there are preconfigured packs for download. Alternatively you can also customize a device pack for download. You will be able to find the same device (STM32L475 Disco board) listed there.

run gazebo on EC2

I'm trying to develop an robot application. But I don't have GPU locally. So I created an EC2 instance, and tried to run gazebo on it. However, it always fails with the following error. Maybe it's because I'm using VNC to connect to the server.
Dec 11 08:26:29 ip-172-31-33-33 kernel: [ 1633.096463] gzclient[3264]: segfault at 20 ip 00007fb23955d867 sp 00007ffc7b0e0820 error 4 in libOgreMain.so.1.9.0[7fb2391f7000+571000]
Did anyone do that before (running gazebo and ros on AWS and connect to it through remote desktop)? It it possible if I don't have local GPU and want to develop an ros application on cloud?
For robotics programming, including ROS1, ROS2, Gazibo, etc, AWS provides managed services called AWS RoboMaker:
AWS RoboMaker is a service that makes it easy to create robotics applications at scale. AWS RoboMaker extends the Robot Operating System (ROS) framework with cloud services.
It supports a number of robotics applications, such as Gazebo:
Gazebo (versions 9 and 11): Tool to simulate robots in an environment.

Unable to connect google glass

I am trying to connect my google glass to my system but every time I connect it is being recognized as Android ADB Interface under Android Devices in the Device Manager (Screenshot attached).
Due to this i am not able to run my applications as it doesn't show up in the Device Picker of Android studio.
I tried connecting it to my friends system and it worked fine on that. But the only difference i noticed was that the device was being shown as Android Composite Device Interface under the Android Devices in the Device Manager.
I have already tried a fix to alter my android_winusb.inf and insert some custom lines but that also dint worked.
Can anyone else help me with some other solution?
Perhaps you aren't getting enough power on that USB hub.

Difference between starting the process directly on machine and from remote desktop connection

I want to know the difference between application started directly on the machine and the application started using remote desktop connection.
Whether both the application are same or will have different privileges.
For example, i had an opengl based application which take higher version of opengl 3 or 4 when started directly on the machine. But when i start the same application from remote desktop connection, it takes only base opengl version 1.1.
One more observation is:
We have a service application which will launch a graphics (OGRE based) application based on request. Request is set from client using web-socket communication.
When we start this service directly in a server, it works fine. But when this service is started from a RDP connection, the graphics application is crashing when user sends request after RDP connection is closed.
IT works if I keep the RDP connection on.
It may loose the graphics driver when you are logged in through RDP.
If you look in the launch the Ogre 'setup' dialog when RDP is enabled it will not list the graphics card - but a different 'RDP driver'.
Also - when you log on\off it might 'reset' the device (since the RDP graphics driver is enabled\disabled) causing your window get loose the device, and then crash.
One way to get around all this - is to use a VNC (for example tightvnc), this does not cause the issues that standard RDP does, since it does not use the RDP graphics drivers and such.

Azure Connection on Intel Galileo

I'm looking to connect an Intel Galileo to Azure through The Windows 8 version for the Internet of things.
I'm looking to store sensor data such as temperature and humidity in Azure, and have some form of message passing from an app on a phone to the service in Azure and on to the board (and back again).
There are plenty of examples doing this for apps etc, but I can't find anything on doing it with the Galileo. I'm pretty novice when it comes to Azure. Any suggestions would be appreciated.
Cheers!
You can use AMQP 1.0 and Azure Service Bus (Event Hubs or Topics). Apache Qpid Proton can be runned on Intel Galileo and Windows 8.
Please, consult Connect The Dots project and its pull requests for more examples.