Skip to content

Latest commit

 

History

History
109 lines (79 loc) · 3.06 KB

README.md

File metadata and controls

109 lines (79 loc) · 3.06 KB

petbuddy-device

Device side code for PetBuddy

  • lua codebase runs on esp-8266
  • Wiki for board: https://github.com/esp8266/esp8266-wiki/wiki
  • using NodeMCU as devkit
  • flowchart file can be opened with draw.io webapp
  • NodeMCU firmware binary/info can be found in the ./fw/ directory

Camera:

  • ov2640 jpeg cam

How to get up and running:

  1. Start ESPlorer by going into the ESPlorer directory and doing:

    sudo java -jar ESPlorer.jar

  2. Connect the NodeMCU (ESP/PetBuddy Device) to your computer via USB

  3. On mac, check that your NodeMCU is detected on the USB. On a terminal, do:

    ioreg -p IOUSB | grep -i cp

    You should see something like this:

    | | +-o CP2102 USB to UART Bridge Controller@14420000 <class AppleUSBDevice, id 0x1002f7bd7, registered, matched, active, busy 0 (458 ms), retain 17>

  4. Go back to ESPlorer.

  5. On the left side there is an "Open File" button, open the main.lua file.

  6. On the top right area of ESPlorer, there is a reload button. Press it. In the dropdown, you should see something like: /dev/cu.SLAB_USBtoUART Make sure that entry is selected.

    If you cannot see the entry, the Silicon Labs drivers for the CP USB <-> UART chip on the nodemcu might not be installed. (eg. it wouldn't work on OSX Sierra without drivers), download the drivers from Silicon Labs' website: https://www.silabs.com/products/development-tools/software/usb-to-uart-bridge-vcp-drivers

    You might also have to play around with the kexts so that silabs driver gets loaded as a kext. Google for more info.

  7. Click the big "Open" button which is underneath the device dropdown. You should see something like:

     PORT OPEN 115200

 Communication with MCU..

  8. Press the "Heap" button at the very bottom on the right pane. You should see something like: Can't autodetect firmware

  9. Press the "Send to ESP" button on the lower left of the screen.

  10. The code should automatically start running. The Petbuddy Wifi should start broadcasting and you should be able to see it in the wifi selection of your phone or macbook.

Servo

In code the servo pwm pin is pin 2. But in the code and the actual board this corresponds to GPIO_4.

The pinout is as follows: D0 = 16 D1 = 5 D2 = 4 D3 = 0 D4 = 2 D5 = 14 D6 = 12 D7 = 13 D8 = 15 D9 = 3 D10 = 1

Virtual python3 environment

Mac OSX ships with python 2.7. We are using python3.

Virtual environments make this really easy:

  1. Go to petbuddy-device repo directory and do: $ virtualenv -p python3 pbd-env

  2. When the last command is done, do: $ source pbd-env/bin/activate

  3. When the last command is done do: $ pip install jupyter

Now the jupyter notebook should run with a python3 kernel

When you are done with doing petbuddy-device stuff, you can do: $ deactivate

This will deactivate the virtual environtmen. Next time when you are making changes make sure to do the original activation command from step 2 above ^^^.