Petoi Camp

I'm having a strange issue with my BiBoard V1.0- when I plug it into my computer, it is making a strange low pitched buzzing noise, but still makes the usual beeps indicating it is connected to the computer. My computer is not recognizing when I plug it in, and type ls /dev/ttyUSB* I've tested on a desktop as well as my laptop, and have the same error. But when I connect a different BiBoard V0_2, I do not have the error, and my computer is able to recognize the connection. Is this a faulty hardware issue? Also, when I turn the faulty board on and don't have it connected to a computer, I am able to control the robot with my raspberry pi connected to the tx2 and rx2 ports.

The documentation for BiBoard programming says to use Arduino 1.x and ESP SDK 2.0.12. Arduino: The v2.x IDE is much, much better than the v1.x. Keeping around an old, lesser version for programming BiBoard is not ideal. This could make sense in an industry environment where legacy equipment is being maintained, but in a learning environment it's not great as it's one step forward (using the Bittle!), two steps back (hassling with multiple versions of an IDE, working around already solved problems, etc...). If Petoi intends to continue on into the future, and it surely seems committed to that!-- then it is inconceivable that it remain on Arduino 1.x now that Arduino 2.x is released, stable, and widely deployed. I understand there's a technical reason for that, but AFAIK OpenCat is the only ESP32 project to be stuck like this so perhaps there's hope a solution can be found. ESP SDK: Arduino IDE does not support multiple installed versions AND it always wants to update to the latest version. Since there are some breakages between Espressif sdk v2 and sdk v3, it's a big deal to have to continually uninstall/reinstall SDK versions. Again, this certainly isn't ideal for a learning environment. It's a lot of instructor overhead to have to support both SDKs, as the student absolutely need to return to v3 for everything else they do. And 2.0.12 isn't even the last version of sdk v2, that's 2.0.17. After watching students use Bittles, both those problems seem like they are high priority and need addressing much sooner than later. These problems are real turn-offs, and they don't have to be. None of us learn anything of any value by hassling with them, and the hours lost cannot be recovered.

I have a few Bittles with BiBoards and would like to trigger skills from a Matlab/Julia/Python script using a wifi connection. Specifically, I want to be able to tell the robot to walk forward, turn left, turn right, and stop (although in general I would like to be able simply to trigger generic skills programmatically). I cannot yet see where this control is documented (although I did find https://docs.petoi.com/apis/serial-protocol for documenting instructions emitted over a serial cable). Obviously it's possible, as the app works for commanding the robot! Anyone could point to some documentation or post a working code sample?