The Pin Outs
- 
					
					
					
					
 Hey All, 
 The Pin Outs are here (edited 08/11/16, updated pinouts)Enjoy! LoPy Pin Out 
 https://www.pycom.io/wp-content/uploads/2016/11/lopy_pinout.pdfWiPy Pin Out 
 https://www.pycom.io/wp-content/uploads/2016/11/wipy_pinout.pdfExpansion Board Pin Out 
 https://www.pycom.io/wp-content/uploads/2016/11/expansion_v02_pinout.pdf
 
- 
					
					
					
					
 @babjerke hi there, I updated the expansion board again yesterday. Should be working now. Let me know if you struggle or I have missed an area. ;-) 
 
- 
					
					
					
					
 Nice to see the pinouts for the LoPy module but the link for the Expansion Board is not working! 
 
- 
					
					
					
					
 Updated 08.11.16 LoPy Pin Out 
 https://www.pycom.io/wp-content/uploads/2016/11/lopy_pinout.pdfWiPy Pin Out 
 https://www.pycom.io/wp-content/uploads/2016/11/wipy_pinout.pdfExpansion Board Pin Out 
 https://www.pycom.io/wp-content/uploads/2016/11/expansion_v02_pinout.pdf
 
- 
					
					
					
					
 @pighixxx 
 Thanks a lot for changes!Michal 
 
- 
					
					
					
					
 @RicoLA said in The Pin Outs: @pighixxx WONDERFUL !! thanks a lot :-) Thanks! 
 I sent PDF's to Pycom. Look forward to publish them
 
- 
					
					
					
					
 @pighixxx WONDERFUL !! thanks a lot :-) 
 
- 
					
					
					
					
 Last pinouts and quick reference cards: 
 LoPy
  
 Quick Reference
  WiPy 
  
 Quick Reference
  
 
- 
					
					
					
					
 @Xykon yes that's to what I was referring to :-) yet given this new "official" Lopy pinout pdf file, there are plenty of other possibilities with theses multipurpose GPIOs . the problem is with alternate functions attached to them, we need to know precisely who is who . e.g. for I2C we need to know either the I2C bus number (like in : i2c = I2C(0, I2C.MASTER, baudrate=100000) ) , or the the SCL pin and SDA pin numbers that we can NOT mix up as we want. (as in i2c = I2C(scl=Pin(5), sda=Pin(4), freq=100000) ) cheers 
 
- 
					
					
					
					
 @Xykon 
 Thanks a lot, your schema is much more intuitive for me. Will you make a Wipy version too?
 
- 
					
					
					
					
 @pighixxx 
 That's OK. What I am complaining about is the fact, that I can easily see the pin usage in Wipy 1.0 layout:
 https://raw.githubusercontent.com/wipy/wipy/master/docs/PinOUT.pngbut I struggle to find the same level of information for Wipy 2.0. For example I wasn't able to identify the fact that UART_1 pins are P3 and P4. It was probably caused by the lack of my knowledge (I don't understand properly some of those pin descriptions) but I might not be the only one who will need more intuitive pin out. Michal 
 
- 
					
					
					
					
 You can refer to this until the official documentation is updated :  
 
- 
					
					
					
					
 Hi there, 
 yes same for me ... it's not clear where are located the 'default' I2C pins :-)
 are P9/P10 (GPIO 12/GPIO13) ok when using example code in quickref doc i2c = I2C(0, I2C.MASTER, baudrate=100000) ?thanks 
 Rico
 
- 
					
					
					
					
 @michal 
 I'm working in quick reference cards with only the basic informations.
 Have a nice day,
 
- 
					
					
					
					
 Hi! New pin outs are beautiful from the aesthetic point of view but the description of pins is not very clear to me. I prefered the style used for Wipy 1.0 pin out. For example the UART code in quick reference docs (https://docs.pycom.io/wipy2/2wipy/quickref.html) mentions UART_1 pins P3 and P4 but it I don't see that information in Wipy 2.0 pin out. Best regards Michal 
 
