Hi
I seem to be doing something wrong. I have connected a DroneCell to my Arduino Uno for testing, powering it with 5V. RX -> RXI and TX -> TXO.
Then I connect to it with screen over the USB cable like this (38400 baud was mentioned in the quick start guide):
$ screen /dev/ttyACM0 38400
Starting logging of the screen session (C-A H)
Then power cycle the dronecell. I See the TX LED flashing for roughly 1 sec. The output i get is as follows (no further input seems to be accepted, not further output sent):
$ hexdump screenlog.0
0000000 ff00 ffff fffe ffff
0000008
The expected output should look something like this (may vary when no SIM card is inserted):
RDY
+CFUN: 1
+CPIN: READY
Has anyone an Idea what's going wrong? Am I doin something wrong or might I have gotten defect hardware ?
Kind regards,
-S
Tags:

did you connect a common ground pin? I initially didn't with my DroneCell and got lots of garbage
Permalink Reply by Simon on July 17, 2011 at 3:48am Thanks for your very quick Answer. I am still very new to electronics, what do you mean by "common ground pin" ?
GND is connected from the DroneCell to a GND pin on the Arduino Uno board. The DroneCell is powered off the 5V pin from Arduino Uno.
Kind regards,
-S
Permalink Reply by Simon on July 17, 2011 at 4:33am OT: Andrew, I have just realized that you are working on the SAMBA project. I guess this makes you an intra-blago-web celebrity ;)
SAMBA is one of the projects which has eased the use of free *NIX for me since the nineties (when I discovered *BSD and linux thanks to the Internet). It is the most important project (IMHO) for interoperability of free *NIX derivates (and even commercial ones today I guess) with the Microsoft world.
I want to thank you for the great work you guys have done in all those years. Keep up the good work!
Kind regards,
-S
Permalink Reply by Simon on July 19, 2011 at 12:43pm This problem is solved. Thanks to Eric (the designer with his quick email support from narobo.com). If you get strange output when connecting the first time enter (try to connect with 38400 baud, if this doesn't work, try 115200):
AT
Then make sure to disable auto-bauding:
AT+IPR=38400
Your baud rate is now set to 38'400 baud. You might choose one of these baud rates: 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200.
Cheers,
-S
Permalink Reply by Richard on August 22, 2011 at 5:16am You need to have a server setup from what I am told.... At least the guy who had one working says so...

Richard, it is not necessary to have a server, though you may need a dynamic DNS, depending on how the dronecell is configured.
I've set up a group to work on Telemetry over cellular IP, where I will be posting development updates.
Season Two of the Trust Time Trial (T3) Contest has now begun. The fourth round is an accuracy round for multicopters, which requires contestants to fly a cube. The deadline is April 14th.6 members
51 members
130 members
686 members
24 members
© 2013 Created by Chris Anderson.
Powered by
