Brewblox assistence

BGutterud · June 5, 2019, 7:05pm

The diode diode is “breathing cyan”

Attempted to run the flash command, but got the same result…
pi@raspberrypi:~/brewblox $ brewblox-ctl flash
Please press ENTER when your Spark is connected over USB
The following shell commands will be used:

     docker-compose down
     docker pull brewblox/firmware-flasher:rpi-edge
     docker run -it --rm --privileged brewblox/firmware-flasher:rpi-edge trigger-dfu
     docker run -it --rm --privileged brewblox/firmware-flasher:rpi-edge flash

Press ENTER to continue, Ctrl+C to cancel

Running command:
docker-compose down

Removing network brewblox_default
WARNING: Network brewblox_default not found.

Running command:
docker pull brewblox/firmware-flasher:rpi-edge

rpi-edge: Pulling from brewblox/firmware-flasher
Digest: sha256:48c3249f92746dc195dc3f5c09222735ec5c24b1724af1f227cb4aba9ecaf7c6
Status: Image is up to date for brewblox/firmware-flasher:rpi-edge

Running command:
docker run -it --rm --privileged brewblox/firmware-flasher:rpi-edge trigger-dfu

Traceback (most recent call last):
File “/usr/local/bin/brewblox-ctl”, line 11, in
sys.exit(main())
File “/usr/local/lib/python3.5/dist-packages/brewblox_ctl/main.py”, line 81, in main
cli()
File “/usr/local/lib/python3.5/dist-packages/click/core.py”, line 764, in call
return self.main(*args, **kwargs)
File “/usr/local/lib/python3.5/dist-packages/click/core.py”, line 717, in main
rv = self.invoke(ctx)
File “/usr/local/lib/python3.5/dist-packages/click/core.py”, line 1137, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File “/usr/local/lib/python3.5/dist-packages/click/core.py”, line 956, in invoke
return ctx.invoke(self.callback, **ctx.params)
File “/usr/local/lib/python3.5/dist-packages/click/core.py”, line 555, in invoke
return callback(*args, **kwargs)
File “/usr/local/lib/python3.5/dist-packages/brewblox_ctl/commands.py”, line 147, in flash
utils.run_all(shell_commands)
File “/usr/local/lib/python3.5/dist-packages/brewblox_ctl/utils.py”, line 130, in run_all
return [run(cmd) for cmd in shell_cmds]
File “/usr/local/lib/python3.5/dist-packages/brewblox_ctl/utils.py”, line 130, in
return [run(cmd) for cmd in shell_cmds]
File “/usr/local/lib/python3.5/dist-packages/brewblox_ctl/utils.py”, line 124, in run
return check_call(shell_cmd, shell=True, stderr=STDOUT)
File “/usr/lib/python3.5/subprocess.py”, line 271, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command ‘docker run -it --rm --privileged brewblox/firmware-flasher:rpi-edge trigger-dfu’ returned non-zero exit status 139

Bob_Steers · June 5, 2019, 7:50pm

Exit code 139 indicates a segfault. That means it’s likely a problem somewhere in the os / docker / docker image chain.

To force reinstall the image you can run

docker rmi brewblox/firmware-flasher:rpi-edge
brewblox-ctl flash

My guess is that something failed to install correctly, but it may take some digging to find out what.

BGutterud · June 5, 2019, 7:58pm

Hi
It seems to still stop at the same message

pi@raspberrypi:~/brewblox $ docker rmi brewblox/firmware-flasher:rpi-edge
Untagged: brewblox/firmware-flasher:rpi-edge
Untagged: brewblox/firmware-flasher@sha256:48c3249f92746dc195dc3f5c09222735ec5c24b1724af1f227cb4aba9ecaf7c6
Deleted: sha256:c93096b904cc458ee98227e79ac607943e57adbb8172828c7a3fde294590699a
Deleted: sha256:74159037e8dc86cad2a7ec6b11d3637c89af2bac5b67e9bef23509395a637709
Deleted: sha256:b11fa175a20eb86f41d0beb78a91e366f522662ef6b5e78de60e9192420548b8
Deleted: sha256:1b976df1d66e36750f5a09841ef4b7af9e07897807b63fe5947804d88d4e1dfa
Deleted: sha256:8fbdf72154f8cb55fe107d28f3369c15bbf914e08ac229b357f2015ec617e3ad
Deleted: sha256:7610b82a20b2881747c4b26a97e115133df69137f5bd1258ce32cda546e3c575
Deleted: sha256:86808855548141eb47c816eec0f32172bdc2d03ff2aef11808c12f7d9dd25436
Deleted: sha256:457c2774c41e760682991266323217c0cc7efac4e897d84b29effca72a592c12
pi@raspberrypi:~/brewblox $ brewblox-ctl flash
Please press ENTER when your Spark is connected over USB
The following shell commands will be used:

     docker-compose down
     docker pull brewblox/firmware-flasher:rpi-edge
     docker run -it --rm --privileged brewblox/firmware-flasher:rpi-edge trigger-dfu
     docker run -it --rm --privileged brewblox/firmware-flasher:rpi-edge flash

Press ENTER to continue, Ctrl+C to cancel

Running command:
docker-compose down

Stopping brewblox_history_1 … done
Stopping brewblox_spark-one_1 … done
Stopping brewblox_eventbus_1 … done
Stopping brewblox_traefik_1 … done
Stopping brewblox_datastore_1 … done
Stopping brewblox_influx_1 … done
Stopping brewblox_ui_1 … done
Stopping brewblox_mdns_1 … done
Removing brewblox_history_1 … done
Removing brewblox_spark-one_1 … done
Removing brewblox_eventbus_1 … done
Removing brewblox_traefik_1 … done
Removing brewblox_datastore_1 … done
Removing brewblox_influx_1 … done
Removing brewblox_ui_1 … done
Removing brewblox_mdns_1 … done
Removing network brewblox_default

Running command:
docker pull brewblox/firmware-flasher:rpi-edge

rpi-edge: Pulling from brewblox/firmware-flasher
05276f4299f2: Already exists
5657e63df536: Already exists
5d6832deb2d6: Already exists
400b3e2413eb: Already exists
ff56fa8df3d3: Already exists
142413ffe2f4: Already exists
ad61118a6736: Pull complete
0aae0638f5ee: Pull complete
87c22db1e75f: Pull complete
5951894b1cb8: Pull complete
0984608e3f8e: Pull complete
a244b1ea6535: Pull complete
4cf477de76f3: Pull complete
Digest: sha256:48c3249f92746dc195dc3f5c09222735ec5c24b1724af1f227cb4aba9ecaf7c6
Status: Downloaded newer image for brewblox/firmware-flasher:rpi-edge

Running command:
docker run -it --rm --privileged brewblox/firmware-flasher:rpi-edge trigger-dfu

Traceback (most recent call last):
File “/usr/local/bin/brewblox-ctl”, line 11, in
sys.exit(main())
File “/usr/local/lib/python3.5/dist-packages/brewblox_ctl/main.py”, line 81, in main
cli()
File “/usr/local/lib/python3.5/dist-packages/click/core.py”, line 764, in call
return self.main(*args, **kwargs)
File “/usr/local/lib/python3.5/dist-packages/click/core.py”, line 717, in main
rv = self.invoke(ctx)
File “/usr/local/lib/python3.5/dist-packages/click/core.py”, line 1137, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File “/usr/local/lib/python3.5/dist-packages/click/core.py”, line 956, in invoke
return ctx.invoke(self.callback, **ctx.params)
File “/usr/local/lib/python3.5/dist-packages/click/core.py”, line 555, in invoke
return callback(*args, **kwargs)
File “/usr/local/lib/python3.5/dist-packages/brewblox_ctl/commands.py”, line 147, in flash
utils.run_all(shell_commands)
File “/usr/local/lib/python3.5/dist-packages/brewblox_ctl/utils.py”, line 130, in run_all
return [run(cmd) for cmd in shell_cmds]
File “/usr/local/lib/python3.5/dist-packages/brewblox_ctl/utils.py”, line 130, in
return [run(cmd) for cmd in shell_cmds]
File “/usr/local/lib/python3.5/dist-packages/brewblox_ctl/utils.py”, line 124, in run
return check_call(shell_cmd, shell=True, stderr=STDOUT)
File “/usr/lib/python3.5/subprocess.py”, line 271, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command ‘docker run -it --rm --privileged brewblox/firmware-flasher:rpi-edge trigger-dfu’ returned non-zero exit status 139

Bob_Steers · June 5, 2019, 8:18pm

If you manually start the flasher image, does that also trigger an error?

docker run -it --rm brewblox/firmware-flasher:rpi-edge

This should start the image, and then enter a terminal inside it. Your prompt (pi@raspberrypi) should change to root# or something like it.

Type exit and press enter to leave.

If you have another SD card, you could also try running the install guide again on that one. Corrupted SD cards are a common source of errors on the Pi.

BGutterud · June 5, 2019, 9:23pm

Hi
That had no effect…

pi@raspberrypi:~/brewblox $ docker run -it --rm brewblox/firmware-flasher:rpi-edge
pi@raspberrypi:~/brewblox $ sudo docker run -it --rm brewblox/firmware-flasher:rpi-edge
pi@raspberrypi:~/brewblox $ cd…
-bash: cd…: command not found
pi@raspberrypi:~/brewblox $ cd
pi@raspberrypi:~ $ docker run -it --rm brewblox/firmware-flasher:rpi-edge

I will get my hands on a new SD card tomorrow and try a fresh install…

Thank you for the help so far…

Bob_Steers · June 5, 2019, 9:37pm

Looks like it did have an effect: it crashed immediately. Indeed best to try fresh install now.

cschmaltz · June 6, 2019, 5:13pm

I apologize in advance if you guys think this should go under a different thread.

Under my spark service page it has a list of my widgets? for temperature sensors, SSR Expansion Boards, and what I believe are the actuator boards for the ball valves.

Things of clarification needed:
1)The 5x PINs portion of the Sparkv3 I have turned on for my temp sensors, not sure what other function I would need them to perform?
2) One Wire Temp sensors, I have verified the cabling/wiring of all them and they work with constant live updates (within a few seconds)
3) I have 4x 2413 Chip SSR Expansion boards, so I have them cabled up with the latches also for the relays as well.
4) I currently have 7x 2413 Actuators showing up, I am ASSUMING this is still my Valve Control Expansion boards I have installed, but do I make a copy of them on this page to control both the A & B Channels of each. Cause I have 13x Valves total.

I keep reading that control for the valves is still in work, I just haven’t found a very good way to verify everything that shows up on this page and which physical devices it correlates to all the time.

Would anyone be interested in doing a Skype like screen share to help explain. I would love to capture as much of this info so we can get it on the documentation page for others going forward. There is some improved stuff there now obviously, I think the more we can contribute as a community the better it will be for new and old users of the product.

also there doesn’t seem to be a “scroll” option to see all the devices or a way to change the layout (have it adjust with the window size better maybe) ?
TIA

BGutterud · June 6, 2019, 7:48pm

Hi
A new SD card and fresh install solved the issue…
Thanks for your support

Bob_Steers · June 6, 2019, 8:34pm

I’m afraid I’m not available for Skype right now, but I’ll try and answer your questions in order.

I think you refer to the actuator pins? These are digital output pins. For a more comprehensive answer you’ll have to ask Elco.
I’m not sure what your question is here.
Same.
The DS2413 Blocks are discovered, and correspond to your extension boards. You can create more DS2413 Actuator Blocks to use them.

So far the simplest approach to identifying plugged (discovered) blocks is to plug them in 1 by 1, and give them a new name. You can do so in the Block Settings (cog wheel icon, click on “Block Settings”, and then the block name).

The Block relations page already scrolls vertically. We’ll also add horizontal scrolling.
For now you can choose to export the diagram. This will generate a full-sized image.

cschmaltz · June 7, 2019, 2:00pm

correct I have them turned on with connections to additional 1 wire sensors or to the expansion boards. Just wanted to verify that correct I guess.
Just stating current status and that they verify registering on the page.
Wanted to verify this is what should occur with them. The actuator numbers show up underneath them, I’m assuming that means the 2x valves connected to them.

image.png1077×809 57.8 KB
So I guess this is where I am a bit confused:

image.png879×514 33.3 KB

The target block only allows me to select up to 4x options, and the previous part asking about the A,B & Unset, I guess the difference. This is what I was asking if I needed to make a “copy” so I can define both the Channels for the valve control.

I hope this makes sense and I’m supplying enough info.

Bob_Steers · June 7, 2019, 3:16pm

Your Actuator6 ValveA can indeed only control one channel on a DS2413 Block. If you also want to control the other channel, you’ll need to create another actuator.

Your end state would be that you have two DS2413 Actuators per DS2413 Block. This matches your first screenshot (“set by” two different actuators)

frizzo · August 7, 2019, 2:26pm

Had lots of problems with disappearing blocks/dashboards due to browser cache data, especially after restarting brewblox. Had to manually clear the browser cache and things started showing up correctly.

Elco · August 8, 2019, 2:49am

I think we already changed how some of that works, but @Bob_Steers should confirm that.

Bob_Steers · August 8, 2019, 7:51am

Blocks shouldn’t be affected, but I’ll run some experiments.