irnas / koruza-pi Goto Github PK

Add a function that will blink the green laser, for example 5s on during 60s period and user can specify during what times of the day that happens.

I tried to build koruza-pi and ran into the following issues:

• raspbian versions from jessie onwards do not make use of the watchdog anymore but rely on systemd. The commands have changed, too, breaking the installation routine
• the python cryptography package requires updating setuptools prior to installation

I intend to rewrite the installation routine to work with newer raspbian editions, however I am currently not even able to bring the koruza unit into a working state. Upon startup

• the status LED blinks

• no connection is established to the motor boards

• manually subscribing to the IPC endpoints only yields the watchdog messages, nothing more. Trying to write to the command endpoint results in an error (see below).

• manually stopping all services and setting the LED GPIOs high/low does not result in any LEDs lighting up other than the status LED

  sudo nanocat --req --connect-ipc /tmp/koruza-command.ipc --ascii --data '{"type": "command", "command": "motor_move", "next_x": 150, "next_y": 200, "next_f": 0}'
  {"message": "Motor not present.", "code": 400, "type": "cmd_error"}

Enable zeroconfig access to the unit via http://koruza.local even when there is no DHCP server, for example a direct link between the unit and laptop.

Web interface in koruza-pi/package/koruza/webui/assets/scripts/drivers/motors.js implements hardcoded maximal positions for motors, but should use the ones defined in koruza-pi/package/koruza/config/koruza.conf

Implement a mechanism for storing raw measurements collected every 50ms to SD card. For conserving space, capture/log interval for every variable on the bus should be defined separately, namely:

RX power in mW to be logged with as fast as possible, for others averaging may be suitable.

Support SNMP protocol for reporting link status and information.

I2c bus appears to hang on certain devices after some time. The reset implemented in koruza-gpio appears to be insufficient to power down the motor controller and media converter as only complete device power-cycle fixes the problem.

A possible reason is parasite powering of UniversalUnipolarStepperController through UART interface RX pin and thus a fix for this should be included in the reset.

Device name in settings should change the hostname of the device to whichever one is set and change the dns broadcast, such that it works by .local allowing for multiple units to co-exist on the same network

On the Log in popup, after entering credentials user must click Log in button. Enter key should perform this function as well.

Show the remote RX power value under local RX power value.