Hello,
Do you plan to make your board supported by circuitpython?
As this fork of micropython is already supporting boards with atsamd51, it couldn’t be very difficult to add this board.
Could you make a pull request to add support for your board in circuitpython ?
Thanks
Ob.
Forget circuitpython, our ArduPy will make you feel the magic of programming again.
http://wiki.seeedstudio.com/Wio-Terminal-ArduPy/
@olivier-boesch
Thanks baozhu but I won’t. Circuitpython seems far more convenient to my needs and it just makes me feel that magic.
That’s a pity that you don’t want to provide support with circuitpython as it could make you sell more hardware.
I will just cancel my pre order of wio terminal.
That is a more than odd response tbh.
Circuitpython already has far more drivers than MicroPython and has a large amount of graphics related libraries that are perfect for hardware like the Wio Terminal.
Mass Storage based programming is also far more convenient. I really hope you reconsider that position.
Actually whether this can be supported or not depends on Adafruit’s attitude. They simply need to add a pin map and usb vid/pid in the code to support it. However, this information is completely open source. @timonsku @olivier-boesch
Hi hi, I’m Scott, the lead for CircuitPython. Me and others are paid by Adafruit to work full-time on CircuitPython.
We love to see non-Adafruit boards supported in CircuitPython. (There are already many.) We will always review pull requests for any addition to CircuitPython including non-Adafruit boards. Those of us paid by Adafruit will only provide limited support for non-Adafruit boards though. It is expected that the board manufacturer is the main contact for support.
In this case it means we won’t add the Wio Terminal ourselves but would happily merge a PR for it.
Adafruit provides USB PIDs to hobby boards for use in CircuitPython but expects companies who sell boards to have a USB VID of their own that they can use in CircuitPython.
ArduPy looks neat and I am curious to see what parts people want to integrate back into CircuitPython. As I said before, we’re always happy to review PRs.
Suggest LoRa can be DASH7, SX1262 can be used as a DASH7 device with a specific firmware flashed. I prefer DASH7 to LoRa due to the industry advantages of DASH7.
If possible, there could be an external EEPROM to extend the program, while an AI helper could be integrated. That will be a powerful ML device for IoT.
How about adding 4G/5G support to the Wio so that the device can be used anywhere?
More ideas may occur to me, but I think the features I mentioned above could make this approaching to an advanced IoT terminal for both hobbyists and professionals.
@tannewt
Hi Scott, it is really nice to have you here. We really appreciate what circuit python has done and hopefully we will soon have PR regarding wio terminal for circuit python. Keeping it up.
@ONLYA
You’re absolutely right, ArduPy was designed with the intention that he would be able to use the product in a professional way.
Thanks Scott, this is Eric Pan from Seeed. We appreicate the openess!
Ardupy is taking quite a different approach and serving different purposes more towards industrial tool. We will surely consider circuit python as users are now asking for it. Cheers!
Thanks @Baozhu and @ESP! Happy be here. Feel free to email me scott@adafruit.com if you ever want to have private discussions.
I’ll add this forum to my rotation so I can help answer any CircuitPython questions I see.
@olivier-boesch Hi Olivier, this is Elaine from Seeed. We will support CircuitPython by June and we will keep updating here, stay tuned with us 
I need
Chassis - CAN Bus: RJ45, OBD-II, Screw Terminal
Is this available for purchase? What is the alternative to apply external power to the Wii Terminal to make it mobile?
I have a project that needs accurate timer so I would like an accurate RTC with an interrupt such as DS3231 to fit in the enclosure. Needs 3v SDA SCL and IO for the square wave
Other requests:
GPS module for position and timing. Needs serial, power and IO for pps signal.
Small plugs to cover up unused ports.
Could the battery chassis have an alternative deeper back to accommodate a 40 pin breakout and user extension boards?
Thanks.
This type of gpio extension may work with a deeper back or additional case spacer to allow users to add their own extensions to the battery chassis.
Cheers
Ted
I noticed a 1 mm misalignment between the Wio Terminal and the battery extension, both vertically and horizontally.
I’ve just read the warning about the Wio Terminal Battery Chassis.
- The charge current will up to 1.5A, which may reduce battery life or cause other issues.
We are optimizing the design of the new version (the estimated release date is unavailable yet), and we recommend the new version if you are a beginner.
*Please contact us for tech support or exchange if you meet any problem during the usage of this version.
For the revision, do you consider adding a gauge controller as I suggested at my post Wio Terminal Chassis Battery monitoring?
I’d also love to have a native SWD connector for debugging, as the access to the SWDIO and SWCLK pads are far from obvious.
Thank you!
“Chassis - CAN Bus: RJ45, OBD-II, Screw Terminal”
+1
This would be extra awesome if it was canfd (atsamc21) and would be very popular in the automotive tuning would.
Alternatively a proto chassis with case would allow custom boards easily.
Thinking about it even more It’s a shame the wio terminal isn’t available with samE51/54
as it could support canbus out of the box.
Maybe for v2? 
We will soon launch corresponding CAN Bus fd software and hardware.
It would be nice to have the ability to turn off the yellow and red LEDs through code, if that’s not already possible. Unfortunately this battery is not very useful over the long term if you can’t reduce the amount of power for projects that require lower power.