@Kazooie yep, the USB data lines should be good to connect. Just not the 5V power

@jonty No. The wireless Arduino IDE method outlined in our documentation has worked consistently since the launch of the Arduino Dock 2 back in 2016. In @Noniono's case, using a programmer is meant to test the MCU. It isn't responding to the Omega. If it also doesn't respond to the programmer, then we know the MCU has somehow gotten into a bad state or has been damaged.

I have tried mblock, Ardublockly and Node-red. Without success with Omega2 +

Hey György, oh man... that wasn´t worth to open a topic... I just grab a NPN and it works. Thank you very much.

@Jagoan-Keren Please try this link http://onioniot.github.io/wiki/ or this one https://github.com/OnionIoT/wiki Good luck!

@Maximilian-Gerhardt wow! Thank you very much for your response, at least I don't have the feeling like I'm shouting into an empty cave! I'm surprised at how beta the i2c library is for something that's been out for ~years. I feel like the first feature for boards like this (after GPIO control on its own pins) should be a matured and robust i2c library. Since, almost anything you want to do with them will require i2c communication... Again, thank you for the heads up with known issues. I'll try to keep stumbling through this and if I succeed I'll make it available.

Hi Andrea Take a look at: https://developers.google.com/calendar/overview Personally i prefer python or php. You can use crontabs to trigger the 30min event. https://docs.onion.io/omega2-docs/running-a-command-on-a-schedule.html I don't really have any expirence with the calendar api, so I can't give you an example. But I hope this may give u an idea on how to start.

The Omeage2 has no analog, limited PWM, non-deterministic timing. Arduinos have a varied number of analog, digital and PWM pins, are deterministic as to how long things take to run, have 'bank' i/o support (which I've not seen implemented on any copy device), software serial, sleep mode, ... So, no.

well after some more research, i am going to drop the linear regulator for step-down buck switching regulators. i will update the schematic and share my final solution when i have it working.

Thanks a lot! Regards

Thank you @Ken-Conrad ! I found a really good example of how to use PySerial on instructables that was written for Pi and it worked out well after i changed UART details. Now just to get mysql installed and we good to go!

Thanks, be attempting a simple DHT22 project with the Omega 2+ and haven't gained any traction as of yet, hoping to piggy back on your work. Appreciate your sharing!

FRDM KL-25Z is an awesome little board based on the MBED platform. And then, old school, home-brewed 8031/51 based boards, which, because of the ease with which you can access every part of the hardware, still kicks arse for some applications because there is no OS that gets in the way.

Make it work via (USB-to-logic-level) serial on a desktop Linux first. It should then be a fairly straightforward port, provided you don't have dependencies that aren't available. ie, low-level solutions in python or C will be preferable.

@Douglas-Kryder said in Omega 2 and Arduino dock.: @Gamaliel-Valencia well, if the thing is still within any type of warranty framework then i would put in a ticket for return, mention the thread so if they have any ideas over what has already been discussed they can join in. but it seems to me you have tried all that you could. other boards have just not responded as well so some of them just may be broken. wish i could offer something else but out of ideas. @Douglas-Kryder I really appreciate your support and I think you are right, I will send my ticket and wait.

@Visti-Stenmo if it helps, here's a tutorial https://ubidots.com/docs/devices/omega.html#onion-omega-and-ubidots

@Syed-Hasan I would support all that @fossette says in the previous post. You should pay particular attention to 2 issues: Make sure that the system is fully operative by using a delay as suggested by @fossette As is mentioned in the referenced post, make sure the program you want to run at boot terminates in a timely manner and doesn't end up blocking the start up process - e.g. run it in the background