Closed yo8aiv closed 4 years ago
step 2: attached https://www.banggood.com/de/Anniversary-Special-Edition-Racerstar-REV35-35A-BLheli_S-3-6S-4-In-1-ESC-Built-in-Current-Sensor-for-RC-Drone-p-1180734.html?rmmds=myorder&cur_warehouse=CN , flahed them successfully via jesc. -> passthrough works fine.
step 3: attached motor on M1. ESC initialisation peep suggests: all fine.
step 4: rc-mode: angle. arming, and look whats happening: https://youtu.be/MdWsASn1UHs
ok, that video might help you guys for debugging:
It might be one of two problems which is
A: ESC Issue - when you arm, the motor spins for awhile and stops even when armed, yeah? That could probably mean a bad ESC or;
B: Timer Conflict - Although I've already made sure that no such conflicts would appear in config.c
I haven't really tested it yet with DShot with a Multirotor config since the ESC I had used in my plane is a generic hobbywing 30A that can only use PWM Signal.
i'd exclude ESC issues. since i had problems with at least 3 different ones that all worked fine with BF. i can support you with hardware if you whish.
That's the deluxe board you're using, right? Mine is the acrk versuon with a blue color on the solder mask of its board
jepp.
there is the barometer:
From what I've read however in the website, the difference between acro and deluxe is that the deluxe has dual gyro and a flash memory while the acro doesn't have those
On Fri, Feb 28, 2020, 20:54 aknack notifications@github.com wrote:
jepp.
there is the barometer:
[image: WhatsApp Image 2020-02-28 at 13 52 11] https://user-images.githubusercontent.com/6792254/75550223-c39d8880-5a31-11ea-8eaa-3ba5a81886c0.jpeg
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/iNavFlight/inav/issues/5002?email_source=notifications&email_token=AHZRTEL3YGK25CFWUHDCDSDRFECORA5CNFSM4IK2E5NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENINMBI#issuecomment-592500229, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHZRTEMFBUI3SH5Q4ZQKXVTRFECORANCNFSM4IK2E5NA .
i tried to switch the gyro from gyro 0 shown as MPU600
set gyro_to_use=1
set acc_hardware = ICM20689
save
the FC now seems to reboot over and over. i'm not able to connect to the FC with inav
as far as i remember gyro #0 in betaflight is the ICM and #1 is MPU,
@aknack @xD90o1 I did not have any problems with getting the motors running and was actually flying a few batteries. I am attaching a dump of my config (that is pretty much standard). I believe the default gyro for INAV is MPU6000.
works on the bench:
even better :D
could you please port the config (diff all) i have the flight controller working but when i try to drive the motors there is a big dead zone about 15% of the throttle doesn't work.
if anyone knows how to set the minimum throttle value please tell me.
only on the bench that 15% . you won't notice if you arm and fly. anyway, here's the diff.
INAV.JHEF7DUAL 2.4.0.diff.all.txt
please note: props direction is reversed!
set yaw_motor_direction = -1
thank you. the config the you attached works better than mine. only 5% is a deadzone not 15% i think that is an acceptable range thank you so much for your help.
i got managed to fiddle the filters/advanced settings until quad wasnt able to fly (escs/motors did shut down like 300ms after thrusting, did not change BL_S firmware): fucked up.txt after reverting to INAV.JHEF7DUAL 2.4.0.diff.all.txt
all was fine again. flys like a dream.
Hello! Please, help. In the PID TUNING tab, the gyro rpm filters menu is not active. I installed this firmware with these controls on the omnibus f4 pro board, everything is fine, this menu is active. Can someone explain this. Thanks.https://drive.google.com/open?id=16DU3ja_0KjXPSg9LjCAOwzo97oiGmigo
even better :D
Hello! Please, help. In the PID TUNING tab, the gyro rpm filters menu is not active. I installed this firmware with these controls on the omnibus f4 pro board, everything is fine, this menu is active. Can someone explain this. Thanks.https://drive.google.com/open?id=16DU3ja_0KjXPSg9LjCAOwzo97oiGmigo
smaller09 , you''re the man ! :)
i can confirm user-modes are working. can't confirm yet, that it will fly. inav_2.4.0_JHEF7DUAL_smaller09_menu_patch.zip Hello! Please, help. I have motor controllers with feedback. On the omnibus f4 controller, a gyroscopic rpm filter worked. In this firmware, activation of this filter is not available. What can you do about this? In the PID TUNING tab, the gyro rpm filters menu is not active. I installed this firmware with these controls on the omnibus f4 pro board, everything is fine, this menu is active. Can someone explain this. Thanks.https://drive.google.com/open?id=16DU3ja_0KjXPSg9LjCAOwzo97oiGmigo
is this parameter active?
betaflight target JHEF7DUA
I completely assembled the copter, ready to test.
Hi guys what is the procedure on this Flight controller ? I have the full baro version, how to get it flashed properly with Inav? Does it work?
As of now, since I've only tested it om my plane, it works. I dunno yet on multirotors though but I'm getting mixed results form other people
On Sat, Apr 18, 2020, 20:39 Dropsleutel notifications@github.com wrote:
Hi guys what is the procedure on this Flight controller ? I have the full baro version, how to get it flashed properly with Inav? Does it work?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/iNavFlight/inav/issues/5002#issuecomment-615861424, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHZRTEL5CJSLYFIWSKNEFA3RNGNO5ANCNFSM4IK2E5NA .
Can you post the target here, so I'll flash it, can do some testing.
Check the linked pull request in this issue
On Sat, Apr 18, 2020, 20:47 Dropsleutel notifications@github.com wrote:
Can you post the target here, so I'll flash it, can do some testing.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/iNavFlight/inav/issues/5002#issuecomment-615863164, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHZRTEOTIK4N3XD4YMFN37DRNGOODANCNFSM4IK2E5NA .
Hello! I put one of the options on my quadrocopter, it did not behave correctly, it flew away, I could not return it. RPM filtering did not work, the sound of the motors was interrupted, the copter was gaining altitude and did not respond to control. I had to make a disarmament and the copter fell from a height of 100 meters. Fortunately, everything remained intact. After that, I changed the controller to the Matec f7se and everything was fine. With default settings, Matek works well. Very sorry. Why the RPM filtering item is not active in the firmware. Maybe publish again that firmware that can work? thanks
I haven't done some experimentation on the RPM Filtering yet since I only used this on a wing and I can't test some of the stuff you were suggesting yet either since the lockdown here prevents me from going out
Hello! I put one of the options on my quadrocopter, it did not behave correctly, it flew away, I could not return it. RPM filtering did not work, the sound of the motors was interrupted, the copter was gaining altitude and did not respond to control. I had to make a disarmament and the copter fell from a height of 100 meters. Fortunately, everything remained intact. After that, I changed the controller to the Matec f7se and everything was fine. With default settings, Matek works well. Very sorry. Why the RPM filtering item is not active in the firmware. Maybe publish again that firmware that can work? thanks
Have you got a blackbox log of that particular flight? I or someone might have a look at it to see why it happened
Hi all, Still no sign of support for this in Inav 2.5 RC2. Is this something that is actively being looked at as it is one of the cheapest f7 boards out there- likely people will have noticed and want to buy if Inav supports. I'm fine using betaflight on it for now but would be nice....
Closing this, as there seem to be little interesting from the manufacturer to follow the INAV hardware policy.
Does anyone have contact with the manufacturer to reach a hardware support agreement with INav?
I think JHE swung by this thread a few posts earlier
On Mon, May 25, 2020, 02:19 cgaxtreme10 notifications@github.com wrote:
Does anyone have contact with the manufacturer to reach a hardware support agreement with INav?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/iNavFlight/inav/issues/5002#issuecomment-633271151, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHZRTEPKJ4KEKZWNWLAUQR3RTFQK7ANCNFSM4IK2E5NA .
Dear @atgfpeyv This card has great potential for its construction and low cost of sale. It is a pity that due to lack of cooperation you cannot get the most out of it with INav. In the last year I have followed this product closely, including the latest version of the JHEMCU F7 BT Dual, however, the lack of support for it ends up making it unattractive. Best regards
Hi guys. i see there has been quite some activity here. Great. Wich is the latest tested or not FW i could try on this FC .. i have deluxe version. Thanks. Great job.
Check my fork. Hopefully the target source code would work on the latest version of iNav
On Sun, Aug 9, 2020, 08:15 yo8aiv notifications@github.com wrote:
Hi guys. i see there has been quite some activity here. Great. Wich is the latest tested or not FW i could try on this FC . Thanks. Great job.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/iNavFlight/inav/issues/5002#issuecomment-670987640, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHZRTELYBAR5NL24E4DSTX3R7XTCHANCNFSM4IK2E5NA .
Check my fork. Hopefully the target source code would work on the latest version of iNav … On Sun, Aug 9, 2020, 08:15 yo8aiv @.***> wrote: Hi guys. i see there has been quite some activity here. Great. Wich is the latest tested or not FW i could try on this FC . Thanks. Great job. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#5002 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHZRTELYBAR5NL24E4DSTX3R7XTCHANCNFSM4IK2E5NA .
link ?! thx.
yeah, sorry, noob here- where can we get the target for manual flashing or is this now part of official INAV targets? Would love a link if poss...
link ?! thx.
http://github.com/xD90o1/iNav Also I had a pull request made a few months ago http://github.com/iNavflight/iNav/pull/5502
can you guys please post a hex file that was tested to be working !! thx
can you guys please post a hex file that was tested to be working !! thx
Here's my try at the code for the JHE F7 Dual
2.2.1 but I've been hearing success from some people trying to make it work on 2.4
that's good news. thanks for sharing. will report back.
can you guys please post a hex file that was tested to be working !! thx
JHEF7DUAL.zip Here's my try at the code for the JHE F7 Dual
2.2.1 but I've been hearing success from some people trying to make it work on 2.4
What all have you got working on this or what is not working, just the user modes? thanks
I'm also interested in this. I just ordered this FC and I'm very interested in using iNav with it.
What all have you got working on this or what is not working, just the user modes?
I've seen someone here modify it a bit to make the user mode work
I tried both hex files for 2.2.1 and 2.5.2 For the both user switch 2 does not work - can not provide 8V to VTX - any fixes for that ? (in betaflight t works, here the vtx might be soldered directly to the battery)
I assume it's the wrong menu id for the piniobox
On Mon, Oct 12, 2020, 19:20 Ivan Kolev notifications@github.com wrote:
I tried both hex files for 2.2.1 and 2.5.2 For the both user switch 2 does not work - can not provide 8V to VTX - any fixes for that ? (in betaflight t works, here the vtx might be soldered directly to the battery)
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/iNavFlight/inav/issues/5002#issuecomment-707058455, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHZRTEMRPWB5NOWJVB47UKDSKLQ7NANCNFSM4IK2E5NA .
In JHEMCU F7 is no user switch. There is pin PC14, which switches cameras and pin PB9, which turns on/off the 8 V power supply for cameras. Pins PC14, PB9 are assigned to CAMERA CONTROL 2 and CAMERA CONTROL 3. Try using modes CAMERA CONTROL 2 and CAMERA CONTROL 3.
On betaflight the camera 8v is controled by user 1 and camera change is controled by user 2. They dont use the camera 2 and 3 tabs.
I tried the user1,2 firmware and it seems to be working in configurator, but when I arm and try to test fly it, my right stick (pitch,roll)on my transmitter acts like it is not connected to flight controller, I can move it all around when armed and props spinning and I get no response. throttle seems to be working but not yaw as far as I can tell. The motors spin up correctly in inav configurator motors tab, and my transmitter is working fine in the receiver tab. Must be something else not matching up?
Hi . i don't know if this is the right way to ask for new FC to be supported.
its called JHEMCU F7 target in BF is JHEF7DUAL. this board could be of better use in iNav than BF since it has so many uart's. more info https://github.com/betaflight/betaflight/issues/8605 https://github.com/betaflight/betaflight/pull/7398
Thanks.