@taiwohazeez You should start here: https://docs.modalai.com/voxl-developer-bootcamp/

@taiwohazeez The forum is the quickest path to the technical team. There are a lot of forum posts where the engineering team has responded, but you haven't. Can you please follow up there so we can resolve the issues?

Each of the drones is flight tested for 20 minutes prior to shipping, so we're confident it was all working when we shipped. Once changes are made we can help debug, but it's not infinitely configurable so it's important to follow the documentation and ask questions about the best approach.

@voxltester And, in general, for all software engineers out there here is a helpful tip. ModalAI is not affiliated with Anthropic in any way but I do want to highlight their Claude Code tool. It can really help you not just write code, but to understand code that is already there. So, for example, in this post there is a question about how the -b option is parsed. It's a bit complicated how all of the pieces fit together but if you were to ask Claude this question: "I'm using the device driver in the file lightware_laser_i2c.cpp. I was told that the LightwareLaser class can take the command line option -b to specify the i2c bus number using the start command. Can you show me where in the code the -b option is parsed?". Claude will then give you this answer:

The -b option is not parsed directly in this file. Looking at the code:

  At line 450, the custom option parsing only handles -R for rotation:
  while ((ch = cli.getOpt(argc, argv, "R:")) != EOF) {
      switch (ch) {
      case 'R':
          cli.rotation = (Rotation)atoi(cli.optArg());
          break;
      }
  }

  The -b option (for I2C bus number) is handled automatically by the BusCLIArguments class, which is instantiated at line 445:
  BusCLIArguments cli{true, false};

  This class is included from <px4_platform_common/i2c_spi_buses.h> (line 47). The cli.getOpt() method internally processes standard I2C/SPI options like -b (bus), -a (address), etc., before returning custom options like -R to this driver's switch statement.

  If you want to see where -b is actually parsed, you'd need to look at the BusCLIArguments class implementation in the PX4 platform common library:

  src/lib/drivers/device/posix/i2c_spi_buses.cpp
  or
  platforms/common/i2c_spi_buses.cpp

  The PRINT_MODULE_USAGE_PARAMS_I2C_SPI_DRIVER(true, false) call at line 435 documents that this driver accepts I2C options (including -b), but the actual parsing is abstracted away in the shared bus infrastructure.

@voxltester Yes, bus 4 corresponds to pins 7 and 8 on J19. I would put an oscilloscope on the data pin and see if you detect any activity when you start the driver to verify.

@voxltester I tried to explain this in one of my previous responses. Let me add more detail. lightware_laser_i2c.cpp is C++ code. The class LightwareLaser has a couple of base classes. One of them is I2CSPIDriver, so it "inherits" the functionality of that class. That class is implemented in i2c_spi_buses.cpp. It uses BusCLIArguments to parse the command line options. That's where the -b option is dealt with.

@sansoy Can you please provide some details on your setup? What hardware are you using? Which software are you using (including versions)?

@Aaky After that much use it could very well be ESD damage. It seems unlikely we would be able to fix via RMA.

@qubotics-admin Hi, we sell all of those components for companies to integrate into their products.

The Flir Hadron adapter (MDK-M0202-1-00) can be requested by reaching out to sales at https://modalai.com/contact

The rest of the components should be available to purchase at modalai.com

@JoonaR Hi Joona, the DP should work to drive an HDMI projector with the appropriate adapter. This adapter has been tested to work: https://www.amazon.com/Cable-Matters-48Gbps-Adapter-Supporting/dp/B08MSWMXT4?th=1

@Piyush-Singh Have you tried voxl-camera-server -d0 found here https://docs.modalai.com/voxl-camera-server/#troubleshooting ?

You cannot plug in cameras arbitrarily, you'll need to use one of the supported camera configurations: https://docs.modalai.com/voxl2-camera-configs/