I’ve given this thing a few attempts, but can’t seem to get it running.
I wrote a little test script that writes to the serial port and successfully sent it to the board. It’s enabled and at#rscript returns it just fine. When I reset the module with the DTR switch high, it doesn’t execute and instead drops me back into the normal serial command interface.
Can some one give me a list of steps to get this running? I’m using minicom on Linux, so I don’t need PythonWin, hyperterminal, etc. tips. I just want to reliably load and execute a script. Perhaps if you’ve got a test script that works you could attach it too. Thanks so much.
oh yeah, my hardware is the V3 eval board and latest firmware from the round solutions site.
It appears my problem was in transmitting a script to the device. I was corrupting it and it would fail to execute on startup, explaining the “drop back to at command interface” behaviour.
My background is with compiled languages, which might make my spotting of syntax errors a little rusty. Is there an easy way to determine if the script is in error or what line it was encountered from the AT command interface? It looks like on windows there are multiple multiplexed serial ports for debugging, but all I have is /dev/ttyUSB0
Ok, I’m pretty much up and running now, but still have a pretty major issue to deal with.
I didn’t read until recently that the python interpreter doesn’t support floats. I’m trying to do a little bit of math on the returned GPS value to cut down on network traffic, but this device seems totally unsuited for the task. atoi() or string._int or even eval() don’t seem to work.
Is the common consensus to go with an external micro?