DaveM
CEO Flite Test
Did you guys not see the video we created explaining which header pin and to use the MSP message? While the video was for BetaFlight, MSP was created by Tridge of ArduPilot and the BetaFlight Devs.
FT EZ ID?
- Thread starter FishbonesAir
- Start date
DaveM
CEO Flite Test
It’s possible. The hesitancy comes from regulation, not technical viability. The remote ID rule requires “tamper resistance”. I’m part of the ASTM Remote ID working group who created the remote IM Means of Compliance. I’m pretty sure it’s the only one approved by the FAA. The MoC is essentially the specification for all Standard and broadcast module remote ID. Most flight controller firmware is open source. Intermingling remote ID software with flight controller software is consider inconsistent with the FAA’s “tamper resistant” requirement. We argued with the FAA for weeks to be more specific than, “tamper resistance.“.
That said there are a few flight controllers with protected space which can hold proprietary code and it is separated from the flight controller code. We have discussed this as a possible solution for Standard remote ID which requires the RID system to be able to ground the aircraft if the RID system fails a power-on test.
DaveM
CEO Flite Test
The FT EZ ID transmits Bluetooth 4 AND Bluetooth 5. That’s why you see two aircraft on drone scanner.
DaveM
CEO Flite Test
Or you could use a flight controller and use the GPS signal from the FT EZ ID. That’s why there’s a UART on the FT EZ ID. It supports BetaFlight and ArduPilot using the MSP protocol (message).
jonbrotherton
New member
Yes but it still isn't working properly. Seems it doesn't update often enough for current Ardupilot. (?) I was able to set it up and fly a copter using the EZID for a GPS and it showed a location but was unable to hover steady at all.
DaveM
CEO Flite Test
Jon rotherton, Do you know the required refresh rate for ArduPilot? The refresh rate we are talking about is the refresh of the MSP message from the FT EZ ID to the Flight Controller for others reading this.
I’ve sent this question to Tridge, System Development Lead of ArduPilot. I know the minimum MSP refresh rate for BetaFlight is 10 Hz.
Last edited:
DaveM
CEO Flite Test
jonbrotherton
New member
I'm sorry I don't know. But if you've got Tridge involved I bet it will get resolved soon. Thank you for working on this!
jonbrotherton
New member
@DaveM @LitterBug
I am working on providing a PnP kit for the thousands of 3DR Solo copters that are still flying, to use the FT EZID. It plugs into the accessory port on the bottom of the Solo for standalone use.
I also plan to provide a kit for installing it in the GPS Bay, including a script for changing the Ardupilot params, for use as the main GPS. But that is contingent on how well it will work as the only GPS unit on the vehicle. 🤞
Let me know when there is a possible solution and I can test it in a timely manner.
I am working on providing a PnP kit for the thousands of 3DR Solo copters that are still flying, to use the FT EZID. It plugs into the accessory port on the bottom of the Solo for standalone use.
I also plan to provide a kit for installing it in the GPS Bay, including a script for changing the Ardupilot params, for use as the main GPS. But that is contingent on how well it will work as the only GPS unit on the vehicle. 🤞
Let me know when there is a possible solution and I can test it in a timely manner.
I would reccommend sending the ArduPilot developers a handful of units to test with. They would be able to give you better recommendations on what if any changes might be needed to the EZID firmware.
DaveM
CEO Flite Test
I got an answer directly from Tridge, ArduPilot sys dev lead. He said ArduPilot only needs 5 Hz MSP refresh Rate. That’s what the FT EZ ID currently has.
What do you plan to use for a compass (mag) ? Copters require a magnetometer for orientation. The forward motion of planes make a compass redundant, but with copters ability to move in any direction and hover, they require the compass.
The old 3DR GPS modules also came with a compass.
jonbrotherton
New member
The 3DR Solo OEM GPS module doesn't have an onboard compass. The Solo has an external compass in the right rear leg, plus an internal compass in the Cube Flight Controller.
Nuts... So I have a limitation with the ArduPilot 4.4.4 firmware for the F405-wing not having MSP sensors baked in to the firmware due to memory limitations. Going to have to switch to a different FC. I have a F765-Wing, and H743-Wing to test with too. I had previous success with the H743-wing in some above messages. I think this was the issue not the refresh rate that was preventing me from using it as a primary GPS on some of my flyers. I had wanted to test it on a Strix Nano Goblin (sub 250 on 2S, >250 on 3S) but it is also running an F405 based FC (OmniBusNanoV6) that does not have MSP_Sensors in the "standard" Ardupilot firmware either.
Last edited:
jonbrotherton
New member
It would be easier to add it back in using the Custom Firmware Builder under the MSP section.
ArduPilot Custom Firmware Builder
ArduPilot Custom Firmware Builder. It allows to build custom ArduPilot firmware by selecting the wanted features.
custom.ardupilot.org
Appears the Matek F765-wing also does not have MSP sensors included in the "standard" firmware. This leaves me with only the H743-wing to test with. So my problem was definitively with the lack of "Standard" MSP-Sensor support, not with the refresh rate. I will continue testing with the H743-wing.
LB
LB
