Mission planner is a mess in comparison. Export current param then compare with a proper software comparison like meld (free and opensource)
Is anybody using Arduplane 4.0.x on a Nimbus V2 with PG20? I would love to hear from you.
Also attached are my Nimbus V2 PG20 parameters, it would be great if someone would have a look and advise if anything seems array. To the best of my knowledge and reading I should be good to go.
https://1drv.ms/u/s!Auv-5QlGCPQojSMCeKGAswiZ2M4N?e=D4TNbp
Kindly
Steve
Steven, sound like you are the person I need to talk to. I am a drone pilot flying the DJI quads. I am looking to play with the Nimbus and have no idea what I need to do to learn the ArduPilot software. Can you give me any advice on training and who I could get with in the USA to see the Nimbus in flight before I waste my money!
Hi Darrell, some would probably say Iām not the person to about the Foxtech Nimbus. I have a number of issues with the Foxtech Nimbus. I mine remains on the ground as a $5000 brick. Foxtech Nimbus V2 has 3 different instructions regarding firmware update. The Manual from the website states you can if required upgrade the firmware, The Firmware updatedocument from the website states to update to the latest Arduplane for enhanced failsafe features- and the video that accompanies this clearly shows arduplane4.0.1 But Foxtech support and Nimbus v2 webpage both state that the firmware is customised for the drone do not upgrade or change it.
Mike Lee ā Skype āyes, this firmware is different from Adduplane and we got it from our suppliersā āPlease never refresh the parameters or firmware by yourselfjust use the default parameters and firmwareā.
Foxtech have not released the source codes (which is against the licencing agreement) for their version of Firmware used in the Nimbus V2.
It is important for all documentation and source codes be available to purchaser of Nimbus V2 because we know that installing the wrong firmware can cause crashes and the Nimbus firmware upgrade states to upgrade firmware for improved performance and safety ā as I have read about some issues with PG20 and Q-YAW and I wonder if this is due to firmware upgrade. Only by releaseing the source code can critical analysis be done to confirm and fix these issues.
Why do I care? Why not just fly the unlicenced unverified code? Insurance, air safety, costly investment, and because in 2018 DJI had battery failures with TB50 and TB55 batteries that went unreported resulting ongoing losses of M200 series drones, fortunately no injuries to people were reported.
Beyond the firmware issue - I have found their support to be good, you just need to be patient and clear on what you want, in the first instance expect a generic type response, if this doesnāt fix the problem be more specific and include photoās or video, and always be polite. I would avoid the PG20 it is definately 1 of the failures that occurs with a firmware upgrade and others have reported fc brown out using this. I also have a MAP-02, which came with a different wiring harness to the MAP-02 Manual, it is a little fussy but I now have it sorted. The ONLY way to change parameters is via HDMI port and the plug in ribbon controls that come with it.
By all accounts when in the air they fly ok - I would just like to see Foxtech get their ducks in a row, with regards to document control and firmware so we can fly them safely and confidently.
Hope that helps
Steve
1 Like
Being just shortly before the maiden of our Foxtech VTOL V2, Iād like to ask the experience of other Nimbus VTOL owner regarding potential, necessary modifications of the aircraft.
We are running the āoriginalā firmware as delivered by Foxtech, have a PG20 that we are currently not using as we are running solely on a Foxtech semi-solid LiPo battery.
Iāve read some issues with servos and/or hinges. Do I need to make any changes on this before maiden?
Thanks in advance,
Pascal
Good luck,
Iām waiting on Mike from Foxtech, says he will send me some 4.0.1 params per their dicumentation.
Hi Steven,
thank you for your good wishes. What improvements for the flight operations are you expecting by running the 4.0.1 version?
Yes, documentation is a difficult issue (for this āRTFā product). Many versions are available, but the one you get along with your product is hardly the one that suits.
Anybody has an idea, how the different flight modes in Ardupilot are used in the Foxtech version? Some flight modes switch from copter to fixwing operation, e g. when going into ACRO modeā¦
Hi Pascal,
@GregCovey would be best to talk about flight modes but ACRO wonāt be one of them for steady flight I have Q Stabilize, Q Hover, FBWA, CRUISE, LOITER, Q Hover.
I canāt afford to put $5000 aircraft in the air with unverified firmware, Tridge has confirmed this and I doubt my insurance would cover me. Also the because the foxtech firmware has its own source code you cannot be certain what effect parameter changes will have on aircraft performance or function.
Foxtech have documentation stating 4.0.1 so I know they have a build that will fly on standard Arduplane upgrades to 4.0.7 from there should be doable and there are obvious benefits to that, and others have been able to fly on standard Arduplane 4.0.x, but Iām not sure if they are using PG20. I was supposed to recieve a copy of these parameters from Foxtech today, but I recieved again standard Foxtech Parameters instead.
I would really like to have Arduplane 4.0.x parameters from anybody with PG20 version. if anyone could share.
Hi Steven,
okay, so running the supplied firmware is not necessarily a danger per se, but the lack of security about the parameter settings.
As far as I could identify, the version on my Cube is 4.1.0dev. I donāt know whether this is of any helpā¦
Hi Pascal, In Mission Planner I donāt get any version displayed, so this is a positive for you. Yes mine is a security/safety issue around firmware version and parameters.
Hi Pascal, So I found Iām running 4.1.0dev chibiOS as well, I cannot find any relevant literature on it though, unlike the stable released versions which have lots of chatter. What dev. actually entails and weather it is inherently stable and weather the source code is consistent to 4.0.x. Hopefully Iāll learn more soon and get in the air.
Steve,
The meanings of the versions from the WiKi are below. When you use a ādevā version, it is from the ālatestā category and meant for developers or experienced testers only. There are no release notes until it moves to the ābetaā and then āstableā categories. There is a thread below for copters that explains some of the process, which should be the same for plane.
- stable - this is the version recommended for new users. It has had the most testing
- beta - this is the firmware to choose if you want to be part of beta testing of new versions prior to release as a stable version. Note that during some development times the beta release will be the same as the stable release
- latest - this is the latest version from our git source code repository. This version is only for developers. The code may have unknown bugs and extreme care should be taken by anyone using it
Cheers!
Thanks Greg,
Well that says it all, looks like Iām on the ground until Foxtech gets its ducks in a row - or I manage to find a set of parameters running 4.0.6. Iām astounded that they would use this code as their retail firmware - Bordering on criminal.
Steve,
What makes you think that you need new parameters?
Hi Greg
With the parameters sent by Foxtech The PG 20 gets switched around ( can be fixed by adjusting servo 10 from 0 to 1 ) and Q-YAW is disabled just by loading stable version 4.0.6. Those are the errors I have been able to identify with my limited experience and just in a hover. I have been warned by Foxtech not to use any other parameters or firmware other then theirs which includes the developer firmware 4.1.0. - on a retail PNP model. I cannot legitimately fly for reward or pay with an aircraft on unstable firmware. I have previously asked for a functioning PG20 parameters on 4.0.x stable versions from this group the FB page and Foxtech, and none have been forthcoming. At this point I have probably annoyed too many people with my ramblings, but in the background my concerns are being taken seriously by Ardupilot and Cube.
Take care
Steve
Steve,
Perhaps itās not as black and white as it seems. Some companies do provide their own custom firmware and parameters. So the ādevā label can also come from a company doing their own compiling and building after making custom changes. This combination would likely have been well tested by the company.
I had a similar situation with the MFE Freeman. They provided custom ādevā software and parameters for their tilt-rotor VTOL which worked much better than the standard release firmware. There were new parameters exposed that could not be entered into the standard release firmware but I knew it was well tested and now others have proven it as well. Their latest model, the Fighter 4+1, can use regular release firmware.
Both Foxtech FPV and MakeFlyEasy are Corporate Partners of ArduPilot.
Cheers!
Hi Nimbus crew, whatās the Servo type for the motor in the aft? I read the documentation a few times but didnāt notice anything about the aft motor, only that the two front motors throttle should be set as left and right motor throttles, which I assume are 73 and 74. I guess the aft motor should be motor #4 per the copter doc, but would appreciate your input. thanks
[edit] i just chanced upon this page which uses servo function 33, 34 for the two front motor throttles, rather than 73,74ā¦i assume because he has flown before, he must be right?
Hi Greg,
I understand that many do and have flown this Firmware, and had it not been bought to my attention I would probably be flying it too. But Iām glad he did.
The Australian standard UAV operations manual states.
ā Avionic and control systems software is only to be updated after the version has been confirmed as being stable 'ā¦āWhere an issue arises with the new software / firmware is to be rolled back to the previous stable versionā.
So even if I wanted to, as a commercial operator in AUS I cannot. This is why I have sought a stable version of PG20 parameters on 4.0.1, which is the last reference I can find on foxtech website of them using Stable firmware.
I work as a full time Rescue officer, some of what we do others would consider dangerous, I donāt because the gear we use is rigorously tested (stable) so it wonāt fail, and we operate to procedures (manuals) that minimise Human factors. The same principals apply throughout aviation.
I have also been following this build of yours and it will probably be my first home build. Iām glad it uses latest Ardulane.
Take Care
Steve
Hi Ron,
There is no servo associated with the rear motor. It is only used when hovering.
Cheers!
hi Greg I meant setting the function of the flight control output connected to the ESC of the aft motor. it was not explicitly explained in the documentation, but i think it should be āmotor 4ā. I am also confused about the ESCs of the two front motors, whether they should be āleft/right motor throttlesā as the documentation suggests or āmotor 1/2ā as the link I pasted used. i donāt want to find out the hard way in a flight test.