@FIREBIRD Sure, reach out at https://modalai.com/contact Yes, it's supported in production volumes

@Vinny As per the parameters you provided, this sensor cannot operate at temperatures below 0 degrees Celsius. Thank you!

Hi @JANG The only time a power module is damaged is when a power supply is used to power the system and the motors are spun up, creating a voltage spike on the input rail that exceeds 28V, not a battery. So, this overall is very surprising to me. You are welcome to use any 5V source for FCv2. It does not need much power (maybe 1-2Amps total) so our power module is overkill for a FCv2, but it helps by providing current and voltage readings to to PX4 or you FC SW of choice.

@wen-max On the datasheet it says take-off weight of 566g https://docs.modalai.com/starling-2-max-datasheet/ Take off weight includes the battery

@wen-max Yes, the 500g payload capacity is in addition to the battery. If you double the weight, flight time will be cut in half

@Bernhard @James-Strawson @Zachary-Lowell-0 @Alex-Kushleyev @nuallaino I have a brand new Starling 2 Max (received 3 days ago), and I'm having the same problem described by nuallaino and Bernhard (no GPS even when outside for a long time). My system info and results of px4-listener are pasted below. I did unplug the Lepton 8-pin JST SH connector as suggested by James Strawson, but that had no effect. Everything else seems to work fine (haven't tried 5G comm yet), but I'm hesitant to fly without GPS functioning properly, so at this point I'm stuck. Any suggestions would be most welcome. Thanks for your help ! system-image: 1.8.02-M0054-14.1a-perf kernel: #1 SMP PREEMPT Mon Nov 11 22:47:44 UTC 2024 4.19.125 hw platform: M0054 mach.var: 1.0.1 voxl-suite: 1.4.1 current IP: wlan0: 10.0.0.19 voxl2:~$ px4-listener sensor_gps TOPIC: sensor_gps sensor_gps timestamp: 841732144 (0.020669 seconds ago) timestamp_sample: 0 time_utc_usec: 0 device_id: 11272245 (Type: 0xAC, SERIAL:6 (0x00)) lat: 0 lon: 0 alt: -17000 alt_ellipsoid: 0 s_variance_m_s: 999.00006 c_variance_rad: 3.14159 eph: 4294967.50000 epv: 3796926.25000 hdop: 99.99000 vdop: 99.99000 noise_per_ms: 64 jamming_indicator: 15 vel_m_s: 0.00000 vel_n_m_s: 0.00000 vel_e_m_s: 0.00000 vel_d_m_s: 0.00000 cog_rad: 0.00000 timestamp_time_relative: 0 heading: nan heading_offset: 0.00000 heading_accuracy: 0.00000 rtcm_injection_rate: 0.00000 automatic_gain_control: 0 fix_type: 0 jamming_state: 0 spoofing_state: 1 vel_ned_valid: False satellites_used: 0 selected_rtcm_instance: 0 voxl2:~$ px4-listener sensor_mag TOPIC: sensor_mag sensor_mag timestamp: 861420482 (0.006257 seconds ago) timestamp_sample: 861420007 (475 us before timestamp) device_id: 527625 (Type: 0x08, I2C:1 (0x0D)) x: -0.04417 y: -0.32142 z: 0.42167 temperature: nan error_count: 0 voxl2:~$

@RSAUser1 It's not something I've tried, but I assume it would work in the same way you would do it on another Ubuntu 18.04 device.

Hi @dew54 , Are you willing to share your schematic with us? We always perform a courtesy review of any customer design. What Alex said is true but there are some more subtle nuances because our Microhard design pre-dates Voxl 2. Everything was designed to be backwards compatible but a custom design can certainly step on some toes of the 5V network. Let us know if you are willing to share and we'll email you to exchange the Sch. Thanks!

@ravi , sounds good. The updated opencv deb is the same that i posted a while ago, but i fixed a small issue related to installation of a symlink as part of deb install (which was mentioned in the other thread, i believe) Alex

@RSAUser1 said in Sierra Modem not showing in Device Manager/wds errors: @tom I just heard back from Sierra wireless and they are stating this is an issue on your guys side. Not sure how to proceed. Any insight on the path forward is appreciated. Maybe if we can speak with you and Sierra wireless in a joint chat that would be easiest? Thanks. Sorry just want to add. We were able to get a connection to our emulator but only when the modem status shows: voxl2:/$ systemctl status -l voxl-modem ● voxl-modem.service - Modem Initialization Loaded: loaded (/etc/systemd/system/voxl-modem.service; enabled; vendor preset: enabled) Active: inactive (dead) Which seems to have confused me more. What we did was disable the vision-hub , just to allow another service to start (in theory) but then disabled modem, adb rebooted, enabled modem all while we were injecting the 5G signal (only band n5 works but handovers to supported bands do work). Any deviation from these steps does not work, like if we reboot then inspect-services or anything besides just enabling modem it will not connect. Is this because if the drone loses power or anything the first thing it needs to do is find the network (another theory)? Even if we are connected and turn of the 5G cell from our side and turn it back on the chipset does not reconnect and it looks like it is not trying to find a cell. Looks like this is on sierra wireless, is there anyway we can have a joint chat to troubleshoot this? Thanks!

@RSAUser1 yeah i'd probably pass to @tom . The modem is seems connected, otherwise you wouldnt see wwan0 come up. Once I had access to AT commands I ditched QMI which I think is more or less a wrapper for those commands anyway.

@KnightHawk06 , please upgrade your VOXL2 SDK, as you have very old release, you can get the latest SDK 1.4.0 and then configure your cameras. https://docs.modalai.com/sdk-1.4-release-notes/ After installing latest SDK and configuring cameras, confirm via ADB shell that camera server is getting camera data: #this test app will subscribe to all camera streams and report stream resolution, fps, etc #please note that this test can put unnecessary stress on the system because it will stream ALL the possible camera streams, so normally you would not run this test all the time voxl-inspect-cam -a after that, if you want to view the camera stream using voxl-portal but you do not have internet connection, you can do that using adb port forwarding trick : https://docs.modalai.com/voxl-portal-via-adb/ Let us know if you have any other questions. Alex

@Jia-Wan Yes, you should be able to do your testing with SITL before trying it on Starling.

@Gary-Holmgren Copying over response from another thread: https://forum.modalai.com/post/20119

@tom thank you. I've been looking through the code. I'd like to test masking areas of non-interest in my tracking cameras. From the voxl-open-vins-server.conf file and from common.h image_data struct it seems like this feature exists, but I cannot find where I can put the masks, or define where they are. Do you know if this is implemented already? Maybe I'm looking in the wrong place?