Co-Pilot II - How To, Made Simple!

[segdoh49]

Originally Posted by nightflyr

I understand you now..
Does that FBL unit also have a built in receiver? or are you using a separate Rx?

Why does it take spookier long for things to post on this site'

Sent from my DROID BIONIC using Tapatalk 2

[segdoh49]

Originally Posted by nightflyr

I understand you now..
Does that FBL unit also have a built in receiver? or are you using a separate Rx?

Built in.

Sent from my DROID BIONIC using Tapatalk 2

[Bob O]

Originally Posted by segdoh49

Why does it take spookier long for things to post on this site'

Sent from my DROID BIONIC using Tapatalk 2

Things should start speeding up for you.

[nightflyr]

Originally Posted by segdoh49

Built in.

Sent from my DROID BIONIC using Tapatalk 2

You will require a separate Rx and non stabilized FBL controller in order to use the CPII for FBL.
The basic hook up is as follows:

Rx>>>>>CPII>>>>>FBL>>>>>servos

[BlueRay]

Just installed a new in the box, but old version, CoPilot II, existing firmware seems quite old at Ver 1.38, when I run the Updater it gives me a choice of 2.37, 2.4 and 2.41, I read that unless you are going to install the hard deck module to not install 2.37 and beyone but my Ver 1.38 seems old and perhaps too out of date, can I install other udates a different way without having to go with these new ones?

[Tim Marks]

Originally Posted by BlueRay

Just installed a new in the box, but old version, CoPilot II, existing firmware seems quite old at Ver 1.38, when I run the Updater it gives me a choice of 2.37, 2.4 and 2.41, I read that unless you are going to install the hard deck module to not install 2.37 and beyone but my Ver 1.38 seems old and perhaps too out of date, can I install other udates a different way without having to go with these new ones?

Hi:

Good question. Sorry for the confusion. Prior to the Hard Deck Module, the newest firmware release was v1.47. When we came out with the Hard Deck Module, we went to v2.xx series altogether. Since it appears you don't have the Hard Deck Module, you want v2.04 firmware which is simply a recompiled form of v1.47. Before you install v2.40, you need to check the "update bootstrap" checkbox, and click the Update Firmware button one time. When that's done, then go back to the list, highlight v2.04 and click Update Firmware a second time.

[BlueRay]

Originally Posted by Tim Marks

Hi:

Good question. Sorry for the confusion. Prior to the Hard Deck Module, the newest firmware release was v1.47. When we came out with the Hard Deck Module, we went to v2.xx series altogether. Since it appears you don't have the Hard Deck Module, you want v2.04 firmware which is simply a recompiled form of v1.47. Before you install v2.40, you need to check the "update bootstrap" checkbox, and click the Update Firmware button one time. When that's done, then go back to the list, highlight v2.04 and click Update Firmware a second time.

Thanks for the reply, I get this error when doing the bootstrap first update?


Software Started 16:50:04 10-30-2012
COM3 Opened 115.2Kbs PASSED 16:50:05
COM3 Opened 115.2Kbs PASSED 16:50:33
COM3 Opened 115.2Kbs PASSED 16:51:16
COM3 Opened 115.2Kbs PASSED 16:51:21
Manual Firmware Update
Starting Firmware Programming on port COM3 0mS 0mS
Send Password 115.2Kbs 359mS 359mS
characters read = 202 63mS 422mS
RX(1) = (112) 0mS 422mS
RX(2) = (112) 0mS 422mS
RX(98) = (112) 0mS 422mS
RX(99) = (112) 0mS 422mS
RX(100) = (80) 0mS 422mS
RX(101) = (32) 0mS 422mS
RX(102) = (32) 0mS 422mS
Bad Product Code Abort = True 0mS 422mS

[BlueRay]

Hi Tim

I figured I may have a driver issue so I went through all the motions to reinstall per your web page, (Vista 64), ran the FUIM3 Tester and PASSED (Com 3), ran the updater in the sequence on the intructions, bootstrap first, then V2.04, the log is brelow, may have done it now, I cant get the programer to function, may have glitched the formware, programer only reads IRNet ROUTER V1.6 and when I press the enter buttom I just get a message "reciver = 5.29V no brown outs" will not do anything else???

Need some help please

Software Started 19:01:24 10-30-2012
COM3 Opened 115.2Kbs PASSED 19:03:06
V2.04 Chosen 19:03:24
COM3 Opened 115.2Kbs PASSED 19:03:25
Auto Firmware Update
Starting Firmware Programming on port COM3 0mS 0mS
Send Password 115.2Kbs 359mS 359mS
characters read = 200 47mS 406mS
Bad Product Code Abort = True 0mS 406mS
Starting Firmware Programming on port COM3 0mS 0mS
Send Password 115.2Kbs 296mS 296mS
characters read = 200 47mS 343mS
Bad Product Code Abort = True 0mS 343mS
Starting Firmware Programming on port COM3 0mS 0mS
Send Password 115.2Kbs 297mS 297mS
characters read = 200 47mS 344mS
Bad Product Code Abort = True 0mS 344mS
Starting Firmware Programming on port COM3 0mS 0mS
Send Password 115.2Kbs 296mS 296mS
characters read = 200 47mS 343mS
Bad Product Code Abort = True 0mS 343mS

[Tim Marks]

Originally Posted by BlueRay

Hi Tim

I figured I may have a driver issue so I went through all the motions to reinstall per your web page, (Vista 64), ran the FUIM3 Tester and PASSED (Com 3), ran the updater in the sequence on the intructions, bootstrap first, then V2.04, the log is brelow, may have done it now, I cant get the programer to function, may have glitched the formware, programer only reads IRNet ROUTER V1.6 and when I press the enter buttom I just get a message "reciver = 5.29V no brown outs" will not do anything else???

Need some help please

Software Started 19:01:24 10-30-2012
COM3 Opened 115.2Kbs PASSED 19:03:06
V2.04 Chosen 19:03:24
COM3 Opened 115.2Kbs PASSED 19:03:25
Auto Firmware Update
Starting Firmware Programming on port COM3 0mS 0mS
Send Password 115.2Kbs 359mS 359mS
characters read = 200 47mS 406mS
Bad Product Code Abort = True 0mS 406mS
Starting Firmware Programming on port COM3 0mS 0mS
Send Password 115.2Kbs 296mS 296mS
characters read = 200 47mS 343mS
Bad Product Code Abort = True 0mS 343mS
Starting Firmware Programming on port COM3 0mS 0mS
Send Password 115.2Kbs 297mS 297mS
characters read = 200 47mS 344mS
Bad Product Code Abort = True 0mS 344mS
Starting Firmware Programming on port COM3 0mS 0mS
Send Password 115.2Kbs 296mS 296mS
characters read = 200 47mS 343mS
Bad Product Code Abort = True 0mS 343mS

Hi:

You only check the box to update the bootstrap and then click Update Firmware one time. Let's assume you got that step done. Hook the FUIM3 back up to the PC, connect it to the CPII Computer Module on the ACCY port. Connect a 4.8v-6v power source to the CPII Computer. Be sure to observe proper polarity. The black wire on the FUIM3 and the battery need to be closest to the label side of the CPII Computer Module.

Now, launch the CPII Update Utility, click on the firmware ver you want, and then click Update Firmware.

Hopefully the bootstrap is O.K., and the firmware update will go right on through.

[BlueRay]

Hey Tim, no luck, results more or less the same? Polarity right on all plugs to the cpu, black ground to the label side, 5.29 volts, update did not take? Anything else i can do to re-flash the unit?



Software Started 12:27:37 10-31-2012
V2.04 Chosen 12:27:42
COM3 Opened 115.2Kbs PASSED 12:27:44
Auto Firmware Update
Starting Firmware Programming on port COM3 16mS 16mS
Send Password 115.2Kbs 374mS 390mS
characters read = 200 47mS 437mS
Bad Product Code Abort = True 0mS 437mS

Starting Firmware Programming on port COM3 0mS 0mS
Send Password 115.2Kbs 312mS 312mS
characters read = 200 46mS 358mS
Bad Product Code Abort = True 0mS 358mS
Starting Firmware Programming on port COM3 0mS 0mS
Send Password 115.2Kbs 312mS 312mS
characters read = 200 46mS 358mS
Bad Product Code Abort = True 0mS 358mS

Starting Firmware Programming on port COM3 0mS 0mS
Send Password 115.2Kbs 312mS 312mS
characters read = 200 47mS 359mS
Bad Product Code Abort = True 0mS 359mS

[Tim Marks]

Originally Posted by BlueRay

Hey Tim, no luck, results more or less the same? Polarity right on all plugs to the cpu, black ground to the label side, 5.29 volts, update did not take? Anything else i can do to re-flash the unit?



Software Started 12:27:37 10-31-2012
V2.04 Chosen 12:27:42
COM3 Opened 115.2Kbs PASSED 12:27:44
Auto Firmware Update
Starting Firmware Programming on port COM3 16mS 16mS
Send Password 115.2Kbs 374mS 390mS
characters read = 200 47mS 437mS
Bad Product Code Abort = True 0mS 437mS

Starting Firmware Programming on port COM3 0mS 0mS
Send Password 115.2Kbs 312mS 312mS
characters read = 200 46mS 358mS
Bad Product Code Abort = True 0mS 358mS
Starting Firmware Programming on port COM3 0mS 0mS
Send Password 115.2Kbs 312mS 312mS
characters read = 200 46mS 358mS
Bad Product Code Abort = True 0mS 358mS

Starting Firmware Programming on port COM3 0mS 0mS
Send Password 115.2Kbs 312mS 312mS
characters read = 200 47mS 359mS
Bad Product Code Abort = True 0mS 359mS

Hi:

It would appear that the bootstrap update was not successful. I would like you to try updating one more time following these instructions:

1) Connect the FUIM3 device to your PC USB port.
2) In the Firmware Update Utility COM setting pull-down, select the COM port #'s manually and watch the LED on the FUIM3. When the LED stays on, that's the correct COM port setting to use. Don't set the COM port setting to AUTO at any time.
3) Now connect the JR pigtail of the FUIM3 to the CPII Computer Module's ACCY port (black wire toward label side).
4) Connect 4.8v - 6v (4 cell Ni battery) to the CPII Computer Module; any open port (black wire toward label side).
5) Now check the bootstrap box and click Firmware Update.
6) When the process is complete, power down for 10 seconds (remove the battery from CPII)
7) Repeat steps 4-5.
8) Power down again for 10 seconds (remove the battery from CPII)
9) Power back up and this time, select the firmware you wish to update to, then click Firmware Update.
10) Try using the IRNet Programmer now. See if you can get to the CPII Welcome Screen (you may need to press and hold DEC and ENTER buttons to scroll through the available IRNet accessories until you get the CPII Welcome screen).
11) If it works, use the CPII welcome screen to confirm the correct firmware # is installed.

If the above does not work, you will need to return your Computer Module for service. Please contact Howard Matos at howard@fmadirect.com for further instructions.

Sorry for the inconvenience. Hope this helps get you going!

[BlueRay]

HI Tim, good news update, turns out (I'm a dummy) and I have the FSIM2 not the FUIM3, my cable looks more like the 3 than the 2 at a quick glance and does have Ver1.3 on the uderside so I thought it was the 3 unit, not to mention the FUIMS3 Tester PASSED and the FSIM2 Tester FAILED, I realized I had a serial plug to the board and it was probebly the 2 and ran the update even thought the test failed and it worked perfect.

If the weather cooperates this weekend I will take it out for a test :-)

[Tim Marks]

Originally Posted by BlueRay

HI Tim, good news update, turns out (I'm a dummy) and I have the FSIM2 not the FUIM3, my cable looks more like the 3 than the 2 at a quick glance and does have Ver1.3 on the uderside so I thought it was the 3 unit, not to mention the FUIMS3 Tester PASSED and the FSIM2 Tester FAILED, I realized I had a serial plug to the board and it was probebly the 2 and ran the update even thought the test failed and it worked perfect.

If the weather cooperates this weekend I will take it out for a test :-)

Hi:

Hey, that's great news! Glad you got it sorted out! Good luck test flying.

[jeremy cooksey]

Hey guys I have a fma copilot 2 that I bought two years ago. Thinking of selling it to get a heli command for my fpv ship. Any ideas what it will bring$. Perfect condition have everything with it

[JDFiend]

Hello everyone. This a great, helpful thread!
I just got a copilot ll system today. Has anyone tried to install this on a heli smaller than a 450 size? Would the copilot work on a Blade SR?

[Howard Matos]

Originally Posted by JDFiend

Hello everyone. This a great, helpful thread!
I just got a copilot ll system today. Has anyone tried to install this on a heli smaller than a 450 size? Would the copilot work on a Blade SR?

Hi,

We did most of the early Hard Deck development and testing on a Blade 400. I have not tried anything smaller.

[BlueRay]

Originally Posted by Tim Marks

Hi:

Hey, that's great news! Glad you got it sorted out! Good luck test flying.

Tim,
* Worked great, still have to dial it in a little but really wish I would have installed this a year ago.......... better late than never :-)

[JDFiend]

Hi,

I just installed Co pilot ll on my 450 Trex (clone.) I'm having some problems getting Co pilot to function properly, and I was hoping that someone here could help me figure it out.

The heli is set up properly, and I can do a nice stable hover when co pilot is turned OFF.

When I turn Co pilot ON after setup and Preflight check, the swashplate tilts to the extreme left (while still on the ground.) If I apply throttle, the heli immediately wants to tip over to the left.

I'm using a DX6i (DSMX version) and I have the On-Off running through the Gear-Gyro channel. My Off position is set to 0% in the Tx, and the On position is set to 100% in the Tx. Mode is set to GYRO.

When I do my PreFlight setup with the programmer, my Pitch and Roll values don't show Zero. My angles are usually showing 2-3 degrees on pitch and roll.

The Co pilot appears to be functioning. If I move my hands around the main sensor, the servos will move, and the swash will move into different positions as I move my hand around the sensor.

Here is my problem in short: When Co pilot is turned ON, I cannot get a level swash. I've tried different ROLL ANGLE values in the PREFERENCES--FLIGHT ANGLES menu, and it tips my swash to the extreme right.

Can anyone offer any advice on what I might be doing wrong? Am I missing a step somewhere in the programming setup values??? ( I should add that I've also gone through the QUICK SETUP to calibrate my sticks and the sensors.)

Any help or advice would be greatly appreciated!

Thanks, Joe

[sutty]

A couple of questions that may help people to assist. When you are doing your swash level testing with CPII on, are you outside, away from heat sources, that may be giving the CPII a false impression of the horizon? Are you standing back, for example, away from trees and buildings, etc, and are you testing on a nice day where you have sufficient gound to sky temperature difference?

Cheers

Sutty

[JDFiend]

^ Yes to all of the above.

I did my set up yesterday in a large open softball field on the grass. The weather was blue skies and 55 degrees. There are buildings and trees surrounding the park, but I had a good 40-50 yards of open space around me in all directions. Is this sufficient for set up?

Joe