@tom yes, will try and do so tomorrow.

actually it might not be feasible for me to snap actual photos I just made an image showing the basic concept

Hello, I'm Chris from Berlin and I just wanted to kind of just introduce myself and say hi and wave over and all. Because I'm likely to ask questions here in the near future but I'm not at the point yet where I have all the information I need to ask the right specific questions you know?
I'm mostly whirling about MAVLINK errors atm but am personally more on the PX4 flying-side, like I know my way around flight controllers and drones and stuff. =P

@modaltb said in GPS/Mag - Connection woes and Firmware versions:

OK OK, I see what you are talking about.

Yes J1009 is a UART... but not configured for TELEM, this is where we map MAVLINK instances to UARTs:

https://github.com/PX4/PX4-Autopilot/blob/master/boards/modalai/fc-v1/default.cmake#L12

There is/was a max MAVLINK instance count (at least in 1.10/1.11) that prevented enabling another instance.

Are you setup to compile PX4? It might be you just need to add another instance after the line called out above.

For the UART instances, this is what we have by default, and you could mess around by changing these to fit your need.

		GPS1:/dev/ttyS0 # UART1  / J1012
		TEL1:/dev/ttyS6 # UART7  / J1010
		TEL2:/dev/ttyS4 # UART5  / (internally routed)
		TEL3:/dev/ttyS1 # USART2 / J1002

The form factor is off of a "racer" style, where we don't have all the interfaces like PX4IO etc, so you might find some limitations if comparing to other flight controllers with more IO.

Hey man, just wanted to let you know that against all odds this actually worked.
I put in the line describing TELEM4 and built the firmware myself and - tadaa!
Thanks again.

Hey everyone,
just wanted to let you know that my fix got merged into master so it should work for everyone now...

I'd have loved to change the title of this to something a little more descriptive but it's too late now I guess.
anyway, cheers everyone, happy flying.

Hi ModalAI,
I'm about to setup some tests to check on the temperature on the pcb but I'm not quite sure where the GPU and the CPU is localized on the voxl. Can anyone tell me which component is the GPU and the CPU and if there's a well known temperature limit for these components? Right know I'm measuring temperatures around 100°C and above which is quite high. How much temperatures can they take and how does the system respond to overheating? Shut down or just decreasing the frequency?

Thanks for your help!!

Hey, just giving some more information and a little bump since I'm still in desperate need of this compass working on my drone.
Please try and have another look into this for me if you could...
thanks so much and a perfect weekend for everyone.
cheers

unit on bus:

Tried starting it manually to no avail:

@modaltb Hello there, I just wanted to give a little update here:
I managed to connect it in a way that it's now appearing on the I2C bus as 23 by putting a 10k resistor on vcc and the I2C-enable pin but it's still not being detected by PX4 as a magnetometer and I couldn't start it manually either.
I do see it on the bus just like with another mag ("gy-85" board using the QMC5883L and two other IMUs which also appear on the bus when scanned) but can't get it to start and work in PX4.

@James-Strawson hello there James.
I've been dumbfounded by the "IMUs" page in your documentation for quite some time now so I'm very thankful that you took that on.^^

Can you please clarify a few things for me here:

1:What do you mean by 'likely DNI'd' for Fligh Ccore IMU3?
Sorry, I actually don't know what that means.

2: For now I'm only using the Flight Core -part of the VOXL-Flight so does that mean PX4 by itself is always only using the 20602 and the 42688p?

3: I've tried using the suggested command "voxl-configure-mpa" in an SSH shell, via ADB and in QGC's nutshell CLI but always get an error "command not found".
Where exactly would I use that? Using other "voxl-" related commands usually work no matter where I enter them so could you please maybe point me in the right direction?

Here's the output when checking for present IMUs:

Thanks a lot for all your guys' work and a nice week to everyone. Cheers.

Hi ModalAI, ^^

I'm encountering issues with a certain compass on your flight controller.
I detailed the issue here link text
but in general I wonder, do you guys have any specific experience with this mag unit?

I'll try and keep you updated. Thanks for your work, guys!

Hey,
just wanted to give an update it looks like the problem was a hardware fault.
The behavior stayed the same after detaching the LTE and the setup works on a different VOXL Flight, so yeah...^^
cheers

One more thing to add I can think of is
that on another drone the same setup but without the LTE module is working normally.
Please tell me if it would make a big difference to have actual photos and I'll see what I can do...

@tom yes, will try and do so tomorrow.

actually it might not be feasible for me to snap actual photos I just made an image showing the basic concept

Hi guys and gals
Sorry for coming up with such a probably weird and quirky issue again and also I really tried my hardest with the title here, so please have some lenience with me here...

I startup the drone with an LTE module (v2) attached and a camera connected to the VOXL-Flight's USB port.
Scanning wifi-IP's this VOXL doesn't show up anymore and I can't connect to it through a GS nor SSH.
Now the thing is, as soon as I pull the camera from the VOXL's USB the wifi on the VOXL starts up and it will connect to a GS and I can SSH in normally.

I tried plugging the camera back in and the wifi (wlan) on the VOXL actually ceases to work again.

Are there possibly any resource conflicts going on here?
Should I try connecting the camera to the LTE module instead? (As I understand this doubles as a USB-hub?)

thanks for any insights.
cheers

@Artur yes, try connecting to Mission Planner. Did you change any MAV related settings?
cheers