remo²hbo Software
The existing software for the signal display of the remo²hbo - repairable patient monitoring in mobile hospital boxes is available in the following repositories:
The current image can be downloaded for testing here.
Please feel free to post your suggestions here or comment/post questions on existing suggestions posted by others.
This is the current signal display:
:~/remo2hbo_oktopus_frontend$ npm install
:~/remo2hbo_oktopus_frontend$ npm start
For an intro into integrating an event stream into a webapp see this tutorial.
In order to construct the Oktopus Operating System (Raspberry Pi image) that includes the frontend display introduced above, you need
- a linux computer
- an SD-card
- a Raspberry Pi with Bluetooth (included on Raspberry Pi 3)
On your linux computer, the following programs/packages/functionalities must be installed:
- a linux kernel with loop support (almost always available)
- make (GNU flavour)
- losetup (GNU flavour)
- qemu-arm-static (e.g. from the qemu-user-static Debian package)
- a C compiler for the ARM platform (i.e. gcc-arm-linux-gnueabi, see submoduel teesock in the repository README)
- mkfs.ext4
- sfdisk
- debootstrap
- ssh-keygen (optional)
The entire process of creating the SD-card image for the Raspberry Pi should be carried out as root. Thus, in your terminal enter
sudo su
Now, clone the original repository to your linux computer. In your terminal, enter
git clone https://github.com/cadus/remo2hbo_oktopus_boot
Now, in order to ensure that the repository is complete, check to make sure that the submodules have been cloned. Go into the repository folder by entering
cd remo2hbo_oktopus_boot
Then, enter
git submodule init
and
git submodule update
In order to ensure that all the above mentioned programs and packages are available on your system, run your package manager and install, i.e.:
apt get install make qemu-user-static binfmt-support sfdisk debootstrap gcc-arm-linux-gnueabi dosfstools
Now you can begin creating the image by entering
make raspi.img
If anything goes wrong, such as missing packages, the process will break off. When this happens, you can fix the problem, then continue with the process. Before you run make again, you should unmount the partition, as this may already have happened and would repeated, if you start the process again. In order to unmount, enter in your terminal
umount imgmount/boot
umount imgmount/
losetup -d dev/loop0
losetup -d dev/loop1
Now continue by entering
make raspi.img
again.
Once the process is finished, you should have a raspi.img in your repository directory. The resulting raspi.img file can be written to an SD-Card using dd. And a Raspberry Pi can be booted from this SD-Card. Once you have inserted the SD-card into the SD-card port, you can check its location either by entering
lsblk
in the terminal or by checking the “Disks” application. It should tell you the device location such as
/dev/mmcblk0
In order to use DD (disc dump) to write the image onto the SD-card, enter the following into the terminal
dd status=progress if=rasi.img of=/dev/mmcblk0
The “if” means input file and “of” means output file. This will write the image file to the output specified, and it should therefore be the location of the sd-card. The sd-card is now ready, and can be inserted into a raspberry pi with Bluetooth capability.
The Oktopus sensor computer displays data on devices connected via Bluetooth. To enable this, it opens a Bluetooth network access point.
Thus, when you want to connect your mobile device to receive the sensory data from the Oktopus sensor computer, you
- Start the Oktopus sensor computer, i.e. insert the SD-card in your Raspberry Pi3 and power up
- Pair your phone with it via Bluetooth. WATCH OUT: you should disable wifi first!!
- Open a browser and enter http://oktopus Now, each device that is connected to the Oktopus sensor computer will receive a copy of the event stream that is received by the sensors connected to it. The display will appear on your phone even if there are no sensors connected.