LinuxMCE - User contributions [en]

Source Code

2010-10-04T23:33:06Z

OmeGa: Source Code moved to Source Code (SVN Repository): Not being found when searching for 'svn'

[[Category:Development]]
[[Category:Programmer's Guide]]
'''LinuxMCE''' is a pretty big project. Not counting [[GSD]] devices, LinuxMCE's own code is already well over a million lines in hundreds of modules, with over 1,000 pages of online documentation, and in addition LinuxMCE also incorporates lots of other big open source projects like [[Asterisk]], [[Xine]], [[MythTV]], [[Firefox]], [http://www.videolan.org/ VideoLan], [http://www.slimdevices.com/pi_features.html SlimServer], [http://www.kubuntu.org/ Kubuntu Linux] itself, etc., all of which have special LinuxMCE 'wrappers' to allow them to work together seamlessly as a total home solution. For the brave of heart, you can also download modules by hand, and see all the dependencies and compatibility for each module.

=SVN repository (always up-to-date)=

Current source is available here:
http://svn.linuxmce.org/svn/
you can browse it using web browser or use Subversion tool to check out code and fetch further updates:

svn checkout http://svn.linuxmce.org/svn/branches/LinuxMCE-0810/ linuxmce

Be sure to read the page [[Building LinuxMCE 0810]] to set up a builder to compile LinuxMCE.

Keywords: svn, source code, checkout, subversion

Source Code

2010-10-04T23:31:00Z

OmeGa:

Add an additional hard drive

2010-09-21T15:42:38Z

OmeGa:

{{versioninfo|810Status=Working|810UpdatedDate=22 Sep 2010|810UpdatedBy=DEMNVT}}
[[Category: Tutorials]]

==Caveat==
WARNING!!! Do not follow this procedure unless you have a basic understanding of how to format hard drives and you know that you are definately working with a hard drive that contains no important data. The process can cause you to lose all of the data on your hard drive.

==Procedure==
If (after installing LinuxMCE) you would like to add a brand-new (BLANK) hard drive to your Core/Hybrid to add additional storage space for Media you can use the following procedure:

*Install the physical hard drive into the computer
*Check that the BIOS settings all look correct (Hard drive boot order etc)
*Boot up LinuxMCE and ssh into the core.
*Create a partition on the disk using the fdisk command (you should have read up on this before you use it)
ie. sudo fdisk /dev/sdX (for a SATA drive where X is the number of the new drive)
*Create a filesystem on this new partition (XFS is the recommended option)
ie. sudo mkfs.xfs /dev/sdXY (for partition 'Y' on SATA drive 'X')
*Watch the screen of your nearest Orbiter for a few minutes to see if the new partition is automatically detected.
*If it does not get auto detected then reboot the core and it should be auto detected.
*Tell LinuxMCE how you want to use the new drive (ie as an Internal Drive that uses the LinuxMCE structure etc)
*Reload the router.
*Enjoy your new storage space.

==Example==
<pre>
user@dcerouter:/dev/disk$ sudo fdisk /dev/sdb
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel with disk identifier 0x3272b98c.
Changes will remain in memory only, until you decide to write them.
After that, of course, the previous content won't be recoverable.

The number of cylinders for this disk is set to 243201.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

Command (m for help): m
Command action
a toggle a bootable flag
b edit bsd disklabel
c toggle the dos compatibility flag
d delete a partition
l list known partition types
m print this menu
n add a new partition
o create a new empty DOS partition table
p print the partition table
q quit without saving changes
s create a new empty Sun disklabel
t change a partition's system id
u change display/entry units
v verify the partition table
w write table to disk and exit
x extra functionality (experts only)

Command (m for help): p

Disk /dev/sdb: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3272b98c

Device Boot Start End Blocks Id System

Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-243201, default 1):
Using default value 1
Last cylinder, +cylinders or +size{K,M,G} (1-243201, default 243201):
Using default value 243201

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.
Syncing disks.

user@dcerouter:/dev/disk$ sudo mkfs.xfs /dev/sdb1
meta-data=/dev/sdb1 isize=256 agcount=4, agsize=122094500 blks
= sectsz=512 attr=2
data = bsize=4096 blocks=488378000, imaxpct=5
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096
log =internal log bsize=4096 blocks=32768, version=2
= sectsz=512 sunit=0 blks, lazy-count=0
realtime =none extsz=4096 blocks=0, rtextents=0

user@dcerouter:~$ df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 106G 15G 86G 15% /
udev 1.7G 2.8M 1.7G 1% /dev
/dev/disk/by-uuid/ec718bdb-9cb0-4be0-9c52-893d4b7c3aad
106G 15G 86G 15% /
/dev/disk/by-uuid/ec718bdb-9cb0-4be0-9c52-893d4b7c3aad
106G 15G 86G 15% /dev/.static/dev
tmpfs 1.7G 0 1.7G 0% /lib/init/rw
varrun 1.7G 376K 1.7G 1% /var/run
varlock 1.7G 0 1.7G 0% /var/lock
tmpfs 1.7G 2.2M 1.7G 1% /lib/modules/2.6.27-17-generic/volatile
tmpfs 1.7G 0 1.7G 0% /dev/shm
/dev/sdb1 1.9T 4.2M 1.9T 1% /mnt/device/60
//192.168.80.2/public
148G 135G 13G 92% /mnt/device/53
</pre>

Keywords: new hard drive, HDD, extra hard drive, second hard drive.

Add an additional hard drive

2010-09-21T15:37:44Z

OmeGa:

{{versioninfo|810Status=Working|810UpdatedDate=22 Sep 2010|810UpdatedBy=DEMNVT}}
[[Category: Tutorials]]

WARNING!!! Do not follow this procedure unless you have a basic understanding of how to format hard drives and you know that you are definately working with a hard drive that contains no important data. The process can cause you to lose all of the data on your hard drive.

If (after installing LinuxMCE) you would like to add a brand-new (BLANK) hard drive to your Core/Hybrid to add additional storage space for Media you can use the following procedure:

*Install the physical hard drive into the computer
*Check that the BIOS settings all look correct (Hard drive boot order etc)
*Boot up LinuxMCE and ssh into the core.
*Create a partition on the disk using the fdisk command (you should have read up on this before you use it)
ie. sudo fdisk /dev/sdX (for a SATA drive where X is the number of the new drive)
*Create a filesystem on this new partition (XFS is the recommended option)
ie. sudo mkfs.xfs /dev/sdXY (for partition 'Y' on SATA drive 'X')
*Watch the screen of your nearest Orbiter for a few minutes to see if the new partition is automatically detected.
*If it does not get auto detected then reboot the core and it should be auto detected.
*Tell LinuxMCE how you want to use the new drive (ie as an Internal Drive that uses the LinuxMCE structure etc)
*Reload the router.
*Enjoy your new storage space.

==Example==
<pre>
lukas@dcerouter:/dev/disk$ sudo fdisk /dev/sdb
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel with disk identifier 0x3272b98c.
Changes will remain in memory only, until you decide to write them.
After that, of course, the previous content won't be recoverable.

The number of cylinders for this disk is set to 243201.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

Command (m for help): m
Command action
a toggle a bootable flag
b edit bsd disklabel
c toggle the dos compatibility flag
d delete a partition
l list known partition types
m print this menu
n add a new partition
o create a new empty DOS partition table
p print the partition table
q quit without saving changes
s create a new empty Sun disklabel
t change a partition's system id
u change display/entry units
v verify the partition table
w write table to disk and exit
x extra functionality (experts only)

Command (m for help): p

Disk /dev/sdb: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3272b98c

Device Boot Start End Blocks Id System

Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-243201, default 1):
Using default value 1
Last cylinder, +cylinders or +size{K,M,G} (1-243201, default 243201):
Using default value 243201

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.
Syncing disks.

lukas@dcerouter:/dev/disk$ sudo mkfs.xfs /dev/sdb1
meta-data=/dev/sdb1 isize=256 agcount=4, agsize=122094500 blks
= sectsz=512 attr=2
data = bsize=4096 blocks=488378000, imaxpct=5
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096
log =internal log bsize=4096 blocks=32768, version=2
= sectsz=512 sunit=0 blks, lazy-count=0
realtime =none extsz=4096 blocks=0, rtextents=0

lukas@dcerouter:~$ df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 106G 15G 86G 15% /
udev 1.7G 2.8M 1.7G 1% /dev
/dev/disk/by-uuid/ec718bdb-9cb0-4be0-9c52-893d4b7c3aad
106G 15G 86G 15% /
/dev/disk/by-uuid/ec718bdb-9cb0-4be0-9c52-893d4b7c3aad
106G 15G 86G 15% /dev/.static/dev
tmpfs 1.7G 0 1.7G 0% /lib/init/rw
varrun 1.7G 376K 1.7G 1% /var/run
varlock 1.7G 0 1.7G 0% /var/lock
tmpfs 1.7G 2.2M 1.7G 1% /lib/modules/2.6.27-17-generic/volatile
tmpfs 1.7G 0 1.7G 0% /dev/shm
/dev/sdb1 1.9T 4.2M 1.9T 1% /mnt/device/60
//192.168.80.2/public
148G 135G 13G 92% /mnt/device/53
</pre>

Keywords: new hard drive, HDD, extra hard drive, second hard drive.

Add an additional hard drive

2010-09-21T15:31:12Z

OmeGa:

{{versioninfo|810Status=Working|810UpdatedDate=22 Sep 2010|810UpdatedBy=DEMNVT}}
[[Category: Tutorials]]

WARNING!!! Do not follow this procedure unless you have a basic understanding of how to format hard drives and you know that you are definately working with a hard drive that contains no important data. The process can cause you to lose all of the data on your hard drive.

If (after installing LinuxMCE) you would like to add a brand-new (BLANK) hard drive to your Core/Hybrid to add additional storage space for Media you can use the following procedure:

*Install the physical hard drive into the computer
*Check that the BIOS settings all look correct (Hard drive boot order etc)
*Boot up LinuxMCE and ssh into the core.
*Create a partition on the disk using the fdisk command
ie. sudo fdisk /dev/sdX (for a SATA drive where X is the number of the new drive)
*Create a filesystem on this new partition (XFS is the recommended option)
ie. sudo mkfs.xfs /dev/sdXY (for partition 'Y' on SATA drive 'X')
*Watch the screen of your nearest Orbiter for a few minutes to see if the new partition is automatically detected.
*If it does not get auto detected then reboot the core and it should be auto detected.
*Tell LinuxMCE how you want to use the new drive (ie as an Internal Drive that uses the LinuxMCE structure etc)
*Reload the router.
*Enjoy your new storage space.

==Example==
<pre>
lukas@dcerouter:/dev/disk$ sudo fdisk /dev/sdb
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel with disk identifier 0x3272b98c.
Changes will remain in memory only, until you decide to write them.
After that, of course, the previous content won't be recoverable.

The number of cylinders for this disk is set to 243201.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

Command (m for help): m
Command action
a toggle a bootable flag
b edit bsd disklabel
c toggle the dos compatibility flag
d delete a partition
l list known partition types
m print this menu
n add a new partition
o create a new empty DOS partition table
p print the partition table
q quit without saving changes
s create a new empty Sun disklabel
t change a partition's system id
u change display/entry units
v verify the partition table
w write table to disk and exit
x extra functionality (experts only)

Command (m for help): p

Disk /dev/sdb: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3272b98c

Device Boot Start End Blocks Id System

Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-243201, default 1):
Using default value 1
Last cylinder, +cylinders or +size{K,M,G} (1-243201, default 243201):
Using default value 243201

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.
Syncing disks.

lukas@dcerouter:/dev/disk$ sudo mkfs.xfs /dev/sdb1
meta-data=/dev/sdb1 isize=256 agcount=4, agsize=122094500 blks
= sectsz=512 attr=2
data = bsize=4096 blocks=488378000, imaxpct=5
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096
log =internal log bsize=4096 blocks=32768, version=2
= sectsz=512 sunit=0 blks, lazy-count=0
realtime =none extsz=4096 blocks=0, rtextents=0

Keywords: new hard drive, HDD, extra hard drive, second hard drive.
</pre>

Add an additional hard drive

2010-09-21T15:28:04Z

OmeGa:

{{versioninfo|810Status=Working|810UpdatedDate=22 Sep 2010|810UpdatedBy=DEMNVT}}
[[Category: Tutorials]]

WARNING!!! Do not follow this procedure unless you have a basic understanding of how to format hard drives and you know that you are definately working with a hard drive that contains no important data. The process can cause you to lose all of the data on your hard drive.

If (after installing LinuxMCE) you would like to add a brand-new (BLANK) hard drive to your Core/Hybrid to add additional storage space for Media you can use the following procedure:

#Install the physical hard drive into the computer
#Check that the BIOS settings all look correct (Hard drive boot order etc)
#Boot up LinuxMCE and ssh into the core.
#Create a partition on the disk using the fdisk command
ie. sudo fdisk /dev/sdX (for a SATA drive where X is the number of the new drive)
#Create a filesystem on this new partition (XFS is the recommended option)
ie. sudo mkfs.xfs /dev/sdXY (for partition 'Y' on SATA drive 'X')
#Watch the screen of your nearest Orbiter for a few minutes to see if the new partition is automatically detected.
#If it does not get auto detected then reboot the core and it should be auto detected.
#Tell LinuxMCE how you want to use the new drive (ie as an Internal Drive that uses the LinuxMCE structure etc)
#Reload the router.
#Enjoy your new storage space.

==Example==
<blockquote>
lukas@dcerouter:/dev/disk$ sudo fdisk /dev/sdb
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel with disk identifier 0x3272b98c.
Changes will remain in memory only, until you decide to write them.
After that, of course, the previous content won't be recoverable.

The number of cylinders for this disk is set to 243201.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

Command (m for help): m
Command action
a toggle a bootable flag
b edit bsd disklabel
c toggle the dos compatibility flag
d delete a partition
l list known partition types
m print this menu
n add a new partition
o create a new empty DOS partition table
p print the partition table
q quit without saving changes
s create a new empty Sun disklabel
t change a partition's system id
u change display/entry units
v verify the partition table
w write table to disk and exit
x extra functionality (experts only)

Command (m for help): p

Disk /dev/sdb: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3272b98c

Device Boot Start End Blocks Id System

Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-243201, default 1):
Using default value 1
Last cylinder, +cylinders or +size{K,M,G} (1-243201, default 243201):
Using default value 243201

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.
Syncing disks.

lukas@dcerouter:/dev/disk$ sudo mkfs.xfs /dev/sdb1
meta-data=/dev/sdb1 isize=256 agcount=4, agsize=122094500 blks
= sectsz=512 attr=2
data = bsize=4096 blocks=488378000, imaxpct=5
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096
log =internal log bsize=4096 blocks=32768, version=2
= sectsz=512 sunit=0 blks, lazy-count=0
realtime =none extsz=4096 blocks=0, rtextents=0

Keywords: new hard drive, HDD, extra hard drive, second hard drive.
</blockquote>

Add an additional hard drive

2010-09-21T15:19:40Z

OmeGa: Instructions on how to add an additional hard drive after installing LinuxMCE

{{versioninfo|810Status=Working|810UpdatedDate=22 Sep 2010|810UpdatedBy=DEMNVT}}
[[Category: Tutorials]]

WARNING!!! Do not follow this procedure unless you have a basic understanding of how to format hard drives and you know that you are definately working with a hard drive that contains no important data. The process can cause you to lose all of the data on your hard drive.

If (after installing LinuxMCE) you would like to add a brand-new (BLANK) hard drive to your Core/Hybrid to add additional storage space for Media you can use the following procedure:

Install the physical hard drive into the computer
Check that the BIOS settings all look correct (Hard drive boot order etc)
Boot up LinuxMCE and ssh into the core.
Create a partition on the disk using the fdisk command (sudo fdisk /dev/sdX for a SATA drive where X is the number of the new drive)
Create a filesystem on this new partition (XFS is the recommended option ie. sudo mkfs.xfs /dev/sdXY for partition 'Y' on SATA drive 'X')
Watch the screen of your nearest Orbiter for a few minutes to see if the new partition is automatically detected.
If it does not get auto detected then reboot the core and it should be auto detected.
Tell LinuxMCE how you want to use the new drive (ie as an Internal Drive that uses the LinuxMCE structure etc)
Reload the router.
Enjoy your new storage space.

Example of the process:

lukas@dcerouter:/dev/disk$ sudo fdisk /dev/sdb
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel with disk identifier 0x3272b98c.
Changes will remain in memory only, until you decide to write them.
After that, of course, the previous content won't be recoverable.

The number of cylinders for this disk is set to 243201.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

Command (m for help): m
Command action
a toggle a bootable flag
b edit bsd disklabel
c toggle the dos compatibility flag
d delete a partition
l list known partition types
m print this menu
n add a new partition
o create a new empty DOS partition table
p print the partition table
q quit without saving changes
s create a new empty Sun disklabel
t change a partition's system id
u change display/entry units
v verify the partition table
w write table to disk and exit
x extra functionality (experts only)

Command (m for help): p

Disk /dev/sdb: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3272b98c

Device Boot Start End Blocks Id System

Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-243201, default 1):
Using default value 1
Last cylinder, +cylinders or +size{K,M,G} (1-243201, default 243201):
Using default value 243201

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.
Syncing disks.

lukas@dcerouter:/dev/disk$ sudo mkfs.xfs /dev/sdb1
meta-data=/dev/sdb1 isize=256 agcount=4, agsize=122094500 blks
= sectsz=512 attr=2
data = bsize=4096 blocks=488378000, imaxpct=5
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096
log =internal log bsize=4096 blocks=32768, version=2
= sectsz=512 sunit=0 blks, lazy-count=0
realtime =none extsz=4096 blocks=0, rtextents=0

Keywords: new hard drive, HDD, extra hard drive, second hard drive.

Mobile Internet Device

2010-09-15T02:12:54Z

OmeGa: Mobile Internet Device Definition

A mobile Internet device (MID) is a multimedia-capable mobile device providing wireless Internet access.

(Source: http://en.wikipedia.org/wiki/Mobile_Internet_device)

MID

2010-09-15T02:09:53Z

OmeGa: Redirect page that points to Mobile Internet Device

#REDIRECT[[Mobile Internet Device]]

Orbiter Skins

2010-08-19T16:35:57Z

OmeGa: /* See Also */ Added line break

Orbiter Skins

2010-08-19T16:35:07Z

OmeGa:

Orbiter Skins

2010-08-19T16:33:17Z

OmeGa: Added links to Skins page

Skins

2010-08-19T16:13:45Z

OmeGa: Added links to Designer and Orbiter_Skins as well as 'Other' info and instructions for changing skins.

[[Category:Documentation]]

LinuxMCE utilizes a GUI (Graphical User Interface) that is referenced as a Skin. The capability for an end user (you) to create your own skins is also a built in option. See [[Designer]] for more info.

===Current Skins===

* [[Orbiter_Skins|Titanium Orbiter Skins]]
* [[Basic Skin|Basic]] - Works well with smaller devices (eg. on a [[Web_Orbiter_2.0|WebOrbiter]] running on an iPhone or iPod Touch).
* Other - There are various other skins to choose from. Please list your experiences with them here or attach some screen shots.

You can change the skin in use on an [[Orbiter]] by going into the [[LinuxMCE_Admin_Website|LinuxMCEAdmin Website]] and selecting Wizard > Devices > Orbiters. On this page you can change the skin for any of your Orbiters and then hit Update to apply the setting. You will then need to do a Full Regen for that particular Orbiter. The full regen is required as the system needs to 're-create' all of the buttons with their new colours and designs.

Skins

2010-08-19T16:05:22Z

OmeGa: /* Current Skins */

[[Category:Documentation]]

LinuxMCE utilizes a GUI (Graphical User Interface) that is referenced as a Skin. The capability for an end user (you) to create your own skins is also a built in option.

===Current Skins===

* [[Orbiter_Skins|Titanium Orbiter Skins]]
* [[Basic Skin|Basic]] - Works well with smaller devices (eg. on a [[Web_Orbiter_2.0|WebOrbiter]] running on an iPhone or iPod Touch).
* Other - There are various other skins to choose from. Please list your experiences with them here or attach some screen shots.

You can change the skin in use on an [[Orbiter]] by going into the [[LinuxMCE_Admin_Website|LinuxMCEAdmin Website]] and selecting Wizard > Devices > Orbiters. On this page you can change the skin for any of your Orbiters and then hit Update to apply the setting. You will then need to do a Full Regen for that particular Orbiter. The full regen is required as the system needs to 're-create' all of the buttons with their new colours and designs.

Skins

2010-08-19T16:03:14Z

OmeGa: /* Current Skins */

[[Category:Documentation]]

LinuxMCE utilizes a GUI (Graphical User Interface) that is referenced as a Skin. The capability for an end user (you) to create your own skins is also a built in option.

===Current Skins===

* [[Orbiter_Skins|Titanium Orbiter Skins]]
* [[Basic Skin|Basic]] - Works well with smaller devices (eg. on a [[Web_Orbiter_2.0|WebOrbiter]] running on an iPhone or iPod Touch.

You can change the skin in use on an [[Orbiter]] by going into the [[LinuxMCE_Admin_Website|LinuxMCEAdmin Website]] and selecting Wizard > Devices > Orbiters. On this page you can change the skin for any of your Orbiters and then hit Update to apply the setting. You will then need to do a Full Regen for that particular Orbiter. The full regen is required as the system needs to 're-create' all of the buttons with their new colours and designs.

Skins

2010-08-19T15:55:10Z

OmeGa: /* Current Skins */

Web Orbiter 2.0

2010-08-19T15:32:13Z

OmeGa:

{{versioninfo|810Status=Relevant|810UpdatedDate=23rd July 2010|810UpdatedBy=Purps}}
{| align="right"
| __TOC__
|}
[[Category: Orbiters]]
[[Category: Tutorials]]

A Web Orbiter is any device (such as a iPhone, iPod Touch, iPad, laptop, PC, etc.) that accesses the Orbiter user interface (UI) through a Web browser.

The new Web Orbiter 2.0 has been re-written from the ground up to make sure it has a much smoother performance overall but especially on slower lower powered devices and devices that are connected over slow LAN connections or even slower external connections...such as a Mobile 3G network or slow WiFi connection.

So what has changed? Well visually your Orbiter UI will look like it does on your existing standard Orbiters but you will notice that unlike the original Web Orbiter the new 2.0 version does not refresh every 5 secs. The new Web Orbiter now only updates if something changes in the system and that requires the UI screen you are currently viewing to be updated or if you click on a UI button or other UI element and that causes a screen update.

To achieve this the proxy_orbiter has been updated so that it sets a flag called 'ANYNEWS' to 'true' if some element of the current displayed screen has been updated. The Web Orbiter makes a light weight call to query the state of this flag once every second and only gets an updated UI screen if the flag is set to 'true' otherwise no screen update is requested. So in use the new Web Orbiter 2.0 behaves in a very similar fashion to the Orbiter on one of your MD's - and now it even performs with a similar performance level too.

Whats a proxy_orbiter? Proxy_orbiter runs on the Core and its job is to render the UI for the Web Orbiter that is running remotely on some other device. Each Web Orbiter has an associated proxy_orbiter and the two work in partnership. Proxy_orbiters do all the 'heavy lifting' rendering the UI and this allows the remote device that is running the Web Orbiter to be much less powerful and very simple devices indeed if needed.

Another change in the new 2.0 Web Orbiter is that screen refreshes are double buffered so that the new Web Orbiter receives the new screen update from your Core in the background and only redraws the screen when it has the complete image stored in memory - this makes the update process smoother and faster.

The overall effect of all these changes is to vastly improve the performance and usability while at the same time reducing the processing overhead of the Web Orbiter massively.

== Setup ==
The procedure to setup a Web Orbiter is simple but the order of steps is important.
#First of all, add a new Generic Web Device as a Child Device for your Core:
##Goto the LinuxMCE Admin website-->Show devices tree-->CORE. The CORE's detail page should appear.
##Click 'Create Child Device'.
##In the Description, enter the name of the specific web orbiter.
##In the Add child device window, click the button 'Pick device template'. The new pop-up window containing device templates will be opened.
##In the 'Device Category' dropdown list, choose 'Peripherals'.
##In the 'Device Template' dropdown list, find and select "Generic Web Device" (or just 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 show.
##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 device your Web Orbiter is intended for from the 'Size' drop down
#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.

==Device Screen Resolutions==
If the 'Device' your planning to use your Web Orbiter on is a Desktop or Laptop then use the biggest resolution that will comfortably fit onto your screen. If your device is a touch screen device like an iPad, iPhone or iPod Touch then choose a resoltion that matches the overall resolution of the devices display;

===iPad===
The iPad has a screen resolution of 1024x768 so if your creating an Orbiter for the iPad this is the resolution you should select for this Web Orbiter.

===iPhone (pre iPhone 4) or iPad Touch===
The iPhone/iPod Touch have a screen resolution of 480x320 so if your creating an Orbiter for either of these this is the resolution you should select for this Web Orbiter.

===iPhone 4===
The iPhone 4 has a screen resolution of 960x640 so if your creating an Orbiter for the iPhone 4 this is the resolution you should select for this Web Orbiter.

===Google Nexus One or HTC Desire (Android)===
If you have a Nexus One you will need to select a resolution of 480x800 (select N770 in the web admin, it is 480x800) so if your creating an Orbiter for the Nexus One this is the resolution you should select for this Web Orbiter.

On the HTC Desire you might also have to go into the web browser settings and change the default zoom to "far away" (mine is danish, so don't know the exact english decription). After that it should be full screen.

===Nokia 5800 XpressMusic===
For a fullscreen orbiter, iPhone resolution 480x320 works quite well. For a screen that's full width (but requires some vertical scrolling), 640x480 (Standard TV) works well. This resolution allows for easier reading of some orbiter buttons, without the need for zooming in.

===Nintendo DSi===
Best screen resolution, 480x320 so far. Lower resolutions may work well also with "Mobile Phone Basic" skin applied.

==Good skins for small screens==

here we should list the skins that can be used on the smaller screens of Phones and alike.

The skin "Mobile Phone Basic" is OK readable on the HTC Desire at 480x800.

iPhone/iPod Touch - The "Basic" skin works well. The Titanium skins should also work ok although might be a little bit harder to make out text in file lists etc. "Mobile Phone Basic" isn't a good choice as it is missing a few buttons (eg. Random in the remote) as it was designed for devices with hardware buttons. Once you load up the web-orbiter on your iPhone the Safari 'menu' bars get in the way a bit. This can be overcome by hitting the '+' symbol on the bottom bar and adding an icon to your home screen. This will then open up with only the 'status' bar at the top.

==Access to the Web Orbiter==

===From within your home===
You can access the Web Orbiter 2.0 from any of the following Web browsers (Google Chrome, Mozilla Firefox, Safari). Others may also work but have not been tested (your experiences with other web browsers would be welcome here) :

'''For the 810 releases the correct URL is:'''
''<nowiki>http://<core_ip>/lmce-admin/weborbiter.php</nowiki>''

:* From within the "internal" LinuxMCE LAN, for example:
::::''http://192.168.80.1/lmce-admin/weborbiter.php'' (0810)
:::::(This assumes the IP address range set by default at installation.)
:*You can also use the network name of the Core in place of the IP address. For example, if the Core was named "dcerouter" during the default installation, you could use:
::::''<nowiki>http://dcerouter/pluto-admin/weborbiter.php</nowiki>''
:*From the "external" WAN side of the Core, the core_ip would be the WAN IP address of the core (ie the one offered to the WAN side NIC on the Core by your broadband Router). If, for example, the core has a WAN side address of 192.168.0.50 offered up by your Broadband Router, use:
:::: ''<nowiki>http://192.168.0.50/lmce-admin/weborbiter.php</nowiki>''

:::::(Note: To use this method, [[Outside Access]] must be enabled.)

===From the Internet===
You could use the IP address:port for your home LAN, with port forwarding to the Core's LAN IP address (enabled by your home LAN router).
*''This is an advanced topic and may not be secure in the current version.''

By default, LinuxMCE is not accessible outside your home. This makes the system secure, but it prevents you from accessing the web site via the Internet while away from home. You can [[Outside_Access|turn on Internet access]], allowing access to the admin website anywhere. For your own security, however, we recommend you first read about [[Security & Privacy Issues]].

===Login page===
*A simple login page should be displayed. Input an existing user name and password, then click "Login".
*From the dropdown list of devices, choose the Web Orbiter you would like to use and click or touch 'Open'. If you have got several web orbiters in your system then they will be displayed in the dropdown and you can choose which one to use. (only one user can use any Web Orbiter at a given time)
*A page that looks similar to this should appear: [[Image:Web Orbiter.jpg|center]]
*Here is another UI1 variation loaded into Web Orbiter 2.0: [[Image:web_orbiter_20_in_chrome1.jpg|center]]
*This image is of Web Orbiter 2.0 running on an iPod Touch: [[Image:Web orbiter on iPod Touch4.JPG|center]]

==Where is the Web Orbiter code on my system?==

===Look in the following directories on your Core===

Look in;
/var/www/lmce-admin/

You will see the following Web Orbiter related files (there are many other unrelated files in this directory too);

weborbiter_command.php
weborbiter_image.php
weborbiter.php

Look in;
/var/www/lmce-admin/weborbiter

You should see the following files;

IT.php
jquery.min.js
jquery.timers.js
login.html
waiting.gif
weborbiter.css
weborbiter.html
weborbiter.js
weborbiter_select.html

==Devices that have been tested with Web orbiter 2.0==
This is a simple list of devices that have been tested with Web Orbiter 2.0. If you have got a new device to add to this list then please add it below...or if you have some experiences with a device already listed then please add some simple notes here too.

===Ipad===

===iPod===

===iPhone 3GS===

===iPhone 4===

===HTC Hero (Android 1.6)===

===HTC Desire (Android 2.1)===
Screen size is a little bit small I think, it is difficult to hit the up/down keys.

===Nokia N800===

===Nokia N900===

===Nokia 5800 XpressMusic===
Both "S60 Browser" (default) and "Opera Mobile" work well.

===Nintendo DSi===

===Eken M002===

See M002 info here [[Eken_m002]]. See video of the M002 running Web Orbiter 2.0 here; [http://www.youtube.com/watch?v=eA0SaYYQb7E Eken m002]

==Web Orbiter 2.0 has been tested on the following browsers==

===Firefox 3.6===
Works fine.

===Chrome 6.0.453.1 dev===
Works fine.

Also works fine as a chrome application shortcut.
Just create the shortcut when you are logged into the orbiter and have the right device chosen.

===OperaMini===
Works fine.

===OperaMobile 10===
Works fine.

===Midori 0.2.2===
Works fine.

===Internet Explorer===
Not working due to javascript issues.

===S60 Browser===
Default Symbian browser - works fine (tested on Nokia 5800 XpressMusic)

===Nintendo DSi Browser===
(based on Opera)

==Troubleshooting==
===Connect failed===
If you try to connect to the Web Orbiter and see this message:
<code>"Connect to proxy orbiter failed, please try again"</code>,
this means that Orbiter generation hasn't finished yet, or that you forgot to do a [[Quick_reload_router|quick restart of the router]].

Keywords: WebOrbiter

Web Orbiter

2010-08-19T15:27:33Z

OmeGa: /* See also */

{{versioninfo}}
{| align="right"
| __TOC__
|}
[[Category: Orbiters]]
[[Category: Tutorials]]

A Web Orbiter is any device (such as a laptop, PC, etc.) that accesses the Orbiter user interface (UI) through a Web browser.

There is now a new version of WebOrbiter (WebOrbiter 2.0) please click [[Web_Orbiter_2.0|here]] for setup instructions.

== Setup ==
The procedure to setup a Web Orbiter is simple but the order of steps is important.
#First of all, add a new Generic Web Device as a Child Device for your Core:
##Goto the LinuxMCE Admin website-->Show devices tree-->CORE. The CORE's detail page should appear.
##Click 'Create Child Device'.
##In the Description, enter the name of the specific web orbiter.
##In the Add child device window, click the button 'Pick device template'. The new pop-up window containing device templates will be opened.
##In the 'Device Category' dropdown list, choose 'Peripherals'.
##In the 'Device Template' dropdown list, find and select "Generic Web Device" (or just 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 show.
##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.
#Do a "[[Quick reload router]]". Otherwise, the Orbiter won't work properly.

==Access to the Web Orbiter==

===From within your home===
You can access the Web Orbiter from any web browser (Mozilla Firefox, IE, Safari):

'''If you are currently using the 810 alpha releases the correct URL is:'''
''<nowiki>http://<core_ip>/lmce-admin/weborbiter.php</nowiki>''

'''The current release 710 uses the information below.'''

*In the browser address bar, type the URL ''<nowiki>http://<core_ip>/pluto-admin/weborbiter.php</nowiki>''.
:* From within the "internal" LinuxMCE LAN, for example:
::::''http://192.168.80.1/pluto-admin/weborbiter.php'' (0710)
::::''http://192.168.80.1/lmce-admin/weborbiter.php'' (0810)
:::::(This assumes the IP address range set by default at installation.)
:*You can also use the network name of the Core in place of the IP address. For example, if the Core was named "dcerouter" during the default installation, you could use:
::::''<nowiki>http://dcerouter/pluto-admin/weborbiter.php</nowiki>''
:*From the "external" home LAN, the core_ip would be the LAN IP address of the core. If, for example, the core is at 192.168.0.50 on the home LAN, use:
:::: ''<nowiki>http://192.168.0.50/pluto-admin/weborbiter.php</nowiki>''

:::::(Note: To use this method, [[Outside Access]] must be enabled.)

===From the Internet===
You could use the IP address:port for your home LAN, with port forwarding to the Core's LAN IP address (enabled by your home LAN router).
*''This is an advanced topic and may not be secure in the current version.''

By default, LinuxMCE is not accessible outside your home. This makes the system secure, but it prevents you from accessing the web site via the Internet while away from home. You can [[Outside_Access|turn on Internet access]], allowing access to the admin website anywhere. For your own security, however, we recommend you first read about [[Security & Privacy Issues]].

===Login page===
*A simple login page should be displayed. Input an existing user name and password, then click "Login".
*From the dropdown list of devices, choose Generic Web Device.
*A page that looks similar to this should appear: [[Image:Web Orbiter.jpg|center]]

==Troubleshooting==
===Connect failed===
If you try to connect to the Web Orbiter and see this message:
<code>"Connect to proxy orbiter failed, please try again"</code>,
this means that Orbiter generation hasn't finished yet, or that you forgot to do a [[Quick_reload_router|quick restart of the router]].

=== Size ===
I was able to change the size of the rendered image in the Wizard-->Orbiters page. Find the Web Orbiter device in the list and resize it. After another orbiter regen, it was the right size for me. (''Source http://forum.linuxmce.org/index.php?topic=3833.0'')

=== Problems with rapid refresh rate ===

Problem:
When using the Web Orbiter over the Internet (instead of from within my home LAN), it refreshed every 5 seconds, making it difficult to use. The images were repeatedly downloaded each time.

Solution:
*Go to [[LinuxMCE Admin Website]]-->Device tree-->CORE-->Generic Web Device-->Device Data
*Set the Refresh Interval to a higher value (I used 60 seconds for mine).

=== Changing default room ===
Changing the default room in the Wizard-->Devices-->Orbiters page has no effect.

Solution:
*Go to [[LinuxMCE Admin Website]]-->Device tree-->CORE-->Generic Web Device
*Check the box for the room to control

===Screen Deadlock===
If the screen of your orbiter becomes "frozen" or stuck and orbiter regens and router reloads do not resolve the issue, run this from the core:
sudo killall -9 Proxy_Orbiter
(Source: http://forum.linuxmce.org/index.php?topic=6844.0)
= See also =
Another example of a web orbiter is the [[IOrbiter]]

WebOrbiter has also been rebuilt from the ground up as [[Web_Orbiter_2.0]]

Web Orbiter

2010-08-19T15:26:45Z

OmeGa: /* See also */

{{versioninfo}}
{| align="right"
| __TOC__
|}
[[Category: Orbiters]]
[[Category: Tutorials]]

A Web Orbiter is any device (such as a laptop, PC, etc.) that accesses the Orbiter user interface (UI) through a Web browser.

There is now a new version of WebOrbiter (WebOrbiter 2.0) please click [[Web_Orbiter_2.0|here]] for setup instructions.

== Setup ==
The procedure to setup a Web Orbiter is simple but the order of steps is important.
#First of all, add a new Generic Web Device as a Child Device for your Core:
##Goto the LinuxMCE Admin website-->Show devices tree-->CORE. The CORE's detail page should appear.
##Click 'Create Child Device'.
##In the Description, enter the name of the specific web orbiter.
##In the Add child device window, click the button 'Pick device template'. The new pop-up window containing device templates will be opened.
##In the 'Device Category' dropdown list, choose 'Peripherals'.
##In the 'Device Template' dropdown list, find and select "Generic Web Device" (or just 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 show.
##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.
#Do a "[[Quick reload router]]". Otherwise, the Orbiter won't work properly.

==Access to the Web Orbiter==

===From within your home===
You can access the Web Orbiter from any web browser (Mozilla Firefox, IE, Safari):

'''If you are currently using the 810 alpha releases the correct URL is:'''
''<nowiki>http://<core_ip>/lmce-admin/weborbiter.php</nowiki>''

'''The current release 710 uses the information below.'''

*In the browser address bar, type the URL ''<nowiki>http://<core_ip>/pluto-admin/weborbiter.php</nowiki>''.
:* From within the "internal" LinuxMCE LAN, for example:
::::''http://192.168.80.1/pluto-admin/weborbiter.php'' (0710)
::::''http://192.168.80.1/lmce-admin/weborbiter.php'' (0810)
:::::(This assumes the IP address range set by default at installation.)
:*You can also use the network name of the Core in place of the IP address. For example, if the Core was named "dcerouter" during the default installation, you could use:
::::''<nowiki>http://dcerouter/pluto-admin/weborbiter.php</nowiki>''
:*From the "external" home LAN, the core_ip would be the LAN IP address of the core. If, for example, the core is at 192.168.0.50 on the home LAN, use:
:::: ''<nowiki>http://192.168.0.50/pluto-admin/weborbiter.php</nowiki>''

:::::(Note: To use this method, [[Outside Access]] must be enabled.)

===From the Internet===
You could use the IP address:port for your home LAN, with port forwarding to the Core's LAN IP address (enabled by your home LAN router).
*''This is an advanced topic and may not be secure in the current version.''

By default, LinuxMCE is not accessible outside your home. This makes the system secure, but it prevents you from accessing the web site via the Internet while away from home. You can [[Outside_Access|turn on Internet access]], allowing access to the admin website anywhere. For your own security, however, we recommend you first read about [[Security & Privacy Issues]].

===Login page===
*A simple login page should be displayed. Input an existing user name and password, then click "Login".
*From the dropdown list of devices, choose Generic Web Device.
*A page that looks similar to this should appear: [[Image:Web Orbiter.jpg|center]]

==Troubleshooting==
===Connect failed===
If you try to connect to the Web Orbiter and see this message:
<code>"Connect to proxy orbiter failed, please try again"</code>,
this means that Orbiter generation hasn't finished yet, or that you forgot to do a [[Quick_reload_router|quick restart of the router]].

=== Size ===
I was able to change the size of the rendered image in the Wizard-->Orbiters page. Find the Web Orbiter device in the list and resize it. After another orbiter regen, it was the right size for me. (''Source http://forum.linuxmce.org/index.php?topic=3833.0'')

=== Problems with rapid refresh rate ===

Problem:
When using the Web Orbiter over the Internet (instead of from within my home LAN), it refreshed every 5 seconds, making it difficult to use. The images were repeatedly downloaded each time.

Solution:
*Go to [[LinuxMCE Admin Website]]-->Device tree-->CORE-->Generic Web Device-->Device Data
*Set the Refresh Interval to a higher value (I used 60 seconds for mine).

=== Changing default room ===
Changing the default room in the Wizard-->Devices-->Orbiters page has no effect.

Solution:
*Go to [[LinuxMCE Admin Website]]-->Device tree-->CORE-->Generic Web Device
*Check the box for the room to control

===Screen Deadlock===
If the screen of your orbiter becomes "frozen" or stuck and orbiter regens and router reloads do not resolve the issue, run this from the core:
sudo killall -9 Proxy_Orbiter
(Source: http://forum.linuxmce.org/index.php?topic=6844.0)
= See also =
Another example of a web orbiter is the [[IOrbiter]]
WebOrbiter has also been rebuilt from the ground up as [[Web_Orbiter_2.0]]

Web Orbiter

2010-08-19T15:25:18Z

OmeGa:

Web Orbiter

2010-08-19T15:24:45Z

OmeGa:

{{versioninfo}}
{| align="right"
| __TOC__
|}
[[Category: Orbiters]]
[[Category: Tutorials]]

A Web Orbiter is any device (such as a laptop, PC, etc.) that accesses the Orbiter user interface (UI) through a Web browser.

There is now a new version of WebOrbiter (WebOrbiter 2.0) please click [[WebOrbiter 2.0|here]] for setup instructions.

== Setup ==
The procedure to setup a Web Orbiter is simple but the order of steps is important.
#First of all, add a new Generic Web Device as a Child Device for your Core:
##Goto the LinuxMCE Admin website-->Show devices tree-->CORE. The CORE's detail page should appear.
##Click 'Create Child Device'.
##In the Description, enter the name of the specific web orbiter.
##In the Add child device window, click the button 'Pick device template'. The new pop-up window containing device templates will be opened.
##In the 'Device Category' dropdown list, choose 'Peripherals'.
##In the 'Device Template' dropdown list, find and select "Generic Web Device" (or just 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 show.
##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.
#Do a "[[Quick reload router]]". Otherwise, the Orbiter won't work properly.

==Access to the Web Orbiter==

===From within your home===
You can access the Web Orbiter from any web browser (Mozilla Firefox, IE, Safari):

'''If you are currently using the 810 alpha releases the correct URL is:'''
''<nowiki>http://<core_ip>/lmce-admin/weborbiter.php</nowiki>''

'''The current release 710 uses the information below.'''

*In the browser address bar, type the URL ''<nowiki>http://<core_ip>/pluto-admin/weborbiter.php</nowiki>''.
:* From within the "internal" LinuxMCE LAN, for example:
::::''http://192.168.80.1/pluto-admin/weborbiter.php'' (0710)
::::''http://192.168.80.1/lmce-admin/weborbiter.php'' (0810)
:::::(This assumes the IP address range set by default at installation.)
:*You can also use the network name of the Core in place of the IP address. For example, if the Core was named "dcerouter" during the default installation, you could use:
::::''<nowiki>http://dcerouter/pluto-admin/weborbiter.php</nowiki>''
:*From the "external" home LAN, the core_ip would be the LAN IP address of the core. If, for example, the core is at 192.168.0.50 on the home LAN, use:
:::: ''<nowiki>http://192.168.0.50/pluto-admin/weborbiter.php</nowiki>''

:::::(Note: To use this method, [[Outside Access]] must be enabled.)

===From the Internet===
You could use the IP address:port for your home LAN, with port forwarding to the Core's LAN IP address (enabled by your home LAN router).
*''This is an advanced topic and may not be secure in the current version.''

By default, LinuxMCE is not accessible outside your home. This makes the system secure, but it prevents you from accessing the web site via the Internet while away from home. You can [[Outside_Access|turn on Internet access]], allowing access to the admin website anywhere. For your own security, however, we recommend you first read about [[Security & Privacy Issues]].

===Login page===
*A simple login page should be displayed. Input an existing user name and password, then click "Login".
*From the dropdown list of devices, choose Generic Web Device.
*A page that looks similar to this should appear: [[Image:Web Orbiter.jpg|center]]

==Troubleshooting==
===Connect failed===
If you try to connect to the Web Orbiter and see this message:
<code>"Connect to proxy orbiter failed, please try again"</code>,
this means that Orbiter generation hasn't finished yet, or that you forgot to do a [[Quick_reload_router|quick restart of the router]].

=== Size ===
I was able to change the size of the rendered image in the Wizard-->Orbiters page. Find the Web Orbiter device in the list and resize it. After another orbiter regen, it was the right size for me. (''Source http://forum.linuxmce.org/index.php?topic=3833.0'')

=== Problems with rapid refresh rate ===

Problem:
When using the Web Orbiter over the Internet (instead of from within my home LAN), it refreshed every 5 seconds, making it difficult to use. The images were repeatedly downloaded each time.

Solution:
*Go to [[LinuxMCE Admin Website]]-->Device tree-->CORE-->Generic Web Device-->Device Data
*Set the Refresh Interval to a higher value (I used 60 seconds for mine).

=== Changing default room ===
Changing the default room in the Wizard-->Devices-->Orbiters page has no effect.

Solution:
*Go to [[LinuxMCE Admin Website]]-->Device tree-->CORE-->Generic Web Device
*Check the box for the room to control

===Screen Deadlock===
If the screen of your orbiter becomes "frozen" or stuck and orbiter regens and router reloads do not resolve the issue, run this from the core:
sudo killall -9 Proxy_Orbiter
(Source: http://forum.linuxmce.org/index.php?topic=6844.0)
= See also =
Another example of a web orbiter is the [[IOrbiter]]

Web Orbiter 2.0

2010-08-19T15:15:54Z

OmeGa: /* Good skins for small screens */

Web Orbiter 2.0

2010-08-19T14:58:00Z

OmeGa: /* iPhone (pre iPhone 4) or iPad Touch */

{{versioninfo|810Status=Relevant|810UpdatedDate=23rd July 2010|810UpdatedBy=Purps}}
{| align="right"
| __TOC__
|}
[[Category: Orbiters]]
[[Category: Tutorials]]

A Web Orbiter is any device (such as a iPhone, iPod Touch, iPad, laptop, PC, etc.) that accesses the Orbiter user interface (UI) through a Web browser.

The new Web Orbiter 2.0 has been re-written from the ground up to make sure it has a much smoother performance overall but especially on slower lower powered devices and devices that are connected over slow LAN connections or even slower external connections...such as a Mobile 3G network or slow WiFi connection.

So what has changed? Well visually your Orbiter UI will look like it does on your existing standard Orbiters but you will notice that unlike the original Web Orbiter the new 2.0 version does not refresh every 5 secs. The new Web Orbiter now only updates if something changes in the system and that requires the UI screen you are currently viewing to be updated or if you click on a UI button or other UI element and that causes a screen update.

To achieve this the proxy_orbiter has been updated so that it sets a flag called 'ANYNEWS' to 'true' if some element of the current displayed screen has been updated. The Web Orbiter makes a light weight call to query the state of this flag once every second and only gets an updated UI screen if the flag is set to 'true' otherwise no screen update is requested. So in use the new Web Orbiter 2.0 behaves in a very similar fashion to the Orbiter on one of your MD's - and now it even performs with a similar performance level too.

Whats a proxy_orbiter? Proxy_orbiter runs on the Core and its job is to render the UI for the Web Orbiter that is running remotely on some other device. Each Web Orbiter has an associated proxy_orbiter and the two work in partnership. Proxy_orbiters do all the 'heavy lifting' rendering the UI and this allows the remote device that is running the Web Orbiter to be much less powerful and very simple devices indeed if needed.

Another change in the new 2.0 Web Orbiter is that screen refreshes are double buffered so that the new Web Orbiter receives the new screen update from your Core in the background and only redraws the screen when it has the complete image stored in memory - this makes the update process smoother and faster.

The overall effect of all these changes is to vastly improve the performance and usability while at the same time reducing the processing overhead of the Web Orbiter massively.

== Setup ==
The procedure to setup a Web Orbiter is simple but the order of steps is important.
#First of all, add a new Generic Web Device as a Child Device for your Core:
##Goto the LinuxMCE Admin website-->Show devices tree-->CORE. The CORE's detail page should appear.
##Click 'Create Child Device'.
##In the Description, enter the name of the specific web orbiter.
##In the Add child device window, click the button 'Pick device template'. The new pop-up window containing device templates will be opened.
##In the 'Device Category' dropdown list, choose 'Peripherals'.
##In the 'Device Template' dropdown list, find and select "Generic Web Device" (or just 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 show.
##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 device your Web Orbiter is intended for from the 'Size' drop down
#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.

==Device Screen Resolutions==
If the 'Device' your planning to use your Web Orbiter on is a Desktop or Laptop then use the biggest resolution that will comfortably fit onto your screen. If your device is a touch screen device like an iPad, iPhone or iPod Touch then choose a resoltion that matches the overall resolution of the devices display;

===iPad===
The iPad has a screen resolution of 1024x768 so if your creating an Orbiter for the iPad this is the resolution you should select for this Web Orbiter.

===iPhone (pre iPhone 4) or iPad Touch===
The iPhone/iPod Touch have a screen resolution of 480x320 so if your creating an Orbiter for either of these this is the resolution you should select for this Web Orbiter.

===iPhone 4===
The iPhone 4 has a screen resolution of 960x640 so if your creating an Orbiter for the iPhone 4 this is the resolution you should select for this Web Orbiter.

===Google Nexus One or HTC Desire (Android)===
If you have a Nexus One you will need to select a resolution of 480x800 (select N770 in the web admin, it is 480x800) so if your creating an Orbiter for the Nexus One this is the resolution you should select for this Web Orbiter.

On the HTC Desire you might also have to go into the web browser settings and change the default zoom to "far away" (mine is danish, so don't know the exact english decription). After that it should be full screen.

===Nokia 5800 XpressMusic===
For a fullscreen orbiter, iPhone resolution 480x320 works quite well. For a screen that's full width (but requires some vertical scrolling), 640x480 (Standard TV) works well. This resolution allows for easier reading of some orbiter buttons, without the need for zooming in.

===Nintendo DSi===
Best screen resolution, 480x320 so far. Lower resolutions may work well also with "Mobile Phone Basic" skin applied.

==Good skins for small screens==

here we should list the skins that can be used on the smaller screens of Phones and alike.

The skin "Mobile Phone Basic" is OK readable on the HTC Desire at 480x800.

==Access to the Web Orbiter==

===From within your home===
You can access the Web Orbiter 2.0 from any of the following Web browsers (Google Chrome, Mozilla Firefox, Safari). Others may also work but have not been tested (your experiences with other web browsers would be welcome here) :

'''For the 810 releases the correct URL is:'''
''<nowiki>http://<core_ip>/lmce-admin/weborbiter.php</nowiki>''

:* From within the "internal" LinuxMCE LAN, for example:
::::''http://192.168.80.1/lmce-admin/weborbiter.php'' (0810)
:::::(This assumes the IP address range set by default at installation.)
:*You can also use the network name of the Core in place of the IP address. For example, if the Core was named "dcerouter" during the default installation, you could use:
::::''<nowiki>http://dcerouter/pluto-admin/weborbiter.php</nowiki>''
:*From the "external" WAN side of the Core, the core_ip would be the WAN IP address of the core (ie the one offered to the WAN side NIC on the Core by your broadband Router). If, for example, the core has a WAN side address of 192.168.0.50 offered up by your Broadband Router, use:
:::: ''<nowiki>http://192.168.0.50/lmce-admin/weborbiter.php</nowiki>''

:::::(Note: To use this method, [[Outside Access]] must be enabled.)

===From the Internet===
You could use the IP address:port for your home LAN, with port forwarding to the Core's LAN IP address (enabled by your home LAN router).
*''This is an advanced topic and may not be secure in the current version.''

By default, LinuxMCE is not accessible outside your home. This makes the system secure, but it prevents you from accessing the web site via the Internet while away from home. You can [[Outside_Access|turn on Internet access]], allowing access to the admin website anywhere. For your own security, however, we recommend you first read about [[Security & Privacy Issues]].

===Login page===
*A simple login page should be displayed. Input an existing user name and password, then click "Login".
*From the dropdown list of devices, choose the Web Orbiter you would like to use and click or touch 'Open'. If you have got several web orbiters in your system then they will be displayed in the dropdown and you can choose which one to use. (only one user can use any Web Orbiter at a given time)
*A page that looks similar to this should appear: [[Image:Web Orbiter.jpg|center]]
*Here is another UI1 variation loaded into Web Orbiter 2.0: [[Image:web_orbiter_20_in_chrome1.jpg|center]]
*This image is of Web Orbiter 2.0 running on an iPod Touch: [[Image:Web orbiter on iPod Touch4.JPG|center]]

==Where is the Web Orbiter code on my system?==

===Look in the following directories on your Core===

Look in;
/var/www/lmce-admin/

You will see the following Web Orbiter related files (there are many other unrelated files in this directory too);

weborbiter_command.php
weborbiter_image.php
weborbiter.php

Look in;
/var/www/lmce-admin/weborbiter

You should see the following files;

IT.php
jquery.min.js
jquery.timers.js
login.html
waiting.gif
weborbiter.css
weborbiter.html
weborbiter.js
weborbiter_select.html

==Devices that have been tested with Web orbiter 2.0==
This is a simple list of devices that have been tested with Web Orbiter 2.0. If you have got a new device to add to this list then please add it below...or if you have some experiences with a device already listed then please add some simple notes here too.

===Ipad===

===iPod===

===iPhone 3GS===

===iPhone 4===

===HTC Hero (Android 1.6)===

===HTC Desire (Android 2.1)===
Screen size is a little bit small I think, it is difficult to hit the up/down keys.

===Nokia N800===

===Nokia N900===

===Nokia 5800 XpressMusic===
Both "S60 Browser" (default) and "Opera Mobile" work well.

===Nintendo DSi===

===Eken M002===

See M002 info here [[Eken_m002]]. See video of the M002 running Web Orbiter 2.0 here; [http://www.youtube.com/watch?v=eA0SaYYQb7E Eken m002]

==Web Orbiter 2.0 has been tested on the following browsers==

===Firefox 3.6===
Works fine.

===Chrome 6.0.453.1 dev===
Works fine.

Also works fine as a chrome application shortcut.
Just create the shortcut when you are logged into the orbiter and have the right device chosen.

===OperaMini===
Works fine.

===OperaMobile 10===
Works fine.

===Midori 0.2.2===
Works fine.

===Internet Explorer===
Not working due to javascript issues.

===S60 Browser===
Default Symbian browser - works fine (tested on Nokia 5800 XpressMusic)

===Nintendo DSi Browser===
(based on Opera)

==Troubleshooting==
===Connect failed===
If you try to connect to the Web Orbiter and see this message:
<code>"Connect to proxy orbiter failed, please try again"</code>,
this means that Orbiter generation hasn't finished yet, or that you forgot to do a [[Quick_reload_router|quick restart of the router]].

Wiring Considerations

2010-03-22T14:36:15Z

OmeGa:

{| align="right"
| __TOC__
|}
[[Category: Networking]]
==Introduction==

Older, proprietary home automation and security systems traditionally have required their own dedicated wiring. Placing that wiring was often the biggest hurdle in installing such systems, and usually entailed tearing open walls in order to run the special cables (which was often very thick and difficult to manage).

In contrast, LinuxMCE uses standard Ethernet wiring and jacks. Because it is IP (Internet Protocol) based (the same protocol that runs the Internet and most local home and office networks), it runs directly over an Ethernet network. Ethernet networks use standard CAT5 (or CAT5e/CAT6) wiring with RJ-45 jacks. This wiring is often already pre-installed in recently-constructed homes, since it is now also used for many phone systems as well as for home networks. Even if your home does not already have CAT5e/CAT6 wiring pre-installed, CAT5e/CAT6 wires are some of the smaller, easier wires to install. Installing CAT5e/CAT6 wiring in a house is well worth the cost and will increase the resale value, even without a LinuxMCE system. Home networks (LANs) that are run over CAT5e-wired Ethernet connections are increasingly popular for Internet access and file/printer sharing throughout the home.

Thus, the only wiring requirement for LinuxMCE is that you have Ethernet (CAT5e/CAT6) wiring. All wired LinuxMCE devices (such as a PC used as a Media Director) will be able to directly plug into the RJ45 jack.

==Wired vs. wireless connections==

Note, however, that not all LinuxMCE devices require a wired connection. Many can connect [[Wireless Networking|wirelessly]], if you have a wireless access point connected to the LinuxMCE [[Core]] server. However, it is easiest for the main components, the [[Core]] and the [[Media Directors]], to be connected in a wired fashion.

==CAT5 vs. CAT5e vs. CAT6 vs. Fiber-optic==

*CAT5 wiring uses the smallest gauge wires, which are stranded. It was the standard for many years and can be used for data speeds up to 100 Mb/sec. However, the increased speeds and loads of modern LANs place a strain on the characteristics of this wire. It is no longer recommended as the wiring standard. In general 100 Mb/sec speeds can transmit 7 simultaneous DVD quality video streams.

*CAT5e wiring was recently used as the wiring standard, and uses a somewhat higher gauge solid wire. This enables the transmission of data at 250 Mb/sec to 1000 Mb/sec (Gigabit), used by newer LANs. At these speeds, it is more reliable over long distances. In general, Gigabit data transmission speeds can transmit 100 simultaneous DVD quality video streams (over short distances).

*CAT6 wiring uses even higher gauge wires. It is preferred for Gigabit speeds (1000 Mb/sec to 10,000 Mb/sec), especially over long distances. Until recently, such speeds were not common, but rapid advancements in routers have made Gigabit networks the norm. Therefore, CAT6 wire should be installed whenever possible.

Obviously, even if you use higher gauge CAT5e and CAT6 wires, you will not achieve the higher data transmission speeds unless all your network components (cables, connectors, network cards, switches, etc.) also support higher data transmission speeds.

*Fiber optic cables theoretically have the highest transmission rate, but are currently expensive and difficult to install (because if they are bent during installation the fibers can break). Routers to connect to fiber optic cables are not readily available for the consumer, either. However, this is the ultimate in forward-thinking cabling for your house, and it will not be long before fiber optic cable will be standard in home construction. Fiber optic cables will replace your phone, television cable, and ethernet cables, so that one fiber optic cable will carry all those signals.

*Many commercial buildings use conduits for cabling, to allow easy cable runs and replacement of existing cables in the future. Conduits can be made of simple PVC pipes (like those used for irrigation), but most builders are reluctant to install them. Nevertheless, they do not take much effort to install during a new home construction, are not expensive, and provide superior protection for cables, especially fragile fiber optic cables. They will also prevent chewing on cables by varmints (such as squirrels and mice).

==Using pre-installed CAT5 placed for telephone systems==

It is possible but not wise to use the same wire for the telephone system and the LAN (see the discussion page for more details). Telephone systems run their own power over the CAT5 lines in a configuration different from Ethernet devices. If you connect an Ethernet device to a live telephone line, you can burn out the Ethernet device unless you are very careful about tracing the leads. While some users have wired analog phone and ethernet on the same CAT5 wire, it is strongly discouraged.

However, most new telephone installations include redundant CAT5 wires that are not connected to the telephone system. (For example, my home is wired with two CAT5 wires to each location, one connected to a telephone jack and one left unconnected.)

It is very easy to use a redundant CAT5 wire for the LAN by connecting it to an additional RJ-45 jack, which can then be added to the same outlet. The wire must then be traced to the other end, which will almost always be at the telephone patch panel for your home (where hopefully it will also be unconnected) and connected to the LAN there, instead. (This presumes, of course, that at the location of the telephone patch panel you have a router, switch, or RJ45 connection (to the rest of your LAN) to which you can connect this wire (using an RJ-45 connector).)

==Ethernet wiring standards==
It is important to note that there are two wiring standards for Ethernet, T568A and T568B. My local electrician was clueless about this and wired all my CAT5 connections wrong.

For a quick tutorial, see [http://www.ertyu.org/steven_nikkel/ethernetcables.html this guide on wiring Ethernet connections].

Most Ethernet wiring is currently done using the T568B standard, and I highly recommend you stick to it. However, you must be aware of deviations from this standard. For example, my Ethernet-wired surveillance cameras all use the T568A standard. This took me a long time to figure out, and, again, my electrician wired them all incorrectly.

It is tricky to adapt T568A to T568B -- you need a special type of cross-over cable. This is somewhat complex. For the most part, I recommend you just wire everything using the T568B standard.

==Audio cabling==
In some instances, you may wish to install cabling for audio signals (line in/out audio, speakers, etc.) to or from your LinuxMCE system. If an audio cable is close to the power lines, the audio cable will pick up 50 or 60 Hz frequency power line noise. This will cause a "humming" in your audio signal which is very annoying. In general low-volt audio wires should be at least 18 inches away from power lines, not run parallel to power lines for more than 2 feet, and should cross perpindicular to power lines whenever possible. If you are planning to install audio cabling in your home, take a look at the [http://www.hometech.com/learn/audio.html Whole-House Audio Tutorial] from HomeTech Solutions. (It is not LinuxMCE specific but is very informative.)

Also see:
[http://en.wikipedia.org/wiki/EIA_568A What is proper CAT5 cabling?]

[http://www.crutchfield.com/Learn/learningcenter/home/inwall_wiring.html In-wall Wiring Guide]

Wiring Considerations

2010-03-22T14:35:43Z

OmeGa:

{| align="right"
| __TOC__
|}
[[Category: Networking]]
==Introduction==

Older, proprietary home automation and security systems traditionally have required their own dedicated wiring. Placing that wiring was often the biggest hurdle in installing such systems, and usually entailed tearing open walls in order to run the special cables (which was often very thick and difficult to manage).

In contrast, LinuxMCE uses standard Ethernet wiring and jacks. Because it is IP (Internet Protocol) based (the same protocol that runs the Internet and most local home and office networks), it runs directly over an Ethernet network. Ethernet networks use standard CAT5 (or CAT5e/CAT6) wiring with RJ-45 jacks. This wiring is often already pre-installed in recently-constructed homes, since it is now also used for many phone systems as well as for home networks. Even if your home does not already have CAT5e/CAT6 wiring pre-installed, CAT5e/CAT6 wires are some of the smaller, easier wires to install. Installing CAT5e/CAT6 wiring in a house is well worth the cost and will increase the resale value, even without a LinuxMCE system. Home networks (LANs) that are run over CAT5e-wired Ethernet connections are increasingly popular for Internet access and file/printer sharing throughout the home.

Thus, the only wiring requirement for LinuxMCE is that you have Ethernet (CAT5e/CAT6) wiring. All wired LinuxMCE devices (such as a PC used as a Media Director) will be able to directly plug into the RJ45 jack.

==Wired vs. wireless connections==

Note, however, that not all LinuxMCE devices require a wired connection. Many can connect [[Wireless Networking|wirelessly]], if you have a wireless access point connected to the LinuxMCE [[Core]] server. However, it is easiest for the main components, the [[Core]] and the [[Media Directors]], to be connected in a wired fashion.

==CAT5 vs. CAT5e vs. CAT6 vs. Fiber-optic==

*CAT5 wiring uses the smallest gauge wires, which are stranded. It was the standard for many years and can be used for data speeds up to 100 Mb/sec. However, the increased speeds and loads of modern LANs place a strain on the characteristics of this wire. It is no longer recommended as the wiring standard. In general 100 Mb/sec speeds can transmit 7 simultaneous DVD quality video streams.

*CAT5e wiring was recently used as the wiring standard, and uses a somewhat higher gauge solid wire. This enables the transmission of data at 250 Mb/sec to 1000 Mb/sec (Gigabit), used by newer LANs. At these speeds, it is more reliable over long distances. In general, Gigabit data transmission speeds can transmit 100 simultaneous DVD quality video streams (over short distances).

*CAT6 wiring uses even higher gauge wires. It is preferred for Gigabit speeds (1000 Mb/sec to 10,000 Mb/sec), especially over long distances. Until recently, such speeds were not common, but rapid advancements in routers have made Gigabit networks the norm. Therefore, CAT6 wire should be installed whenever possible.

Obviously, even if you use higher gauge CAT5e and CAT6 wires, you will not achieve the higher data transmission speeds unless all your network components (cables, connectors, network cards, switches, etc.) also support higher data transmission speeds.

*Fiber optic cables theoretically have the highest transmission rate, but are currently expensive and difficult to install (because if they are bent during installation the fibers can break). Routers to connect to fiber optic cables are not readily available for the consumer, either. However, this is the ultimate in forward-thinking cabling for your house, and it will not be long before fiber optic cable will be standard in home construction. Fiber optic cables will replace your phone, television cable, and ethernet cables, so that one fiber optic cable will carry all those signals.

*Many commercial buildings use conduits for cabling, to allow easy cable runs and replacement of existing cables in the future. Conduits can be made of simple PVC pipes (like those used for irrigation), but most builders are reluctant to install them. Nevertheless, they do not take much effort to install during a new home construction, are not expensive, and provide superior protection for cables, especially fragile fiber optic cables. They will also prevent chewing on cables by varmints (such as squirrels and mice).

==Using pre-installed CAT5 placed for telephone systems==

It is possible but not wise to use the same wire for the telephone system and the LAN (see the discussion page for more details). Telephone systems run their own power over the CAT5 lines in a configuration different from Ethernet devices. If you connect an Ethernet device to a live telephone line, you can burn out the Ethernet device unless you are very careful about tracing the leads. While some users have wired analog phone and ethernet on the same CAT5 wire, it is strongly discouraged.

However, most new telephone installations include redundant CAT5 wires that are not connected to the telephone system. (For example, my home is wired with two CAT5 wires to each location, one connected to a telephone jack and one left unconnected.)

It is very easy to use a redundant CAT5 wire for the LAN by connecting it to an additional RJ-45 jack, which can then be added to the same outlet. The wire must then be traced to the other end, which will almost always be at the telephone patch panel for your home (where hopefully it will also be unconnected) and connected to the LAN there, instead. (This presumes, of course, that at the location of the telephone patch panel you have a router, switch, or RJ45 connection (to the rest of your LAN) to which you can connect this wire (using an RJ-45 connector).)

==Ethernet wiring standards==
It is important to note that there are two wiring standards for Ethernet, T568A and T568B. My local electrician was clueless about this and wired all my CAT5 connections wrong.

For a quick tutorial, see [http://www.ertyu.org/steven_nikkel/ethernetcables.html this guide on wiring Ethernet connections].

Most Ethernet wiring is currently done using the T568B standard, and I highly recommend you stick to it. However, you must be aware of deviations from this standard. For example, my Ethernet-wired surveillance cameras all use the T568A standard. This took me a long time to figure out, and, again, my electrician wired them all incorrectly.

It is tricky to adapt T568A to T568B -- you need a special type of cross-over cable. This is somewhat complex. For the most part, I recommend you just wire everything using the T568B standard.

==Audio cabling==
In some instances, you may wish to install cabling for audio signals (line in/out audio, speakers, etc.) to or from your LinuxMCE system. If an audio cable is close to the power lines, the audio cable will pick up 50 or 60 Hz frequency power line noise. This will cause a "humming" in your audio signal which is very annoying. In general low-volt audio wires should be at least 18 inches away from power lines, not run parallel to power lines for more than 2 feet, and should cross perpindicular to power lines whenever possible. If you are planning to install audio cabling in your home, take a look at the [http://www.hometech.com/learn/audio.html Whole-House Audio Tutorial] from HomeTech Solutions. (It is not LinuxMCE specific but is very informative.)

Also see:
[http://en.wikipedia.org/wiki/EIA_568A What is proper CAT5 cabling?]
[http://www.crutchfield.com/Learn/learningcenter/home/inwall_wiring.html In-wall Wiring Guide]

MD Usplash

2010-03-18T13:16:24Z

OmeGa:

[[Category:Tutorials]]

== Overview ==

Booting up our cores, we always had the usplash from Kubuntu. However, when an MD or Media Director boots up
we always had to look at lines and lines of text. Well those days are over.

See it in action: [http://www.youtube.com/watch?v=sW4AwtD2GG8 MD Action Video]

== Special Thanks ==

This Usplash that we will be using was created by castlec. He handled the graphics, I just put the pieces
together in resolving how to get usplash to work on the diskless/non-grub booting MD's.
Below are the steps I used to make it happen.

== Procedure ==

The first part takes place on the booted up Media Director.
To get to it log into the core via ssh and become root:

sudo su

Next ssh into the MD you wish to work on:

ssh moon72 <your number my be different of course, you should be able to spot it when your MD is booting up>

cd /usr/lib/usplash

mv usplash-theme-kubuntu.so usplash-theme-kubuntu.so.orig

wget http://dataless.jeromenet.org/lmce-stuff/usplash.tar

tar xvf usplash.tar

cd /etc/alternatives

rm usplash-artwork.so

ln -s /usr/lib/usplash/usplash-theme-kubuntu.so /etc/alternatives/usplash-artwork.so

update-initramfs -u

Find the MAC address of this MD, and write it down, we will need it in the next step:

ifconfig | grep HWaddr

The second part tkes place on the core as root user.

cd /tftpboot/pxelinux.cfg

vi <MAC Address of MD>

Find the kernel append line, it will look like this:

APPEND initrd=72/initrd.img ramdisk=10240 rw root=/dev/nfs boot=nfs nfsroot=192.168.80.1:/usr/pluto/diskless/72

Add "quiet" and "splash" to this line so it now looks like below:

APPEND initrd=72/initrd.img quiet splash ramdisk=10240 rw root=/dev/nfs boot=nfs nfsroot=192.168.80.1:/usr/pluto/diskless/72

Save the file and reboot. That is all it takes.

Now you can sit back and enjoy your new MD boot screen.

--[[User:Sethj|Sethj]] 04:29, 18 March 2010 (CET)

I also found that if the usplash init script is moved to later in the process, we get a bit more splash and a bit less text
rm /etc/rc2.d/S98usplash && ln -s /etc/init.d/usplash /etc/rc2.d/S99usplash

--[[User:castlec|castlec]] 11:35, 18 March 2010 (EDT)

Installing 0810

2010-03-16T14:23:19Z

OmeGa:

Installing LinuxMCE-0810 is a fairly easy process that involves:
* Installing Kubuntu 8.10
* Updating Kubuntu 8.10
* Installing LinuxMCE-0810 on top of the updated Kubuntu 8.10

Before proceeding its wise to read the FAQ.
Because of the fact that its a delicate installation small things make a huge difference.

Please see below for details on Internet Installation and DVD Installation methods.

==Internet Installation==
# Install Kubuntu Intrepid desktop and update it. (download Kubuntu 8.10 '''desktop''' release from one of these: [http://mirrors.ccs.neu.edu/releases.ubuntu.com/kubuntu/8.10/ Northeastern University Mirror, USA], [http://swtsrv.informatik.uni-mannheim.de/pub/linux/distributions/ubuntu-release/kubuntu/8.10/ Mannheim University Mirror, Germany]) '''Currently, only the 32bit version of LinuxMCE is available. Only download the i386 version of 8.10 Kubuntu, even if your system can support 64bit versions.''' Note: If Kubuntu asks whether you would like to install/activate 'Restricted Drivers' for your video card, ignore it and continue to step 2.
# Run aptitude update and aptitude dist-upgrade to get the latest Kubuntu updates.
# Grab the latest installer script from [http://deb.linuxmce.org/ubuntu here], unpack them and change into the freshly created ''new-installer'' directory.
# Run the following scripts (as root, in order): pre-install-from-repo.sh, mce-install.sh, post-install.sh.
# Reboot, wait for the activity to stop (see progress on console 8).

'''EDIT: MAKE SURE YOUR INTERNET CONNECTION IS ON ETH0!''' (For linux Newbies ETH0 is probably the network card on your motherboard...or plug all NICs into a switch that has Internet access)

In other words, after installing Kubuntu:
sudo su - #This might ask for the password you specified earlier during the install of kubuntu.
apt-get update
sudo apt-get dist-upgrade
wget -c http://deb.linuxmce.org/ubuntu/new-installer-latest.tar.gz
tar xvf new-installer-latest.tar.gz
cd new-installer
./pre-install-from-repo.sh
./mce-install.sh
./post-install.sh
reboot

[[User:GargFunk|GargFunk]] 08:41, 19 January 2010 (CET): ''In my experience, the sources.list after this process contained
deb http://www.avenard.org/files/ubuntu-repos/ intrepid testing
''where it should have contained
deb http://www.avenard.org/files/ubuntu-repos/ intrepid release
''Fixing that error solved several problems including "LaunchOrbiter.sh not found" and libvpdau1 not being installable. Caveat Installer.''

==DVD Installation==

However, if you want to install the DVD, grab it via the torrent [http://www.linuxmce.org/index.php/download here].

Upon DVD boot, select LinuxMCE install(it is the bottom option). This will install a regular Kubuntu 810 system, with an additional button on the desktop to install LinuxMCE upon restart. Let Kubuntu's install run through, and after restart, login.
Open a terminal and run
sudo su - #This might ask for the password you specified earlier during the install of kubuntu.
apt-get update
sudo apt-get dist-upgrade

Once you have done this, you can go to the Desktop and double click on the LinuxMCE icon. This will run the fullinstall.sh in /root/new-installer and install LinuxMCE-0810 on top of you updated Kubuntu installation.

The DVD installer per default does not create the initial [[MD|MD]] image, as that creation takes a very long time, and most people probably prefer to give 810 a test, without the MDs. If you want to setup MDs, you have to manually run
/usr/pluto/bin/Diskless_CreateTBZ.sh
(You should only have to do this once)

If you have problems running Diskless_CreateTBZ.sh, check [[Error Running Diskless CreateTBZ.sh|this article]].

If you then have problems netbooting your diskless media directors because you are receiving the error message "Diskless Setup Failed", check [[Diskless setup failed error in 0810 beta|this article]].

Note 21/01/2010: If MythTV fails to correctly install it may be due to some changes in the avenard repository. See the following thread for a fix: [http://forum.linuxmce.org/index.php?topic=9513.msg65087#msg65087]

== Keeping Up-to-date with updates ==
Once you have installed LinuxMCE-0810, all you need to do to keep up-to-date with the latest and greatest, is run the following from a terminal on the core and each MD:
sudo apt-get update
sudo apt-get upgrade
Note: You should NOT run apt-get dist-upgrade after LinuxMCE is installed, as it can cause several problems, including having different kernel versions on your core and media directors, and the installation of new Kubuntu packages that can break some features!

[[Category:Tutorials]]

Installing 0810

2010-03-16T14:22:31Z

OmeGa:

Installing LinuxMCE-0810 is a fairly easy process that involves:
* Installing Kubuntu 8.10
* Updating Kubuntu 8.10
* Installing LinuxMCE-0810 on top of the updated Kubuntu 8.10

Before proceeding its wise to read the FAQ.
Because of the fact that its a delicate installation small things make a huge difference.

Please see below for details on Internet Installation and DVD Installation methods.

==Internet Installation==
# Install Kubuntu Intrepid desktop and update it. (download Kubuntu 8.10 '''desktop''' release from one of these: [http://mirrors.ccs.neu.edu/releases.ubuntu.com/kubuntu/8.10/ Northeastern University Mirror, USA], [http://swtsrv.informatik.uni-mannheim.de/pub/linux/distributions/ubuntu-release/kubuntu/8.10/ Mannheim University Mirror, Germany]) '''Currently, only the 32bit version of LinuxMCE is available. Only download the i386 version of 8.10 Kubuntu, even if your system can support 64bit versions. If Kubuntu asks whether you would like to install/activate 'Restricted Drivers' for your video card, ignore it and continue to step 2.'''
# Run aptitude update and aptitude dist-upgrade to get the latest Kubuntu updates.
# Grab the latest installer script from [http://deb.linuxmce.org/ubuntu here], unpack them and change into the freshly created ''new-installer'' directory.
# Run the following scripts (as root, in order): pre-install-from-repo.sh, mce-install.sh, post-install.sh.
# Reboot, wait for the activity to stop (see progress on console 8).

'''EDIT: MAKE SURE YOUR INTERNET CONNECTION IS ON ETH0!''' (For linux Newbies ETH0 is probably the network card on your motherboard...or plug all NICs into a switch that has Internet access)

In other words, after installing Kubuntu:
sudo su - #This might ask for the password you specified earlier during the install of kubuntu.
apt-get update
sudo apt-get dist-upgrade
wget -c http://deb.linuxmce.org/ubuntu/new-installer-latest.tar.gz
tar xvf new-installer-latest.tar.gz
cd new-installer
./pre-install-from-repo.sh
./mce-install.sh
./post-install.sh
reboot

[[User:GargFunk|GargFunk]] 08:41, 19 January 2010 (CET): ''In my experience, the sources.list after this process contained
deb http://www.avenard.org/files/ubuntu-repos/ intrepid testing
''where it should have contained
deb http://www.avenard.org/files/ubuntu-repos/ intrepid release
''Fixing that error solved several problems including "LaunchOrbiter.sh not found" and libvpdau1 not being installable. Caveat Installer.''

==DVD Installation==

However, if you want to install the DVD, grab it via the torrent [http://www.linuxmce.org/index.php/download here].

Upon DVD boot, select LinuxMCE install(it is the bottom option). This will install a regular Kubuntu 810 system, with an additional button on the desktop to install LinuxMCE upon restart. Let Kubuntu's install run through, and after restart, login.
Open a terminal and run
sudo su - #This might ask for the password you specified earlier during the install of kubuntu.
apt-get update
sudo apt-get dist-upgrade

Once you have done this, you can go to the Desktop and double click on the LinuxMCE icon. This will run the fullinstall.sh in /root/new-installer and install LinuxMCE-0810 on top of you updated Kubuntu installation.

The DVD installer per default does not create the initial [[MD|MD]] image, as that creation takes a very long time, and most people probably prefer to give 810 a test, without the MDs. If you want to setup MDs, you have to manually run
/usr/pluto/bin/Diskless_CreateTBZ.sh
(You should only have to do this once)

If you have problems running Diskless_CreateTBZ.sh, check [[Error Running Diskless CreateTBZ.sh|this article]].

If you then have problems netbooting your diskless media directors because you are receiving the error message "Diskless Setup Failed", check [[Diskless setup failed error in 0810 beta|this article]].

Note 21/01/2010: If MythTV fails to correctly install it may be due to some changes in the avenard repository. See the following thread for a fix: [http://forum.linuxmce.org/index.php?topic=9513.msg65087#msg65087]

== Keeping Up-to-date with updates ==
Once you have installed LinuxMCE-0810, all you need to do to keep up-to-date with the latest and greatest, is run the following from a terminal on the core and each MD:
sudo apt-get update
sudo apt-get upgrade
Note: You should NOT run apt-get dist-upgrade after LinuxMCE is installed, as it can cause several problems, including having different kernel versions on your core and media directors, and the installation of new Kubuntu packages that can break some features!

[[Category:Tutorials]]