Sorry, I misunderstood. I can only tell you that the Pygate mounting hole spacing is the same as the Expansionboard 3.0's spacing. We provide that here: https://docs.pycom.io/gitbook/assets/specsheets/Pycom_002_Specsheets_Pygate_v1.pdf in section 12. I will work on getting the Expansionboard spacing out there on its own page!

You do not need 0.5 ppm at least not for 125/250/500 kHz bandwidth.

Can you please first try another firmware update (we have released 1.10.2.b1). If that doesn't help please try to format the internal flash: import os; os.mkfs('/flash') If that still doesn't help please email support@pycom.io

@tcb Thank you!

The same USB cable works fine with all other LoPys so I don't think it is a problem related to the cables nor the USB ports...

@littlebat It said max current 40 mA in the maximum ratings sections, but I myself did not trust that anyhow. Even if, the output levels then are somewhat off GND/Vcc. So 12 mA sounds much more convenient.

@jmarcelino exactly if someone have acces to device it can break it in really simpler manner than do some supported by some device reset features ;-) @lawrence Think about as @jmarcelino show sample, hammer, drill i can add more e.g.: water, remove power source, electric shock, put into metal case...

I am looking the shematic of the expansion board forWipy 2.0. Somebody can help me ?

@daniel I think the 2.8uA of video is due to a little part of current drawn from pullup resistor of serial connection instead from the power supply. Without serial connection I think the current rise up 6uA (5uA for ESP32, like in Espressif documentation, and 1uA for LoRa module in sleep mode). what do you think about it? regards Federico

The ESP32 chip supports native Ethernet through an external RMII chip (for example the popular LAN8720, breakouts can be bought for $3) I tested this on another ESP32 about a week ago! Works really well. https://twitter.com/jmarcelino/status/843256681807171585 It is still only on the C-interface side (ESP-IDF) but no doubt it will be ported to MicroPython. There is an issue with pin assignments on the LoPy and SiPy, one of the necessary (non-changeable) pins conflicts with the communications chip in those. But should work on the WiPy. (I don't have one to test...) That said if you have PoE it generally means you have ample power available so the board would be competing with the $10 Pis / OpenWRT etc of this world which offer full-fat Python at very high speeds and ample interfacing options. Other than being smaller I don't see how a major market could come from competing with those.

@danielm @daniel I've uploaded my own Eagle library for the W01 WiPy OEM chip here Check yourself that you are happy that the libraries match the specs and are fit for your purposes. If the W01 library proves useful to people and there's enough interest then I could create and share an Eagle library for the L01 too.

@jmarcelino seeing the results of the poll we will continue having both options available ;-)

@mo-seph said in Hardware improvement suggestions: In addition to what other said: having the analogue reference voltage available would be really helpful, especially as it is a strange one (1.1v). Yes, for application where a reference voltage is required it would be good to have it, even if that will create new trouble. But .. I did not find an esp32 pin in the specs. more ground pins would also be good Yes, solid GND posts on either side a jumper for firmware boot mode on the expansion board would surely be useful - Yes, or better a switch. That would sort out some confusion. the boxes/bags that they come in should really take a lopy and an expansion board, as that's how they mostly get used In the box I got both a lopy and the expansion fixes. so no complaint.