Hi.
I was reading this:
https://docs.modalai.com/voxl-datasheets-connectors/#j13-expansion-b2b-connection
and wanted to make sure I understood corrrectly:
There are 2 I2C ports/buses available on this connector (J13 - B2B) ?
If so, can one be used as an I2C master/host, and the other as a slave (for use with external master) ?

Also, I haven't seen any information about PWM outputs. Does the VOXL have any hardware PWM outputs? If so, on which pins?

Thanks.

Hello.
I noticed that the /mnt/sdcard/ and /sdcard/ mounts exists even when the sdcard is not inserted into the VOXL.
This came up when the root mount (eMMC) got full for some odd reason. I then noticed that the sdcard on the VOXL had popped out and my docker was writing stuff to /sdcard. This filled up the eMMC. This situation is a bit dangerous, because while you think you are writing to the sdcard, in fact you are writing to the eMMC.

I would like to know if there is a way to disable these mounts if the sdcard isn't inserted or happened to pop out (the spring on the sdcard holder of the VOXL is kind of weak).

Thanks

Hi.
We have a few VOXLs and we've come by some intermittent Wifi connection issues, when working in "station" mode:
Sometimes the VOXL will connect just fine to the Wifi router (TP-Link Archer VR600), and sometimes it simply doesn't. Even after running voxl-wifi with the correct credentials several times, it doesn't always work. This has been tested on multiple VOXLs, all running system image 3.3.0. We have also tested this using different routers of the exact same model - same behaviour. Wifi antennas are in place of course, and 5Ghz wifi is disabled on the router (only using 2.4Ghz).

Rebooting the router doesn't help either. We do not have any problems connecting our laptops to the router, nor do we see this behaviour with other various SBCs (NanoPi/Raspberry Pi etc..). The VOXLs work fine in AP mode and we are able to connect to them separately, but its very inconvenient.

My question is:

1. Is this a known issue? If so, how do we work around it ?
2. Is there any way to "debug" wifi issues on the VOXL ? We haven't seen anything special on journalctl.

Thanks.

@Chad-Sweet
I'm trying to read some sensor data using UART/I2C, from within a Docker container.

I will look into libmodal_pipe , thanks.

Hi,
I understand that currently using libvoxl_io.so from Docker is not supported.

I wanted to know if it's on your road map, and if so, when can we expect Docker support for this?

If not, I would like to know what it would take to port it to Docker ?

Thanks

OK.
So what about SPI or UART on the B2B connector?
Are they available and supported in OS/SW? If so, what modes does the SPI support (master/slave) ?
What baudrate does the UART support?

Thanks.

@Eric-Katzfey Thanks for the reply.
Is this a hardware limitation (i2c ports being host only) ?
Are there any plans to enable i2c in slave mode on the VOXL ?

Thanks for your reply.
Yeah, I was planning on breaking out the B2B connector to a PCB for dev purposes.

So I shouldn't have any problems using the two I2C ports (on as master and other as slave) on the B2B, correct?

Also, if I want to do SW based PWM, is there any GPIO pin on the B2B that you would recommend using, or can I choose any free GPIO pin ?

Hi.
I was reading this:
https://docs.modalai.com/voxl-datasheets-connectors/#j13-expansion-b2b-connection
and wanted to make sure I understood corrrectly:
There are 2 I2C ports/buses available on this connector (J13 - B2B) ?
If so, can one be used as an I2C master/host, and the other as a slave (for use with external master) ?

Also, I haven't seen any information about PWM outputs. Does the VOXL have any hardware PWM outputs? If so, on which pins?

Thanks.