Submitted by Matt on Thu, 05/13/2010 - 19:20
Posted in
Hi,
I got OM Slim working on my netbook and it does work with all axes. Connecting to the engine and moving motors works fine, but I have a hard time running scripts. I tried the sample scripts, but neither camera nor motors seem to respond. I'm using API 0.03, Slim version 0.12 and engine 0.82.
Is there something I am missing ?
Matthias
Matthias, That's odd. Since
Matthias,
That's odd. Since running a script is the same as typing the commands in... =) (Well, it does open a file and read each line - sending it through the same code path at this point as if you had typed it in.)
Are there any errors reported to you? Do you have a proper 'port' and 'connect' command in-use? And, finally, if you turn on debugging, does it print out at least one line for every script command that should run.
The only thing I can think of, outside of those statements, is it is having some issue opening the script files?
!c
It's working now and I don't
It's working now and I don't know what I've done ;-)...I love when this happens...
Maybe I was too impatient. I guess I was waiting for something to happen, that indeed happend, I just did not realize, because the moves were minimal...
M.
Strange things happen. If I
Strange things happen. If I enter commands directly in slim, it usually works, unless I use a status command. If I run a script, I often get a "Timeout reading from engine" error and the program does not run.
It seems to me that the Arduino understands what the computer tells it, but not the other way round. Any ideas ?
Matthias
When you use a status
When you use a status command, does it give you an error, or a timeout?
Generally, it would imply that you're running an incompatible version of the engine (i.e. earlier than 0.82) - but I doubt you're doing that. =)
On which command do you get a timeout error? It will always be in response to one command, if you turn on debugging (debug 1) it will print what command its working on when the timeout happens. That would help me find the problem for you immensely.
!c
Hi Chris, I reflashed the
Hi Chris,
I reflashed the engine. Now it seems to work... No idea why, but maybe I had a dev version of 0.82 running, can't remember.... sometimes the error is between the headphones ;-))
Matthias