Our ArduStation MEGA boards arrived today and I am truly excited to see how they work. Now starts small assembly job for them and then we can start doing testing for those.
Big thanks for Colin for his original ASM work, it's great to see what great minds can create.
New boards looks just awesome. Few connectors are missing but those are quickly soldered. These boards are from the first batch and we have them now small qty in stock. If there are any changes that needs to be made, we will do it and then first production batch will come.
Technical specs:
- MCU: Atmel 2560 with Atmel 8u2 USB "adapter"
- XBee footprint for telemetry with external pins
- IO: Buzzer, Analog, I2C, GPS
- SDCard holder for storage needs
- 128 x 64 pixel Graphics LCD
- 3 x TTL Serial output pins
- 2 x Servo outputs with internal/external power feed
- Encoder port for menus etc use
- Connection for I2C Keyboard
- 4 x LEDs for showing different statues
Jani / jDrones
Comments
Yup, new version with GPS on serial 1 is here:
https://github.com/cgwood/ArdustationMega/raw/master/binaries/Ardus...
Here's a slightly more direct link to the binary
https://github.com/cgwood/ArdustationMega/raw/master/binaries/Ardus...
Also, I uploaded this using the mission planner and it worked as advertised. Just click the "Load custom firmware" link after selecting the correct serial port top right
I've just pushed a new release to github. You can find the compiled .hex here:
https://github.com/cgwood/ArdustationMega/blob/master/binaries/Ardu...
The release doesn't fundamentally add a huge amount, but the front page is a lot nicer to look at and I should at least have an idea of what code is loaded on the unit now!
I've only tested this latest version with my PX4... I'll have to fiddle with the rover stuff on another day.
It occurs to me that I don't know what port your GPS is connected to, the firmware is currently pointing at Serial2. The sat count on the front page is currently the sat count of the ASM, rather than the UAV/rover. I might amend this in the future...
Colin
That sounds like my firmware, probably what I'm showing in this video:
http://youtu.be/NWU-0-62owI
Maybe compass is something Jani has added... The nearest thing to a compass heading that I have displayed would be yaw. I do also recall coding up bearing to the UAV from the position of the ASM, so it could be that showing up. This would be fairly meaningless if there is no lat / lon for the ASM.
I've never used the firmware upload from the mission planner before, I've only heard people talking about it! I can't see why it wouldn't work though, the micro controller in the ASM is the same as in the APM anyway.
Hi Tom,
Thanks for the updates. Very interesting.
To be honest, I have no idea what firmware Jani has loaded onto the shipped ASM units. Jani?
As you've said in your PM, the version of my code that added ublox gps support prints to the console
Serial.println("GPS UBLOX library test");
when you turn it on. So if it's running a version of my code that has gps support, you should be seeing that in your console.
About the compass. Is there a screen that has five lines reading Roll, pitch, yaw, lat and lon? And are you referring to the yaw for compass heading?
You say you're using this with a rover, I presume that means you're using this firmware? I have never played with rovers, so I would need to check that it doesn't require an additional special set of mavlink datatypes to be parsed...
It probably isn't too surprising the parameter download doesn't work for the rover as I think I'm only grabbing certain roll pitch yaw values that are non existent or called something else in rover world. In my latest build, I automatically detect the autopilot type. So in the future it will be possible to get it to vary what parameters are loaded given the system it is talking to. My longer term goal is to have some kind of model memory like you get on an rc computer transmitter, whereby the model can be automatically detected as mavlink allows you to number your mavs 1 - 255.
I've got a new version of code that I will push to github tonight. While I'm at it, I'll upload the .hex, so you should be able to load it through the mission planner rather than having to compile it yourself. Compiling the code can be tricky, because it will conflict with APM libraries that are installed (I think the gps one), and you need to update the source code to point at your working directory for the mavlink includes.
Regards,
Colin
MANUAL ,INSTRUCTIONS?
Saiful, yes that indeen looks to be upside down. I really wonder what happened there. Most likely it is single case as those power modules are coming ready made for us and we just solder them on boards. Can you contact our customer support and we will send new power unit for you.
We just had meeting with my engineers and talked about this issue and our staff is now checking every single powerunit on our stock to see if there are others like this.
and poof... my capacitor blow up magic smoke. Did the capacitor reverse polarity?
As I could see, it is possible to place previous orders.
But who will order without knowing how to use?
Where can we find the documentation?
For example: What baud rate for XBEE, which GPS is recommended (different settings are possible there)
Open source is good, but open manual also. Do a good job and write about to tell averybody how to use al the features.
I'm shure it will be a great succes.
I am waiting for the manual bevor ordering. Probably many others also.
Thank you for your development.
Oyvind, that is possible too. Software will be fully open and there are several UART ports that you can use. Easiest way would be just monitor main serial port and write byte per byte all the incoming data to for example Serial 2 output.
Serial 0 is USB uart,
Serial 1, GPS (reserved)
Serial 2, nothing yet
Serial 3, Telemetry modems
-
13
-
14
-
15
-
16
-
17
of 18 Next