mrbeam / beamos Goto Github PK

it looks like there is a error in the software_update_information.py

2021-04-20 11:11:03,276 - octoprint.plugins.findmymrbeam - INFO - FindMyMrBeam registration: OK - ip4_status: 200, public_ip: 212.114.227.216, ip6_status: 200, public_ip6: 2001:a61:58a:9001:ba27:ebff:fe88:95ff, hostname: MrBeam-5595, local_ips: 192.168.100.193, netconnectd_state: {'ap': False, 'wifi': True, 'wired': False}, internal_modes: []
2021-04-20 11:11:03,280 - octoprint.plugins.softwareupdate - ERROR - Error while retrieving update information from plugin mrbeam
Traceback (most recent call last):
 File "/home/pi/oprint/lib/python2.7/site-packages/octoprint/plugins/softwareupdate/__init__.py", line 111, in _get_configured_checks
  hook_checks = hook()
 File "/home/pi/oprint/local/lib/python2.7/site-packages/octoprint_mrbeam/__init__.py", line 2544, in get_update_information
  return get_update_information(self)
 File "/home/pi/oprint/local/lib/python2.7/site-packages/octoprint_mrbeam/util/log.py", line 83, in wrapped
  ret = f(*a, **kw)
 File "/home/pi/oprint/local/lib/python2.7/site-packages/octoprint_mrbeam/software_update_information.py", line 57, in get_update_information
  _set_info_netconnectd_daemon(plugin, tier, beamos_date),
 File "/home/pi/oprint/local/lib/python2.7/site-packages/octoprint_mrbeam/software_update_information.py", line 193, in _set_info_netconnectd_daemon
  version = get_version_of_pip_module(package_name, pip_command)
NameError: global name 'package_name' is not defined
2021-04-20 11:11:03,291 - octoprint.plugins.softwareupdate - WARNING - Unknown update check type for target netconnectd: <n/a>

Improvements

• Can ship an image with newest software version -> No need to update
• Could start mrb_check automatically
  1. plug in power and ethernet
  2. No usb stick required

Reset stick

• Restart the whole mrb check
• Select specific test to redo (watterott )
• Generate mrb check config file and then mrb_check -c config_file

Watterott

• Reactionary : Create the sticks as the issues are found
• Still need sticks to
• The device series is linked into the device image
• Online check :
  • Is this the latest PROD image available? -> Warning
  • List of allowed images -> If not : Err + stop

GUI / TUI

• Select the local mr beam through a list provided by find.mr-beam
• Select list of checks to run
• Send the list of checks to the selected mr beam and start mrb check again

Network

• BeamOS image large size image
  • Not necessary to have the latest update to create the Mr Beams
  • Only a critical issue is arising
    • They need to download the image (~1hour)
    • they need to re-flash all of the SD cards
  • Do not flash too many cards in advance?
    • Up to watterott to manage supply

Careful

• If it gets added as a migration or a repair device gets flashed, old devices should not run the mrb check
  • Track a file that is already generated on older devices and properly transferred in the backup / apply script

Analysis

• Is the mrb check validation file present?
• mrb_check logs should be on the device.

Failed to refresh the list of images.
Please check your connection to the device.

Last observed with DEV-2021-04-21 on Mr Beam DC (Raspi 3b)
In fact it went off two times now...

Not sure if it's only the first boot though.

https://github.com/mrbeam/BeamOS/blob/mrbeam/TODO.md

mrbeam/OctoPrint-FindMyMrBeam#27
mrbeam/MrBeamLedStrips#22
#29
mrbeam/MrBeamPlugin#1218

OctoPrint diffs (no beta branch)

https://github.com/mrbeam/OctoPrint/commits/mrbeam-buster

Create the devpi.mr-beam.org server and have it contain all of the necessary wheels.

Auto change the hostname of the device if explicited in /etc/mrbeam, and do it before shutdown.

Also

• bring this to the old image (per Mr Beam plugin migration)
• remove logic which changes the hostname from Mr Beam plugin completely.

• on login welcome message

OP does not automatically connect to GRBL

The current netconnectd version shipped on the image only has the "MrBeam-AP" ssid, making it difficult to know which machine we connected to.

The device with the RPI3B+ shuts down immedeatly after releasing the power button

I assume its's the reboot timing issue.

Every Usb stick that provides the software update module must discriminate towards the octopi key in /etc/mrbeam and provide the correct update in these cases.

• please spell beamOS with lowercase b
• please replace Mr Beam GmbH by Mr Beam Lasers GmbH
• please fix serial number (currently it's just 2T)
• please consider that the device might have more than one local IP (Wifi and ethernet or ethernet an AP). Rename to Local IPs and list all (external) local IPs

nice ascii art btw ;-)

Perhaps they can be mounted to the image when building.

Relevant links

https://lab.github.com/githubtraining/github-actions:-publish-to-github-packages
https://docs.github.com/en/packages/guides/using-github-packages-with-github-actions

The Software update manager runs the updates with a simple pip install -U <package> command.

The ~/.pip/pip.conf file would only be added after the update ran.

Can the setup.py be changed to point to a separate server for the update? Keep in mind that the devices only have pip version 9.0 ...

See download_url option for setuptools

https://bitbucket.org/mrbeam/iobeam/pull-requests/69
mrbeam/MrBeamPlugin#1221

SP : 15/8

• oprint2 (py2)

• oprint3 (py3)

• packages

  • octoprint
  • octoprint_mrbeam
  • octoprint_netconnectd
  • netconnectd
  • iobeam
  • mount_manager

• avr_dude

• LED strips server

• mrb_hw_info

• Fix systemd unit files

• mrbeam-2X
  • Creates mrbeam dreamcut values in /etc/mrbeam
• mrbeam-dev
  Prepopulate /etc/mrbeam/ with the latest mr beam model and set the BEAMOS_DEV flag

OctioPrint version is systemwide 'mrbeam2-stable'

https://docs.google.com/document/d/1QSNB3VfGbOz3BhHJKwfiPpVaE32lHU6CXk0aqPaw2Ts/edit

Tested on https://github.com/mrbeam/beamOS/actions/runs/751842829

The idea:

• Stable images pull from latest release
• Dev images pull from latest commit

@amrsoll @khaledsherkawi @Gallore

Contents:

• Modules requested
  • lnav
  • exfat-utils
  • ntfs-3g
  • bindfs
  • lsof
• Python packages requested
  • psutil
• other
  • bitte in /boot/config.txt einfügen: dtparam=spi=on (SPI Treiber laden für LEDs spreading)
• bash history:
  • iobeamcli (various things like: fan off, fan_dynamic_data, ...)
  • vcgencmd measure_temp
  • i2cdetect -y 1
  • sudo nano /etc/mrbeam
  • nano ~/.octoprint/config.yaml

1. needs to be created automatically (including model, serial, hostname)
2. use nicer image fingerprint (eg: "PROD-2021-03-19")
3. make /etc/mrbeam writeable for everyone. (my point is convenience from the terminal and some user space processes are going to write there as well in the future.)
4. Is it "the only source of truth" and all other file follow the values in here? (hostname?)

• iobeam new logfile location

we need to define when this is set.

fine tune the new image

bash history:

• i2cdetect -y 1
• vcgencmd measure_temp
• 'iobeamcli'
• 'iobeamcli -c fan off'
• 'iobeamcli -c fan on 100'
• i2cset -y 1 0x2a 0x81 0x64 //Exhaust 100%
• i2cset -y 1 0x2a 0x81 0x00 //Exhaust off
• i2cset -y 1 0x2c 0x82 0x64 //Compressor 200 mbar
• i2cset -y 1 0x2c 0x82 0x00 //Compressor off
• i2cset -y 1 0x2c 0x87 0x64 //Ozon 100 PPM
• i2cset -y 1 0x2c 0x87 0x00 //Ozon off
• sudo reboot now

aliases:

• alias ..="cd .."
• alias ...="cd ../.."
• alias ll="ls -l"
• alias l="ls -al"

data on login screen

• serial number
• image version
• plugin version
• current OP state (idle, slicing, printing - I know, probably hard to get this information…)
• iobeam details (lid open/closd, i2c devices, …)

If the device series is given in /etc/mrbeam (e.g. 2T), then generate the appropriate serial number (e.g. 00000000XXXXXXXX-2T) on first boot.

Can't be sure atm since I can't ssh into current image. but I do not get any reaction if I plug in one of our usb sticks (tested with support stick)