Initial cut on MATEKF722 target

[digitalentity]

Matek F722 board initial support - per #2552

[saliimam]

Looks good - will test this weekend. Any reason for putting motor 2 to signal 5? Also smart move bringing in the added compass from the newest BF revision.

[MATEKSYS]

@saliimam S5 is on TIM3, same as S1, no confliction with other servo outputs

[MATEKSYS]

Following firmware tested.

http://www.mateksys.com/Downloads/FW/inav_1.8.1_MATEKF722.hex

[MATEKSYS]

Frsky smartport(inverted) can't work on TX pin.
non-inverter hack can work on TX pin
set telemetry_inversion = ON, Frsky smartport work on TX pin.

[KnuckleUpFPV]

Flashed this firmware to test. Unable to connect to configurator after flashing. Tried flashing via inav, cleanflight, and betaflight

[digitalentity]

@KnuckleUpFPV try flashing with full erase

[KnuckleUpFPV]

I've tried it with every setting. It doesn't work. Board isnt even recognized after flashing. Its only seen in dry mode. I even went to the matek site and downloaded it from there. Same deal. Fc is not seen. Blue led flashes rapidly. On first plug in red and blue that are side by side flash like police lights alternate of each other very fast.

[KnuckleUpFPV]

Did mode not dry mode. Can't edit from my phone

[KnuckleUpFPV]

DFU*

[MATEKSYS]

I got the same status after flashing this inav firmware. wrong com port detected by computer(win10 x64). show " FS mode" , I tried BF firmware, F722 com port works normal with BF GUI.

then I reinstall the VirtualCOM driver with this. fixed.
http://www.mateksys.com/downloads/fc/STM32-VirtualCOM-Dvr-64bit.exe

[KnuckleUpFPV]

Its not wrong com port issue. It doesnt recognize the fc. Tried the impulserc driver fixer and it didn't find it either because the pc doesnt see it after flashing. I get no detection beeps or anything unless in dfu mode.

[MATEKSYS]

@KnuckleUpFPV , I got the same issue as yours, fixed with new COM driver.
check your computer device manager. if you find "comport FS mode". that is wrong.

[KnuckleUpFPV]

I do not see that. Computer doesn't see anything when its flashed with this hex.....i can use any other hex and it finds the fc just fine. Had betaflight on it prior to this. I was hoping inac fixed the i2c errors. Why is there a continuous chain of hoops to jump through with matek flight controllers? I can flash it with a completely wrong target and the pc will see it. Just something about this firmware.

[KnuckleUpFPV]

Let me dig out the windows 7 pc and see if that works.

[MATEKSYS]

[digitalentity]

Can you post a close up of the board?

…

On Dec 25, 2017 12:57, "KnuckleUpFPV" ***@***.***> wrote: I do not see that. Computer doesn't see anything when its flashed with this hex.....i can use any other hex and it finds the fc just fine. Had betaflight on it prior to this. I was hoping inac fixed the i2c errors. Why is there a continuous chain of hoops to jump through with matek flight controllers? I can flash it with a completely wrong target and the pc will see it. Just something about this firmware. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2611 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AKi_mywpvL9cdaxhajVqZy_ZjYhSXWhOks5tDw8FgaJpZM4RKsJg> .

[KnuckleUpFPV]

That's awesome there are no starting i2c errors. Maybe I can use an external mag and gps now.
You want a pic of my fc? I literally just flew it on betaflight. My buddy pm'd me this firmware was here. So i didn't fly another pack, I came inside and tried the flash.

[MATEKSYS]

I flashed this firmware again just now. unable to connect to GUI after flashing. I am curious they worked normal yesterday everning.
uninstall & install COM driver again. fixed.
Try to restart computer just now. it still works

[MATEKSYS]

[KnuckleUpFPV]

Might want to post that on the site for those that it might work for. No luck here. Its getting late and Christmas is in a few hours. Im going to call it a night soon.

[KnuckleUpFPV]

windows 7 pc worked after reinstalling virtual comport. windows 10 pc still isnt seeing it. I will configure it from windows 7 pc for now. Thank you for your time. I will test this in flight asap. Probably day after christmas.

[marwady]

For those of you with Win10, if you received an auto update, you will probably have to reinstall com port drivers, etc.
This happened about the same time the new hex was available.
I had the same problems however, after reinstalling drivers, stm, etc, it is now working.

Cheers!!

[digitalentity]

Ok, so this is a driver issue. I believe this can be merged then. @MATEKSYS ?

[MATEKSYS]

@digitalentity Pls merge it. thanks

[Spoonman61]

i have uninstalled and reinstalled every driver imaginable including the win10 driver from matek's site, no luck. is a fix planned? i can flash betaflight target and its fine.

[digitalentity]

@HipoxiK this is usual if you have something connected to I2C and it's not powered along with the board. If you have external GPS/Compass connected you must power them.

[HipoxiK]

Ah ok thanks. This is where I was going wrong. I'm new to drone builds coming from quads and betaflight.

Thanks for keeping this thread running, I'm getting lots of good info from you guys.

[HipoxiK]

To clear my issues up then the latest Matek F722 iNav 24 Jan candidate is working fine on my laptop with the latest STM32 drivers. It was just that I needed battery power connected.

I'll start setting the gps, compass, bluetooth, camera switcher, pay load release servo and the TBS Micro RX V2 up and see how we go.

[ghost]

@digitalentity
Well, I had the choice of U2 to U5 and managed to pick the one that would not work!

[solmag]

Before I embark on building this FC, has anyone actually flown with this firmware and how's the AUTO POS HOLD and RTH working?

[ghost]

@digitalentity
Reference your comment about BMP280 and HMC5883 not being happy on the same I2C bus.
Do you think removing the BMP280 might eliminate the I2C errors I am getting with the SE100 GPS unit?
As mentioned previously reducing i2c_speed to 200KHZ stops the errors but I am not really happy that this is a real cure.

[HipoxiK]

I have now set up the GPS and Compass which have calibrated and work although the compass keeps drifting back to 8 degrees when I turn the drone to north. I believe this is due to a clone Mag (QMC5983) which radiolink have been using in their SE100 GPS/Compass even though iNav reads mine as HMC5883. From another thread it sounds like its an issue with the mag gains and by removing the magGain code it can fix this issue, eg.
magDev->magADCRaw[X] = (int16_t)(buf[0] << 8 | buf[1]) * magGain[X];
magDev->magADCRaw[Z] = (int16_t)(buf[2] << 8 | buf[3]) * magGain[Z];
magDev->magADCRaw[Y] = (int16_t)(buf[4] << 8 | buf[5]) * magGain[Y];
to
magDev->magADCRaw[X] = (int16_t)(buf[0] << 8 | buf[1]) ;
magDev->magADCRaw[Z] = (int16_t)(buf[2] << 8 | buf[3]) ;
magDev->magADCRaw[Y] = (int16_t)(buf[4] << 8 | buf[5]) ;

You guys encounter this?

[ghost]

@HipoxiK
My one is the same, it needs the mods you have listed.
After the mod, I had to reduce i2c_speed to 200KHZ to eliminate (or cover up) I2C errors from the mag.
Be interested to hear how your one performs after the mod.

[HipoxiK]

@flyfisher2
I have reduced the i2c speed down to 200khz already to stop the i2c errors.

Could I get a copy of your .hex if you have already modded it and removed the magGain?

I don't have time to learn how to mod .hex files right now and would really like to get this drone in the air. At this stage the magGain issue is all that's stopping me.

Cheers

[ghost]

Never done this before hope it works:

inav_1.8.1_MATEKF722 SE100.hex.zip

[HipoxiK]

@flyfisher2

I'll test it today and see if it works for me.

Edit: Seems to be working @flyfisher2, thanks for editing that .hex. My magnetometer now sits on a heading without slowly drifting back to a set heading.

I'm still running it at 200khz though.

I need to finish the setup and test fly still but looking good so far.

[ghost]

@HipoxiK
I don't have anything to flight test it at the moment but it seems to be OK on the bench (apart from the I2C errors).
Just be aware that I compiled that hex from the development branch and as such it may have some bugs or funnies.

[HipoxiK]

@flyfisher2
Are you able to remap resources such as the PWM pad, motor 7 (B08) to a servo, same with S5 and S6 pads.

I need these to be channel forwarded to servo's but can't seem to edit these resources using what I thought was the correct commands in the CLI.

[ghost]

@HipoxiK
Sorry mate, I'm a hardware type and can do minor/simplistic code changes but this is beyond my capabilities.

[HipoxiK]

@flyfisher2
Haha no worries mate. I'll keep looking into it as I can't seem to be able to remap resources in the CLI as you normally could which means the spare pwm pads are stuck on motors 5,6,7 out and can't be changed for servo's.

[shellixyz]

@HipoxiK 6 and 7 can already be used for servos but for 5 (PB1) you need to edit line 35 of target/MATEKF722/target.c

[HipoxiK]

@shellixyz
Yes I am aware they can be used for servos but when I check the resources in CLI they are both assigned Motor6 out and Motor7 out respectively. How can I change these to servo outputs because as far as I'm away iNav doesn't support resource remapping yet.
Thanks

[ghost]

Finally installed the board into our 650mm Quad last night.
Before leaving for the flying field this morning, I decided to re calibrate the sensors, just to be sure.
Glad I did. On the first attempt I got accgains of 6336 0 4090
Second attempt 16651 0 4096, then 0 6712 4091.
The original calibration was 4091 4095 4092.
Looks like I have a hardware problem now, so I think its time to give up.

[shellixyz]

@HipoxiK You don't need to they will be used for servo outputs if they are defined in the mixer.

[HipoxiK]

@flyfisher2
Thats no good, mine are:
accgain_x = 3240
accgain_y = 4800
accgain_z = 4100

[ghost]

Yes, my initial calibration a couple of weeks ago was fine but something seems to have gone drastically wrong with the board since then.
Glad I decided to do another cal before the maiden flight, otherwise I could now be looking at a pile of expensive scrap.

[HipoxiK]

@shellixyz
Ok thanks mate I'll give that a shot.

[HipoxiK]

Test flew the drone today. All Nav functions are working correctly. Alt Hold is good, GPS Hold and RTH work great.

@shellixyz
Can I leave the mixer as QuadX and just define smix for the servo pads. I assume pads 1-5 are motor pads and 6,7(pwm) pads are servo's?

Or will I need to use a custom mix and define the motors using pads 1-5? Then smix servo pads 6,7?

[ghost]

@HipoxiK
Great news and good to know the hex was OK.
Don't know whether to take a chance and buy another MATEK or revert back to ANYFCF7 and put up with the hassle of MWOSD.

[HipoxiK]

@flyfisher2
Well if I can get the servo's working for the camera switcher on pad 7 (pwm) and the pay load release servo on pad 6 then I'd say the Matek F722 is tough to beat seems the other minor issues are getting sorted/worked out.

[MATEKSYS]

S7=servo via CH5 of transmitter

[HipoxiK]

Thanks @MATEKSYS I'll try that tomorrow. Is there a way to get a 2nd servo out of S6?

Just tried CH5 as the camera switcher which is connected to S7 and it works perfect. Thanks for the help as I tried it with other AUX channels but not 5.

I wonder if there isn't a solution to get S6 to control a 2nd servo using another Aux channel on the transmitter maybe I could wire the signal from the servo to the 3rd camera switcher signal out and see if that activates the servo as the 3rd position on CH5.

[MATEKSYS]

@HipoxiK Seams S6 can't be used for AUX channel.
according to my guess, S7=CH5, S8=CH6, S9=CH7..., so need additional PWM definition in target.c

[HipoxiK]

@MATEKSYS
Is it possible to enable S6 PA8 as servo-6 in the Quad x mixer like it is in the Airplane mixer. If so I would assume that you could then assign this servo-6 to a channel in the Servo tab of iNav and use it to control a servo on a drone.
I have the channel forwarding turned on and use CH5 to control the camera switcher but would like another servo control as well.

[leonvuksic]

Hi all,
I have read the complete thread and I decided to ask for help, I'm having a lot of issues using external gps and magnetometer on this board.
Yesterday I chatted with Pavel and he compiled the latest hex for f722-std but I still cant use magnetometer and gps because barro dies.
I have lowered the i2c speed but it didnt help.
I have a pmw reciver, gps m8n+compass hmc5883 and i have 2 servos for camera gimbal.

Please help me and tell me what is the best place on the board to connect everything including servos and please attach the besd hex I should flash.

Also I am willing to test flight any future builds/releases for this board!