Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add *new* magnetometer DA 5883(QMC5883) into the list of mag_hardware in future firmware. #2558

Closed
chan2328 opened this issue Dec 6, 2017 · 13 comments

Comments

@chan2328
Copy link

chan2328 commented Dec 6, 2017

as #2299 the solution is found and tested which is removing the magGain. is it possible to add new magnetometer DA 5883(QMC5883) into the list of mag_hardware in future firmware?

@digitalentity
Copy link
Member

QMC5883 is supported already. What you are asking for is support for poorly cloned HMC5883 compass. I'm not sure that removing magGain from HMC5883 driver is a proper way of doing this as it will break existing setups.

@chan2328
Copy link
Author

chan2328 commented Dec 8, 2017

@digitalentity Sorry, May be my explanation is not clear, I mean that add a additional driver for particular magnetometer (DA 5883), no need to change existing driver, because I have HMC5883 too, the existing driver for HMC5883 is good and works great.
after flight few days. DA 5883 did very well, so I suggest adding into the list of mag_hardware for future firmware. and we should understand that we need to take a risk when using this magnetometer (DA 5883). Trial and Error.
Actually, I want to modify firmware by myself, but it is out of my knowledge, as there is no easy way to get into the coding, no tutorial i can follow step by step to create custom firmware, whatever thank you very much.

@shellixyz
Copy link
Collaborator

@chan2328
Developer documentation exists: https://github.com/iNavFlight/inav/tree/master/docs/development
Compiling a custom firmware is relatively easy. Once you installed the ARM compiler toolchain just download the iNav source code and execute make TARGET=your_target.

@stronnag
Copy link
Collaborator

stronnag commented Dec 8, 2017

@chan2328
Copy link
Author

chan2328 commented Dec 9, 2017

@shellixyz @stronnag followed the step, but it is not work. what should i do next? install 1, 2, 3 steps in RUBY windows?
1

@chan2328
Copy link
Author

chan2328 commented Dec 9, 2017

I am using windows 7 64bit . should i install 64bit version of RUBY or else

@parnz
Copy link

parnz commented Dec 9, 2017

Use docker solution to build inav is super easy :)

@shellixyz
Copy link
Collaborator

@chan2328 What Ruby installer did you use ? The installer downloaded from https://rubyinstaller.org/ (the URL from Building in Windows) should be a GUI and automatically add Ruby to your PATH. The problem is that the installer you used did not add the path of your Ruby binaries to the PATH environment.

@chan2328
Copy link
Author

chan2328 commented Dec 9, 2017

Ruby 2.4.2-2 (x86) 2

i lost.........
3

@shellixyz
Copy link
Collaborator

I'm not using Windows but I installed the same version along with Cygwin (all defaults) in a fresh VM and it is working.
inav_build_win

@chan2328
Copy link
Author

@shellixyz I also follow the steps but there is no git completion, it is different.
4

@shellixyz
Copy link
Collaborator

shellixyz commented Dec 11, 2017

@chan2328 You don't need the bash completion for git just skip it. Also if the ruby installer doesn't work you can install ruby from Cygwin it is in the Interpreters category.

@stronnag
Copy link
Collaborator

stronnag commented Apr 4, 2018

The firmware now supports this device, closing.

@stronnag stronnag closed this as completed Apr 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants