Outline

Kevin's main.py does (in order as read thru the file):

• Sets up each submodule, checking for errors, logging them
• Starts up a webserver
• Prepares USB conns (for scale)
• resources_dir - No idea
• get_cli_arguements - Prepares CLI invocation
• enumerate_images - Checks for existing images
• lookup_sku - Polls database for required SKU/Item data
• handler_hid - No idea
• handler_shutdown - Handles shutdowns gracefully
• capture_image - Captures images from specified cam to specified destination
• get_cameras - Enumerates the connected cameras
• get_scale - Enumerates the scale as connected
• _tare_scale - self explanitory
• capture_weight - async lookup/display to webpage the active scale load
• record - create json string of sku, metadata, path, cameras, pool (pool?)
• Classes for:
  • Broadcast Handler
  • RecordHandler
  • SearchHandler
  • ScaleHandler
  • RestartHandler

---

By Dave:

camstationv2.py - The first pass to recreate the functionality of main.py

CAMERA - Camdata.py

Successfully connects to and captures using the DSLR

* ToDo: Streamline the enumeration of cameras
* ToDo: Add CSI PiCamera interface for under-view

SCALE - Test series

Working on recreating the main.py functionality using the "test" code. We've replaced the USB HID interface with a serial interface to the Sparkfun Openscale load-scale interface. I have testindex reading and reporting back the scale data when "testserver.py" is run

• testindex.html
• testserver.py
• testerialworker.py
• testmain.js

SCANNER - to do

LOOKUP - to do

Next to do

1. Well, if you wanna do a small task, go and integrate Picam into the camera module
2. Bigger task - write/adapt the database lookup
3. Start figuring out the JSON data assembly and how you wanna record the information.