Difference between revisions of "Dianemo S"

Revision as of 18:18, 9 August 2011

Dianemo S10.10 is a paid for software product, that shares a common heritage with LinuxMCE, that enables you to have a Dianemo installation on almost any LinuxMCE compatible Core hardware that you already own. The software only product is supported by the CHT Tech Support team via the LinuxMCE forum to keep its cost to a minimum. We cannot guarantee that all hardware will work with Dianemo S10.10 so there will be some restrictions as to which hardware you can install it on. One key restriction is that both for Hybrid NerveCentre's (Intel GPU's may work in UI1 only) and Media Managers we will only be supporting nVidia GPU's. Each installation will have a Dianemo installation ID and will be upgradable to future releases using a disc-less online update/upgrade procedure. You will get 12 month's of updates/upgrades included in your initial purchase cost and there will be an annual charge to continue to receive updates/upgrades for subsequent years. Updates will be released as and when we develop them and will be available at the same time as they are made available to our hardware products and OS upgrades will follow shortly after Ubuntu OS releases and dates. Any customer who does not sign-up for the paid for updates will not loose access to their system they will just not receive any updates/upgrades.

See the Dianemo Forum Thread for more information about pricing and the procedure for purchasing a license.

Installing Dianemo S10.10

Below are the simple steps needed to install Dianemo S10.10 on your existing LinuxMCE compatible hardware;

• Install 32bit Desktop edition Ubuntu 10.10 from a LiveCD
• When prompted to upgrade to 11.04 say NO.
• At this point you should have the dianemo-licence and dianemo-installer debs somewhere on the drive (via e-mail from CHT).
• Install the dianemo-temporary-licence deb first
• Install the dianemo-installer deb second
• Open a termnial
• Execute in terminal:

/usr/pluto/install/install-dianemo.sh

It will prompt you for your user password for sudo, to become root ie the user/password you created in the Ubuntu installer. Go make yourself a cup of tea or coffee, bake a few biscuits, that kind of thing!... while the installer does its thing.

The installer will download the debs and install them for you without asking any questions. After the system is installed, it will run Diskless_CreateTBZ.sh as well. If installation finishes successfully, reboot your system and Dianemo will start.

Dianemo Permanent License Key

Within 14 days of your Dianemo S10.10 installation contacting our servers you will receive another deb called 'Dianemo-license-nnnnnn' this should be copied to your NerveCentre and installed. This deb installs a securely signed file that completes your installation.

Notes

The following are some temporary work around's.

Detecting Shares when adding a NAS

The shares detection problem is due to the Configure_1837.sh script not getting called correctly by some other scripts. We're working on a fix for that. In the meantime if your server has been detected and added but the shares have failed to get detected automatically then run this script from the console and your shares will be detected. Firstly use Web Admin's device tree to find out the Device ID for the newly added NAS and note it down. Now from the console run the following scripts to detect the shares;

sudo /usr/pluto/bin/Configure_1837.sh -d <device_ID>

Next run the the script below to create the file structure;

sudo /usr/pluto/bin/StorageDevices_Setup.sh

Make sure you have an Orbiter displayed so that you can respond to the standard setup questions for your shares... ie 'use pluto file structure' etc etc. Once this script has run your good to go.

Adding SqueezeSlave Devices

Follow the steps below steps to add Squeezeslave Audio streaming devices to your Dianemo system;

• Click 'Show Devices Tree' in Web Admin
• Select the Core & then use the 'Add Child Device' option at the top of the screen on the right.
• In the 'Add Child Device' screen click 'Pick Device Template' button
• Now enter Device ID 1964 and click 'OK'
  • 'Squeezebox Slave' & '1964' will be visible next to the 'Pick Device Template' button - click it to select this template
• You will now see your new Squeezeslave device template screen;
  • Add a meaningful Device Description to uniquely identify which Squeezeslave this is (a reference to the Room Or zone is a good idea)
  • Set the Room & Entertainment Area
  • In the Device Info section set the (**ie the top most section of the template**);
    • Set the Mac Address. This should be in the form of; 00:00:00:00:00:01 and unique on the system
  • In the Device Data section set the;
    • Sound card this Squeezeslave will use

Next you need to create a Squeezebox Player to be associated with the SqueezeSlave you created above;

• Click 'Show Devices Tree' in Web Admin
• If there is already a 'Slimserver Streamer' section under the 'Core' then;
  • Add a child device under the 'Slimserver Streamer'
  • In the 'Add Child Device' screen click 'Pick Device Template' button
  • Now enter Device ID 58 and click 'OK'
  • A new Squeezebox Player will be added under the 'Slimserver-Streamer'
  • Give it a matching name to the Squeezeslave you are associating it with and locate in in the same Room/EA & enter the same Mac Address too.
  • Save the changes
• Now do a reload
• Next you should start the Squeezeslaves manually (on boot they will be started automatically);

sudo /usr/pluto/bin/Start_SqueezeBox_Slaves.sh

• Test your new devices to make sure they work correctly

Adding iOS Orbiters to your System

Please download the latest Dianemo App from Apple's iOS App Store. The Dianemo App is a free download from the App store.

Follow the steps below to add an iOS device to your Dianemo S10.10 NC;

The procedure to setup a new iOS Device on your NC is simple but the order of the steps is important.

• First of all, add a new Generic Web Device as a Child Device of your Core:
  • Goto the Dianemo Admin website--> Pull down Advanced --> Configuration --> Devices --> This shows the devices tree on the left window --> click CORE. The CORE's detail page should appear.
  • Click 'Create Child Device'.
  • In the Description, enter the name of the specific web orbiter (choose a device descriptive name ie 'Paul's iPod4G')
  • In the Add child device window, click the button 'Pick device template'. A new pop-up window containing device templates will be opened.
  • Type the template id: 1748 and press go.
  • Click the button 'Pick Device Template'. The Add Child Device Window will close, and the Generic Web Device will be added to the Core, as the updated Device Tree will be displayed.
  • A new Generic Proxy Orbiter will also be created automatically. Watch the Orbiter generation process on the Orbiters page: Wizard-->Devices-->Orbiters.
• Wait till the Orbiter generation procedure finishes. A message on an active Orbiter or on the Orbiter page will indicate when it has completed.
• Set the appropriate screen resolution to suit the iOS device you are adding from the 'Size' drop down
  • iPad1 or iPad2 = 1024x768
  • iPhone 3G, 3GS, iPod 1-3 Generation = 480x320
  • iPhone4 or iPod4G = 960x640
• Set the 'Skin' drop down to the skin you want to use (normally this would mean the UI1 Standard Variation or a derivative)
• Click on your new Generic Proxy Orbiter in the device tree, give it a unique name and then scroll to the bottom of the page on the right and look for the field called 'Listen Port'. This field will be set to '3461' by default (if this Web Orbiter is not your first then you should increment this value by one ie to '3462' - each Web Orbiter must have a unique 'Listen Port' number)
• Now click the 'Save' button at the bottom of the screen to save the changes you have made.
• Now do a 'Full Regen' from the 'Wizard - Orbiters' page (use the 'Full Regen' for the specific Web Orbiter you have created and not the overall 'Full Regen' button at the top of the page). Next when the Regen has completed do a "Quick reload router". Otherwise, the Web Orbiter won't work properly.