@Benjamin-Mirad-Gurini there are plenty, the most obvious being the the Pysense has additional sensors (accelerometer, temperature, humidity etc.) which the expansion board doesn’t have, and conversely the expansion board gives easy access to all pins and has a few jumpers.

Depending on which hardware version of the Pysense you're using, you should load the correct pycoproc file. You can find the latest versions of the file here: https://github.com/pycom/pycom-libraries/tree/master/shields/lib pycoproc_2.py is for Pysense v2.0 X, where pycoproc_1.py is for Pysense 1. This also changes the initialisation argument. For Pysense 1, you should put py = Pycoproc(Pycoproc.PYSENSE), whereas Pycoproc 2 does not require an argument To get a working example, you can load one of the zip files from here: https://github.com/pycom/pycom-libraries/releases/tag/v2.0.0 for the correct board version

@Chandan-Verma see https://forum.pycom.io/topic/6963/pytrack-s-accelerometer-sampling-rate/4 for a discussion on the topic.

@Filisia-Melissari With the pysense the pycom updater will switch the FiPy to download mode. (assuming you mean bootloader mode). besides that, you can always force bootloader mode by connecting P2 to GND and pushing the reset button on the FiPy. P2 is available on the external IO header of PySense, the middle pin in the row with the square pin, or at the FiPy itself.

I must have totally missed your message. I posted the firmwares on the forum some time ago for a different user in your situation, but now we have the latest firmwares published in the documentation: https://docs.pycom.io/updatefirmware/expansionboard/ Best, Gijs

The most common issue here is using a USB charging cable that does not support a communication link. Make sure you have a USB cable with all conductors present :-) Next to that you can check the device manager to see if the COM port is created correctly, sometimes (rarely) Windows will have driver issues where the board gets assigned the wrong driver. Let me know! Gijs

@jcaron Thanks, I will keep that in mind !

You could look for NVRAM here: https://docs.pycom.io/firmwareapi/pycom/pycom.html

@misterlisty you already asked the same question in January.

Same topic: https://forum.pycom.io/topic/2469/easy-way-to-tell-what-expansion-board-is-in-use Here's a method to create a generic exp. board object: from pycoproc import Pycoproc from pysense import Pysense from pytrack import Pytrack # create exp board object using unknown board type pyexp = Pycoproc(1) if pyexp.read_product_id() == 61458: print("Using Pysense") pyexp = Pysense() if pyexp.read_product_id() == 61459: print("Using Pytrack") pyexp = Pytrack() Later on use eg: if pyexp.board_type == pyexp.PYSENSE: si7006 = SI7006A20() Perhaps someone can tell us the id for the Pyscan board.

I ended up using Atom on my windows pc and was able to talk on the port no problem. I'm not sure why the port was closed on the fedora pc. Hopefully this helps someone in their setup.

@robert-hh ah ok, thank you for explaining. so I set it to 3.28 V and I am on the safe side ;) thanks

@catalin Is it possible the pins of the external io header on the pysense are reversed in the online datasheet ? Pins 3 and 4 are reversed ? or the names are confusing ? For sure: Pin 4(ext io header) is coming from the voltage regulator.(5pins - pin5) ----- is called 3V3_Pymodule online. Pin 3(ext io header) is coming from FiPy 3V3 output and goes to the sensors (power). ----- is called 3V3_Sensors online. What is the purpose of control pin 2 PWR_EN (ext io header) ? connected by two resistors to pin GPIO24 I believe. Found some topics in the forum, but no clear answer and/or I'm looking at the wrong topics/datasheet. ( I always start with pycom.io to search for information ) I ask this questions because before buying other boards with that PIC chip, I want to understand the working and be sure not having the same problems again. I still can't imagine that all power (3V-5V) for the mounted module is coming from that PIC16lf1459 ( pin RC2 ). Thanx.

@momentaj When using the pycom uploader 1.15.2, you have tghe option to erase the device on uploading a new firmware image.