ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. Alex Kushleyev
    3. Posts
    • Profile
    • Following 0
    • Followers 11
    • Topics 1
    • Posts 2122
    • Best 125
    • Controversial 2
    • Groups 1

    Posts made by Alex Kushleyev

    • RE: Inquiry about camera lens for M0161, Starling 2

      @yaoyuh, sorry for the delay. It looks like we have the lenses in stock, so you could fill out the contract form for a custom order and mention part number "M10000513 - Lens for M0161 Camera without IR filter".

      https://www.modalai.com/pages/contact-us

      Also, you can remove the IR filter from your current lenses. You have to be a bit careful so that the pieces of filter are not spread in your work space. My suggestion would be to first place a small piece of tape on top of the filter which will keep all the pieces together if the filter breaks during removal. The filter has a rectangular shape and is attached to the back side of the lens with an adhesive in 4 corners. It should be possible to just pry it off from the back of the lens (after completely removing the lens from the camera module). When you remove the lens from the camera module, you should cover it up so that dust does not get inside and on the sensor itself.

      Please note that removing the filter from the lens is not an official guideline, but you could do it at your own risk.

      Please see the following post where we also discussed removing the IR filter from AR0144 (which was actually more difficult because the filter there has a round shape) : https://forum.modalai.com/topic/4826/msu-m0149-1-ir-filter

      Alex

      posted in Image Sensors
      Alex KushleyevA
      Alex Kushleyev
    • RE: Hadron ov64b snapshots have a vertical image artifact

      @cguzikowski , if you want, you can attache a cropped image, so that it's smaller size.

      In general, the pixel noise increases as you the pixel gain is increased. Part of Auto Exposure control is controlling exposure time and gain (both of which contribute to the image brightness), but higher gain has higher pixel noise and higher exposure values will result in motion blur.

      The Qualcomm ISP has lots of liters, including noise reduction, which are applied when you use the ISP snapshot (even though they have not been tuned for the particular camera, the ISP output may result in better de-noised image). There are several types of filters, for example spatial (such as bilateral filter) and temporal (TNR - temporal noise reduction), and it's usually a combination of both with the filter weights increasing as the gain increases (more noise requires more noise reduction).

      Currently, MISP does not have any de-noise filtering, but we are working on adding some. That is why i was discussing with you the ability to process the image offline (from the original bayer source). You could save the full raw image and perform any filtering you need in post processing. This approach is similar to using a RAW image on a fancy camera and then importing that into image processing software on a laptop / desktop, which can perform a lot more filters / effects directly on the raw image (loss-less).

      What i suspect is that you are testing in the low-light environment and you are seeing the effects of high gain (high pixel noise). the MISP auto exposure tries to balance exposure and gain and there are a few parameters for that, but in your tests you should see what exposure and gain values the camera is at when you see the noisy image. You can use voxl-portal to control exposure and gain to see what the difference is. I believe the max gain for ov64b is 16x (1600).

      I am about to set up your use case again for testing and i will investigate the noise and the original ISP snapshot artifact and we can also compare the image noise from the ISP snapshot and misp snapshot.

      Unfortunately the lens for ov64b in the Hadron unit is very small, which reduces the amount of light that gets into the sensor. The sensor is 8+K resolution which means the pixel size is small, so the amount of light that gets to each pixel is small. To compensate for that, we would typically want a larger lens, but it is probably not possible to change the lens in this specific Hadron unit (we have not tried).

      If you want to explore offline image processing, you would need:

      • the original raw bayer (which you can already save)
      • the gain and exposure used for that frame (i will need to check, i thin we had an option to save the exposure and gain as part of the file name).
      • then you can have offline processing that is dependent on exposure / gain and apply the filters of your choice.
      • the only down side is that the raw snapshots are huge, but you can probably zip them up if needed to store a lot of them on voxl2 before offloading.

      Alex

      posted in Video and Image Sensors
      Alex KushleyevA
      Alex Kushleyev
    • RE: Snapshot crashes voxl-camera-server

      @rddrone , thanks for the information. I will look into this. I have not heard of this issue before, so maybe something new, but i will test it out today.

      Alex

      posted in Video and Image Sensors
      Alex KushleyevA
      Alex Kushleyev
    • RE: Periodic Intra Video Refresh

      @Anthony-Kang , we are looking into this. However, initial attempts to enable Intra Refresh on VOXL2 via the OMX api did not succeed either for h264 or h265. Also h265 does not work with fixed Macro Blocks (Coding Tree Units instead), so it seems the OMX structures for this param would not work with h265.

      Alex

      posted in Video and Image Sensors
      Alex KushleyevA
      Alex Kushleyev
    • RE: Multiple Critical Bugs in voxl-imu-server: Incorrect FIFO Latching and HiRes Indexing (ICM-42688)

      @Igor ,

      You are absolutely correct about the incorrect parsing of the accel data. This is a typo and it was not detected because the effect of it is very small (4 LSB of the 20-bit number). The accelerometer noise in flight will dominate and these bytes will have no effect. We will fix this bug.

      Regarding the order of the reading of FIFO_COUNT, we looked at many other sources, including the reference code from TDK and all the implementations read the FIFO_COUNTH first, so we suspect that the documentation has a typo (which makes sense, otherwise the implementation would have to have separate transactions for reading the H and L parts).

      Thank you again for your bug report.

      Alex

      posted in VOXL SDK
      Alex KushleyevA
      Alex Kushleyev
    • RE: Snapshot crashes voxl-camera-server

      @rddrone , can you please provide your voxl-camera-server.conf to help us debug / reproduce?

      Alex

      posted in Video and Image Sensors
      Alex KushleyevA
      Alex Kushleyev
    • RE: C29 Configuration

      @RoyAzriel , we were temporarily out of stock on some components and C29 configuration of Starling 2 Max is available again.

      The TOF sensor kit (M0177 + M0171 + TOF Sensor) will plug in directly into M0173 camera front end and the Front camera mount already has a spot to mount for the TOF sensor. So you should be able to turn C28 into C29. See C27 here for reference how the TOF sensor is connected : https://docs.modalai.com/voxl2-coax-camera-bundles/#kit-pictures-and-descriptions

      Alex

      posted in Starling & Starling 2
      Alex KushleyevA
      Alex Kushleyev
    • RE: Starling 2 / VOXL2 M0129 ESC not detected during voxl-esc scan or firmware upgrade

      @boron , thank you for performing the test. Were you also to check if the 5V output (that normally goes to VOXL2) has 5V on it?

      The capacitor that you circled in RED definitely appears to be damaged. This is a bypass capacitor on VBATT that is right next to the Mosfet Driver. It is possible that the capacitor was faulty and burned out, however since there is no short circuit or further overheating (based on the zero current draw from the power supply), the capacitor is probably not preventing the ESC MCUs from booting.

      I suspect that there is another issue somewhere, but it would be good to know if the 5V rail is functional (i suspect that it is not). There is no on/off power switch on the ESC, so the main 5V regulator provides 5V from VBATT (which is used for VOXL2) and then another regulator that provides 3.3V (from 5.0V) for the four MCUs.

      Alex

      posted in ESCs
      Alex KushleyevA
      Alex Kushleyev
    • RE: Hadron ov64b snapshots have a vertical image artifact

      @cguzikowski , sorry for the delay.

      Long term, our plan is to add snapshot functionality directly into misp (just like you were getting snapshots from the ISP). That is not too difficult to achieve, may be a few weeks away.

      Also let me ask you this: would you want to save the raw bayer and get that from voxl2 and convert to jpg / png offline? That would give you maximum control over quality / processing algorithm. Alternatively, de-bayering can be done on voxl2 and saved as lossy or lossless image?

      We do have tools to convert bayer -> yuv -> jpeg but not yet in a standalone app.

      You you can do for now is the following:

      • set misp output resolution equal to the raw resolution
      • this will enable misp to publish the de-bayered yuv to the image pipe
      • then you can use voxl-record-raw-image to save the yuv. Alternatively, you can test a WIP version of this tool which can save yuv as jpeg : https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-mpa-tools/-/merge_requests/37
      • ideally this logging would be done within camera server to reduce overhead for sending these huge images over the pipe. But the approach i described should work for now.

      I will be able to test this again mid next week, meanwhile please let me know if you run into the saving issue. I will double check the issue with snapshot resolution being too large. How large was the isp snapshot that you tested before and had artifacts?

      Alex

      posted in Video and Image Sensors
      Alex KushleyevA
      Alex Kushleyev
    • RE: Which STEP file do I need for Starling2 MAX GPS mast?

      @MikeD , you will need D0012-4-V3-C28-M36-T7-K0-Starling2-Max-V3-20260317.step, which contains the latest gps receiver mast. You will need to open the whole assembly and extract the gps mast. The assembly is large and may take a few minutes to load. Please let us know if you are having issues with that.

      Alex

      posted in 3D Models
      Alex KushleyevA
      Alex Kushleyev
    • RE: Stinger & Hadron 640r

      With M0195, C34 is the camera configuration that you would need. See https://docs.modalai.com/M0195/#support-camera-configs

      posted in FPV Drones
      Alex KushleyevA
      Alex Kushleyev
    • RE: Stinger & Hadron 640r

      @dstylesunf ,

      Please check my post from January, which states that M0188 does not support a Boson sensor and you need M0195 if you want a drop-in replacement for M0188.

      https://docs.modalai.com/M0188/
      https://docs.modalai.com/M0195/

      Can you double check what you have plugged into your voxl2 mini?

      You can remove M0188 and install M0194 (which you have) as another option. You would need to transfer the ucoax connections from M0181 to M0194. The diagram above in this post shows you how to connect Boson and hires camera (essentially a Hadron combo) using M0194 to a voxl2 mini. Do you need more details on this connection?

      If you use the second option, you would lose the dual tracking capability though.

      Alex

      posted in FPV Drones
      Alex KushleyevA
      Alex Kushleyev
    • RE: Hadron ov64b snapshots have a vertical image artifact

      @cguzikowski , you need to update your camera server to allow misp to accept the new resolutions. You can install the latest one from voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/

      posted in Video and Image Sensors
      Alex KushleyevA
      Alex Kushleyev
    • RE: Station Mode Issue with Voxl Suite 1.6.3

      @SKA , thank you for providing all the information. We are doing more testing and will get back to you. So far cannot reproduce.

      Alex

      posted in Ask your questions right here!
      Alex KushleyevA
      Alex Kushleyev
    • RE: Station Mode Issue with Voxl Suite 1.6.3

      can you please check output of ifconfig ? i wonder if wlan0 is not the primary interface for some reason

      posted in Ask your questions right here!
      Alex KushleyevA
      Alex Kushleyev
    • RE: Station Mode Issue with Voxl Suite 1.6.3

      @SKA ,

      I have the same same error, but wifi is working (/etc/network/interfaces: No such file or directory).

      I also see that your dhcp client is able to get an ip address 10.10.10.116 for wlan0, which is strange that you don't see that ip address in ifconfig..

      posted in Ask your questions right here!
      Alex KushleyevA
      Alex Kushleyev
    • RE: Station Mode Issue with Voxl Suite 1.6.3

      @SKA , can you also please check journalctl -u dhcpcd to see if there is anything interesting there?

      Apr 03 18:10:27 m0054 systemd[1]: Starting LSB: IPv4 DHCP client with IPv4LL support...
      Apr 03 18:10:27 m0054 dhcpcd[1982]: grep: /etc/network/interfaces: No such file or directory
      Apr 03 18:10:28 m0054 dhcpcd[2095]: DUID 00:01:00:01:2b:93:59:dc:ea:a6:9f:04:b1:61
      Apr 03 18:10:28 m0054 dhcpcd[2095]: wlan0: IAID ca:b3:a4:ec
      Apr 03 18:10:28 m0054 dhcpcd[2095]: wlan0: adding address fe80::10c0:dcc6:145e:c4cd
      Apr 03 18:10:28 m0054 dhcpcd[2095]: bond0: waiting for carrier
      Apr 03 18:10:28 m0054 dhcpcd[2095]: dummy0: waiting for carrier
      Apr 03 18:10:28 m0054 dhcpcd[2095]: wlan0: carrier lost
      Apr 03 18:10:28 m0054 dhcpcd[2095]: wlan0: deleting address fe80::10c0:dcc6:145e:c4cd
      Apr 03 18:10:28 m0054 dhcpcd[2095]: wlan0: carrier acquired
      Apr 03 18:10:28 m0054 dhcpcd[2095]: wlan0: IAID ca:b3:a4:ec
      Apr 03 18:10:28 m0054 dhcpcd[2095]: wlan0: adding address fe80::10c0:dcc6:145e:c4cd
      Apr 03 18:10:28 m0054 dhcpcd[2095]: wlan0: carrier lost
      Apr 03 18:10:28 m0054 dhcpcd[2095]: wlan0: deleting address fe80::10c0:dcc6:145e:c4cd
      Apr 03 18:10:28 m0054 dhcpcd[2095]: dummy0: carrier acquired
      Apr 03 18:10:28 m0054 dhcpcd[2095]: dummy0: IAID 5b:b6:cf:20
      Apr 03 18:10:28 m0054 dhcpcd[2095]: dummy0: adding address fe80::8837:2803:320d:3a20
      Apr 03 18:10:29 m0054 dhcpcd[2095]: dummy0: soliciting a DHCP lease
      Apr 03 18:10:29 m0054 dhcpcd[2095]: dummy0: soliciting an IPv6 router
      Apr 03 18:10:34 m0054 dhcpcd[2095]: wlan0: carrier acquired
      Apr 03 18:10:34 m0054 dhcpcd[2095]: wlan0: IAID ca:b3:a4:ec
      Apr 03 18:10:35 m0054 dhcpcd[2095]: wlan0: soliciting an IPv6 router
      Apr 03 18:10:35 m0054 dhcpcd[2095]: wlan0: rebinding lease of 192.168.10.179
      Apr 03 18:10:35 m0054 dhcpcd[2095]: wlan0: probing address 192.168.10.179/24
      Apr 03 18:10:40 m0054 dhcpcd[2095]: wlan0: leased 192.168.10.179 for 7200 seconds
      Apr 03 18:10:40 m0054 dhcpcd[2095]: wlan0: adding route to 192.168.10.0/24
      Apr 03 18:10:40 m0054 dhcpcd[2095]: wlan0: adding default route via 192.168.10.1
      Apr 03 18:10:40 m0054 dhcpcd[2095]: forked to background, child pid 2755
      Apr 03 18:10:40 m0054 systemd[1]: Started LSB: IPv4 DHCP client with IPv4LL support.
      Apr 03 18:10:41 m0054 dhcpcd[2755]: dummy0: no IPv6 Routers available
      
      
      posted in Ask your questions right here!
      Alex KushleyevA
      Alex Kushleyev
    • RE: Station Mode Issue with Voxl Suite 1.6.3

      @SKA , please check the output of syslog, it may contain a hint as to why wlan0 has a static ip, maybe dhcpcd is not working properly.

      posted in Ask your questions right here!
      Alex KushleyevA
      Alex Kushleyev
    • RE: Station Mode Issue with Voxl Suite 1.6.3

      Also, here is output of tail -n 100 /var/log/syslog:

      Apr  3 18:17:22 m0054 dhcpcd[2755]: wlan0: carrier lost
      Apr  3 18:17:22 m0054 wpa_supplicant[1996]: wlan0: CTRL-EVENT-DISCONNECTED bssid=5c:e9:31:0a:78:23 reason=3 locally_generated=1
      Apr  3 18:17:22 m0054 kernel: [  402.693093] RTW: rtw_ndev_uninit(wlan0) if1
      Apr  3 18:17:22 m0054 systemd[1]: Starting Load/Save RF Kill Switch Status...
      Apr  3 18:17:22 m0054 systemd-rfkill[4368]: Failed to open device rfkill3: No such device
      Apr  3 18:17:22 m0054 systemd[1]: Started Load/Save RF Kill Switch Status.
      Apr  3 18:17:22 m0054 dhcpcd[2755]: wlan0: deleting address fe80::5c1e:5176:405d:82d8
      Apr  3 18:17:22 m0054 dhcpcd[2755]: wlan0: deleting default route via 192.168.10.1
      Apr  3 18:17:22 m0054 dhcpcd[2755]: wlan0: deleting route to 192.168.10.0/24
      Apr  3 18:17:22 m0054 dhcpcd[2755]: wlan0: removing interface
      Apr  3 18:17:29 m0054 kernel: [  409.880457] usb 1-1: new high-speed USB device number 5 using xhci-hcd
      Apr  3 18:17:30 m0054 kernel: [  410.369086] RTW: HW EFUSE
      Apr  3 18:17:30 m0054 kernel: [  410.369100] RTW: 0x000: 29 81 00 BC  09 00 21 00  6E 04 A4 34  10 00 30 0B  
      Apr  3 18:17:30 m0054 kernel: [  410.369142] RTW: 0x010: 26 26 26 26  26 26 27 27  27 27 27 13  FF FF FF FF  
      Apr  3 18:17:30 m0054 kernel: [  410.369221] RTW: 0x030: 13 FF FF FF  FF FF E0 FF  FF FF 28 28  28 28 28 28  
      Apr  3 18:17:30 m0054 kernel: [  410.369299] RTW: 0x050: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      Apr  3 18:17:30 m0054 kernel: [  410.369377] RTW: 0x070: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      Apr  3 18:17:30 m0054 kernel: [  410.369454] RTW: 0x090: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      Apr  3 18:17:30 m0054 kernel: [  410.369532] RTW: 0x0B0: FF FF FF FF  FF FF FF FF  7F 1A 1B 00  FF FF FF FF  
      Apr  3 18:17:30 m0054 kernel: [  410.369609] RTW: 0x0D0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      Apr  3 18:17:30 m0054 kernel: [  410.369687] RTW: 0x0F0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      Apr  3 18:17:30 m0054 kernel: [  410.369764] RTW: 0x110: 65 61 6C 74  65 6B 0E 03  38 30 32 2E  31 31 61 63  
      Apr  3 18:17:30 m0054 kernel: [  410.369842] RTW: 0x130: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      Apr  3 18:17:30 m0054 kernel: [  410.369920] RTW: 0x150: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      Apr  3 18:17:30 m0054 kernel: [  410.369997] RTW: 0x170: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      Apr  3 18:17:30 m0054 kernel: [  410.370075] RTW: 0x190: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      Apr  3 18:17:30 m0054 kernel: [  410.370153] RTW: 0x1B0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      Apr  3 18:17:30 m0054 kernel: [  410.370230] RTW: 0x1D0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      Apr  3 18:17:30 m0054 kernel: [  410.370308] RTW: 0x1F0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      Apr  3 18:17:30 m0054 kernel: [  410.562635] RTW: [RF_PATH] ver_id.RF_TYPE:RF_1T1R
      Apr  3 18:17:30 m0054 kernel: [  410.562646] RTW: [RF_PATH] HALSPEC's rf_reg_trx_path_bmp:0x11, rf_reg_path_avail_num:1, max_tx_cnt:1
      Apr  3 18:17:30 m0054 kernel: [  410.562653] RTW: [RF_PATH] PG's trx_path_bmp:0x00, max_tx_cnt:0
      Apr  3 18:17:30 m0054 kernel: [  410.562665] RTW: [RF_PATH] HALDATA's trx_path_bmp:0x11, max_tx_cnt:1
      Apr  3 18:17:30 m0054 kernel: [  410.562680] RTW: [TRX_Nss] HALSPEC - tx_nss:1, rx_nss:1
      Apr  3 18:17:30 m0054 kernel: [  410.562686] RTW: [TRX_Nss] Registry - tx_nss:0, rx_nss:0
      Apr  3 18:17:30 m0054 kernel: [  410.562691] RTW: [TRX_Nss] HALDATA - tx_nss:1, rx_nss:1
      Apr  3 18:17:30 m0054 kernel: [  410.562700] RTW: txpath=0x1, rxpath=0x1
      Apr  3 18:17:30 m0054 kernel: [  410.562707] RTW: txpath_1ss:0x1, num:1
      Apr  3 18:17:30 m0054 kernel: [  410.563928] RTW: rtw_regsty_chk_target_tx_power_valid return _FALSE for band:0, path:0, rs:0, t:-1
      Apr  3 18:17:30 m0054 kernel: [  410.567269] RTW: rtw_ndev_init(wlan0) if1 mac_addr=00:c0:ca:b3:a4:ec
      Apr  3 18:17:30 m0054 systemd[1]: Starting Load/Save RF Kill Switch Status...
      Apr  3 18:17:30 m0054 systemd-rfkill[4511]: Failed to parse state file /var/lib/systemd/rfkill/platform-xhci-hcd.0.auto-usb-0:1:1.2:wlan: Invalid argument
      Apr  3 18:17:30 m0054 systemd[1]: Started Load/Save RF Kill Switch Status.
      Apr  3 18:17:31 m0054 dhcpcd[2755]: wlan0: waiting for carrier
      Apr  3 18:17:31 m0054 systemd-udevd[4512]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
      Apr  3 18:17:36 m0054 kernel: [  416.679144] RTW: wlan0- hw port(0) mac_addr =00:c0:ca:b3:a4:ec
      Apr  3 18:17:36 m0054 wpa_supplicant[1996]: wlan0: Trying to associate with 5c:e9:31:0a:78:24 (SSID='xxxxxx' freq=5200 MHz)
      Apr  3 18:17:36 m0054 wpa_supplicant[1996]: FT: Invalid key management type (2)
      Apr  3 18:17:36 m0054 kernel: [  416.734679] RTW: rtw_set_802_11_connect(wlan0)  fw_state=0x00000008
      Apr  3 18:17:36 m0054 kernel: [  416.868146] RTW: start auth
      Apr  3 18:17:36 m0054 kernel: [  416.871600] RTW: auth success, start assoc
      Apr  3 18:17:36 m0054 kernel: [  416.883349] RTW: assoc success
      Apr  3 18:17:36 m0054 wpa_supplicant[1996]: wlan0: Associated with 5c:e9:31:0a:78:24
      Apr  3 18:17:36 m0054 wpa_supplicant[1996]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
      Apr  3 18:17:36 m0054 kernel: [  416.888060] RTW: curr_tx_rate : CCK_1M (L)
      Apr  3 18:17:36 m0054 kernel: [  416.888070] RTW: curr_retry_ratio : 0
      Apr  3 18:17:36 m0054 kernel: [  416.888075] RTW: ra_mask : 0x00000000003ffff0
      Apr  3 18:17:36 m0054 kernel: [  416.898522] RTW: recv eapol packet 1/4
      Apr  3 18:17:36 m0054 wpa_supplicant[1996]: wlan0: WPA: Key negotiation completed with 5c:e9:31:0a:78:24 [PTK=CCMP GTK=CCMP]
      Apr  3 18:17:36 m0054 wpa_supplicant[1996]: wlan0: CTRL-EVENT-CONNECTED - Connection to 5c:e9:31:0a:78:24 completed [id=0 id_str=]
      Apr  3 18:17:36 m0054 kernel: [  416.925772] RTW: set group key camid:1, addr:5c:e9:31:0a:78:24, kid:1, type:AES
      Apr  3 18:17:36 m0054 dhcpcd[2755]: wlan0: carrier acquired
      Apr  3 18:17:36 m0054 dhcpcd[2755]: wlan0: IAID ca:b3:a4:ec
      Apr  3 18:17:36 m0054 dhcpcd[2755]: wlan0: adding address fe80::5c1e:5176:405d:82d8
      Apr  3 18:17:37 m0054 dhcpcd[2755]: wlan0: soliciting an IPv6 router
      Apr  3 18:17:37 m0054 dhcpcd[2755]: wlan0: rebinding lease of 192.168.10.179
      Apr  3 18:17:37 m0054 dhcpcd[2755]: wlan0: truncated packet (179) from 127.0.0.1
      Apr  3 18:17:37 m0054 dhcpcd[2755]: wlan0: truncated packet (207) from 127.0.0.1
      Apr  3 18:17:37 m0054 dhcpcd[2755]: wlan0: probing address 192.168.10.179/24
      Apr  3 18:17:42 m0054 dhcpcd[2755]: wlan0: leased 192.168.10.179 for 7200 seconds
      Apr  3 18:17:42 m0054 dhcpcd[2755]: wlan0: adding route to 192.168.10.0/24
      Apr  3 18:17:42 m0054 dhcpcd[2755]: wlan0: adding default route via 192.168.10.1
      Apr  3 18:17:50 m0054 dhcpcd[2755]: wlan0: no IPv6 Routers available
      
      posted in Ask your questions right here!
      Alex KushleyevA
      Alex Kushleyev
    • RE: Station Mode Issue with Voxl Suite 1.6.3

      @SKA , can you please try to power down the wifi device and power it back up (using the commands below) and check the output of dmesg.

      #turn off USB VBUS
      voxl-gpio write 157 0
      
      #turn on USB VBUS
      voxl-gpio write 157 1
      

      my dmesg output:

      [   24.123592] usb 1-1: USB disconnect, device number 2
      [   24.152384] RTW: rtw_ndev_uninit(wlan0) if1
      [   24.172973] RTW: rtw_dev_unload: driver not in IPS
      [   33.464284] usb 1-1: new high-speed USB device number 3 using xhci-hcd
      [   33.602465] usb 1-1: New USB device found, idVendor=0bda, idProduct=c820, bcdDevice= 2.00
      [   33.602487] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
      [   33.602502] usb 1-1: Product: 802.11ac NIC
      [   33.602517] usb 1-1: Manufacturer: Realtek
      [   33.602531] usb 1-1: SerialNumber: 123456
      [   33.614447] RTW: [HALMAC]55772M
                     HALMAC_MAJOR_VER = 1
                     HALMAC_PROTOTYPE_VER = 6
                     HALMAC_MINOR_VER = 6
                     HALMAC_PATCH_VER = 22
      [   33.760178] vdd_tof: disabling
      [   33.760182] vdd_hap_boost: disabling
      [   33.835010] qcom_rpmh DRV:apps_rsc TCS Busy, retrying RPMH message send: addr=0x40d00
      [   33.835034] qcom_rpmh DRV:apps_rsc TCS Busy, retrying RPMH message send: addr=0x40d00
      [   33.835055] qcom_rpmh DRV:apps_rsc TCS Busy, retrying RPMH message send: addr=0x40d00
      [   33.835075] qcom_rpmh DRV:apps_rsc TCS Busy, retrying RPMH message send: addr=0x40d00
      [   33.835095] qcom_rpmh DRV:apps_rsc TCS Busy, retrying RPMH message send: addr=0x40d00
      [   33.835115] qcom_rpmh DRV:apps_rsc TCS Busy, retrying RPMH message send: addr=0x40d00
      [   33.951477] RTW: HW EFUSE
      [   33.951489] RTW: 0x000: 29 81 00 BC  09 00 21 00  6E 04 A4 34  10 00 30 0B  
      [   33.951530] RTW: 0x010: 26 26 26 26  26 26 27 27  27 27 27 13  FF FF FF FF  
      [   33.951570] RTW: 0x020: FF FF 2D 2D  2D 2D 2D 2D  2D 2D 2D 2D  2D 2D 2D 2D  
      [   33.951632] RTW: 0x030: 13 FF FF FF  FF FF E0 FF  FF FF 28 28  28 28 28 28  
      [   33.951671] RTW: 0x040: 28 28 28 28  28 02 FF FF  FF FF FF FF  FF FF FF FF  
      [   33.951710] RTW: 0x050: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      [   33.951749] RTW: 0x060: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      [   33.951788] RTW: 0x070: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      [   33.951827] RTW: 0x080: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      [   33.951866] RTW: 0x090: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      [   33.951904] RTW: 0x0A0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      [   33.951943] RTW: 0x0B0: FF FF FF FF  FF FF FF FF  7F 1A 1B 00  FF FF FF FF  
      [   33.951982] RTW: 0x0C0: FF 22 00 00  00 E6 00 00  00 FF 26 FF  FF FF FF FF  
      [   33.952179] RTW: 0x0D0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      [   33.952291] RTW: 0x0E0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      [   33.952331] RTW: 0x0F0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      [   33.952369] RTW: 0x100: DA 0B 20 C8  C3 46 02 00  C0 CA B3 A4  EC 09 03 52  
      [   33.952408] RTW: 0x110: 65 61 6C 74  65 6B 0E 03  38 30 32 2E  31 31 61 63  
      [   33.952447] RTW: 0x120: 20 4E 49 43  08 03 31 32  33 34 35 36  FF FF FF FF  
      [   33.952486] RTW: 0x130: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      [   33.952533] RTW: 0x140: FF FF FF FF  00 00 31 0F  FF FF FF FF  FF FF FF FF  
      [   33.952602] RTW: 0x150: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      [   33.952641] RTW: 0x160: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      [   33.952691] RTW: 0x170: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      [   33.952730] RTW: 0x180: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      [   33.952769] RTW: 0x190: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      [   33.952808] RTW: 0x1A0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      [   33.952847] RTW: 0x1B0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      [   33.952885] RTW: 0x1C0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      [   33.952924] RTW: 0x1D0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      [   33.952963] RTW: 0x1E0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      [   33.953002] RTW: 0x1F0: FF FF FF FF  FF FF FF FF  FF FF FF FF  FF FF FF FF  
      [   33.953329] RTW: hal_com_config_channel_plan chplan:0x7F
      [   34.184253] RTW: [RF_PATH] ver_id.RF_TYPE:RF_1T1R
      [   34.184263] RTW: [RF_PATH] HALSPEC's rf_reg_trx_path_bmp:0x11, rf_reg_path_avail_num:1, max_tx_cnt:1
      [   34.184269] RTW: [RF_PATH] PG's trx_path_bmp:0x00, max_tx_cnt:0
      [   34.184276] RTW: [RF_PATH] Registry's trx_path_bmp:0x00, tx_path_lmt:0, rx_path_lmt:0
      [   34.184283] RTW: [RF_PATH] HALDATA's trx_path_bmp:0x11, max_tx_cnt:1
      [   34.184288] RTW: [RF_PATH] HALDATA's rf_type:RF_1T1R, NumTotalRFPath:1
      [   34.184296] RTW: [TRX_Nss] HALSPEC - tx_nss:1, rx_nss:1
      [   34.184301] RTW: [TRX_Nss] Registry - tx_nss:0, rx_nss:0
      [   34.184307] RTW: [TRX_Nss] HALDATA - tx_nss:1, rx_nss:1
      [   34.184315] RTW: txpath=0x1, rxpath=0x1
      [   34.184321] RTW: txpath_1ss:0x1, num:1
      [   34.185543] RTW: rtw_regsty_chk_target_tx_power_valid return _FALSE for band:0, path:0, rs:0, t:-1
      [   34.188733] RTW: rtw_ndev_init(wlan0) if1 mac_addr=00:c0:ca:b3:a4:ec
      [   35.507557] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
      
      posted in Ask your questions right here!
      Alex KushleyevA
      Alex Kushleyev