-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
problem in blink led gobot #176
Comments
@myalexer Is your arduino flashed with firmata and are you sure that COM15 is the correct port number? I just tested on windows 7 and it worked for me... |
yes i test it with arduino program - in arduino ide port is COM15 - blink program with arduino syntax is ok and it work |
how can i found COM port number? |
Hi, I also struggled with this problem. it might be an idea for this page: http://gobot.io/documentation/getting-started/ to also tell users to run the firmata example first. |
i test it but it can't work |
I have the same problem on Arduino uno, but Ubuntu 14.10. It blinks three times no matter what port I set, even when led is not in that port. According to me, my serial port is correct 'ttyACM0'. If I get something I will let you know. |
I can run it now! I'm not really sure, but, in gobot's getting started documentation there is nothing about firmata. |
@LaraChicharo I'll add more documentation about steps for loading firmata on your arduino, sorry for the confusion! |
zankich please help me for solved this problem |
Yea I;m kinda stuck with Firmata not working also,... amd confused.. |
Hi guys, First things first, the process to get the blink example working is as follows: Upload Firmata Sketch to the Arduino.You can do this using the Arduino IDE or using (gort.io)[gort.io]. When using the Arduino IDE just click on file > examples > firmata > StandardFirmata and upload that sketch to the arduino. When using (gort.io)[gort.io] first install it, then run:
Compile and run arduino_blink.goMake sure you are using the correct port, in the case of windows you can check the port is the correct one if you can upload an example (like blink sketch) in the arduino IDE. If it uploads and works you should be good. Just update the port in the gobot example and compile. In Linux is even easier to identify the serial port by using either Compile and run the program, after that it should work fine. Let me know if that helps. |
Hi, everyone I think the docs located here are sufficient: https://github.com/hybridgroup/gobot/blob/dev/platforms/firmata/README.md If not, someone can re-open this issue. Thanks, and closing. |
Same problem here, Arduino Uno with the firmata firmware flashed fine ( I could use pyFirmata to test), nothing happens, I added some logs in the program to have more information :
It's not even running the work function. The TTY port is correct (Detected by Arduino IDE and working fine with pyFirmata) What could be the cause ? |
Ok I found the issue, looks like for master part is missing from the example code, here is the working one :
|
Hi @kedare the original example code works for me, albeit by changing my serial port to
Since the v1.0 release you can use "Classic Gobot" as the first example does, so no need for the I then tested the code on OSX, and both examples worked with my serialport Hope that helps! |
hi
my platform is arduino - os : win7
my code :
package main
import (
"time"
"github.com/hybridgroup/gobot"
"github.com/hybridgroup/gobot/platforms/firmata"
"github.com/hybridgroup/gobot/platforms/gpio"
)
func main() {
gbot := gobot.NewGobot()
}
all things is ok
i type go run blink.go
it return :
2015/02/21 00:07:40 Initializing Robot bot3 ...
2015/02/21 00:07:40 Initializing connections...
2015/02/21 00:07:40 Initializing connection arduino ...
2015/02/21 00:07:40 Initializing devices...
2015/02/21 00:07:40 Initializing device led ...
2015/02/21 00:07:40 Starting Robot bot3 ...
2015/02/21 00:07:40 Starting connections...
2015/02/21 00:07:40 Starting connection arduino on port COM15...
program start successful but led do not Toggle every 1 second
how do i do?
The text was updated successfully, but these errors were encountered: