Topics created by wilkinsaf

Hi Andrew, This is great info, thanks for clarifying. Unfortunately, our current product offerings do not support the "Pixhawk" style APM ADC inputs for current and voltage monitoring. However, I would bet that you could find source code for an Arduino or STM project where these ADC values have been converted to appropriate PX4 I2C digital formats that you can then feed into our products. Keep in mind, the I2C bus needs to be at 5V and you should provide the I2C pullups on your converter module (anything from 10K to 4.7K works well for our I2C translator). Thanks! Vinny

I realize I made a mistake and meant 12S, but same problem

Thank you. I just realized it said "standard Manufacturer lead time: 34 weeks" but they have plenty in stock. Appreciate it!

This is for the STM32 based FlightCore.... not SLPI which I think you're super aware of but making sure!

@Chad-Sweet Is it ready? Where I can purchase voxl2io?

@Chad-Sweet That is what I was thinking. I'll check in with the boss and see what he wants to do. Thanks!

@tom Yes! we were able to make a connection! Thank you @tom

Thanks Eric!

Yeah, all systemd-journal-flush.service is doing is running journalctl --flush which is not doing anything when run manually

@Chad-Sweet Right on. I will take a look at it. See what I can do

Hardware people on my team asked me to send it to send it to them at a different facility after posting this. My apologies @Alex-Gardner Will follow up if I see this happening with another board Marking as DEAD

@Alex-Gardner I see why you created a separate tool for checking the connected cameras as the code in that tool is implemented in much lower level files on voxl-camera-server. I did quickly put together a flag option that would list cameras if they are setup in /etc/modalai/voxl-camera-server.conf I created a pull request here Let me know if this is useful. If the needed feature requires all cameras to be listed let me know and I can see what I can do. Also, I was trying to find a way to get some form of id off of the cameras, but I see in code that we compare the resolutions and that is how we distinguish a stereo from a tracking. Was trying to find some HAL3 data member that could give more of an "id". I found this ANDROID_REQUEST_ID variable in this documentation, but I could not get it working

@wilkinsaf Thank you for posting your solution, very helpful!

@wilkinsaf Hahaha appreciate you sharing your expertise

If you could run camera server manually with additional debug prints (i.e. voxl-camera-server -d 0) and paste the output here, you'll be able to see more info about whats going on that'll make it easier to debug

It appears this happens when the sensors are not calibrated on the drone. voxl-vision-px4 picks up on sensor inconsistency and restarts PX4. So, calibrated the sensors. Looks better resolved

@Eric-Katzfey microhard addition

I'm not sure if you can have 2 slaves join the same network. From my understanding these modems only support 1 master and 1 slave

So, here is how we solved our issue. Even though EKF2 bitmask was set to only listen to GPS, heading still appeared to take VIO into consideration. After turning off VIO on VOXL we got MUCH better readings. Then, after we realized this, we changed out bitmask to 329 (which is in the instructions for flying outdoors without GPS here: https://docs.modalai.com/flying-without-gps/ So, our problem appears to be resolved right now. We just need to test repeatability for this solution