@danielm Hi, Great points! There will be 2 functions: Two pins will be for power and 4 pins (universal inputs/outputs with digital/analogue capabilities) so that you can connect different types of sensors and actuators. Indeed we will ensure no shorting can take place. The PyGo will in any event have such a circuitry protection built in. Best wishes Fred

@bettina said in Can I use the PyGo on the Moon?: We’re also thinking of making some of the pins available on the PyGo device itself (whilst still retaining its IP67 properties)… I am glad to hear this. By implementing these pins the PyGo will become very interesting platform for wearable products for which using Enterprise cradle would be impractical. Please make sure that: it will be possible to power external circuitry from PyGo (and vice-versa?) it will be possible to init UART, I2C or SPI bus on available pins it will be possible to use of-the-shelf mating connector on the host device In my opinion it is also important that to find a way how to fix PyGo onto the host device without any structures required on the housing of the host device which would be too difficult to manufacture (mold, CNC-machine, 3D-print). Maybe magnets?

Great to see : "STRETCH GOAL 1 At €100,000 funding we'll create the Enterprise Cradle and you'll have the opportunity to add it to your pledge for €14.95." Before it was at EUR500,000. I think that many Pycom users are interested to use PyGo1/2 with Enterprise Cradle, so now it is more feasible.

@bettina Having exposed pins/pads available directly on PyGo would allow to use PyGo as a platform for wearables which could be extended via different peripheral and interfaces - e.g. NFC, barcode reader, etc. The cradle is not a solution for these use-cases. Another approach might be to offer "OEM" PyGo which could interface with custom PCB designed by developer. It could be just the PyGo PCB or a PCB with one side of housing (with touchscreen display). The other side would be designed by developer depending on custom circuits/PCB. I am looking forward for F01 to be released. Is it going to use the same pinout of current OEM modules? What about module size? Is it going to be bigger? I would be grateful for more details as we are currently developing new product which might significantly benefit from F01.

Is this available for direct purchase?

@Martinnn i guess they also included the esp32 community and the micro python community. although they didn't use the plural form

Hi @co_buckfast, You could do this with Pygo (the actual device from Pylife system). If you struct.pack you data as timestamp, latitude, longitude 4B each * 3 = 12Bytes per record; there are 4MB available for user. So @30 sec update rate (I guess it's enough), 2 hours are 120 data records, so just 2.9 KB. This could also be quickly prototyped with any Wipy/Lopy/Fipy + Pytrack, battery and IP67 case. Downloading the data could be done over FTP/Wifi.