Topics

1

General Discussion / Raspberry Pi 3

« on: January 29, 2020, 04:02:28 AM »

So I have downloaded your Pi installation package on to a fresh Raspian image, It works.

The processing power required for the wave motion is just too much for the Raspberry Pi 3. To fix this I change a setting in MovingWater.cpp. I change 'segments = 32' to 'segments=10'. This is on line 86.  Then I compile as per the instructions below.
I haven't had a crash or a freeze on the Pi since I set this.

Compile Bridgecommand for the Raspberry Pi 3 (and Linux Mint)

Ensure Raspbian is up to date:
https://www.raspberrypi.org/documentation/raspbian/updating.md
sudo apt-get update
sudo apt-get dist-upgrade

Enable opengl in Raspbian:
Run raspi-config
choose '7 - advanced' then 'A7 GL Driver' then 'G2 - GL Fake KMS'
Reboot

Install: mesa-common-dev
sudo apt-get install mesa-common-dev

Install: libxcursor-dev
sudo apt-get install  libxcursor-dev

Install: libgl1-mesa-dev
sudo apt-get install libgl1-mesa-dev

Get source code from:
https://www.bridgecommand.co.uk/
https://github.com/bridgecommand/bc

UPDATE: The processing power required for the wave motion is just too much for the Raspberry Pi. To fix this I change a setting in MovingWater.cpp. I change 'segments = 32' to 'segments=10'. This is on line 86. 
I haven't had a crash or a freeze on the Pi since I set this.

I have yet to get the sound to compile with the Pi, but I am not giving up yet.

Go to source root in console and run 'make'

Notes for PI:
Run off a SD card, not a USB. It crashes often.
You must run at 800x600 or less (640 x 480). I have found the best performance is with Raspbian set to 800x600 and BridgeCommand set to windowed 640 x 480 and set to auto size (width=0)
Turn off Shading.
You can set these by running bridgecommand-ini.
Sound does not work.
Use IP addresses not network name on the Pi for repeater and network settings.

2

General Discussion / Instrumentation Options

« on: May 09, 2019, 02:51:22 PM »

Instrumentation Options:

For those interested in an alternative instrumentation option for the bridgecommand NEMA output I have done the following:

I have a program that converts the UDP NEMA output from bridgecommand and turns it into both an update NEMA.txt file and an http (port 8080) output. 
https://github.com/vpelss/BridgeCommand_NEMA_UDP_to_File_HTML

This output can be used in an HTML / Javascript page to display your NEMA output.

The benefits are:
-easy to modify
-cross platform (can use on a tablet or phone)
-easily resized as browser is resized (if so designed)

A demo can be seen here (click on DEMO to start):
http://www.emogic.com/bc/

3

Bug reports / nema ip set to other than localhost

« on: April 22, 2019, 03:21:57 PM »

When nema ip set to other than localhost (another IP on the same subnet) , Bridgecommand-bc performance is reduced, takes seconds to respond, etc...

After some thought, I realized that the server IP can not be anything but the server IP, unless you had multiple NIC cards.

So I guess this is not really a bug report but maybe a suggestion to make that setting dummy proof against someone like me who might set it to an IP that will choke bridgecommand-bc

 

4

Development / Compiling with Sound : Linux

« on: March 21, 2019, 02:53:48 AM »

Looking at the code briefly, it looks like I might need to download and compile the sound libraries separately. Would this be an accurate statement?

When I added #define WITH_SOUND, it said it couldn't find sndfile.h.

So before I went down a rabbit hole, I thought I would ask.