@ Piotr (pitlab)

Since the 360/90 is an option now in the GS.
Will you add a new tracking mechanism with servo's on the website?
I would really like to use this.

with the 180/180 system sometimes my panel flips around.
Within 15km no problem but when above 20km out i can see much more grainy picture.
This happens because when panel flips around the upside becomes the negative and the downside the positive.

Originally Posted by KillerbeanNL

Since the 360/90 is an option now in the GS.
Will you add a new tracking mechanism with servo's on the website?

The mechanism is 3rd party construction - our friend who is CNC specialist (also modeller) do it.
Will ask him if he can design and manufacture such tracker.

ps. every tracker has it's limits, so also 360x90 will have to do something like flip if it go to end of 360°.

Originally Posted by KillerbeanNL

Hmm i also played around with the settings of the runcam eagle camera.

on NTSC its all the same. Changing settings make no difference.
Maybe it is something in the pitlab osd?
I hope other ntsc users will reply.

when im on PAL, no problems.

I've checked my OSD with 2.60 firmware and NTSC video signal from Mobius camera. I do not see any problem:

Pitlab&Zbig OSD with NTSC video input (0 min 45 sec)

Maybe this is problem with wiring? On this video there is also shown proper wiring scheme

Originally Posted by pitlab

The mechanism is 3rd party construction - our friend who is CNC specialist (also modeller) do it.
Will ask him if he can design and manufacture such tracker.

ps. every tracker has it's limits, so also 360x90 will have to do something like flip if it go to end of 360°.

Im not sure how to 360/90 works but i think when pan servo reaches maximum, so 359 degrees, it will rotate fully back to 0 degrees.
This is what you mean correct?

That would be better for me, then panel is always with the positive side on top (same as TX)

Originally Posted by Zbig

I've checked my OSD with 2.60 firmware and NTSC video signal from Mobius camera. I do not see any problem:

http://youtu.be/3GYBxGVxKkU

Maybe this is problem with wiring? On this video there is also shown proper wiring scheme

Lol, you should be ashame
i think it has something to do with the camera's then.
I am sure its not in the wiring but it must be something in the camera.
The problem is not there when i use my NTSC 4k camera, then its fine.

cmos/ccd problem??
i have to think about this

Originally Posted by KillerbeanNL

Lol, you should be ashame
i think it has something to do with the camera's then.
I am sure its not in the wiring but it must be something in the camera.
The problem is not there when i use my NTSC 4k camera, then its fine.

cmos/ccd problem??
i have to think about this

I would suspect a "cheap" (yes, these are cheap cameras we're using) camera problem before a Pitlab problem.

Originally Posted by KillerbeanNL

Im not sure how to 360/90 works but i think when pan servo reaches maximum, so 359 degrees, it will rotate fully back to 0 degrees.
This is what you mean correct?

Yes.

Originally Posted by KillerbeanNL

That would be better for me, then panel is always with the positive side on top (same as TX)

In fact there is absolutely no difference when you rotate antenna 180 degree (upside-down). Polarization and gain will stay this same. So if you experience difference in video quality after antenna flip, it may suggest wrong pan/tilt servo calibration, or antenna maximum gain direction is slightly off.

Originally Posted by bmw111

I would suspect "cheap" (yes, these are cheap cameras we're using) camera problem before Pitlab problem.

Yes it might be the camea's
But i do think the difference PAL/NTSC and CCD/CMOS does make a (small) difference
I found another person with the same problem. Except he doesnt think its a problem:

RunCam Eagle Flight Footage (3 min 3 sec)

Originally Posted by Zbig

In fact there is absolutely no difference when you rotate antenna 180 degree (upside-down). Polarization and gain will stay this same. So if you experience difference in video quality after antenna flip, it may suggest wrong pan/tilt servo calibration, or antenna maximum gain direction is slightly off.

Ok, i keep an eye on it.
But i still prefer the 360 rotation over 180/180

Hello,
I built a new plane with 4s lipo.
With my old plane in 3s, I connected directly the battery in the OSD (12v).
With my new 4s, can you confirm that it's necessary to use a 12v ubec for the OSD and a 5v ubec for autopilot ?
No problem to connect the 2 ubec in parallel from the battery ?
I only cut the red wire of the esc as usualy ?
Thank you !

Originally Posted by PhilZeph

Hello,
I built a new plane with 4s lipo.
With my old plane in 3s, I connected directly the battery in the OSD (12v).
With my new 4s, can you confirm that it's necessary to use a 12v ubec for the OSD and a 5v ubec for autopilot ?
No problem to connect the 2 ubec in parallel from the battery ?
I only cut the red wire of the esc as usualy ?
Thank you !

Yes, you neeed two UBEC: 12 and 5V.
No problem with supply everything from one battery.
Yes, disconnect red wire from ESC.
You're welcome!

Is it possible to set the AP to continue a route or waypoint mission in the event of a FS?

Originally Posted by austntexan

Is it possible to set the AP to continue a route or waypoint mission in the event of a FS?

Yes you can ignore failsafe for a laps of Time you can set up .

Originally Posted by austntexan

Is it possible to set the AP to continue a route or waypoint mission in the event of a FS?

Yes it is. This was the exact reason we asked for and Zbig kindly included the feature called "ignore failsafe for XX".
XX = time in minutes.

You will find this in the OSD menu.

This is useful for when you have mission waypoint or route that you KNOW will probably trigger failsafe (like it goes behind a mountain and comes back out on the other side).

PS.: It is also called "Brass balls mode" that is what you need to enable this feature. Not for the faint heart-ed.

Originally Posted by Relaxincherry

Yes you can ignore failsafe for a laps of Time you can set up .

Originally Posted by Pompecukor

Yes it is. This was the exact reason we asked for and Zbig kindly included the feature called "ignore failsafe for XX".
XX = time in minutes.

You will find this in the OSD menu.

This is useful for when you have mission waypoint or route that you KNOW will probably trigger failsafe (like it goes behind a mountain and comes back out on the other side).

Thanks guys

Originally Posted by Pompecukor

PS.: It is also called "Brass balls mode" that is what you need to enable this feature. Not for the faint heart-ed.

LoL, no kidding!