Discussion Paparazzi, the RTF Autopilot?

[bmw330i]

Originally Posted by zik

Sounds like you've had quite a journey! Good luck with getting it all working well. I'm following your story with interest - since I'm using some of the paparazzi code myself I'll be keen to see how well it works out for you.

Ya, it has been a mind expanding thing and a lot of fun. I have a long ways to go though. Good luck with yours as well...I will be following that thread as well and it sounds like it is going very well. Good work.

[bmw330i]

Well, I had one Tiny2.11 assembled with an LEA-5H just to see what happens...what happens is I can load the bootloader, I can load the tunnel, I can connect with u-center...but then it freezes. Recycle the power to the Tiny and it comes back...then freezes after about 20seconds.

Very odd. But I have noticed this:
- changing any setting with u-center and issuing "send" freezes u-center and or the GPS and I have to power off/on the Tiny2.11 to get it back.
- THe 5H with "supersense" is SUPER FAST. Wow, inside in the garage in 1 to 2 seconds it has 4 or 5 satellites and a 3D fix...it's just incredible to see how fast it goes from power on to a 3D fix.
- The thing will if left along just freeze after the same period of time. I didn't time it (I will) but it appears to be around 20-30 seconds.
- It is on 9600BPS (default) and like the first thing trying to change that results in immediate freeze forcing a reboot of the Tiny/GPS

Bummer, it seems incredibly fast but I thought I would post this because I know people are buying LEA-5H for their Tiny2.11 projects. Just be aware it may take some debugging. I'm sure a fix can be had and the LEA-5H seems already way better than the LEA-4P for locking in satellites but right now I am having issues.

So, putting that aside I'm going to continue with my LEA-4P based Tiny2.11 now...

[AntonK]

David,
You were talking about installing Ubuntu on a laptop and the formatting and blah blah blah. I thought I would chime in with what I have been using, as a potential option. A bit of a tangent, but Im known for those.

Anton

[bmw330i]

Originally Posted by AntonK

David,
You were talking about installing Ubuntu on a laptop and the formatting and blah blah blah. I thought I would chime in with what I have been using, as a potential option. A bit of a tangent, but Im known for those.

Anton

Anton, your comments always welcome...even ones I don't understand.

I took a break from the Tiny2.11 today and took some time to do the Rx Mod on my Berg 4L receiver. I quickly found although I easily found the pin on the IC to solder the wire to for the PPM I was lost when it came to where to wire up the (-) and (+). Then I found a good image on RCGroups in another forum showing where to solder the + / - wires...nice. Went pretty smoothly. Something like:
1. removed outer case (shrink wrap really)
2. found the pin on the corder just like the photo on the Wiki and soldered a wire to it.
3. Then removed the pins as like the directions say you won't need them with Paparazzi.
4. Tinned and soldered the + and - wires to the right pads.
5. soldered the XTal pins in the holes so the XTal can't come loose (Per the Wiki)
6. added a 5-pin Molex Picoblade connecter per the pinout given for Tiny2.11

Always tomorrow...supposed to go Moto-X riding in the AM (wife insists we get out and ride...I agree) We are lucky in SoCal to have a few Moto-X tracks within an hours drive. I hope to get some time in the afternoon to get the RF Modems working per my plans this weekend.

[bmw330i]

Well, nothing too much to update. I worked on following things yesterday:
1. The LEA-5H based Tiny2.11
2. The LEA-4P based Tiny2.11 getting the RF modems talking
3. The Berg 4L Rx Mod to grab the PPM signal (aka the wiring of it)

1. It freezes, oddly exactly 30 seconds after power on. Did it at least 10 and timed it to be sure it was exactly 30 sec each time. Odd. I will load the latest firmware and see if that still happens.
2. Well, I installed the LEA-4P on a Tiny that didn't have a GPS module. So after tracking down and fixing an issue with the module not correctly soldered I was soon talking to it in u-center and verifying all was working. After I tried many times to get the RF Modems talking. I'm using MaxStream 2.4ghz XBee. USB version for the ground station and OEM module for the Tiny side. Very very odd. I mean according to the Wiki all is setup right. This is very very much an area with almost no documentation on what to do if it's not working. I am searching the Development Archives and trying new things. I tried to fallback to using just the "Transparent" serial communications...then to 9600bps, then back to verifying 38400 was setup for both...non-API mode...nothing. THere are no lights on the module but the ground station has them and at times they seem to be connected based on the activity of the LED on the USB modem. BUt in ALL cases nothing in GCS (The GUI ground station window/app)...

Well, as promised when I sort it out I'll update this thread...

3. That was pretty easy. I de-soldered all the pins (not needed all servos are driven from the Tiny autopilot not the Rx. Found the pin from a picture with PPM signal. Then easily (photos on RCGroups) found the (-) and (+) and soldered wires there. Now I have a Berg 4L ready to go.

[dmgoedde]

Have any idea of the # of channels the PPM output of the Berg4 gives? I assume it is more than the basic 4 Ail/Elev/Thrott/Rudd. I "hacked" a Berg Stamp 4 channel Rx by desoldering the servo pins, and soldering the crystal permanently on.

Dean

[air]

8 according to the wiki

[AntonK]

yes, like almost all RC receivers all 8 channels are on the RF side of the receiver, its just that only 4 are actually driven to servos. Bypassing the servo driver allows for all 8 channels.

[bmw330i]

UPDATE:

Well, got the XBee-Pro Modems up tonight. I'm still confused by it though. I had to set everything to 9600bps. Once I did that it worked. I had them set to 38400. At that speed I could see when I launched the ground station the lites on the ground station modem blink, then a rx light blink...then all but the power light go off. Very weird.

But like I said, setting all to 9600bps and it all worked. I then quickly found out that using "google fill" option triggers google to block your IP for a while. This leaves me with the problem of how to get the cool background now. If Google can't be used then what can be?

Tomorrow after work I will connect the Receiver and the IR sensors and get those working.

I will upload a screen shot of my GCS showing the GPS is working and telemetry is up and working.

[AntonK]

Google typically lets you fill in quite a bit of area before you get banned. In fact Ive never been banned. Make sure you are centered around your house/flying area before you start downloading tiles, and also make sure you are not zoomed out crazy far. You will get unbanned soon.

Anton

[bmw330i]

Ah, ok, it seemed to be around 5min. Ya, I had zoomed out. The GPS had me a very long ways away from where I actually was. Is that normal? The LEA-5H said quickly I was at: -116.9 x 33.01 .. the Tiny I was using last night with the LEA-4P said 117.x / 34.x ... and google showed a terrain I imagine is quite far away.

I will try outside with the laptop this AM. I really hope to get the LEA-5H Tiny to stop freezing. Can you think of anything in the programming that tries to update the GPS every 30 seconds? That's the magic timing. 30 seconds after power on...freeze. Anytime I try with u-center to "send" to the GPS ... freeze. The LEA-4P and LEA-5H are virtually pin for pin identical just the LEA-5H has higher tolerance for input voltage (slightly) so I am hopeful I will/can get it working.

[Prashanth]

Thanx david
A thread like this was what I was hoping someone would start,
buffs like me can learn and follow and prevent the magic smoke especially when parts are hard and rare to find from this part of the world....
Subscribed and will be following

Prashanth

[bakketti]

Great thread! I am planning on buying a ppz board from you towards the end of the year. Your "lessons learned" will definitely help. Thanks again for supporting the community.

[Mr_westie]

Excellent work
Saving my pennies now.

[bmw330i]

Hey all,

Thanks for the comments. Remember, when it seems totally a blur I have been there. I guess for some this is all routine but for the rest hopefully what I post will be simple enough for us.

Latest update. Not a lot new to report. I had to build a few kits for people. Very time consuming...So, it's a tedious task and the cost of these kits are truly for my own time to make them.

So, that said (reason why not much progress lately) I did find I need to do some more homework to get past the next stage. I have the following ready to hook up:
1. Receiver (Berg 4L)
2. XBee-Pro OEM Module (2.4ghz)
3. Two Hitech HS65 (elevons)
4. Tiny2.11
5. Generic ESC (25A)
6. 300 Motor
7. 3 cell Lipo
8. FunJet
9. Dual-IR sensor
The cabling is slowing me own. It's the Dual-IR sensor. I'm having a hard time sorting out the pin1 on the board connector (on the Sensor). The Tiny2.11 has a good pinout on the Wiki but not the Sensor. Often the pinout is viewed from the bottom of the board not the top. Well when you plug it in your plugging it in from the top. The info on the Wiki is not clear...so, as soon as I get that wire made I'll be ready to plug it all together.

NExt Steps (after wiring up the Dual-IR sensor):
1. Calibrate all the above. This requires setting zeros for them, then their max values. Then set min, max and neutrals...going to have to study the Wiki more and the List (Paparazzi Development List) for info.

I have found that going to the Wiki is good first. Then go to the List and do a search on terms like "GPS", "IR", or errors if you get them. Usually someone else has had the same issue and you can find your answer there without bugging the members. I have found if you do your homework and ask a good question that shows you did some homework they are quick to respond to your requests.

Also as always feel free to ask me...

Oh, I'm at a Tibco Conference next week...not going to get anything new done next week...just a head's up.