Sorry to be so blunt, but:
- The code.circuitmess.com site doesn’t provide a project page for clockstar v2, only for v1
- Doing some poking around in the code for the clockstar v1 webpage, it appears to specifically filter out the v2 chip from the USB connection script
- There are a number of posts here and in the support page asking for help connecting v2 to the web IDE, and none of them have a resolution from CircuitMess
Please do not ask me to send an email to contact@circuitmess.com – you can instead reply to the one I already sent! 
First of all, please don’t apologize for being blunt, we truly appreciate the clear and direct feedback. It helps us identify exactly where our documentation or software is falling short, and in this case, you’ve pointed out some very valid concerns.
To address your points specifically:
-
Missing Examples: You are correct that there isn’t currently a dedicated copy of the Clockstar v1 examples for the v2 revision on the project page. This was a mistake on our part, and we are working to include these examples for Clockstar v2 officially. In the meantime, if you manually copy the v1 code examples into a new v2 project in CircuitBlocks, the code will function perfectly.
-
USB Filtering & Hardware Differences: The reason you noticed a filter in the connection script is due to a significant hardware upgrade. The original Clockstar used a standard ESP32, whereas the v2 revision features a much more powerful ESP32-S3 SoC (System on a Chip). Because of this change in processors, the firmware structures are different. We implemented the USB interface check to ensure that the correct firmware is always flashed to the correct chip to prevent any compatibility issues.
We are currently updating the web IDE to make this transition seamless for v2 users so that you don’t have to “poke around” to get it working.
Thank you for your patience and for your investigative work, it’s exactly this kind of community feedback that helps us squash these bugs.
1 Like