…hine. Then I add a new checkpoint to verify that the firmware correspond to the one we want. I had to remove the declaration of the pin 9 as out in the setup the pytentiostat_firmata.ino to use the board.firmware attribute because with the original it returns None. I don't know if it's a little confusing the result because if the wrong firmata was uploaded into the board it print that the pytenstiostat is connected to the port after telling you that the board is not a pytentiostat.

…inux machine. Then I add a new checkpoint to verify that the firmware correspond to the one we want. I had to remove the declaration of the pin 9 as out in the setup the pytentiostat_firmata.ino to use the board.firmware attribute because with the original it returns None. I don't know if it's a little confusing the result because if the wrong firmata was uploaded into the board it print that the pytenstiostat is connected to the port after telling you that the board is not a pytentiostat."

This reverts commit 0cca2c8.

…hine. Then I add a new checkpoint to verify that the firmware correspond to the one we want. I had to remove the declaration of the pin 9 as out in the setup the pytentiostat_firmata.ino to use the board.firmware attribute because with the original it returns None. I don't know if it's a little confusing the result because if the wrong firmata was uploaded into the board it allows you to run the config file after telling you that the board is not a pytentiostat.

…hine. Then I add a new checkpoint to verify that the firmware correspond to the one we want. I had to remove the declaration of the pin 9 as out in the setup the pytentiostat_firmata.ino to use the board.firmware attribute because with the original it returns None. I don't know if it's a little confusing the result because if the wrong firmata was uploaded into the board it print that the pytenstiostat is connected to the port after telling you that the board is not a pytentiostat.

…inux machine. Then I add a new checkpoint to verify that the firmware correspond to the one we want. I had to remove the declaration of the pin 9 as out in the setup the pytentiostat_firmata.ino to use the board.firmware attribute because with the original it returns None. I don't know if it's a little confusing the result because if the wrong firmata was uploaded into the board it print that the pytenstiostat is connected to the port after telling you that the board is not a pytentiostat."

This reverts commit 0cca2c8.

…hine. Then I add a new checkpoint to verify that the firmware correspond to the one we want. I had to remove the declaration of the pin 9 as out in the setup the pytentiostat_firmata.ino to use the board.firmware attribute because with the original it returns None. I don't know if it's a little confusing the result because if the wrong firmata was uploaded into the board it allows you to run the config file after telling you that the board is not a pytentiostat.

…hine. Then I add a new checkpoint to verify that the firmware correspond to the one we want. At last I change the test_routines.py to recognized the firmware.

…ing_juami

# Conflicts:
#	pytentiostat/routines.py

…hine. Then I add a new checkpoint to verify that the firmware correspond to the one we want. At last I change the test_routines.py to recognized the firmware.

…hine. Then I add a new checkpoint to verify that the firmware correspond to the one we want. At last I change the test_routines.py to recognized the firmware.

…hine. Then I add a new checkpoint to verify that the firmware correspond to the one we want. At last I change the test_routines.py to recognized the firmware.

…hine. Then I add a new checkpoint to verify that the firmware correspond to the one we want. At last I change the test_routines.py to recognized the firmware.

Using the firmware method from the Arduino class you can check
the name of the firmware running in arduino. If the name of the
firmware is not "pytentiostat_firmata.ino" the program halt.

…ing_juami

…hine. Then I add a new checkpoint to verify that the firmware correspond to the one we want. I had to remove the declaration of the pin 9 as out in the setup the pytentiostat_firmata.ino to use the board.firmware attribute because with the original it returns None. I don't know if it's a little confusing the result because if the wrong firmata was uploaded into the board it allows you to run the config file after telling you that the board is not a pytentiostat.

…hine. Then I add a new checkpoint to verify that the firmware correspond to the one we want. At last I change the test_routines.py to recognized the firmware.

…hine. Then I add a new checkpoint to verify that the firmware correspond to the one we want. At last I change the test_routines.py to recognized the firmware.

…hine. Then I add a new checkpoint to verify that the firmware correspond to the one we want. At last I change the test_routines.py to recognized the firmware.

…hine. Then I add a new checkpoint to verify that the firmware correspond to the one we want. At last I change the test_routines.py to recognized the firmware.

…hine. Then I add a new checkpoint to verify that the firmware correspond to the one we want. At last I change the test_routines.py to recognized the firmware.

Messages changed to recognize the possible problems in the startup routine.

Messages changed to standardize the alerts.

Modify the regular expression to recognize only the desired ports