Recent Posts

Pages: 1 ... 7 8 [9] 10
Marketplace / Dianemo Athena UI & iPhone Orbiter Preview
« Last post by totallymaxed on March 19, 2015, 10:24:15 am »
I've posted some more early UI screens from testing we are currently doing with Beta builds of the new iPhone iOS App. This time I have two new images of the new responsive screen layout for the Sky TV STB Remote screens (this is a very popular European STB/PVR for accessing the Satellite based Sky TV service).. On smartphones with < 5" screens we implement a swipe left/right gesture to allow the user to navigate to all the screens related to this device. In most cases there are two screens. Swiping between the two is fast and a familiar gesture for phone UI's. In these screens we are testing the best size/scaling of the screen elements (all graphics are svg's so they can be scaled in real-time to any size required by the device the UI is rendered on). Note these screens and the others I have posted are still not finished and contain some layout errors - see the status area at the bottom of these screens for example.

I'll post more of these images as we debug both the App and the Responsive Athena UI Skin for iPhone.

All the best

Users / Re: Dianemo Installation
« Last post by huh on March 19, 2015, 12:58:57 am »
Quick update/reply to may post.  After update && upgrade on the standard Ubuntu packages (pre-Dianemo) my nics were not supported by default.  Don't fully understand why, but not a Dianemo issue.

That said, Andrew and his Dianemo team were extremely responsive and helpful getting the system up and running- beyond the scope of what I thought my license did/should have included.

In-laws are happy again to have their squeezeboxes running.
Installation issues / Re: Pluto-vdr
« Last post by posde on March 18, 2015, 11:25:35 pm »
ver was broken

is not very descriptive. Would you mindto a bit more verbose.
Installation issues / Re: Dependancy issues running
« Last post by Govo on March 18, 2015, 09:19:34 pm »
Thanks for the reply but I updated my ram and ran the command again this evening, and hey its installed

Creating chroot for MD creation at: /opt/Diskless_CreateTBZ.P8t71ANhY
Wed Mar 18 20:07:14 GMT 2015 - Untarring /usr/pluto/install/PlutoMD_Debootstraped.tar.bz2
Wed Mar 18 20:08:16 GMT 2015 - Preparing the diskless system
/opt/Diskless_CreateTBZ.P8t71ANhY/usr/pluto/deb-cache/ubuntu-trusty-i386 ~
/opt/Diskless_CreateTBZ.P8t71ANhY/usr/pluto/deb-cache/ubuntu-trusty-i386 /opt/Diskless_CreateTBZ.P8t71ANhY/usr/pluto/deb-cache/ubuntu-trusty-i386 ~
/opt/Diskless_CreateTBZ.P8t71ANhY/usr/pluto/deb-cache/ubuntu-trusty-i386 ~
Wed Mar 18 20:15:38 GMT 2015 - Setting up /etc/apt/sources.list for ubuntu
Wed Mar 18 20:15:38 GMT 2015 - Setting up SSH
Wed Mar 18 20:15:38 GMT 2015 - Setting up kernel postinst.d/
Wed Mar 18 20:15:38 GMT 2015 - Setting up Foxconn NT330i compatability
Wed Mar 18 20:15:38 GMT 2015 - PreSeeding package installation preferences
Reading package lists...
Building dependency tree...
debconf-i18n is already the newest version.

Somethings never ceases to amaze me!

Installation issues / Pluto-vdr
« Last post by pointman87 on March 18, 2015, 08:49:55 pm »
yesterday i did an apt-get upgrade and got pluto-vdr installed. After install VDR was broken, downgrade back to got vdr working again.
Marketplace / Dianemo Revealed - Why Dianemo-Rpi2 ?
« Last post by totallymaxed on March 18, 2015, 02:26:14 pm »
Dianemo Revealed - Dianemo-Rpi2 for ARM v7
A New Era in Smart Home Technology

We've been looking at lower cost, small form factor & low energy hardware for Dianemo for a number of years now. In the very early days we looked at hardware based around VIA processors/chipsets which were early attempts at low-cost/low-energy hardware and then the Intel Atom processor arrived and of course a whole host of new small form factor hardware arrived built around it. But although these platforms represented big improvements over what we had before they were still not ideal and still often ran very hot.

Meanwhile the mobile world was evolving around ARM based processors and SOC's which were incredibly power efficient and ran without getting overly hot and delivered ever increasing amounts of computing power. Apart from desktop PC's and laptops everything else around us today has evolved around small low power processors and that means mostly ARM based hardware.

Out of this wave of tiny low power hardware has emerged the phenomenon that is Raspberry Pi (Rpi). The Rpi has sold millions of units and the hardware ecosystem and developer community that has evolved around it is now worldwide and incredibly vibrant. The release of the new Raspberry Pi2 (Rpi2) at the beginning of 2015 was a turning point, as for the first time we had enough performance and memory to envisage running a Dianemo NC software stack on a Rpi.

We see the Rpi2 as the perfect embodiment of what we have in the X86 PC driven world shrunk down to ARM footprint/cost; we have incredibly vibrant hardware add-on communities built around the Rpi architecture (and Rpi2 is backwardly compatible with almost all the Rpi hardware out there) and we also have an equally vibrant and dedicated software community too. So in Rpi2 we have not just an ARM based piece of hardware that for the first time has the performance we have been looking for, but we also have a ready built ecosystem too. Having that ecosystem is incredibly important when you analyse it because it means that we are not 'swimming' alone and can leverage the work going on in other parts of the Rpi community to amplify and extend our efforts and enjoyment. The 'our' in the last sentence applies to both Dianemo the company and to our software customers in equal amounts. There are other ARMv7 based boards out there that would also have the performance we are looking for but none of those hardware platforms have ecosystems like the Rpi. In the end you need a critical mass of other people, most of whom are not interested in Home Automation, but who all share a common enjoyment, commitment and love of a common hardware platform. Joining this community collectively benefits everyone in it too.

So here we are. I'm not going to talk about the specifics of what Dianemo-Rpi2 is or will be here today. That's for the future. But I am sure that ARM based hardware is where we need to be and that Dianemo-Rpi2 is going to be a very exciting platform for all of us to build around.

I'd encourage anyone with an interest in low cost/energy home automation that leverage’s the Rpi hardware/software ecosystem to get signed up for our Dianemo-Rpi2 Preview here;



Installation issues / Re: Dependancy issues running
« Last post by posde on March 18, 2015, 02:12:00 pm »
Google for apt-get out of memory - I can't remember the setting, but google never fails to remember ;)
Installation issues / Re: CuBox-i from SolidRun
« Last post by pigdog on March 18, 2015, 02:03:19 am »

I just cut and pasted part of my notes as what I had kinda done to date.

Tftpboot and other junk not included.

This is based on the installation of the 12.04 variant of LMCE.

My notes (so far) for investigation of Cubox ARM support on LMCE.

Log in as root.

apt-get update
apt-get upgrade
apt-get dist-upgrade

Preparing to build from sources.

We need to have gcc-arm-linux-gnueabi installed.

apt-get install gcc-arm-linux-gnueabi

We also need to have u-boot-tools installed (for mkimage).

apt-get install u-boot-tools

Plus, we need to have lzop installed (for "make zImage").

apt-get install lzop

Finally, we need git installed

apt-get install git

If logged in as root when we check our directory tree...


... we have 'Desktop' and 'new-installer' as directories.

Step 1. - u-boot for cu-box with pxe patches

To build the bootloader...

git clone

Now when we check our directory tree...


... we now have 'Desktop', 'new-installer' and 'u-boot-imx6' as directories.


cd u-boot-imx6

Set up our environment variables.

export ARCH=arm
export CROSS_COMPILE=/usr/bin/arm-linux-gnueabi-

Then we build the bootloader.

make mx6_cubox-i_config


A successful build will create u-boot-* files (including u-boot-img) plus a SPL file.

The SPL file is used for the actual machine detection and initialization. 
This file must be flashed on offset 1KByte of the boot micro SD.

The  u-boot.img is the second stage bootloader.
It can be flashed at offset 42KByte from the start of the boot micro SD. 
Or it can alternatively be put as-is on the first partition of the micro SD.

The general bootloader flashing procedure is...

dd if=SPL of=/dev/sdX bs=1K seek=1

...where /dev/sdX is the location of your microSD card.

For flashing u-boot.img as raw to the micro SD -

dd if=u-boot.img of=/dev/sdX bs=1K seek=42

WARNING: Make sure you are flashing u-boot to the proper target device.  Putting the wrong device identifier could wipe your hard drive.

You can boot from the microSD at this point without booting a Linux system (only the u-boot).

Step 2. - Kernel build (with appropriate patches)

Compiling the kernel.

Change directory to /u-boot-imx6/arch/arm in order to edit the file

modify the line

CROSS_COMPILE ?= arm-linux-


CROSS_COMPILE ?= arm-linux-gnueabi-

cd back to the 'Desktop', 'new-installer' and 'u-boot-imx6' directories

The 3.10 LTS kernel is the main kernel to be used for end users and general availability.

It is based on Linaro kernel 3.10 LTS, i.MX6 Freescale patches and patches from Russell King, Jon Nettleton and various other developers.

The kernel can be built using the following commands.

git clone

Upon completion when we now check our directory tree...


... we now have 'Desktop', 'new-installer', 'u-boot-imx6' and 'linux-linaro-stable-mx6' as directories.

cd linux-linaro-stable-mx6
Set up our environment variables.

export ARCH=arm
export CROSS_COMPILE=/usr/bin/arm-linux-gnueabi-

make imx_v7_cbi_hb_defconfig

make zImage imx6q-cubox-i.dtb imx6dl-cubox-i.dtb imx6dl-hummingboard.dtb
make modules

The generated files are -


The first file is the actual kernel. The other three are device tree files loaded by the boot loader.

So from what I looked at in DisklessCreate - yeah this approach was 'different'.

Don't know if I can use "trusty image" because of the patches.

I was going to create a menuconfig for pxelinux.cfg and chose the package I wanted to install something like...

DISPLAY message
DEFAULT cubox blah blah
LABEL cubox blah blah
   kernel /where the heck my vmlinux is
   append root=/dev/nfs boot=casper netboot=nfs nfsroot=IP.OF.YOUR.SERVER:/srv/tftpboot/cubox blah blah initrd= cubox/blah blah/initrd.lz --

kinda thing.  You know. HACKABILLY.

I also need those .dtb files to support the different variants of the cubox-hummimgboard I believe.  (I don't know for sure.  Suppose to automatically load the proper .dtb depending upon hardware).

Anyway I'll poke around at this end.

Developers / Re: Developing a Weather Plugin, videos
« Last post by SBCC on March 18, 2015, 12:14:50 am »
Hi Guys

Sorry I've been distracted.

Carlos I did not have a chance to look at your code but I made some substantial changes to the code. It dose have an Open Weather Map option now.

I removed the mutexes and used the pluto mutexes... though I'm not completely sure how they work. There is a lot of code to look at there. I have 2 classes. 1 for NOAA and one for OWM (Open Weather Map). I will look at your code now Carlos and see how we can merge the two. Thanks for all your help!!

Here is the link to my code;


Installation issues / Re: Dependancy issues running
« Last post by Govo on March 17, 2015, 10:31:11 pm »
My apologies, when he said memory I taught he was referring to ram, as basic  user, is it something I can fix ?

Pages: 1 ... 7 8 [9] 10