LinuxMCE - User contributions [en]

File:Avetana-bluetooth-license.20080216.tgz.this-file-is-tgz-not-gif.gif

2008-02-16T15:57:42Z

Matthew: Avetana Bluetooth 14-day and unlimited-time development license This file is .tgz (gzipped tar file), not .gif, but the wiki upload rejects .tgz files.

Avetana Bluetooth 14-day and unlimited-time development license

This file is .tgz (gzipped tar file), not .gif, but the wiki upload rejects .tgz files.

PcHDTV HD5500

2008-02-06T15:18:13Z

Matthew: Fix typo in list numbering, text style

[[Category: Hardware]]
[[Category: Video]]
[[Category: TV Cards]]

(Adapted from "Installation Issues" forum post [http://forum.linuxmce.org/index.php?topic=2546.msg23775#msg23775 Re: My LinuxMCE Problems].)

I ([http://forum.linuxmce.org/index.php?action=profile;u=40104 chuckfox]) currently have the latest beta (at February 03, 2008, 04:43:53 am 0710b3) running as a hybrid with a PCHDTV-5500 installed. I am by no means a linux expert, but playing with linuxmce has helped me alot.

=Hardware=
Cheap ECS MOBO + intel dual core + 1 gig mem + 120gig PATA hard drive + PCHDTV-5500

=Installation=
# After a fresh install I navigate to the KDE desktop, then open up a terminal to add a line to '''/etc/modules''' to load the cx88-dvb module on startup.
#: Heres the line to type into the terminal to bring the file up for modification.
#: <pre>kate /etc/modules</pre>
#: This will bring up /etc/modules which is mostly empty. Add the line below on a new line and save the file.
#: <pre>cx88-dvb</pre>
# After saving the file I then goto settings and click on MythTV Backend Setup -mythtv-setup.
#: This will get you a dialog box that will tell you that you need to be added to a user group(Not sure of the exact wording here).
#: Click OK. At this point reboot your machine. (You can use "sudo reboot" without the quotes, at the command line.)
# After reboot navigate to the KDE desktop and goto settings and click on MythTV Backend Setup -mythtv-setup.
#:You should be able to enter mythtvsetup at this point and set up capture cards.
# Set up capture card -You want to pick DVB DTV capture card(v3.x) '''NOT''' pcHDTV DTV capture card(w/V4L drivers).
#: When done you should see a capture card [DVB:0] listed.
# Set up a video source. I have two video sources, one is Digital and one is analog. I subscride to SchedulesDirect to grab the channel data. For both, the Channel frequency table is set to us-cable. (I'm not sure about the PCHDTV-3000, but the 5500 has digital and analog tuners).
# Set up Input Connections. I set up two connections Digital and analog.
#: '''Digital''': choose [DVB:0](DVBInput) -> Digital, add the digital video source you created earlier. Click scan for channels. Select; full scan, cable high, Cable (QAM-256) [If you are connected to cable, otherwise pick the one that applies to you], I like the period to seperate channels and Minimal Updates as the last option.
#: Click next and you should see Scan progress with a mostly(hopefully) full signal meter. Let the scan finish and move on to the analog channels.
#: '''Analog''': choose [V4L:dev/video0](Televison) ->analog, add the analog video source you created earlier. Same process as digital, only scan for cable instead of cable high. This scan should run alot quicker. After both scans I click Fetch channels from listing source, to add the channel data.
# This should get your card working if there are no other conflicts. Here are some things that caught me up along the way.
#: The admin password for the latest beta is linuxmce. You will need to input this a few times, it took me a few minutes of RTFM to find this one.
#: For some reason when exiting myth backend setup the dialog box that asks if I would like to run mythfilldatabase, would not run mythfilldatabase when clicking OK. To resolve this, open a command line and type sudo mythfilldatabase to run the program.

PcHDTV HD5500

2008-02-06T15:13:15Z

Matthew: Cleanup intro

[[Category: Hardware]]
[[Category: Video]]
[[Category: TV Cards]]

(Adapted from "Installation Issues" forum post [http://forum.linuxmce.org/index.php?topic=2546.msg23775#msg23775 Re: My LinuxMCE Problems].)

I ([http://forum.linuxmce.org/index.php?action=profile;u=40104 chuckfox]) currently have the latest beta (at February 03, 2008, 04:43:53 am 0710b3) running as a hybrid with a PCHDTV-5500 installed. I am by no means a linux expert, but playing with linuxmce has helped me alot.

=Hardware=
Cheap ECS MOBO + intel dual core + 1 gig mem + 120gig PATA hard drive + PCHDTV-5500

=Installation=
# After a fresh install I navigate to the KDE desktop, then open up a terminal to add a line to /etc/modules to load the cx88-dvb module on startup.
#: Heres the line to type into the terminal to bring the file up for modification.
#: <pre>kate /etc/modules</pre>
#: This will bring up /etc/modules which is mostly empty. Add the line below on a new line and save the file.
#: <pre>cx88-dvb</pre>
# After saving the file I then goto settings and click on MythTV Backend Setup -mythtv-setup.
#: This will get you a dialog box that will tell you that you need to be added to a user group(Not sure of the exact wording here).
#: Click OK. At this point reboot your machine. (You can use "sudo reboot" without the quotes, at the command line.)
# After reboot navigate to the KDE desktop and goto settings and click on MythTV Backend Setup -mythtv-setup.
#:You should be able to enter mythtvsetup at this point and set up capture cards.
# Set up capture card -You want to pick DVB DTV capture card(v3.x) NOT pcHDTV DTV capture card(w/V4L drivers).
#: When done you should see a capture card [DVB:0] listed.
#: Set up a video source. I have two video sources, one is Digital and one is analog. I subscride to SchedulesDirect to grab the channel data. For both, the Channel frequency table is set to us-cable. (I'm not sure about the PCHDTV-3000, but the 5500 has digital and analog tuners).
# Set up Input Connections. I set up two connections Digital and analog.
#: Digital -choose [DVB:0](DVBInput) -> Digital, add the digital video source you created earlier. Click scan for channels. Select; full scan, cable high, Cable (QAM-256) [If you are connected to cable, otherwise pick the one that applies to you], I like the period to seperate channels and Minimal Updates as the last option.
#: Click next and you should see Scan progress with a mostly(hopefully) full signal meter. Let the scan finish and move on to the analog channels.
#: Analog: choose [V4L:dev/video0](Televison) ->analog, add the analog video source you created earlier. Same process as digital, only scan for cable instead of cable high. This scan should run alot quicker. After both scans I click Fetch channels from listing source, to add the channel data.
# This should get your card working if there are no other conflicts. Here are some things that caught me up along the way.
#: The admin password for the latest beta is linuxmce. You will need to input this a few times, it took me a few minutes of RTFM to find this one.
#: For some reason when exiting myth backend setup the dialog box that asks if I would like to run mythfilldatabase, would not run mythfilldatabase when clicking OK. To resolve this, open a command line and type sudo mythfilldatabase to run the program.

PcHDTV HD5500

2008-02-06T15:11:13Z

Matthew: Create reformatted

[[Category: Hardware]]
[[Category: Video]]
[[Category: TV Cards]]

(Adapted from "Installation Issues" forum post [http://forum.linuxmce.org/index.php?topic=2546.msg23775#msg23775 Re: My LinuxMCE Problems].)
I ([http://forum.linuxmce.org/index.php?action=profile;u=40104 chuckfox]) currently have the latest beta (at February 03, 2008, 04:43:53 am 0710b3) running as a hybrid with a PCHDTV-5500 installed. I am by no means a linux expert, but playing with linuxmce has helped me alot.

=Hardware=
Cheap ECS MOBO + intel dual core + 1 gig mem + 120gig PATA hard drive + PCHDTV-5500

=Installation=
# After a fresh install I navigate to the KDE desktop, then open up a terminal to add a line to /etc/modules to load the cx88-dvb module on startup.
#: Heres the line to type into the terminal to bring the file up for modification.
#: <pre>kate /etc/modules</pre>
#: This will bring up /etc/modules which is mostly empty. Add the line below on a new line and save the file.
#: <pre>cx88-dvb</pre>
# After saving the file I then goto settings and click on MythTV Backend Setup -mythtv-setup.
#: This will get you a dialog box that will tell you that you need to be added to a user group(Not sure of the exact wording here).
#: Click OK. At this point reboot your machine. (You can use "sudo reboot" without the quotes, at the command line.)
# After reboot navigate to the KDE desktop and goto settings and click on MythTV Backend Setup -mythtv-setup.
#:You should be able to enter mythtvsetup at this point and set up capture cards.
# Set up capture card -You want to pick DVB DTV capture card(v3.x) NOT pcHDTV DTV capture card(w/V4L drivers).
#: When done you should see a capture card [DVB:0] listed.
#: Set up a video source. I have two video sources, one is Digital and one is analog. I subscride to SchedulesDirect to grab the channel data. For both, the Channel frequency table is set to us-cable. (I'm not sure about the PCHDTV-3000, but the 5500 has digital and analog tuners).
# Set up Input Connections. I set up two connections Digital and analog.
#: Digital -choose [DVB:0](DVBInput) -> Digital, add the digital video source you created earlier. Click scan for channels. Select; full scan, cable high, Cable (QAM-256) [If you are connected to cable, otherwise pick the one that applies to you], I like the period to seperate channels and Minimal Updates as the last option.
#: Click next and you should see Scan progress with a mostly(hopefully) full signal meter. Let the scan finish and move on to the analog channels.
#: Analog: choose [V4L:dev/video0](Televison) ->analog, add the analog video source you created earlier. Same process as digital, only scan for cable instead of cable high. This scan should run alot quicker. After both scans I click Fetch channels from listing source, to add the channel data.
# This should get your card working if there are no other conflicts. Here are some things that caught me up along the way.
#: The admin password for the latest beta is linuxmce. You will need to input this a few times, it took me a few minutes of RTFM to find this one.
#: For some reason when exiting myth backend setup the dialog box that asks if I would like to run mythfilldatabase, would not run mythfilldatabase when clicking OK. To resolve this, open a command line and type sudo mythfilldatabase to run the program.

DCE from commandline

2008-01-22T00:30:59Z

Matthew: Specify MessageSend command

[[Category: Programmer's Guide]]
=Sending DCE events from command line=
There is a utility in pluto (/usr/pluto/bin/[[MessageSend]]) that allows sending proper DCE message from command line. If you want for instance to trip motion sensors on/off you can achieve this in simple way (ID means ID of particular device that you send event for) :

Event "tripped on"
ID -1000 2 9 25 1

Event "tripped off"
ID -1000 2 9 25 0

Event "temperature changed"
ID -1000 2 25 30 temperature_value

Event "output on"
ID -1000 2 28

Event "output off"
ID -1000 2 29

Event "light on"
ID -1000 2 48 10 1

Event "light off"
ID -1000 2 48 10 0

For instance -

A. tripping security sensor with ID of 195 to ON :
/usr/pluto/bin/MessageSend dcerouter 195 -1000 2 9 25 1

B. play media (/home/public/data/tts/0.wav) on Xine player with ID of 44 :
/usr/pluto/bin/MessageSend localhost 0 44 1 37 29 "" 41 "" 42 "" 59 "/home/public/data/tts/0.wav"

C. report that light with ID of 210 is ON :
/usr/pluto/bin/MessageSend dcerouter 210 -1000 2 48 10 1

=Sending DCE commands from command line=

Change HouseMode command :
I've sniffed DCERouter logs and this is what happens when you change security state from Orbiter :
06 09/11/07 16:06:53.512 Evaluated Event Handler: 1 to: 0 once per: 0 last fired 1189519147 (time is 1189519613)
07 09/11/07 16:06:53.512 Received Message from 13 (Security Plug-in / Utility) to -1001 (unknown / ), type 2 id 43 Event:House Mode Changed, parameters:
07 09/11/07 16:06:53.512 Parameter 38(PK_DeviceGroup): 0
07 09/11/07 16:06:53.512 Parameter 39(PK_HouseMode): 1
08 09/11/07 16:06:53.512 Received Message from 13 (Security Plug-in / Utility) to Apex Destiny 6100(217), type 1 id 19 Command:Set House Mode, parameters:
08 09/11/07 16:06:53.512 Parameter 5(Value To Assign): 1
08 09/11/07 16:06:53.512 Parameter 17(PK_Users): 7
08 09/11/07 16:06:53.512 Parameter 99(Password): 5678
08 09/11/07 16:06:53.512 Parameter 100(PK_DeviceGroup): 0
08 09/11/07 16:06:53.512 Parameter 101(Handling Instructions): R
08 09/11/07 16:06:53.513 Received Message from 13 (Security Plug-in / Utility) to OnScreen Orbiter(20),tinia Symbian Series 60 mobile(31),Lapitopi(38),OnScreen Orbiter(40),OnScreen Orbiter(88),Windows XP PC/tablet (Horiz)(102),Generic Proxy Orbiter(164),Windows XP PC/tablet (Horiz)(170),HC Center(174),Ati Symbian Series 60 mobile(247), type 1 id 8 Command:Remove Screen From History, parameters:
08 09/11/07 16:06:53.513 Parameter 10(ID):
08 09/11/07 16:06:53.513 Parameter 159(PK_Screen): 13
05 09/11/07 16:06:53.513 The target device 217 (routed to 217) has not registered.
13 09/11/07 16:06:53.513 No response expected. returning

But sending this command from command line doesn't work :

/usr/pluto/bin/MessageSend localhost 0 -1000 1 19 5 2 17 7 99 5678 100 0 101 R

Also sending event House Mode Changed doesn't actually change house mode (that's ok, cause events are meant for notifying):

/usr/pluto/bin/MessageSend localhost 0 -1000 2 43 38 0 39 2

I have found out the reason. -1000 is DCERouter address, but this kind of message should be addressed directly to Security plugin - in my case this is ID of 13. I'm following this, although don't understand distinction of -1000 and 13 - if DCERouter is addressed it should relay message to security plugin anyway - so I don't understand why this is necessary - any opinion ?
<div style="padding-left: 30px; background: #DDDDDD;">As far as I can tell, the reason for '-1000' is to allow devices to broadcast events to the system as a whole rather than to a specific device, presumably for event-based devices that do not do a specific function. I shall look more into this... -AVJohn.</div>

/usr/pluto/bin/MessageSend localhost 0 13 1 19 5 6 17 7 99 5678 100 0 101 R

Now it changes security mode properly... Parameters in this command line are :
0 from, 13 to Security plugin, 1-Type: Command, 19-Command "Set house mode", and the rest:
08 09/11/07 16:06:53.512 Parameter 5(Value To Assign): 1
08 09/11/07 16:06:53.512 Parameter 17(PK_Users): 7
08 09/11/07 16:06:53.512 Parameter 99(Password): 5678
08 09/11/07 16:06:53.512 Parameter 100(PK_DeviceGroup): 0
08 09/11/07 16:06:53.512 Parameter 101(Handling Instructions): R

=Other interesting DCE messages=

Will parse the meaning of DCE messages below in future. Just wrote it here to remember....

It seems like "Goto Screen" command
/usr/pluto/bin/MessageSend localhost 0 64 1 741 10 "Whatever" 159 53 9 'A message|Ok|Remind me later' 137 '-targetType device <%=!%> 15 1 67 13 "/root/Something.sh" 51 "--answer yes"|-targetType device <%=!%> 15 1 67 13 "/root/Something.sh" 51 "--answer no"'

To display Text Alert on Orbiter :
/usr/pluto/bin/MessageSend localhost 0 20 1 809 9 "Text to Display" 70 "alert" 182 "30" 251 "??"

Also interesting command is #397 "Show popup", but I have yet to discover how to use it...

Does anyone know how to display popup with question and few answer buttons (yes/no for example) ? Can this be done without Designer to create screen - just to specify question, texts on buttons and actions on click ?

DCE from commandline

2008-01-22T00:30:24Z

Matthew: Shift section degrees down to start at 1

[[Category: Programmer's Guide]]
=Sending DCE events from command line=
There is a utility in pluto (/usr/pluto/bin) that allows sending proper DCE message from command line. If you want for instance to trip motion sensors on/off you can achieve this in simple way (ID means ID of particular device that you send event for) :

Event "tripped on"
ID -1000 2 9 25 1

Event "tripped off"
ID -1000 2 9 25 0

Event "temperature changed"
ID -1000 2 25 30 temperature_value

Event "output on"
ID -1000 2 28

Event "output off"
ID -1000 2 29

Event "light on"
ID -1000 2 48 10 1

Event "light off"
ID -1000 2 48 10 0

For instance -

A. tripping security sensor with ID of 195 to ON :
/usr/pluto/bin/MessageSend dcerouter 195 -1000 2 9 25 1

B. play media (/home/public/data/tts/0.wav) on Xine player with ID of 44 :
/usr/pluto/bin/MessageSend localhost 0 44 1 37 29 "" 41 "" 42 "" 59 "/home/public/data/tts/0.wav"

C. report that light with ID of 210 is ON :
/usr/pluto/bin/MessageSend dcerouter 210 -1000 2 48 10 1

=Sending DCE commands from command line=

Change HouseMode command :
I've sniffed DCERouter logs and this is what happens when you change security state from Orbiter :
06 09/11/07 16:06:53.512 Evaluated Event Handler: 1 to: 0 once per: 0 last fired 1189519147 (time is 1189519613)
07 09/11/07 16:06:53.512 Received Message from 13 (Security Plug-in / Utility) to -1001 (unknown / ), type 2 id 43 Event:House Mode Changed, parameters:
07 09/11/07 16:06:53.512 Parameter 38(PK_DeviceGroup): 0
07 09/11/07 16:06:53.512 Parameter 39(PK_HouseMode): 1
08 09/11/07 16:06:53.512 Received Message from 13 (Security Plug-in / Utility) to Apex Destiny 6100(217), type 1 id 19 Command:Set House Mode, parameters:
08 09/11/07 16:06:53.512 Parameter 5(Value To Assign): 1
08 09/11/07 16:06:53.512 Parameter 17(PK_Users): 7
08 09/11/07 16:06:53.512 Parameter 99(Password): 5678
08 09/11/07 16:06:53.512 Parameter 100(PK_DeviceGroup): 0
08 09/11/07 16:06:53.512 Parameter 101(Handling Instructions): R
08 09/11/07 16:06:53.513 Received Message from 13 (Security Plug-in / Utility) to OnScreen Orbiter(20),tinia Symbian Series 60 mobile(31),Lapitopi(38),OnScreen Orbiter(40),OnScreen Orbiter(88),Windows XP PC/tablet (Horiz)(102),Generic Proxy Orbiter(164),Windows XP PC/tablet (Horiz)(170),HC Center(174),Ati Symbian Series 60 mobile(247), type 1 id 8 Command:Remove Screen From History, parameters:
08 09/11/07 16:06:53.513 Parameter 10(ID):
08 09/11/07 16:06:53.513 Parameter 159(PK_Screen): 13
05 09/11/07 16:06:53.513 The target device 217 (routed to 217) has not registered.
13 09/11/07 16:06:53.513 No response expected. returning

But sending this command from command line doesn't work :

/usr/pluto/bin/MessageSend localhost 0 -1000 1 19 5 2 17 7 99 5678 100 0 101 R

Also sending event House Mode Changed doesn't actually change house mode (that's ok, cause events are meant for notifying):

/usr/pluto/bin/MessageSend localhost 0 -1000 2 43 38 0 39 2

I have found out the reason. -1000 is DCERouter address, but this kind of message should be addressed directly to Security plugin - in my case this is ID of 13. I'm following this, although don't understand distinction of -1000 and 13 - if DCERouter is addressed it should relay message to security plugin anyway - so I don't understand why this is necessary - any opinion ?
<div style="padding-left: 30px; background: #DDDDDD;">As far as I can tell, the reason for '-1000' is to allow devices to broadcast events to the system as a whole rather than to a specific device, presumably for event-based devices that do not do a specific function. I shall look more into this... -AVJohn.</div>

/usr/pluto/bin/MessageSend localhost 0 13 1 19 5 6 17 7 99 5678 100 0 101 R

Now it changes security mode properly... Parameters in this command line are :
0 from, 13 to Security plugin, 1-Type: Command, 19-Command "Set house mode", and the rest:
08 09/11/07 16:06:53.512 Parameter 5(Value To Assign): 1
08 09/11/07 16:06:53.512 Parameter 17(PK_Users): 7
08 09/11/07 16:06:53.512 Parameter 99(Password): 5678
08 09/11/07 16:06:53.512 Parameter 100(PK_DeviceGroup): 0
08 09/11/07 16:06:53.512 Parameter 101(Handling Instructions): R

=Other interesting DCE messages=

Will parse the meaning of DCE messages below in future. Just wrote it here to remember....

It seems like "Goto Screen" command
/usr/pluto/bin/MessageSend localhost 0 64 1 741 10 "Whatever" 159 53 9 'A message|Ok|Remind me later' 137 '-targetType device <%=!%> 15 1 67 13 "/root/Something.sh" 51 "--answer yes"|-targetType device <%=!%> 15 1 67 13 "/root/Something.sh" 51 "--answer no"'

To display Text Alert on Orbiter :
/usr/pluto/bin/MessageSend localhost 0 20 1 809 9 "Text to Display" 70 "alert" 182 "30" 251 "??"

Also interesting command is #397 "Show popup", but I have yet to discover how to use it...

Does anyone know how to display popup with question and few answer buttons (yes/no for example) ? Can this be done without Designer to create screen - just to specify question, texts on buttons and actions on click ?

DCERouter

2008-01-22T00:27:11Z

Matthew: Use MessageSend

[[Category: Programmer's Guide]]

DCERouter has no options or user interface, so there is no documentation for users--only technical documentation.

DCERouter is the central piece of software that all [[LinuxMCE DCE Devices]] for documentation on the DCE socket-based messaging protocol

Normally DCE Devices run separately from the router. Since they communicate over a socket, they can be on the same computer, or another computer with an internet connection. A DCE Device can also be run in the DCE Router's memory space. These devices are called plug-ins. However, they are really identical to the other DCE Devices. In fact, all DCE Devices come with 2 projects/Makefiles--1 to run as a normal, external DCE Device, and 1 to run as a plug-in. Of course, running as a plug-in is much more dangerous since it is in the same memory space and can therefore crash the whole router, and bring the whole LinuxMCE system down. Therefore it is encourages to run devices as plug-ins only when necessary because the device needs to be able to intercept messages that may not be directed to it. Since all the plug-ins run in the same memory space, they have access to the actual class pointers for the other plug-ins, and can therefore efficiently share data and call each other's functions. To make your DCE Device a plug-in, just check the "Is Plug-in" box when defining the device in the "Device Template" section of the configuration web site. Then compile it using the DLL-version of the project under Windows, or the so (for shared object) switch on the Makefile under Linux.

=Programmer's Guide=

<pre>Router, v.2.0.0.44.0709022200
Usage: Router [-i installation] [-d device] [-h hostname]
[-u username] [-p password] [-D database] [-P mysql port]
[-t tcp/ip port to listen on] [-f Base Path][-l Logger]
-h hostname -- address or DNS of database host, default is `dcerouter`
-u username -- username for database connection
-p password -- password for database connection, default is `` (empty)
-D database -- database name
-P port -- port for database connection, default is 3306
-f base path -- device requests for files will be relative to this path
-l logger -- where to put the log</pre>

Messages can be sent on the commandline to the DCERouter (and thereby to devices) using the [[MessageSend]] utility.

DCERouter

2008-01-22T00:25:54Z

Matthew: Shift section degrees down to start at 1

[[Category: Programmer's Guide]]

DCERouter has no options or user interface, so there is no documentation for users--only technical documentation.

DCERouter is the central piece of software that all [[LinuxMCE DCE Devices]] for documentation on the DCE socket-based messaging protocol

Normally DCE Devices run separately from the router. Since they communicate over a socket, they can be on the same computer, or another computer with an internet connection. A DCE Device can also be run in the DCE Router's memory space. These devices are called plug-ins. However, they are really identical to the other DCE Devices. In fact, all DCE Devices come with 2 projects/Makefiles--1 to run as a normal, external DCE Device, and 1 to run as a plug-in. Of course, running as a plug-in is much more dangerous since it is in the same memory space and can therefore crash the whole router, and bring the whole LinuxMCE system down. Therefore it is encourages to run devices as plug-ins only when necessary because the device needs to be able to intercept messages that may not be directed to it. Since all the plug-ins run in the same memory space, they have access to the actual class pointers for the other plug-ins, and can therefore efficiently share data and call each other's functions. To make your DCE Device a plug-in, just check the "Is Plug-in" box when defining the device in the "Device Template" section of the configuration web site. Then compile it using the DLL-version of the project under Windows, or the so (for shared object) switch on the Makefile under Linux.
=Programmer's Guide=

<pre>Router, v.2.0.0.44.0709022200
Usage: Router [-i installation] [-d device] [-h hostname]
[-u username] [-p password] [-D database] [-P mysql port]
[-t tcp/ip port to listen on] [-f Base Path][-l Logger]
-h hostname -- address or DNS of database host, default is `dcerouter`
-u username -- username for database connection
-p password -- password for database connection, default is `` (empty)
-D database -- database name
-P port -- port for database connection, default is 3306
-f base path -- device requests for files will be relative to this path
-l logger -- where to put the log</pre>

Control LinuxMCE using other types of mobile phones

2008-01-17T14:25:57Z

Matthew: Cleanup, link to mobile Orbiter, obsolescence warning

[[Category: Phones]]
[[Category: Orbiters]]
<pre>This article needs to be updated to current LinuxMCE version functionality</pre>

There are 2 ways to control LinuxMCE using your mobile phone. The first is using Bluetooth, the other is by WAP.

=Bluetooth=

This works only when you are near a media director. Your cellular service is not used; the phone doesn't even need to be activated. Using Bluetooth the phone makes a very comfortable remote control, and can be used to control your media just like a normal remote control. However this Bluetooth control requires LinuxMCE's mobile orbiter software to be running on the phone. When you leave the house, the mobile orbiter software switches from Bluetooth to using your mobile phones data services, so you retain control whether you're in the home or not. The mobile orbiter software right now only works with Symbian Series 60 phones, although a version for Microsoft smart phones is expected in September, 2005.

=WAP=
The second way to control LinuxMCE with a mobile phone is using the phone's built in web browser (or WAP). This works on any phone that has a browser built-in. It uses the data service from your mobile phone provider, and gives you control anywhere you have mobile phone service. With this web page you can monitor the cameras in your home, control the alarm system, execute scenarios, and so on.

The only challenge here is that the phone needs to make a connection to the web server running on your core, and many residential ISP's (dsl and cable modem providers) block incoming web connections because they don't want their customers to run a web server from the home. Another possible obstacle is that many residential ISP's do not give you a static IP address, making it difficult to reach your home network from an internet connection on the outside. There is a solution for this. You have 4 options:

#If you have an static, externally accessible ip, then in Wizard, Security, Outside access check the box "Allow outside access to the website on port 80". Then in your phone's browser go to [http://<your_ip_address>/pluto-admin/check.wml] Enter the username, phone #, and the mobile phone's number. The mobile phone's number is used as a callback number to broadcast your voice through the house. If your ISP blocks port 80, you can check "Allow outside to the website on port" and choose another port. Then change the URL to: [http://<your_ip_address>:port/pluto-admin/check.wml]. Note though that some mobile phone companies do not allow connections on ports other than 80.
#LinuxMCE will soon have an optional service that provides a secure tunneling through our server to your home. This will work around any issues. The service will be available soon.
#If you're technically inclined, you can also use another Linux machine that does have a routable IP. There, you'll have to create a file "check.wml" which uses 'curl' to access the wap page from the core, like this:
#:<pre>
#:<?php
#:Header( "Content-type: text/vnd.wap.wml");
#:$Message=queryServer($_SERVER['QUERY_STRING'],'[http://<your_core_ip_address>/pluto-admin/check.wml]';
#:
#:print $Message;
#:
#:function queryServer($params,$url)
#:{
#: $defined_vars = get_defined_vars();
#: $user_agent = @$defined_vars['HTTP_USER_AGENT'];
#:
#: $ch = curl_init();
#: $serverAddress=($_SERVER['QUERY_STRING']!='')?$url.'?'.$_SERVER['QUERY_STRING']:$url;
#:
#: curl_setopt($ch, CURLOPT_URL, $serverAddress);
#: curl_setopt($ch, CURLOPT_HEADER, 0);
#: curl_setopt($ch, CURLOPT_USERAGENT, $user_agent);
#: curl_setopt($ch, CURLOPT_RETURNTRANSFER,1);
#:
#: $result=curl_exec ($ch);
#: curl_close ($ch);
#:
#: return $result;
#:}
#:?>
#:</pre>
#If you are stuck with a Dynamic IP (one that changes when you reset the router or your dialup DSL) then you have one more option. Register a free account with [http://www.no-ip.com/services/managed_dns/free_dynamic_dns.html No-IP.com] and install a small utility (available for Linux as well) that will update your Dynamic IP on a user set interval to a Static DNS obtained from their server. Then follow step 1 and type in the Static DNS that you registered with at No-IP.com.

Once you have WAP access to your LMCE Core, you can use [WAP/GPRS Settings the mobile Orbiter[/url], or your own WAP pages that you create.

WAP/GPRS Settings

2008-01-17T14:14:35Z

Matthew: Link to other mobile access

[[Category:Admin Website]]

[[Image:WAPGPRSSettings.jpg|thumb|200px|WAP/GPRS Setting Admin Page]]
This page allows you to gain access via WAP/GPRS services. Follow the instructions and you will have access via your mobile phone.

= Setting up the WAP/GPRS settings =

Once your core is internet accessible, you can then proceed to the WAP/GPRS settings page.

Once the page loads, you need to enter the following information:

* '''WAP/GPRS URL'''. This is the URL that your phone will use to access your core. It must contain a full URL with host name, and the file '''check.wml''' ... If you set up a DynDNS account as recommended previously, your host is the domain name you set up with DynDNS. If not, the host is your internet accessible IP address.
* '''Caller ID Number'''. This is the number to your house. This assumes that you have set up telecom and have a number which dials into LinuxMCE's telephone system. It should be the number that is displayed when you call out to other phones, i.e. area code and telephone number without any additional characters. PlutoMO will use this information to determine if it should show a security breach warning.

[[Image:wap_gprs_settings.jpg]]

Once this information is entered, save.

Congratulations! You should now have a tuned mobile orbiter setup. You can now create [[Mobile Orbiter Scenarios]] so that you can trigger house events, as well as many other features including:

* View your security cameras
* Set house modes (Armed/unarmed/etc)
* Speak Inside the House

=See Also=
[[Control LinuxMCE using other types of mobile phones]]

WAP/GPRS Settings

2008-01-17T14:14:05Z

Matthew: Shift section degrees down to start at 1

UI3

2008-01-15T05:52:09Z

Matthew: Proposal section; link to forum discussion

=Proposal=
'''Background'''

Macromedia Flash has become the defacto standard for creating user interface's for the web, with a rich development environment to create an appealing UI, and an efficient player to do the rendering with lot's of eye candy and visual effects. Media centric applications with 10' user interfaces ("MCE apps") have the same needs, but there really does not exist any software that can do this for desktop applications, like Flash does for web applications.

A few MCE apps try to use Flash for their user interfaces. But this does not work very well since this isn't Flash's intended purpose. For example, the UI in a MCE app cannot be stand alone and isolated, rather it must be a UI that floats on top of whatever media the MCE app is delivering. The Flash player is not able to blend it's rendered output on top of the media application, like Xine or MythTV. So although you could create a really attractive EPG program guide in Flash, you cannot blend that guide on top of the live TV in MythTV.

Therefore, nearly all the MCE applications, like Xine, Myth, Windows MCE, etc., typically code their own UI's. This is inefficient; it is like re-inventing the wheel each time. And, most of the time, the developers are more focused on their core application, not the UI, and cannot create a rich UI engine. For example, Xine, MythTV, Mplayer, Freevo, etc., all have their own UI's, but none are rich with eye candy and visual effects. In general, only Microsoft has been able to develop a really eye-candy rich UI with lots of visual effects, and most other media center applications have fairly boring, static UI's, even if the core media application itself is rich. For example, while MythTV developers began implementing a rich OpenGL UI engine over two years ago, this is still only used for some of the menu system and had not been extended to the video overlay or plug-ins, and because there is no UI editor the capabilities of it's graphics engine go largely unused.

The goal, therefore, is to create (1) a UI player, like the Flash player, which is efficient and can render high-res, 3d, user interfaces with lots of eye candy on a variety of platforms (x86 Linux/Windows, PDA's, cell phones, etc.), and (2) a comprehensive development environment, like the one Macromedia developed for Flash, that is well documented and not overly technical so creative designers can use it to build innovate UI's.

The intention is that this can be used to create UI's for a variety of MCE apps, like MythTV, MPlayer, etc., and that unlike Flash which is designed to run as an isolated application, this UI will be designed from the ground up to bolt on top of the core MCE app. In other words, you can create a beautiful EPG, like you could with Flash, but it can be blended on top of MythTV's live tv feed and used to control MythTV. The UI tool should be modular and flexible so graphics designers can create interesting UI's without needing the help of the coders of the core MCE app. For example, a designer could create, say, an innovate 3d TV program guide on a rotating sphere and add it to MythTV without needing the MythTV developers to write new code. Having a unified UI will also allow us to address some of the vexing issues, like text entry using remote controls of various types, with new UI widgets which only need to be learned once for the entire class of 10' applications.

It is understood that this is a big, complicated task which hasn't really been done before. However, we feel it is an important gap that needs to be filled. The first thing most end users notice is the eye candy in the UI and how pretty it is, and only Apple and Windows Vista have had the resources to create such UI's. This will allow other MCE apps to have UI's that are just as catchy and the developers can focus on the core functionality.

'''Target user / financial model'''

Naturally this tool would be an asset to the FOSS MCE apps, like MythTV. However, there are many commercial applications as well. For example, only TiVo and Moxi have created rich UI's for their PVR's. There are tens of millions of PVR's out there from Motorola and Scientific Atlantic distributed by the cable operators, but they cannot justify the huge expense of creating a rich UI, so in general they have ugly, plain, static UI's. If there were an inexpensive, easy way to add a beautiful UI to these PVR's it would be worth it. Also, most TV's have a user interface for on screen menu's that is static and boring even though the TV's themselves have graphics processing chips in them that have the power to render a rich UI. There are numerous DMA's and set top boxes as well that could benefit from a rich UI as well. Mobile phones and PDA's also have media players and mini MCE apps.

In general these UI's are powered by a few single chip solutions, such as Sigma Designs, Broadcom and Marvell, and specialty chips for TV's, like AMD's Xillion. Macromedia Flash's player has been ported to many of these platforms so you can, for example, navigate a flash UI on a mobile phone. But, again, since Flash doesn't work well with MCE apps, in general these MCE apps all have crude, basic UI's, or they look to specialized middle-ware providers like Syabase, Mediabolic, Digion, etc., to create a UI for them.

The UI player will first be developed for X86, probably Linux and Windows in parallel. The software would be developed in such a way that the UI itself was subject to the GPL license, so there is an immediate potential to license the UI player for some commercial MCE apps. There's concern, for example, that SageTV will have a hard time remaining viable since it just doesn't have the pretty UI that Windows MCE does. They would be a potential customer to license the UI player outside the GPL since they would not want to release their UI under the terms of the GPL.

Over time the UI player could be ported to other platforms, like the Sigma, Broadcom, etc. Then the makers of set top boxes could use the UI generator to build rich UI's which could be played back on those set top boxes. By being cross-platform, we would have a strong advantage because the UI developer could target any platform for which the player existed, like Flash developers do now. Also, by being open source, the barrier of entry would be quite low. Anybody could start using the tool set, build it upon it if needed to add new visual effects, and only need to license it when they wanted to deploy a commercial application. And there would not be a concern of being locked into a closed, proprietary solution like the existing middle ware providers.

This relates to Pluto's core business of licensing an interoperability platform. Once a company adopted the use of the UI, Pluto would be able to offer a variety of modules, like lighting control, telephony, etc., that could easily 'bolt on' to the UI delivering a lot of extra functionality without writing any specialized code. If SageTV, for example, used the UI as their front end, Pluto could then offer lighting control modules, some to view security cameras, make phone calls, etc. which could be added to the SageTV package without them writing any new code. Pluto will be willing to sponsor the development of this new UI in exchange for receiving a license allowing Pluto to commercially license the UI software outside the GPL.

If QT is providing the underlying graphics library and hardware abstraction, then this benefits Trolltech as well because every commercial user who didn't want to release the UI under the GPL would also need to obtain a license to QT. The hope is that QT would also have an interest in furthering the development of this software.

'''How this relates to LinuxMCE'''

The UI in LinuxMCE, Orbiter, was developed to accomplish this same task. It has succeeded in some ways. For example, LinuxMCE's UI can be played on both Linux and Windows pc's, web pads, pda's, mobile phones, desktop phones, and web browsers. All those platforms are rendering the same UI and same set of screens created with a single design tool, called Designer. The problem is that Orbiter and Designer were created nearly 5 years ago, and were not very well designed. They are still quite crude. Designer is nearly impossible to use and does not appeal to graphic designers. The limited eye candy and visual effects in LinuxMCE, like the 3d cube media browser, are hardcoded into the player, Orbiter, rather than being part of the design as they should be. So, Orbiter and Designer are not general purpose enough to be useful to other MCE apps.

'''Skill sets needed'''

Here are 4 groups we need:

# First we need people who really understand how to design a great UI. These could be Flash designers who have created rich UI's before. They need to outline what the new UI software must do to appeal to the designers that will be building the UI's. That is the most essential thing since, if designers are creating, say beautiful, rich TV program guides with this software, it will be easy to approach the commercial PVR makers and show them why they need to use this UI in their product. So this team is more composed of graphic designers, not C++ coders.
# Next we need to know how to develop the UI design tool. There will be a lot of overlap with #1 since the people in #1 will be the users of the code written by this group. The UI design tool will not need to be cross platform. Windows/Linux x86 is acceptable. But it will have to be logical and similar to other design tools, like Macromedia's flash development tools, so designers can start using it without a steep learning curve.
# Next we need people who create MCE apps and know what the player must do to integrate well with those apps. For example, what are the low level C-language hooks the player must have to handle alpha blending the UI on top of MythTV. What is the socket-based control needed to allow the player and MythTV to seamlessly communicate as though the player were developed as part of MythTV, so the user is not aware that the UI is in fact a separate piece of software.
# The player needs to be highly efficient using a lot of the tricks that the video game industry uses to create high res 3d effects with smooth animation. For this we need some people who understand the Windows Direct X architecture, as well as the OpenGL fragment programs used by Linux and OS X, and some of the single chip solutions, so the player can be designed in such a way that as much code as possible is shared across all platforms, yet the player takes advantage of the unique hardware acceleration tricks each platform offers to be lean and efficient.

'''Proposed next steps'''

Some of the people needed will be in the Bay Area anyway for the KDE/Google event on Jan 18. We propose having a mini developers conference on Jan 19th. Pluto has agreed to sponsor this and provide airfare and accomodations to some key people, as well as pay change fees for some already at the KDE/Google event who want to stay an extra day.

The goal is to get representative people from the four skill sets to brainstorm some of the general concepts and come up with an organizational structure and delegate responsibilities. Also, key developers could be chosen to be sponsored full time.

We would also like to finalize an agreement with Trolltech so that if a committment is made to use QT as the underlying library for this new UI, it can be determined how Trolltech and Pluto will work together on the commercial licensing, and what resources Trolltech is willing to commit to the project.

=Community Discussion=
There is a discussion of this UI3 proposal in the developers forum, topic [http://forum.linuxmce.org/index.php?topic=3820 UI3 Discussion].

Bug Reports

2008-01-14T20:28:15Z

Matthew: Clearer explanation of reporting to mantis

Bugs may be reported via [http://mantis.linuxmce.com the project's mantis server], the bug/issue tracking system.

[[Category:Development]]

Bug Reports

2008-01-14T20:26:59Z

Matthew: Correct URL for mantis link

Bugs may be [http://mantis.linuxmce.com reported] via the bug tracking system, [http://www.mantisbugtracker.com/ Mantis].

[[Category:Development]]

Main Page

2008-01-14T20:26:01Z

Matthew: Documentation section/links/structure

__NOTOC__ __NOEDITSECTION__
<div align="center">
<div style="font-size:175%; font-weight:bold">The '''[http://linuxmce.org LinuxMCE]''' wiki</div>
'''Your guide to a smarter home!'''
</div>

{| style="clear: both; border: 1px solid #aaa; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.5em; float: right; text-align:center"
|'''Screenshots'''
[[Image:MainMenu2.jpg|200px]] The main menu with media in the background 
|-
|[[Image:FileBrowserUI1.jpg|200px]] Browsing media files 
|-
|[[Image:DialNumberUI1.jpg|200px]] Telephone dial pad [[Screenshots|More screenshots and videos]]
|}
'''LinuxMCE is the only all-in-one open source solution that seamlessly combines:'''
* ''Media & entertainment'' with a server for music and video plus a [[PVR]] like TiVo or Sky+
* ''Home automation'' to control everything from lights to heating with a touch-screen tablet or your mobile phone
* ''Phone system'' with video conferencing
* ''Security system'' that feeds live video to your mobile during a security breach

[[LinuxMCE|Read more]] to see all the possibilities that LinuxMCE offers.

LinuxMCE Video hardware link is here http://wiki.linuxmce.org/index.php/Video

=Download=
Please take a moment to read about '''[[Known_Issues|known issues]]''' before downloading our ''Quick Install DVD'' or the ''Two-CD Installer''.

{| cellspacing=5 cellpadding=5 border=0 width=100%
|width=48|{{Click || image=Globe.gif | link=Download_Instructions | width=48px | height=48px }}
|'''[[Download_Instructions|Download LinuxMCE]] or buy [[LinuxMCE Products]]''' After checking known issues please download from an appropriate mirror
|}

=Project News=
*[http://wiki.linuxmce.org/index.php/Insteon_-_Setting_Up_PLM_Template Beta Insteon Support now available] ''(4-January-08)''
*[http://www.osweekly.com/index.php?option=com_content&task=view&id=2664 Linux Media Center PCs Review Roundup] ''(4 October)''
*[http://www.news.com/DRM-troubles-drive-ex-Microsoft-employee-to-Linux/2100-1016_3-6210131.html DRM troubles drive ex-Microsoft employee to Linux] ''(26 September)''
*[http://linuxmce.org/news.php?id=10| New SchedulesDirect service for MythTV] ''(31 August)''
*[[Download_Instructions|LinuxMCE 0704 is out!]] ''(7 August)''

{| cellspacing=5 cellpadding=5 border=0 width=100%
|width=48|{{Click || image=Newspaper.gif | link=LinuxMCE_media_coverage | width=48px | height=48px }}
|'''[[LinuxMCE media coverage|More LinuxMCE media coverage]]''' Third party media and blog coverage
|}

=Documentation Access=
This Wiki has many [[Special:Categories categories]] of articles. There are also developer maillists, [[source code]] repositories (with attached discussions), [http://mantis.linuxmce.org bug/issue report mangement] and [http://forum.linuxmce.org/index.php forums] for discussion among users, developers and other members of the LinuxMCE community.

==Support==
{| cellspacing=5 cellpadding=5 border=0
|width=48|{{Click || image=Manual.gif | link=User Manual | width=48px | height=48px }}
|'''[[User Manual]]''' LinuxMCE User Manual
|width=48|{{Click || image=Guides.gif | link=:Category:Tutorials | width=48px | height=48px }}
|'''[[:Category:Tutorials|Guides]]''' HOWTO guides describing common scenarios
|-
|width=48|{{Click || image=FAQ.gif | link=Frequently Asked Questions | width=48px | height=48px }}
|'''[[Frequently Asked Questions]]''' Responses to the most common questions
|width=48|{{Click || image=Hardware.gif | link=Hardware | width=48px | height=48px }}
|'''[[Hardware]]''' Hardware documentation
|-
|width=48|{{Click || image=Troubleshooting.gif | link=Troubleshooting | width=48px | height=48px }}
|'''[[Troubleshooting]]''' Help with common problems
|width=48|{{UrlClick || image=Mail.gif | link=Developers | width=48px | height=48px }}
|'''[http://www.charonmedia.org/mailman/listinfo Mailing List]''' Stay up to date with regular emails
|-
|width=48|{{UrlClick || image=Forum.gif | link=kjh | width=48px | height=48px }}
|'''[http://forum.linuxmce.com Forum]''' Support forum
|width=48|{{Click || image=Forum.gif | link=Chat | width=48px | height=48px }}
|'''[[Chat]]''' Support chat
|}

==Development==
{| cellspacing=5 cellpadding=5 border=0
|width=48|{{Click || image=Contacts.gif | link=Contacts | width=48px | height=48px }}
|'''[[Contacts|Contact Information]]''' Contact people involved with the project
|width=48|{{Click || image=Manual.gif | link=Programmer's Guide | width=48px | height=48px }}
|'''[[Programmer's Guide]]''' A guide for software developers
|-
|width=48|{{Click || image=Software.gif | link=Software components | width=48px | height=48px }}
|'''[[Software components|Software Components]]''' Open source software used by LinuxMCE
|width=48|{{Click || image=Bug.gif | link=Bug Reports | width=48px | height=48px }}
|'''[[Bug Reports]]''' Help improve the software by reporting bugs
|-
|width=48|{{Click || image=Binary.gif | link=Source Code | width=48px | height=48px }}
|'''[[Source Code]]''' Access the LinuxMCE source code
|width=48|{{UrlClick || image=CDR.gif | link=Versions | width=48px | height=48px }}
|'''[[Versions]]''' View version histories and changes
|}

Main Page

2008-01-14T20:20:48Z

Matthew: Shift section degrees down to start at 1

__NOTOC__ __NOEDITSECTION__
<div align="center">
<div style="font-size:175%; font-weight:bold">The '''[http://linuxmce.org LinuxMCE]''' wiki</div>
'''Your guide to a smarter home!'''
</div>

{| style="clear: both; border: 1px solid #aaa; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.5em; float: right; text-align:center"
|'''Screenshots'''
[[Image:MainMenu2.jpg|200px]] The main menu with media in the background 
|-
|[[Image:FileBrowserUI1.jpg|200px]] Browsing media files 
|-
|[[Image:DialNumberUI1.jpg|200px]] Telephone dial pad [[Screenshots|More screenshots and videos]]
|}
'''LinuxMCE is the only all-in-one open source solution that seamlessly combines:'''
* ''Media & entertainment'' with a server for music and video plus a [[PVR]] like TiVo or Sky+
* ''Home automation'' to control everything from lights to heating with a touch-screen tablet or your mobile phone
* ''Phone system'' with video conferencing
* ''Security system'' that feeds live video to your mobile during a security breach

[[LinuxMCE|Read more]] to see all the possibilities that LinuxMCE offers.

LinuxMCE Video hardware link is here http://wiki.linuxmce.org/index.php/Video

=Download=
Please take a moment to read about '''[[Known_Issues|known issues]]''' before downloading our ''Quick Install DVD'' or the ''Two-CD Installer''.

{| cellspacing=5 cellpadding=5 border=0 width=100%
|width=48|{{Click || image=Globe.gif | link=Download_Instructions | width=48px | height=48px }}
|'''[[Download_Instructions|Download LinuxMCE]] or buy [[LinuxMCE Products]]''' After checking known issues please download from an appropriate mirror
|}

=Project News=
*[http://wiki.linuxmce.org/index.php/Insteon_-_Setting_Up_PLM_Template Beta Insteon Support now available] ''(4-January-08)''
*[http://www.osweekly.com/index.php?option=com_content&task=view&id=2664 Linux Media Center PCs Review Roundup] ''(4 October)''
*[http://www.news.com/DRM-troubles-drive-ex-Microsoft-employee-to-Linux/2100-1016_3-6210131.html DRM troubles drive ex-Microsoft employee to Linux] ''(26 September)''
*[http://linuxmce.org/news.php?id=10| New SchedulesDirect service for MythTV] ''(31 August)''
*[[Download_Instructions|LinuxMCE 0704 is out!]] ''(7 August)''

{| cellspacing=5 cellpadding=5 border=0 width=100%
|width=48|{{Click || image=Newspaper.gif | link=LinuxMCE_media_coverage | width=48px | height=48px }}
|'''[[LinuxMCE media coverage|More LinuxMCE media coverage]]''' Third party media and blog coverage
|}

=Support=
{| cellspacing=5 cellpadding=5 border=0
|width=48|{{Click || image=Manual.gif | link=User Manual | width=48px | height=48px }}
|'''[[User Manual]]''' LinuxMCE User Manual
|width=48|{{Click || image=Guides.gif | link=:Category:Tutorials | width=48px | height=48px }}
|'''[[:Category:Tutorials|Guides]]''' HOWTO guides describing common scenarios
|-
|width=48|{{Click || image=FAQ.gif | link=Frequently Asked Questions | width=48px | height=48px }}
|'''[[Frequently Asked Questions]]''' Responses to the most common questions
|width=48|{{Click || image=Hardware.gif | link=Hardware | width=48px | height=48px }}
|'''[[Hardware]]''' Hardware documentation
|-
|width=48|{{Click || image=Troubleshooting.gif | link=Troubleshooting | width=48px | height=48px }}
|'''[[Troubleshooting]]''' Help with common problems
|width=48|{{UrlClick || image=Mail.gif | link=Developers | width=48px | height=48px }}
|'''[http://www.charonmedia.org/mailman/listinfo Mailing List]''' Stay up to date with regular emails
|-
|width=48|{{UrlClick || image=Forum.gif | link=kjh | width=48px | height=48px }}
|'''[http://forum.linuxmce.com Forum]''' Support forum
|width=48|{{Click || image=Forum.gif | link=Chat | width=48px | height=48px }}
|'''[[Chat]]''' Support chat
|}

=Development=
{| cellspacing=5 cellpadding=5 border=0
|width=48|{{Click || image=Contacts.gif | link=Contacts | width=48px | height=48px }}
|'''[[Contacts|Contact Information]]''' Contact people involved with the project
|width=48|{{Click || image=Manual.gif | link=Programmer's Guide | width=48px | height=48px }}
|'''[[Programmer's Guide]]''' A guide for software developers
|-
|width=48|{{Click || image=Software.gif | link=Software components | width=48px | height=48px }}
|'''[[Software components|Software Components]]''' Open source software used by LinuxMCE
|width=48|{{Click || image=Bug.gif | link=Bug Reports | width=48px | height=48px }}
|'''[[Bug Reports]]''' Help improve the software by reporting bugs
|-
|width=48|{{Click || image=Binary.gif | link=Source Code | width=48px | height=48px }}
|'''[[Source Code]]''' Access the LinuxMCE source code
|width=48|{{UrlClick || image=CDR.gif | link=Versions | width=48px | height=48px }}
|'''[[Versions]]''' View version histories and changes
|}

Outside Access

2008-01-14T16:26:26Z

Matthew: Explicit checkbox text

[[Category:Security]]
[[Category:Admin Website]]

[[Image:OutsideAccess.jpg|thumb|200px|Outside Access Admin Page]]
If both of these boxes ("Allow outside access to the website" & "... on port (-port#-)") are unchecked, then it will not be possible for anyone to access any part of your system from outside the home unless you manually make changes to the firewall in the Advanced section.

Check the first box if you want to be able to access the LinuxMCE Admin website from outside your home. Once checked, you will be able to go to any internet browser anywhere and go to the URL <nowiki>http://youripaddress/pluto-admin</nowiki> to reach the site.

==2 Potential Problems==
===Knowing your IP Address===
The first is that to access your home system you need to know the ip address that globally identifies your computer, and put it in the "youripaddress" on the URL. But most residential DSL and cable internet services do not provide their customers with a static ip address--it changes all the time. To fix this problem, a domain name should be assigned to the core. This can be done by going to [http://dyndns.org/ dyndns.org] and creating an account and domain name for this machine. The username and password you created at dyndns.org can be entered into the web admin, so that if it changes, the core will automatically contact DynDNS to update its information appropriately.

This can be changed from '''Advanced > Network > Dynamic DNS Settings'''

[[Image:dyndns_settings.png]]

===Secure Connection===
The second problem is that if you check that box the connection will not be secure and it would be possible for someone to "listen" to your communication and intercept your password, thereby being able to control your house. To solve this you can obtain your own SSL secure certificate from a company like Verisign. This is what banks and online merchants use to encrypt confidential financial transactions. With a secure certificate you would access your web site with an "https://" instead--the s means secure. Everything would be secure and encrypted using the same method you use to access online banking and other secure sites. However setting up your own secure certificate can be costly and complicated.

If you do check the box to allow outside access, you may find that even if you know your ip address you still cannot access your server because your ISP blocked incoming connections on port 80. Port 80 is what internet browsers use to connect to a web server. You can try changing the port from 80 to something else, like 3080. If you do, then you will need to access your web site like this: <nowiki>http://youripaddress:3080/pluto-admin</nowiki>. If that still doesn't work, you may need to talk to your ISP.

The '''Allow outside access''' is mainly used when you want tech support to be able to help you configure or troubleshoot. There is no 'back door' to LinuxMCE, and LinuxMCE staff have no way to connect to your system unless you check this box.

'''This Feature is still an Option but LinuxMCE does not offer Tech Support'''

If you request tech support and you want to allow LinuxMCE to access your system, check the box and then type in a password. You will then give the support rep the password, and with that password, the support rep will be able to login to your system, inspect the logs, look at your configuration, and run diagnostics. As soon as you uncheck the box or change the password the connection your Core will immediately drop the connection and the support rep will not have access anymore. When you enable remote access, the connection the support rep uses to access your system is secure and encrypted using a protocol called SSH.

Developers

2008-01-14T15:28:02Z

Matthew: Link to dev maillist

Visit [[Contacts]] to see a list of current developers, and [[Contribute]] to learn how you can help out. The [http://www.charonmedia.org/mailman/listinfo Developers mail list] is available.

LinuxMCE was at the outset a fork of [[Pluto]]'s debian based [[Linux]] distribution for home automation. The founder of the LinuxMCE project, [[Paul Webber]], contacted Pluto after seeing a demo of their software at a trade conference. The Pluto folks were happy to let Paul create his own Linux distribution using their foundation so long as he renamed the project. Since then LinuxMCE has moved from debian to Ubuntu (a debian based distribution), and is now moving from being primarily run by Paul alone to being a more open project all around.

BTW [[Pluto]] allowed us to import all their existing Wiki pages, including their [[Programmer's Guide|Programmer's Guide]]. The information is largely accurate for LinuxMCE as well and we've updated many of the parts that didn't apply to us since then.

Read about the [[History|History of LinuxMCE]] for more expansive background information.

[[Category:Development]]

Main Page

2008-01-14T15:26:45Z

Matthew: Link developer maillist icon to "Developers". How do you link an icon to an offsite URL?

__NOTOC__ __NOEDITSECTION__
<div align="center">
<div style="font-size:175%; font-weight:bold">The '''[http://linuxmce.org LinuxMCE]''' wiki</div>
'''Your guide to a smarter home!'''
</div>

{| style="clear: both; border: 1px solid #aaa; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.5em; float: right; text-align:center"
|'''Screenshots'''
[[Image:MainMenu2.jpg|200px]] The main menu with media in the background 
|-
|[[Image:FileBrowserUI1.jpg|200px]] Browsing media files 
|-
|[[Image:DialNumberUI1.jpg|200px]] Telephone dial pad [[Screenshots|More screenshots and videos]]
|}
'''LinuxMCE is the only all-in-one open source solution that seamlessly combines:'''
* ''Media & entertainment'' with a server for music and video plus a [[PVR]] like TiVo or Sky+
* ''Home automation'' to control everything from lights to heating with a touch-screen tablet or your mobile phone
* ''Phone system'' with video conferencing
* ''Security system'' that feeds live video to your mobile during a security breach

[[LinuxMCE|Read more]] to see all the possibilities that LinuxMCE offers.

LinuxMCE Video hardware link is here http://wiki.linuxmce.org/index.php/Video

==Download==
Please take a moment to read about '''[[Known_Issues|known issues]]''' before downloading our ''Quick Install DVD'' or the ''Two-CD Installer''.

{| cellspacing=5 cellpadding=5 border=0 width=100%
|width=48|{{Click || image=Globe.gif | link=Download_Instructions | width=48px | height=48px }}
|'''[[Download_Instructions|Download LinuxMCE]] or buy [[LinuxMCE Products]]''' After checking known issues please download from an appropriate mirror
|}

==Project News==
*[http://wiki.linuxmce.org/index.php/Insteon_-_Setting_Up_PLM_Template Beta Insteon Support now available] ''(4-January-08)''
*[http://www.osweekly.com/index.php?option=com_content&task=view&id=2664 Linux Media Center PCs Review Roundup] ''(4 October)''
*[http://www.news.com/DRM-troubles-drive-ex-Microsoft-employee-to-Linux/2100-1016_3-6210131.html DRM troubles drive ex-Microsoft employee to Linux] ''(26 September)''
*[http://linuxmce.org/news.php?id=10| New SchedulesDirect service for MythTV] ''(31 August)''
*[[Download_Instructions|LinuxMCE 0704 is out!]] ''(7 August)''

{| cellspacing=5 cellpadding=5 border=0 width=100%
|width=48|{{Click || image=Newspaper.gif | link=LinuxMCE_media_coverage | width=48px | height=48px }}
|'''[[LinuxMCE media coverage|More LinuxMCE media coverage]]''' Third party media and blog coverage
|}

==Support==
{| cellspacing=5 cellpadding=5 border=0
|width=48|{{Click || image=Manual.gif | link=User Manual | width=48px | height=48px }}
|'''[[User Manual]]''' LinuxMCE User Manual
|width=48|{{Click || image=Guides.gif | link=:Category:Tutorials | width=48px | height=48px }}
|'''[[:Category:Tutorials|Guides]]''' HOWTO guides describing common scenarios
|-
|width=48|{{Click || image=FAQ.gif | link=Frequently Asked Questions | width=48px | height=48px }}
|'''[[Frequently Asked Questions]]''' Responses to the most common questions
|width=48|{{Click || image=Hardware.gif | link=Hardware | width=48px | height=48px }}
|'''[[Hardware]]''' Hardware documentation
|-
|width=48|{{Click || image=Troubleshooting.gif | link=Troubleshooting | width=48px | height=48px }}
|'''[[Troubleshooting]]''' Help with common problems
|width=48|{{UrlClick || image=Mail.gif | link=Developers | width=48px | height=48px }}
|'''[http://www.charonmedia.org/mailman/listinfo Mailing List]''' Stay up to date with regular emails
|-
|width=48|{{UrlClick || image=Forum.gif | link=kjh | width=48px | height=48px }}
|'''[http://forum.linuxmce.com Forum]''' Support forum
|width=48|{{Click || image=Forum.gif | link=Chat | width=48px | height=48px }}
|'''[[Chat]]''' Support chat
|}

==Development==
{| cellspacing=5 cellpadding=5 border=0
|width=48|{{Click || image=Contacts.gif | link=Contacts | width=48px | height=48px }}
|'''[[Contacts|Contact Information]]''' Contact people involved with the project
|width=48|{{Click || image=Manual.gif | link=Programmer's Guide | width=48px | height=48px }}
|'''[[Programmer's Guide]]''' A guide for software developers
|-
|width=48|{{Click || image=Software.gif | link=Software components | width=48px | height=48px }}
|'''[[Software components|Software Components]]''' Open source software used by LinuxMCE
|width=48|{{Click || image=Bug.gif | link=Bug Reports | width=48px | height=48px }}
|'''[[Bug Reports]]''' Help improve the software by reporting bugs
|-
|width=48|{{Click || image=Binary.gif | link=Source Code | width=48px | height=48px }}
|'''[[Source Code]]''' Access the LinuxMCE source code
|width=48|{{UrlClick || image=CDR.gif | link=Versions | width=48px | height=48px }}
|'''[[Versions]]''' View version histories and changes
|}

Main Page

2008-01-14T14:52:28Z

Matthew: Current developer maillist

__NOTOC__ __NOEDITSECTION__
<div align="center">
<div style="font-size:175%; font-weight:bold">The '''[http://linuxmce.org LinuxMCE]''' wiki</div>
'''Your guide to a smarter home!'''
</div>

{| style="clear: both; border: 1px solid #aaa; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.5em; float: right; text-align:center"
|'''Screenshots'''
[[Image:MainMenu2.jpg|200px]] The main menu with media in the background 
|-
|[[Image:FileBrowserUI1.jpg|200px]] Browsing media files 
|-
|[[Image:DialNumberUI1.jpg|200px]] Telephone dial pad [[Screenshots|More screenshots and videos]]
|}
'''LinuxMCE is the only all-in-one open source solution that seamlessly combines:'''
* ''Media & entertainment'' with a server for music and video plus a [[PVR]] like TiVo or Sky+
* ''Home automation'' to control everything from lights to heating with a touch-screen tablet or your mobile phone
* ''Phone system'' with video conferencing
* ''Security system'' that feeds live video to your mobile during a security breach

[[LinuxMCE|Read more]] to see all the possibilities that LinuxMCE offers.

LinuxMCE Video hardware link is here http://wiki.linuxmce.org/index.php/Video

==Download==
Please take a moment to read about '''[[Known_Issues|known issues]]''' before downloading our ''Quick Install DVD'' or the ''Two-CD Installer''.

{| cellspacing=5 cellpadding=5 border=0 width=100%
|width=48|{{Click || image=Globe.gif | link=Download_Instructions | width=48px | height=48px }}
|'''[[Download_Instructions|Download LinuxMCE]] or buy [[LinuxMCE Products]]''' After checking known issues please download from an appropriate mirror
|}

==Project News==
*[http://wiki.linuxmce.org/index.php/Insteon_-_Setting_Up_PLM_Template Beta Insteon Support now available] ''(4-January-08)''
*[http://www.osweekly.com/index.php?option=com_content&task=view&id=2664 Linux Media Center PCs Review Roundup] ''(4 October)''
*[http://www.news.com/DRM-troubles-drive-ex-Microsoft-employee-to-Linux/2100-1016_3-6210131.html DRM troubles drive ex-Microsoft employee to Linux] ''(26 September)''
*[http://linuxmce.org/news.php?id=10| New SchedulesDirect service for MythTV] ''(31 August)''
*[[Download_Instructions|LinuxMCE 0704 is out!]] ''(7 August)''

{| cellspacing=5 cellpadding=5 border=0 width=100%
|width=48|{{Click || image=Newspaper.gif | link=LinuxMCE_media_coverage | width=48px | height=48px }}
|'''[[LinuxMCE media coverage|More LinuxMCE media coverage]]''' Third party media and blog coverage
|}

==Support==
{| cellspacing=5 cellpadding=5 border=0
|width=48|{{Click || image=Manual.gif | link=User Manual | width=48px | height=48px }}
|'''[[User Manual]]''' LinuxMCE User Manual
|width=48|{{Click || image=Guides.gif | link=:Category:Tutorials | width=48px | height=48px }}
|'''[[:Category:Tutorials|Guides]]''' HOWTO guides describing common scenarios
|-
|width=48|{{Click || image=FAQ.gif | link=Frequently Asked Questions | width=48px | height=48px }}
|'''[[Frequently Asked Questions]]''' Responses to the most common questions
|width=48|{{Click || image=Hardware.gif | link=Hardware | width=48px | height=48px }}
|'''[[Hardware]]''' Hardware documentation
|-
|width=48|{{Click || image=Troubleshooting.gif | link=Troubleshooting | width=48px | height=48px }}
|'''[[Troubleshooting]]''' Help with common problems
|width=48|{{UrlClick || image=Mail.gif | link=:Category:Hardware | width=48px | height=48px }}
|'''[http://www.charonmedia.org/mailman/listinfo Mailing List]''' Stay up to date with regular emails
|-
|width=48|{{UrlClick || image=Forum.gif | link=kjh | width=48px | height=48px }}
|'''[http://forum.linuxmce.com Forum]''' Support forum
|width=48|{{Click || image=Forum.gif | link=Chat | width=48px | height=48px }}
|'''[[Chat]]''' Support chat
|}

==Development==
{| cellspacing=5 cellpadding=5 border=0
|width=48|{{Click || image=Contacts.gif | link=Contacts | width=48px | height=48px }}
|'''[[Contacts|Contact Information]]''' Contact people involved with the project
|width=48|{{Click || image=Manual.gif | link=Programmer's Guide | width=48px | height=48px }}
|'''[[Programmer's Guide]]''' A guide for software developers
|-
|width=48|{{Click || image=Software.gif | link=Software components | width=48px | height=48px }}
|'''[[Software components|Software Components]]''' Open source software used by LinuxMCE
|width=48|{{Click || image=Bug.gif | link=Bug Reports | width=48px | height=48px }}
|'''[[Bug Reports]]''' Help improve the software by reporting bugs
|-
|width=48|{{Click || image=Binary.gif | link=Source Code | width=48px | height=48px }}
|'''[[Source Code]]''' Access the LinuxMCE source code
|width=48|{{UrlClick || image=CDR.gif | link=Versions | width=48px | height=48px }}
|'''[[Versions]]''' View version histories and changes
|}

Source Code

2008-01-11T22:47:55Z

Matthew: build size

'''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.

=Current Source=
You can browse the [http://svn.charonmedia.com/trac.cgi/browser LinuxMCE source] at the [http://svn.charonmedia.com/ Charon Media Trac website]. Or you can download it from SVN:
<pre>
# Download snapshot (391MiB)
wget http://www.charonmedia.org/lmce-1465.tbz

# Test checksum to ensure it was downloaded intact.
md5sum lmce-1465.tbz # should be b3d4b3f6b33ff5e6c4641390f2314095

# Update snapshot (uncompressed: 1823MiB either snapshot or updated).
tar xfj lmce-1465.tbz
cd lmce
svn update

# Build from source (optional) to 3692MiB, total source+build = 5515MiB.
./configure
make
</pre>

The old version of the source code description (of the old SVN) could be a good starting point for identifying what each of the code in the current SVN does, but it's no guarantee. An updated version of that description would be very useful.

=Obsolete Source=
This section refers to the obsolete sourcecode stored at SourceForge. The current (recent 0704 and all 0710) source is stored at Charon Media, as mentioned in [#Current_Source]. The descriptions of the obsolete code might also be wrong descriptions of the current structure and content of the source code, but it could be a clue where none others exist, because that's where the current source code evolved from. (- [[User:Matthew|Matthew]] 08:51, 10 January 2008 (MST))

You can browse the [http://linuxmce.svn.sourceforge.net/viewvc/linuxmce/trunk/ web based repository viewer]. Or you can do an anonymous svn checkout as follows:

svn co <nowiki>http://</nowiki>linuxmce.svn.sourceforge.net/svnroot/linuxmce/trunk/''modulename''

You can checkout all the software with if you use http://linuxmce.svn.sourceforge.net/viewvc/linuxmce/trunk/ as the repository location for the module name, or go to the [http://linuxmce.svn.sourceforge.net/viewvc/linuxmce/trunk/ repository viewer] to find the name of the SVN directory for the module you are interested in.

Here are short instructions if you want compile your module with svn sources : [[Building_From_Source|Building from source]].

----

I've made a start at some pointers to finding your way around the code. [Note, I'm a noob here, so I may have got this wrong, so feel free to add/change. Also, it's by no means complete yet!]

'''''trunk/config-pkgs/''''' contains ...
* ''intel8x0/'' -
'''''trunk/installers/''''' contains ...
* ''CD_Installer/'' -
* ''Installers/'' -
* ''PhoneInstall/'' -
* ''WindowsInstaller/'' -
'''''trunk/libs/''''' contains ...
* ''CrossPlatform/'' -
* ''Libraries/'' -
'''''trunk/src/''''' contains ...
* ''ANSI-to-HTML/ '' -
* ''AVWizard/ '' -
* ''Add_Software/ '' -
* ''App_Server/ '' -
* ''AptUtils/ '' -
* ''Asterisk/ '' -
* ''BD/ '' -
* ''Basic_XML_Data_Source_Plugin/ '' -
* ''Bluetooth_Dongle/ '' -
* ''BootScripts/ '' -
* ''CDDB_Identifier/ '' -
* ''CM11A/ '' -
* ''CheckDependencyScript/ '' -
* ''CliUtils/ '' -
* ''Climate_Plugin/ '' -
* ''ColorSplitter/ '' -
* ''ConfirmDependencies/ '' -
* ''ConfirmDependencies_Script/ '' -
* ''ConfirmDependencies_Script_Offline/ '' -
* ''CreateDevice/ '' -
* ''Crystal_Fontz_USBRS232/ '' -
* ''DCE/ '' -
* ''DCEGen/ '' -
* ''DCERouter/ '' -
* ''Datagrid_Plugin/ '' -
* ''Dhcpd-Plugin/ '' -
* ''DiskMonitor/ '' -
* ''Disk_Drive/ '' -
* ''Disk_Drive_Functions/ '' -
* ''Diskless-Add-Ons/ '' -
* ''DynamicDNS/ '' -
* ''EIB/ '' -
* ''Event_Plugin/ '' -
* ''FakeEPG/ '' -
* ''File_Grids_Plugin/ '' -
* ''Firewire2Video4Linux/ '' -
* ''FirewireVideo/ '' -
* ''GalleryViewer/ '' -
* ''Gen_Devices/ '' -
* ''General_Info_Plugin/ '' -
* ''Generic_Serial_Device/ '' -
* ''GyrationMouse/ '' -
* ''HAL/ '' -
* ''HAL_DeviceFinder/ '' -
* ''HDHomeRun/ '' -
* ''Hooks_rcS/ '' -
* ''IR/ '' -
* ''IRBase/ '' -
* ''IRTrans/ '' -
* ''Infrared_Plugin/ '' -
* ''JobHandler/ '' -
* ''LIRC_DCE/ '' -
* ''Lighting_Plugin/ '' -
* ''Linphone/ '' -
* ''MaemoOrbiterLauncher/ '' -
* ''MakeRelease/ '' -
* ''MakeRelease_PrepFiles/ '' -
* ''Media_Live_LCDButtons/ '' -
* ''Media_Plugin/ '' -
* ''MessageSend/ '' -
* ''MessageTranslation/ '' -
* ''Motion_Wrapper/ '' -
* ''MythTV_Backend_Proxy/ '' -
* ''MythTV_Player/ '' -
* ''MythTV_PlugIn/ '' -
* ''Network_Storage/ '' -
* ''NewMD_interactor/ '' -
* ''Orbiter/ '' -
* ''OrbiterGen/ '' -
* ''Orbiter_Plugin/ '' -
* ''OutlookSync/ '' -
* ''Photo_Screen_Saver/ '' -
* ''Plug_And_Play_Plugin/ '' -
* ''PlutoDHCP/ '' -
* ''PlutoMO/ '' -
* ''PlutoRaidTools/ '' -
* ''PlutoStorageDevices/ '' -
* ''PlutoUpdateSystem/ '' -
* ''PlutoUpgradeHelper/ '' -
* ''PlutoUtils/ '' -
* ''PlutoVIP/ '' -
* ''Powerfile_C200/ '' -
* ''Proxy_Orbiter/ '' -
* ''Qos/ '' -
* ''RA/ '' -
* ''RemoteAssistance/ '' -
* ''SDL_Helpers/ '' -
* ''SMPTE_Fountain/ '' -
* ''STEngine/ '' -
* ''SVNLog/ '' -
* ''SambaScan/ '' -
* ''ScreenGen/ '' -
* ''Security_Plugin/ '' -
* ''Serial/ '' -
* ''SerializeClass/ '' -
* ''Setup_CaptureCards/ '' -
* ''Setup_SoundCards/ '' -
* ''SimplePhone/ '' -
* ''SlimServer_PlugIn/ '' -
* ''Slim_Server_Streamer/ '' -
* ''SoundScripts/ '' -
* ''Speech/ '' -
* ''Splitter/ '' -
* ''Telecom_Plugin/ '' -
* ''TestSerialPort/ '' -
* ''Test_Treo/ '' -
* ''Text_To_Speech/ '' -
* ''Tira/ '' -
* ''Tribune/ '' -
* ''Tribunexml/ '' -
* ''UPnP/ '' -
* ''USB_PNP/ '' -
* ''USB_UIRT_0038/ '' -
* ''UbuntuDiskless/ '' -
* ''Ubuntu_Helpers/ '' -
* ''UpdateEntArea/ '' -
* ''UpdateMedia/ '' -
* ''VDR/ '' -
* ''VDRPlugin/ '' -
* ''VFD_LCD/ '' -
* ''VIPDesign/ '' -
* ''VIPEstablishment/ '' -
* ''VIPServer/ '' -
* ''VIPShared/ '' -
* ''VideoLan_Client/ '' -
* ''VideoLan_PlugIn/ '' -
* ''VideoLan_Server/ '' -
* ''VoiceMailMonitor/ '' -
* ''WinBluetooth/ '' -
* ''Windows_Share_Scanner/ '' -
* ''X-KbLayout/ '' -
* ''X-Resolution/ '' -
* ''XML_Data_Handler_Plugin/ '' -
* ''XinePlayerTest/ '' -
* ''Xine_Player/ '' -
* ''Xine_Plugin/ '' -
* ''bin/ '' -
* ''convert_color/ '' -
* ''convert_mac/ '' -
* ''convert_time/ '' -
* ''database/ '' -
* ''database_audi/ '' -
* ''database_marbella/ '' -
* ''designer/ '' -
* ''docs/ '' -
* ''drivers/ '' -
* ''fakepkgs/ '' -
* ''gc100/ '' -
* ''inotify/ '' -
* ''kernel-upgrade/ '' -
* ''lib/ '' -
* ''mce-installer/ '' -
* ''mce-launcher/ '' -
* ''pluto-ati-drivers/ '' -
* ''pluto-nvidia-drivers/ '' -
* ''pluto_gcs-2.6_module/ '' -
* ''pluto_main/ '' -
* ''pluto_media/ '' -
* ''pluto_media_updater/ '' -
* ''pluto_security/ '' -
* ''pluto_speech/ '' -
* ''pluto_telecom/ '' -
* ''pnp_detection_scripts/ '' -
* ''shift_state/ '' -
* ''skins/ '' -
* ''so_postinst/ '' -
* ''sql2cpp/ '' -
* ''sqlCVS/ '' -
* ''ussp-push/ '' -
* ''utilities/ '' -
* ''BuildWinBinaries.bat '' -
* ''Construct '' -
* ''MakeRelease_All.bat '' -
* ''MakeRelease_Symbian_S60.bat '' -
* ''MakeRelease_Windows.bat '' -
* ''MakeRelease_WindowsCE.bat '' -
* ''Makefile '' -
* ''Makefile_all '' -
* ''SwitchToLinuxMCE.bat '' -
* ''SwitchToPluto.bat '' -
* ''build.xml '' -
* ''pluto.sln '' -
'''''trunk/ubuntu''''' contains ...
* ''asterisk/'' -
* ''libsdl1.2-1.2.10/'' -
* ''libsdl1.2-1.2.7+1.2.8cvs20041007/'' -
* ''lirc-pluto-0.1/'' -
* ''lshwd-2.0-rc4/'' -
* ''mtx-1.3.10/'' -
* ''tee-pluto/'' -
* ''xine-lib-1.1.3/'' -
'''''trunk/web''''' contains the two web-based configuration programs:
* ''Amp'' - The Asterisk (IP Phone exchange) management program
* ''pluto-admin'' - LinuxMCE Web Admin

[[Category:Development]]

Source Code

2008-01-10T20:29:33Z

Matthew: Source code sizes

'''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.

=Current Source=
You can browse the [http://svn.charonmedia.com/trac.cgi/browser LinuxMCE source] at the [http://svn.charonmedia.com/ Charon Media Trac website]. Or you can download it from SVN:
<pre>
# Download snapshot (391MiB)
wget http://www.charonmedia.org/lmce-1465.tbz

# Test checksum to ensure it was downloaded intact.
md5sum lmce-1465.tbz # should be b3d4b3f6b33ff5e6c4641390f2314095

# Update snapshot (uncompressed: 1823MiB either snapshot or updated).
tar xfj lmce-1465.tbz
cd lmce
svn update

# Build from source (optional).
./configure
make
</pre>

The old version of the source code description (of the old SVN) could be a good starting point for identifying what each of the code in the current SVN does, but it's no guarantee. An updated version of that description would be very useful.

=Obsolete Source=
This section refers to the obsolete sourcecode stored at SourceForge. The current (recent 0704 and all 0710) source is stored at Charon Media, as mentioned in [#Current_Source]. The descriptions of the obsolete code might also be wrong descriptions of the current structure and content of the source code, but it could be a clue where none others exist, because that's where the current source code evolved from. (- [[User:Matthew|Matthew]] 08:51, 10 January 2008 (MST))

You can browse the [http://linuxmce.svn.sourceforge.net/viewvc/linuxmce/trunk/ web based repository viewer]. Or you can do an anonymous svn checkout as follows:

svn co <nowiki>http://</nowiki>linuxmce.svn.sourceforge.net/svnroot/linuxmce/trunk/''modulename''

You can checkout all the software with if you use http://linuxmce.svn.sourceforge.net/viewvc/linuxmce/trunk/ as the repository location for the module name, or go to the [http://linuxmce.svn.sourceforge.net/viewvc/linuxmce/trunk/ repository viewer] to find the name of the SVN directory for the module you are interested in.

Here are short instructions if you want compile your module with svn sources : [[Building_From_Source|Building from source]].

----

I've made a start at some pointers to finding your way around the code. [Note, I'm a noob here, so I may have got this wrong, so feel free to add/change. Also, it's by no means complete yet!]

'''''trunk/config-pkgs/''''' contains ...
* ''intel8x0/'' -
'''''trunk/installers/''''' contains ...
* ''CD_Installer/'' -
* ''Installers/'' -
* ''PhoneInstall/'' -
* ''WindowsInstaller/'' -
'''''trunk/libs/''''' contains ...
* ''CrossPlatform/'' -
* ''Libraries/'' -
'''''trunk/src/''''' contains ...
* ''ANSI-to-HTML/ '' -
* ''AVWizard/ '' -
* ''Add_Software/ '' -
* ''App_Server/ '' -
* ''AptUtils/ '' -
* ''Asterisk/ '' -
* ''BD/ '' -
* ''Basic_XML_Data_Source_Plugin/ '' -
* ''Bluetooth_Dongle/ '' -
* ''BootScripts/ '' -
* ''CDDB_Identifier/ '' -
* ''CM11A/ '' -
* ''CheckDependencyScript/ '' -
* ''CliUtils/ '' -
* ''Climate_Plugin/ '' -
* ''ColorSplitter/ '' -
* ''ConfirmDependencies/ '' -
* ''ConfirmDependencies_Script/ '' -
* ''ConfirmDependencies_Script_Offline/ '' -
* ''CreateDevice/ '' -
* ''Crystal_Fontz_USBRS232/ '' -
* ''DCE/ '' -
* ''DCEGen/ '' -
* ''DCERouter/ '' -
* ''Datagrid_Plugin/ '' -
* ''Dhcpd-Plugin/ '' -
* ''DiskMonitor/ '' -
* ''Disk_Drive/ '' -
* ''Disk_Drive_Functions/ '' -
* ''Diskless-Add-Ons/ '' -
* ''DynamicDNS/ '' -
* ''EIB/ '' -
* ''Event_Plugin/ '' -
* ''FakeEPG/ '' -
* ''File_Grids_Plugin/ '' -
* ''Firewire2Video4Linux/ '' -
* ''FirewireVideo/ '' -
* ''GalleryViewer/ '' -
* ''Gen_Devices/ '' -
* ''General_Info_Plugin/ '' -
* ''Generic_Serial_Device/ '' -
* ''GyrationMouse/ '' -
* ''HAL/ '' -
* ''HAL_DeviceFinder/ '' -
* ''HDHomeRun/ '' -
* ''Hooks_rcS/ '' -
* ''IR/ '' -
* ''IRBase/ '' -
* ''IRTrans/ '' -
* ''Infrared_Plugin/ '' -
* ''JobHandler/ '' -
* ''LIRC_DCE/ '' -
* ''Lighting_Plugin/ '' -
* ''Linphone/ '' -
* ''MaemoOrbiterLauncher/ '' -
* ''MakeRelease/ '' -
* ''MakeRelease_PrepFiles/ '' -
* ''Media_Live_LCDButtons/ '' -
* ''Media_Plugin/ '' -
* ''MessageSend/ '' -
* ''MessageTranslation/ '' -
* ''Motion_Wrapper/ '' -
* ''MythTV_Backend_Proxy/ '' -
* ''MythTV_Player/ '' -
* ''MythTV_PlugIn/ '' -
* ''Network_Storage/ '' -
* ''NewMD_interactor/ '' -
* ''Orbiter/ '' -
* ''OrbiterGen/ '' -
* ''Orbiter_Plugin/ '' -
* ''OutlookSync/ '' -
* ''Photo_Screen_Saver/ '' -
* ''Plug_And_Play_Plugin/ '' -
* ''PlutoDHCP/ '' -
* ''PlutoMO/ '' -
* ''PlutoRaidTools/ '' -
* ''PlutoStorageDevices/ '' -
* ''PlutoUpdateSystem/ '' -
* ''PlutoUpgradeHelper/ '' -
* ''PlutoUtils/ '' -
* ''PlutoVIP/ '' -
* ''Powerfile_C200/ '' -
* ''Proxy_Orbiter/ '' -
* ''Qos/ '' -
* ''RA/ '' -
* ''RemoteAssistance/ '' -
* ''SDL_Helpers/ '' -
* ''SMPTE_Fountain/ '' -
* ''STEngine/ '' -
* ''SVNLog/ '' -
* ''SambaScan/ '' -
* ''ScreenGen/ '' -
* ''Security_Plugin/ '' -
* ''Serial/ '' -
* ''SerializeClass/ '' -
* ''Setup_CaptureCards/ '' -
* ''Setup_SoundCards/ '' -
* ''SimplePhone/ '' -
* ''SlimServer_PlugIn/ '' -
* ''Slim_Server_Streamer/ '' -
* ''SoundScripts/ '' -
* ''Speech/ '' -
* ''Splitter/ '' -
* ''Telecom_Plugin/ '' -
* ''TestSerialPort/ '' -
* ''Test_Treo/ '' -
* ''Text_To_Speech/ '' -
* ''Tira/ '' -
* ''Tribune/ '' -
* ''Tribunexml/ '' -
* ''UPnP/ '' -
* ''USB_PNP/ '' -
* ''USB_UIRT_0038/ '' -
* ''UbuntuDiskless/ '' -
* ''Ubuntu_Helpers/ '' -
* ''UpdateEntArea/ '' -
* ''UpdateMedia/ '' -
* ''VDR/ '' -
* ''VDRPlugin/ '' -
* ''VFD_LCD/ '' -
* ''VIPDesign/ '' -
* ''VIPEstablishment/ '' -
* ''VIPServer/ '' -
* ''VIPShared/ '' -
* ''VideoLan_Client/ '' -
* ''VideoLan_PlugIn/ '' -
* ''VideoLan_Server/ '' -
* ''VoiceMailMonitor/ '' -
* ''WinBluetooth/ '' -
* ''Windows_Share_Scanner/ '' -
* ''X-KbLayout/ '' -
* ''X-Resolution/ '' -
* ''XML_Data_Handler_Plugin/ '' -
* ''XinePlayerTest/ '' -
* ''Xine_Player/ '' -
* ''Xine_Plugin/ '' -
* ''bin/ '' -
* ''convert_color/ '' -
* ''convert_mac/ '' -
* ''convert_time/ '' -
* ''database/ '' -
* ''database_audi/ '' -
* ''database_marbella/ '' -
* ''designer/ '' -
* ''docs/ '' -
* ''drivers/ '' -
* ''fakepkgs/ '' -
* ''gc100/ '' -
* ''inotify/ '' -
* ''kernel-upgrade/ '' -
* ''lib/ '' -
* ''mce-installer/ '' -
* ''mce-launcher/ '' -
* ''pluto-ati-drivers/ '' -
* ''pluto-nvidia-drivers/ '' -
* ''pluto_gcs-2.6_module/ '' -
* ''pluto_main/ '' -
* ''pluto_media/ '' -
* ''pluto_media_updater/ '' -
* ''pluto_security/ '' -
* ''pluto_speech/ '' -
* ''pluto_telecom/ '' -
* ''pnp_detection_scripts/ '' -
* ''shift_state/ '' -
* ''skins/ '' -
* ''so_postinst/ '' -
* ''sql2cpp/ '' -
* ''sqlCVS/ '' -
* ''ussp-push/ '' -
* ''utilities/ '' -
* ''BuildWinBinaries.bat '' -
* ''Construct '' -
* ''MakeRelease_All.bat '' -
* ''MakeRelease_Symbian_S60.bat '' -
* ''MakeRelease_Windows.bat '' -
* ''MakeRelease_WindowsCE.bat '' -
* ''Makefile '' -
* ''Makefile_all '' -
* ''SwitchToLinuxMCE.bat '' -
* ''SwitchToPluto.bat '' -
* ''build.xml '' -
* ''pluto.sln '' -
'''''trunk/ubuntu''''' contains ...
* ''asterisk/'' -
* ''libsdl1.2-1.2.10/'' -
* ''libsdl1.2-1.2.7+1.2.8cvs20041007/'' -
* ''lirc-pluto-0.1/'' -
* ''lshwd-2.0-rc4/'' -
* ''mtx-1.3.10/'' -
* ''tee-pluto/'' -
* ''xine-lib-1.1.3/'' -
'''''trunk/web''''' contains the two web-based configuration programs:
* ''Amp'' - The Asterisk (IP Phone exchange) management program
* ''pluto-admin'' - LinuxMCE Web Admin

[[Category:Development]]

Source Code

2008-01-10T15:51:11Z

Matthew: Use current source SVN

'''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.

=Current Source=
You can browse the [http://svn.charonmedia.com/trac.cgi/browser LinuxMCE source] at the [http://svn.charonmedia.com/ Charon Media Trac website]. Or you can download it from SVN:
<pre>
# Download snapshot.
wget http://www.charonmedia.org/lmce-1465.tbz

# Test checksum to ensure it was downloaded intact.
md5sum lmce-1465.tbz # should be b3d4b3f6b33ff5e6c4641390f2314095

# Update snapshot.
tar xfj lmce-1465.tbz
cd lmce
svn update

# Build from source (optional).
./configure
make
</pre>

The old version of the source code description (of the old SVN) could be a good starting point for identifying what each of the code in the current SVN does, but it's no guarantee. An updated version of that description would be very useful.

=Obsolete Source=
This section refers to the obsolete sourcecode stored at SourceForge. The current (recent 0704 and all 0710) source is stored at Charon Media, as mentioned in [#Current_Source]. The descriptions of the obsolete code might also be wrong descriptions of the current structure and content of the source code, but it could be a clue where none others exist, because that's where the current source code evolved from. (- [[User:Matthew|Matthew]] 08:51, 10 January 2008 (MST))

You can browse the [http://linuxmce.svn.sourceforge.net/viewvc/linuxmce/trunk/ web based repository viewer]. Or you can do an anonymous svn checkout as follows:

svn co <nowiki>http://</nowiki>linuxmce.svn.sourceforge.net/svnroot/linuxmce/trunk/''modulename''

You can checkout all the software with if you use http://linuxmce.svn.sourceforge.net/viewvc/linuxmce/trunk/ as the repository location for the module name, or go to the [http://linuxmce.svn.sourceforge.net/viewvc/linuxmce/trunk/ repository viewer] to find the name of the SVN directory for the module you are interested in.

Here are short instructions if you want compile your module with svn sources : [[Building_From_Source|Building from source]].

----

I've made a start at some pointers to finding your way around the code. [Note, I'm a noob here, so I may have got this wrong, so feel free to add/change. Also, it's by no means complete yet!]

'''''trunk/config-pkgs/''''' contains ...
* ''intel8x0/'' -
'''''trunk/installers/''''' contains ...
* ''CD_Installer/'' -
* ''Installers/'' -
* ''PhoneInstall/'' -
* ''WindowsInstaller/'' -
'''''trunk/libs/''''' contains ...
* ''CrossPlatform/'' -
* ''Libraries/'' -
'''''trunk/src/''''' contains ...
* ''ANSI-to-HTML/ '' -
* ''AVWizard/ '' -
* ''Add_Software/ '' -
* ''App_Server/ '' -
* ''AptUtils/ '' -
* ''Asterisk/ '' -
* ''BD/ '' -
* ''Basic_XML_Data_Source_Plugin/ '' -
* ''Bluetooth_Dongle/ '' -
* ''BootScripts/ '' -
* ''CDDB_Identifier/ '' -
* ''CM11A/ '' -
* ''CheckDependencyScript/ '' -
* ''CliUtils/ '' -
* ''Climate_Plugin/ '' -
* ''ColorSplitter/ '' -
* ''ConfirmDependencies/ '' -
* ''ConfirmDependencies_Script/ '' -
* ''ConfirmDependencies_Script_Offline/ '' -
* ''CreateDevice/ '' -
* ''Crystal_Fontz_USBRS232/ '' -
* ''DCE/ '' -
* ''DCEGen/ '' -
* ''DCERouter/ '' -
* ''Datagrid_Plugin/ '' -
* ''Dhcpd-Plugin/ '' -
* ''DiskMonitor/ '' -
* ''Disk_Drive/ '' -
* ''Disk_Drive_Functions/ '' -
* ''Diskless-Add-Ons/ '' -
* ''DynamicDNS/ '' -
* ''EIB/ '' -
* ''Event_Plugin/ '' -
* ''FakeEPG/ '' -
* ''File_Grids_Plugin/ '' -
* ''Firewire2Video4Linux/ '' -
* ''FirewireVideo/ '' -
* ''GalleryViewer/ '' -
* ''Gen_Devices/ '' -
* ''General_Info_Plugin/ '' -
* ''Generic_Serial_Device/ '' -
* ''GyrationMouse/ '' -
* ''HAL/ '' -
* ''HAL_DeviceFinder/ '' -
* ''HDHomeRun/ '' -
* ''Hooks_rcS/ '' -
* ''IR/ '' -
* ''IRBase/ '' -
* ''IRTrans/ '' -
* ''Infrared_Plugin/ '' -
* ''JobHandler/ '' -
* ''LIRC_DCE/ '' -
* ''Lighting_Plugin/ '' -
* ''Linphone/ '' -
* ''MaemoOrbiterLauncher/ '' -
* ''MakeRelease/ '' -
* ''MakeRelease_PrepFiles/ '' -
* ''Media_Live_LCDButtons/ '' -
* ''Media_Plugin/ '' -
* ''MessageSend/ '' -
* ''MessageTranslation/ '' -
* ''Motion_Wrapper/ '' -
* ''MythTV_Backend_Proxy/ '' -
* ''MythTV_Player/ '' -
* ''MythTV_PlugIn/ '' -
* ''Network_Storage/ '' -
* ''NewMD_interactor/ '' -
* ''Orbiter/ '' -
* ''OrbiterGen/ '' -
* ''Orbiter_Plugin/ '' -
* ''OutlookSync/ '' -
* ''Photo_Screen_Saver/ '' -
* ''Plug_And_Play_Plugin/ '' -
* ''PlutoDHCP/ '' -
* ''PlutoMO/ '' -
* ''PlutoRaidTools/ '' -
* ''PlutoStorageDevices/ '' -
* ''PlutoUpdateSystem/ '' -
* ''PlutoUpgradeHelper/ '' -
* ''PlutoUtils/ '' -
* ''PlutoVIP/ '' -
* ''Powerfile_C200/ '' -
* ''Proxy_Orbiter/ '' -
* ''Qos/ '' -
* ''RA/ '' -
* ''RemoteAssistance/ '' -
* ''SDL_Helpers/ '' -
* ''SMPTE_Fountain/ '' -
* ''STEngine/ '' -
* ''SVNLog/ '' -
* ''SambaScan/ '' -
* ''ScreenGen/ '' -
* ''Security_Plugin/ '' -
* ''Serial/ '' -
* ''SerializeClass/ '' -
* ''Setup_CaptureCards/ '' -
* ''Setup_SoundCards/ '' -
* ''SimplePhone/ '' -
* ''SlimServer_PlugIn/ '' -
* ''Slim_Server_Streamer/ '' -
* ''SoundScripts/ '' -
* ''Speech/ '' -
* ''Splitter/ '' -
* ''Telecom_Plugin/ '' -
* ''TestSerialPort/ '' -
* ''Test_Treo/ '' -
* ''Text_To_Speech/ '' -
* ''Tira/ '' -
* ''Tribune/ '' -
* ''Tribunexml/ '' -
* ''UPnP/ '' -
* ''USB_PNP/ '' -
* ''USB_UIRT_0038/ '' -
* ''UbuntuDiskless/ '' -
* ''Ubuntu_Helpers/ '' -
* ''UpdateEntArea/ '' -
* ''UpdateMedia/ '' -
* ''VDR/ '' -
* ''VDRPlugin/ '' -
* ''VFD_LCD/ '' -
* ''VIPDesign/ '' -
* ''VIPEstablishment/ '' -
* ''VIPServer/ '' -
* ''VIPShared/ '' -
* ''VideoLan_Client/ '' -
* ''VideoLan_PlugIn/ '' -
* ''VideoLan_Server/ '' -
* ''VoiceMailMonitor/ '' -
* ''WinBluetooth/ '' -
* ''Windows_Share_Scanner/ '' -
* ''X-KbLayout/ '' -
* ''X-Resolution/ '' -
* ''XML_Data_Handler_Plugin/ '' -
* ''XinePlayerTest/ '' -
* ''Xine_Player/ '' -
* ''Xine_Plugin/ '' -
* ''bin/ '' -
* ''convert_color/ '' -
* ''convert_mac/ '' -
* ''convert_time/ '' -
* ''database/ '' -
* ''database_audi/ '' -
* ''database_marbella/ '' -
* ''designer/ '' -
* ''docs/ '' -
* ''drivers/ '' -
* ''fakepkgs/ '' -
* ''gc100/ '' -
* ''inotify/ '' -
* ''kernel-upgrade/ '' -
* ''lib/ '' -
* ''mce-installer/ '' -
* ''mce-launcher/ '' -
* ''pluto-ati-drivers/ '' -
* ''pluto-nvidia-drivers/ '' -
* ''pluto_gcs-2.6_module/ '' -
* ''pluto_main/ '' -
* ''pluto_media/ '' -
* ''pluto_media_updater/ '' -
* ''pluto_security/ '' -
* ''pluto_speech/ '' -
* ''pluto_telecom/ '' -
* ''pnp_detection_scripts/ '' -
* ''shift_state/ '' -
* ''skins/ '' -
* ''so_postinst/ '' -
* ''sql2cpp/ '' -
* ''sqlCVS/ '' -
* ''ussp-push/ '' -
* ''utilities/ '' -
* ''BuildWinBinaries.bat '' -
* ''Construct '' -
* ''MakeRelease_All.bat '' -
* ''MakeRelease_Symbian_S60.bat '' -
* ''MakeRelease_Windows.bat '' -
* ''MakeRelease_WindowsCE.bat '' -
* ''Makefile '' -
* ''Makefile_all '' -
* ''SwitchToLinuxMCE.bat '' -
* ''SwitchToPluto.bat '' -
* ''build.xml '' -
* ''pluto.sln '' -
'''''trunk/ubuntu''''' contains ...
* ''asterisk/'' -
* ''libsdl1.2-1.2.10/'' -
* ''libsdl1.2-1.2.7+1.2.8cvs20041007/'' -
* ''lirc-pluto-0.1/'' -
* ''lshwd-2.0-rc4/'' -
* ''mtx-1.3.10/'' -
* ''tee-pluto/'' -
* ''xine-lib-1.1.3/'' -
'''''trunk/web''''' contains the two web-based configuration programs:
* ''Amp'' - The Asterisk (IP Phone exchange) management program
* ''pluto-admin'' - LinuxMCE Web Admin

[[Category:Development]]

HDTV

2008-01-06T16:49:16Z

Matthew: Created as summary & link to MythTV wiki

LinuxMCE supports HDTV with its MythTV component. So LMCE support is dependent on how MythTV supports it.

=External Info=
[http://www.mythtv.org/wiki/index.php/HDTV The MythTV wiki HDTV articles].

User talk:Rwilson131

2007-12-22T22:10:19Z

Matthew: PNG/JPG

==Useful Wiki Code Snippets==
The Table of contents can be forced onto a floating table on the right hand of the screen with the code below:

<nowiki> {| align="right"
| __TOC__
|}</nowiki>
Image tips

<nowiki>[[Image:Example.jpg|thumb|500px|left|Resolution Settings]]
 
</nowiki>

Hi R Wilson,
I've made a request for comment with regard to a debate we're having about categorization of articles. If you could take a look here [[LinuxMCE Wiki talk:Community Portal]] when you have time and perhaps leave a comment I'd be very grateful.

Thanks. [[User:Lozzo|Lozzo]] 11:36, 8 October 2007 (MST)

:Hi, thanks for your comments before. I've expanded a bit [[LinuxMCE Wiki talk:Community Portal|here]] on the differences between lists and categories, and why I think that a list article might be better. To clarify, I do believe that a big list of hardware is very useful - but that categories are not the best way to achieve this. I look forward to hearing your comments!

:Many thanks! [[User:Lozzo|Lozzo]] 07:07, 9 October 2007 (MST)

== Minor changes ==

Thanks for all the work you do on the wiki... I really appreciate it as it gives the wiki a lot of structure...

But let me make a suggestion... When you do minor changes like adding a cathegorie to a page, could you please mark them as a minor change ? I look at the recent changes quite frequently to stay up2date and it would be nice to see, when it's a minor change.

By the way, you can also setup to have the minor-change-box be checked by default, if that helps...

Best regards, --[[User:Chewi|Chewi]] 01:41, 15 October 2007 (MST)

== Image delete ==

The image has been deleted as requested :-)
[[User:Lozzo|Lozzo]] 03:21, 16 October 2007 (MST)

==Reply==
Hello and thanks for the welcome. I realize [[What hardware I will need]] and [[System Requirements]] are similar. I was using [[System Requirements]] as a rough draft for my revision of the [[What hardware I will need]] page. I just finished adding content from [[What hardware I will need]] and once I finish adding system req's for MDs, I may have the pages merged, with one redirecting to the other, depending on the feedback I get from wiki admins and the like. Thanks again and let me know if there's any other pages I can help with. --[[User:Bmk789|Bmk789]] 16:47, 6 December 2007 (MST)

== PNG/JPG ==

Hello Matthew,

I noticed that you uploaded a few images. Unfortunately, pngs are displayed, but coverting to jpgs will allow your images to be displayed.

convert foo.png foo.jpg

I hope this helps. I ran into this very problem when I started uploading files. --Rwilson131 11:09, 22 December 2007 (MST)
<HR>

Thanks. How did you notice?

FWIW, I was just using the wiki as a server at which to store images with a URL so I could insert the URL in a forum post with the [img] tag. But that discussion is about revisions to an articke ([[Cisco 7970]]) into which I expect to insert those images later. There's no wiki feature for converting on the server, right? And why does the wiki not display the PNGs? The wiki also seems not to support some other features from Wikipedia.org , like some table templates. Maybe the admin should turn those features on, or upgrade the Wiki SW if that's necessary.
- [[User:Matthew|Matthew]] 15:10, 22 December 2007 (MST)

User:Matthew

2007-12-22T04:00:42Z

Matthew:

[[Special:Upload]]

[[Image:Adminsite-gui.advanced-configuration-device-templates.png]] 
[[Image:Pick-device-template.1.png]] 
[[Image:Pick-device-template.2.png]]

File:Pick-device-template.2.png

2007-12-22T02:50:11Z

Matthew: Adminsite GUI Pick Device Template form page (2nd, lower part)

Adminsite GUI Pick Device Template form page (2nd, lower part)

File:Pick-device-template.1.png

2007-12-22T02:48:52Z

Matthew: Adminsite GUI Pick Device Template form page

Adminsite GUI Pick Device Template form page

File:Adminsite-gui.advanced-configuration-device-templates.png

2007-12-22T02:30:57Z

Matthew: Screenshot of Advanced > Configuration > Device Templates form page

Screenshot of Advanced > Configuration > Device Templates form page

User:Matthew

2007-12-22T02:28:46Z

Matthew: Create with upload test

[[Special:Upload]]
TEST

User:Matthew

2007-12-22T02:28:20Z

Matthew: Create with upload test

[Special:Upload]
TEST

Cisco 7970

2007-12-22T02:04:49Z

Matthew: Revert to even older version with instructions reported to work

[[Category: NeedsToBeFixed]][[Category: Hardware]]
[[Category: Phones]]
[[Category: Orbiters]]

== Preface ==
[[Image:Cisco7909.JPG]]

LinuxMCE allows to use many devices as Orbiters. One of them is CISCO 7970. You can use it to make calls and control your home as well. To add a new CISCO 7970 phone and Orbiter you should follow by this simple instruction. Basically I get the information in the LinuxMCE support forum. But I think it's good to accumulate odd posts in one place. If you have some suggestions send me email - stepanov.michael [at] gmail [dot] com or leave a comment.

== Preparation ==

CISCO 7970 phone is plug-in-play device and LinuxMCE adds it automatically when it'll be plugged in the network. But to do it we have to make some preparations. Run an Orbiter. Be sure that no others tasks are there!
Check DHCP setting of your phone. It should be something like that: "get IP via DHCP an no alternative servers".
Check the range of MAC addresses:
1. Go to Advanced --> Configuration --> Device Template.
2. Chose manufacture CISCO. You should see in the right list at least two models: 7079 and 7076.
3. Press the button 'Show model'.
4. On the opened window check 'Range MAC addresses'. The range contains two big decimal digits. To get correct range for your phone first see its MAC address. MAC address is six groups of two hexadecimal digits, separated by hyphens (-) or colon (:). The first three groups identify a maker. You leave them and fill the rest by 0 and F. For example, if MAC is 00:16:78:CD:01:D8 its range will be 00:16:78:00:00:00 - 00:14:69:FF:FF:FF. After that you should convert those two values into LinuxMCE representation. To do that run a script /usr/pluto/bin/convert_mac and pass the hexadecimal values as parameters:
<code>/usr/pluto/bin/convert_mac 00:16:78:00:00:00
/usr/pluto/bin/convert_mac 00:14:69:FF:FF:FF</code>
As result you will get two big decimal digits. Add them to the phone template and store.
5. There is a possibility to have some problems with phone installation related with its firmware. It should be latest. But I didn't have any problem with existing firmware on my CISCO 7079. But you should bear in mind it.
Well, after this preparation you can install your CISCO 7079 in LinuxMCE.

== Installation ==

1. Plug the phone power and network cable. Note if you have two network cards on your core you should plug network cable in the right switch.
2. During boot of the phone after 2-3 minutes you should see on the Orbiter a message about new device with your phone MAC address was detected. You should click by caption "Cisco 7970" below that.
3. After that the phone should be registered with asterisk and you can see a normal CISCO screen.
4. However, it'll take another 2-3 minutes to generate a new Orbiter for CISCO7079.
5. When this operation finishes you'll see a message on the Orbiter screen. Make a quick reload of router (Wizard -- Reboot -- Quick Reload Router. I also rebooted CISCO 7079 because I didn't see anything in the menu Services).
6. Now go to menu Services on CISCO 7970 and chose Orbiter.

== Troubleshooting ==
1. Problem: Phone boots successfully but there is no any message on the Orbiter's screen.
Solution: If the message doesn't appear check MAC addresses range.

== Some useful tips ==
1. To reset a Network configuration of CISCO7079 go to menu 'Network Setting' and press the following sequence of buttons:
<code>**#**</code>
2. To check network communications between CISCO7079 and CORE run tcpdump on the CORE:
<code>tcpdump -i eth1 [CISCO7079 IP Address]</code>
or to see detailed packets information:
<code>tcpdump -i -vv eth1 [CISCO7079 IP Address]</code>

== See also ==
* [[CISCO 7079 Orbiter]]

Cisco 7970

2007-12-22T01:20:28Z

Matthew: Revert to 21:46, 20 December 2007 version, + kept NeedsToBeFixed category

[[Category: NeedsToBeFixed]]
[[Category: Hardware]]
[[Category: Phones]]
[[Category: Orbiters]]
[[Image:Cisco7909.JPG]]

LinuxMCE allows to use many devices as Orbiters. One of them is the Cisco 7970. You can use it to make calls and control your home as well. To add a new Cisco 7970 phone and Orbiter you should follow these simple instructions. Basically I got the information in the [http://forum.linuxmce.org/index.php?action=search2&search=Cisco+7970 LinuxMCE support forum]. But I think it's good to accumulate odd posts in one place. If you have some suggestions send me email - stepanov.michael [at] gmail [dot] com or leave a comment.

There is also [http://forum.linuxmce.org/index.php?topic=3190.0 some discussion of upgrading Cisco 7970 firmware for using SIP instead of SCCP]. Complete info should be included in this wiki page.

=Preparation=
Cisco 7970 phone is plug-in-play device and LinuxMCE adds it automatically when it'll be plugged in the network. But to do it we have to make some preparations.
#Run an Orbiter.
#Be sure that no others tasks are pending ( Orbiter Home -> LinuxMCE:More -> Advanced Options -> Pending Tasks ) .
#Check DHCP setting on your phone. It should be configured as something like: "get IP via DHCP if no alternative servers".
#Check the range of MAC addresses LinuxMCE is configured to serve:
##Go to Admin website Home -> Advanced -> Configuration -> Device Template.
##Chose manufacture Cisco. You can filter the Device Template list by using a Device Category like "Hard Phones < Phones < Peripherals" (or a subset of that compound category). You should see in the Device Template list at least two models: 7960 and 7970.
##Press the button "Pick device template".
##On the opened window check 'Range MAC addresses'. The range contains two big decimal digits.
###To get correct range for your phone first see its MAC address.
###MAC address is six pairs of hexadecimal digits, separated by hyphens (-) or colon (:). The first three pairs identify a maker. You use them and fill the rest with three "00" or "FF" pairs as the start and end of the range. For example, if MAC is 00:16:78:CD:01:D8 its range will be 00:16:78:00:00:00 - 00:16:78:FF:FF:FF.
###Convert those two range delimiting values into LinuxMCE representation.
####Run the script /usr/pluto/bin/convert_mac, passing the hexadecimal values as parameters: <code>/usr/pluto/bin/convert_mac 00:16:78:00:00:00 ; /usr/pluto/bin/convert_mac 00:16:78:FF:FF:FF</code>
####You will get two big decimal numbers, one from each conversion of a hexadecimal MAC address.
####Add the decimal numbers to the phone template and store.

There is a possibility to have some problems with the phone installation related with its firmware. The firmware version should be the latest. I didn't have any problem with existing firmware on my Cisco 7970. But you should bear it in mind, as some more recent SIP firmware has failed to register with LinuxMCE's Asterisk subsystem. See Asterisk's own documentation (separate project) for details.

=Installation=
#Plug in the phone power and network cable. Note if you have two network cards in your core's machine you should plug network cable in the "inside" ethernet segment.
#During boot of the phone after 2-3 minutes you should see on the Orbiter a message about new device with your phone MAC address was detected. You should click by caption "Cisco 7970" below that.
#After that the phone should be registered with LinuxMCE's Asterisk subsystem and you can see a normal Cisco screen.
#However, it'll take another 2-3 minutes to generate a new Orbiter for the Cisco 7970.
#When this operation finishes you'll see a message on the Orbiter screen. Run a quick reload of router (Wizard -> Reboot -> Quick Reload Router; If the Cisco 7970 Services menu doesn't contain "Orbiter", reboot the phone).
#Now go to the Services menu on the Cisco 7970 and chose "Orbiter".

=Troubleshooting=
*Problem: Phone boots successfully but there isn't any message on the Orbiter's screen.
Solution: If the message doesn't appear check the LinuxMCE MAC addresses range to ensure the phone's correct MAC address is in the specified range

*next

=Useful tips=
#To reset a Network configuration of Cisco 7970 go to Admin website menu "Home -> Advanced -> Network Settings" and press the following sequence of buttons on the phone: **#**
#To check network communications between Cisco 7970 and CORE run tcpdump on the CORE: <code>tcpdump -i eth1 <Cisco 7970 IP Address></code>
#To see detailed packets information: <code>tcpdump -i -vv eth1 <Cisco 7970 IP Address></code>

=See also=
[[Orbiter]]

Nokia 770

2007-12-21T22:34:00Z

Matthew: Merge in "Tune Nokia770 to use it as LinuxMCE Orbiter"

[[Category: Hardware]]
[[Category: WebPads]]
[[Category: Orbiters]]

[[Image:Nokia770.jpg|right]]

[http://europe.nokia.com/770 Official Site]

=About the device=
'''Microprocessor:''' 220-MHz, ARM9-based Texas Instruments (TI) OMAP 1710 
'''RAM:''' 64MB DDR 
'''On-board memory:''' 128 MB, more than 64 MB available to the user 
'''Memory slot:''' RS-MMC (Reduced size MultiMedia Card) 
'''Battery:''' Standard Li-ion BP-5L Battery 1500 mAh (3 hours browse, 7 hours standby) 
'''Screen:''' 800×480 touch screen with up to 65,536 colors 
'''WiFi:''' 802.11 b/g 
'''Bluetooth:''' Bluetooth 1.2 - dial-up networking, file transfer, generic access, SIM access, and serial port profiles 
'''Audio:''' Audio out 
'''PC connectivity:''' USB (slave mode only) via DKE-2 cable 
'''OS:''' Internet Tablet 2005 (Maemo-based) 
'''Linux specs:''' 2.6 kernel, GNOME-based GUI 
'''Dimensions:''' Dimensions: 5.5 inches x 3.1 inches x 0.70 inch 
'''Weight:''' 8.1 ounces 
'''Price''': $140

The Nokia 770 works pretty well as a LinuxMCE Orbiter.

The Orbiter package and all dependences can be found in the [https://garage.maemo.org/frs/?group_id=162 Maemo garage], for information on how to use it read "[http://smart-home-blog.com/writes/nokia770-as-plutohome-orbiter-os2006/ Using Nokia770/N800 as a Plutohome Orbiter]" on the [[SmartBlog]].

See also [[Tune_Nokia770 Tune Nokia770 to use it as LinuxMCE Orbiter]]

=Preparing the Tablet=
==Before you begin==
First of all this is work in progress so don't expect the orbiter to be fully functional at full speed on this tablet. There are some known bugs so far:
* It will only run on OS 2005 for now so don't try to install this on newer firmware versions
* TTF rendering is not working so you won't see any text when browsing you media files :(
* Crashing and working a little slow

Thanks to Michael "[[User:Nite man|Nite man]]" Stepanov from IPTRIPLEPLAY Ltd [[mailto:info@iptp.net info@iptp.net]] who ported Orbiter on maemo platform.

==Installing OS 2005 on Nokia 770==
Since LinuxMCE Orbiter won't run on firmware version newer that SO 2005, you'll need to get that firmware version installed before you begin.

To check you current firmware version you can go to : MainMenu -> Control Panel -> Device -> About Product. There it should say 'Version: 3.2005...". If you already have this version installed then you can skip to next paragraph, else follow up this steps to get it installed.

The next steps are copy pasted from [[http://maemo.org/maemowiki/HOWTO_FlashLatestNokiaImageWithLinux the maemo wiki]] and adapted to meet your needs :

Beware that flashing a new image on the Nokia 770 will remove all user changes to the system, including preferences, bookmarks, news feeds, user installed applications... Everything not on the memory card will be gone and the device will behave as if just purchased with the single exception that any previously-set lock code will be kept and not reset to the factory-default of "12345" (even the code is not preserved on some images).
#PC: Download the Linux flasher at [[http://maemo.org/downloads/d3.php maemo.org]].
#PC: In the same directory download the image you want: [[http://www.maemo.org/downloads/nokia_770 Nokia_770_3.2005.51-13.bin]]
#770: Unplug charger and switch off the Nokia 770. Connect it to your computer via USB.
#PC: Execute as root (or as a normal user with rights to use the USB port):
#:<pre>
#: ./flasher-2.0 -F Nokia_770_3.2005.51-13.bin -f -R
#:</pre>
#PC: "Suitable USB device not found, waiting" is displayed on the console.
#770: Now plug in the charger to switch on the 770 or switch it on using the power button WHILE holding the Home-button.
#PC: Watch the messages as the image loads to the 770 after which it reboots automatically -- you're done now!

==Tune Nokia770 to use it as LinuxMCE Orbiter==
Many users of Nokia770 claim that the device work unstable as [http://pluto-nokia.garage.maemo.org LinuxMCE Orbiter]. The Orbiter crashes very often, especially on Video screen. So, [[User:Nite_man|I]] decided to make a brief research to make device more stable. Here area few suggestions.

#'''Apply WLAN memory corruption bugfix.'''
#:<pre>
#: > dmesg | grep CX3110x
#: Unloaded CX3110x driver, version 0.8
#: CX3110x chip variant: STLC4370
#: CX3110x: firmware version: 2.13.0.0.a.13.14
#: Loaded CX3110x driver, version 0.8.1-bug2006-fix1
#:</pre>
#:If your output diesn't show the "bug" fix like that, it needs to be patched. It's well-known [http://bugs.maemo.org/show_bug.cgi?id=2006 bug] from a long time ago but it was fixed just in the latest OS2007HE. There is a [http://fanoush.wz.cz/maemo/cx3110x-hotfix-bug2006_0.2_armel.deb package] which can also apply the WLAN memory corruption bugfix.
#'''Enable swap.'''
#:In the most of the cases when the Orbiter crashes there is no enough memory for the application. You can increase it by adding swap. Go to Control Panel --> Memory and chose tab 'Virtual'. You find there an information about available memory on the MMC card, box to activate swap and the list of offered sizes. Tick the box, chose appropriate size and press 'Ok'. Swap will be created on the MMC card and system starts to use it. Note: before remove the MMC card you should deactivate swap!.
#:In my test the Orbiter works stable with swap 48Mb. It didn't crash on the Video screen at all.
#'''Use seat belt.'''
#:[https://garage.maemo.org/projects/seatbelt Seat belt] is a small script for the Nokia 770 which changes the way memory is allocated to make more use of caches and swap. As a result it prevents crashes of the browser and other programs.
#'''Using access point with support WLAN Power Save Mode.'''
Nokia770 uses Power Save Mode to save energy. If the access point doesn't support that mode properly the device can loose its physical connection. Connection Manager may show high quality signal but the device is not accessible from the LAN.

(merged in from "[Tune Nokia770 to use it as LinuxMCE Orbiter]" originated by [[User:Nite_man]] 09:39, 21 December 2007)

=Configuring/Installing SW=

==Configuring the Core==
#Open up a web admin interface, go to Orbiter page and add a new device of type 'Orbiter'
#Locate the newly added device and change the resolution to 640x480 as the Nokia 770 won't support the default of 800x600
#Memorize the numeric id that LinuxMCE assigns to your new orbiter since you'll need it later, you can see it right of the 'Description' filed on the same page.
#Do a full regen of that orbiter and a quick reload router after that

==Configuring the Tablet==
#Setup you wireless connection. To use your tablet as an orbiter you'll need to make sure that the tablet is located within the internal network of the core.
#Upload the deb package to you tablet using the usb cable or by downloading it directly from our website. You can fetch the deb file [[http://plutohome.com/pluto-orbiter_0.1_arm.deb here]]
#Install it by double clicking the deb file from Nokia 770's File Manager.

==Starting the Orbiter==
#There is no easy way to start you orbiter yet, and you'll need an X terminal emulator to do this task. If you don't have it yet installed, download the osso-xterm deb package from [[http://770.fs-security.com/xterm/ fs-security.com]] and install it on you tablet the same way you installed the LinuxMCE orbiter package.
#Open up an xterminal using nokia 770's main menu: Extras -> X Terminal
#Make sure the network connection is available
#Type this in the terminal to start you orbiter
/var/lib/install/bin/startOrbiter.sh -r <ROUTER_INTERNAL_IP> -d <ORBITER_ID>
You can also start the orbiter with verbose logging to debug possible problems, but this will bring a slowdown in orbiter's screen changing :
/var/lib/install/bin/startOrbiterVerbose.sh -r <ROUTER_INTERNAL_IP> -d <ORBITER_ID>

==Getting Help==
For getting help and troubleshooting possible problems related to nokia 770 and LinuxMCE you can always talk to other users the [[http://plutohome.com/support/phpbb2/ forum]] and don't forget that this is still WiP.

=Building an Orbiter=
These are the instructions to build a version of [[Orbiter]] for the Nokia 770 internet platform. Nokia 770 has an ARM family processor, therefore you will need to cross-compile if your build machine is an Intel.

[[Image:Nokia-orbiter-small-400.jpg]]

==Requirements==
You will need:
* an Ubuntu box to host the build
* the Maemo 1.1 SDK for ARM ( http://repository.maemo.org/stable/1.1/arm/Maemo_Dev_Platform_RS_v1.1_arm.tgz )
* Scratchbox cross-compilation toolkit 0.9.8.5 (http://www.scratchbox.org/download/files/sbox-releases/0.9.8/deb/ )
scratchbox-core_0.9.8.5_i386.deb
scratchbox-devkit-debian_0.9.8.5_i386.deb
scratchbox-doctools_0.9.8.5_i386.deb
scratchbox-libs_0.9.8.5_i386.deb
scratchbox-toolchain-arm-glibc_0.9.8.5_i386.deb
scratchbox-toolchain-i686-glibc_0.9.8.5_i386.deb

==Preparing the Nokia tablet==
# Make sure it is connected to the network - check the Connection manager for a WiFi connection
# Open an X terminal on the tablet; make a directory in your home dir to hold the Orbiter binaries, say <tt>/home/user/orbiter</tt>
# You'll need a way to transfer files from the build machine to the tablet. Either have an HTTP server somewhere on your network, or install OpenSSH on the tablet. If you install OpenSSH, remember to also start it, by doing <tt>/etc/init.d/ssh start</tt>. To get a root prompt, use <tt>sudo gainroot</tt>.

==Preparing the build machine==
# Install Scratchbox debs on the build machine
# Add yourself as a Scratchbox user: <tt>'''/scratchbox/sbin/sbox_adduser ''username'''''</tt>
# Check out a fresh working copy of LinuxMCE from http://svn.plutohome.com/pluto/trunk/src/ into <tt>/scratchbox/users/username/pluto/trunk/src</tt> (username is assumed to be your user name on the build machine)
# Copy or symlink the Maemo SDK into <tt>/scratchbox/packages</tt>
# Log in to Scratchbox by typing <tt>'''scratchbox'''</tt>
# Configure Scratchbox cross-compile target:
#:<pre> > '''sbox-config -ct Nokia770'''
#:
#: Available compilers:
#: 0) arm-linux-gcc-3.3_3.3.4-glibc-2.3.2.ds1
#: 1) host-gcc
#: 2) i686-linux-gcc-3.3_3.3.4-glibc-2.3.2.ds1
#: Enter compiler number: '''0'''
#:
#: Available CPU-transparency methods:
#: sbrsh
#: qemu-arm
#: qemu-ppc
#:
#: Enter method name (qemu-arm): '''qemu-arm'''
#:
#: Available devkits:
#: debian
#:
#: Enter list of devkit names (none): '''debian'''
#:</pre>
# Select the new cross-compile target: <tt>'''sbox-config -st Nokia770'''</tt>
# Unpack the Maemo rootstrap: <tt>'''sbox-config -er /scratchbox/packages/Maemo_Dev_Platform_RS_v1.1_arm.tgz'''</tt>
# <tt>'''sbox-config -cc'''</tt>
# <tt>'''sbox-config -cf'''</tt>
# Update the package list inside Scratchbox by typing <tt>apt-get update</tt>
# Install the following build-time dependencies (with <tt>apt-get install</tt>)
#* libmysqlclient12-dev
#* libid3-dev
#* xlibmesa-gl-dev
# Before starting to compile Orbiter and its dependencies, type: export SNR_CPPFLAGS="-DMAEMO_NOKIA770" (add there -DDEBUG if you want to see all debug messages) and export SNR_LDFLAGS="". Also, apply that patch to Orbiter Makefile to remove GL and HID dependences:

<pre>
--- src-2.0.0.44/src/Orbiter/Makefile 2007-03-05 13:44:44.000000000 -0800
+++ tmp/Makefile 2007-06-07 08:02:09.000000000 -0700
@@ -23,9 +23,9 @@

CXXFLAGS += -g -O0
-CPPFLAGS += -I/usr/include/SDL -DORBITER -DCACHE_IMAGES -DENABLE_MOUSE_BEHAVIOR -I$(ROOT)/Splitter -I$(ROOT)/OrbiterGen -I$(ROOT)/SDL_Helpers -DHID_REMOTE
+CPPFLAGS += -I/usr/include/SDL -DORBITER -DCACHE_IMAGES -DENABLE_MOUSE_BEHAVIOR -I$(ROOT)/Splitter -I$(ROOT)/OrbiterGen -I$(ROOT)/SDL_Helpers
LDFLAGS += -L/usr/X11R6/lib
-XTRALDLIBS += -lDCECommon -lSDL -lSDL_ttf -lSDL_image -lSGE -lSDL_gfx -lXtst -lXext -lGL -lXrender -lGLU -lSDL_Helpers -lhid
+XTRALDLIBS += -lDCECommon -lSDL -lSDL_ttf -lSDL_image -lSGE -lSDL_gfx -lXtst -lXext -lXrender -lSDL_Helpers -lhid

# wmctrl wrapper
CPPFLAGS += -I/usr/X11R6/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
@@ -38,7 +38,6 @@
../utilities/linux/wrapper/wrapper_x11.cpp \
../utilities/linux/wrapper/image_file.cpp \
Linux/win_list_manager.cpp \
- Linux/HIDInterface.cpp \
Linux/OrbiterRenderer_Linux.cpp \
Linux/WindowContext.cpp \
DesignObj_Data.cpp \
</pre>

==Building Orbiter==
# While inside Scratchbox, go into /pluto/trunk/src/SerializeClass and type <tt>'''make'''</tt>
# Go into /pluto/trunk/src/PlutoUtils and type <tt>'''make'''</tt>
# Go into /pluto/trunk/src/DCE and type <tt>'''make'''</tt>
# Go into /pluto/trunk/src/SDL_Helpers and type <tt>'''make'''</tt>
# Go into /pluto/trunk/src/Orbiter and type <tt>'''make bin'''</tt>
# After a while, the following files will result in /pluto/trunk/src
#* lib/libDCECommon.so
#* lib/libSerializeClass.so
#* lib/libPlutoUtils.so
#* lib/libSDL_Helpers.so
#* bin/Orbiter
# Copy these files over to the tablet, in /home/user/orbiter
# Don't forget strip Orbiter binaries to save space:
#* strip lib/*
#* strip bin/*

==Running Orbiter==

Before starting Orbiter following applications and libraries should be installed:

* mysql-common
* libmysqlclient
* libhttpfetcher
* libhid (should be removed soon)
* libsdl-sge
* libsdl-gfx
* libsdl
* libgle
* libxmu
* libsdl-ttf
* libsdl-image
* libsm
* libice
* libxt
* xterm
* ssh

To do that just add additional repository repository.maemo.org and activate [http://wiki.snc.sapmi.net/doku.php?id=snc:nokia#red_pill_mode Red Pill Mode]. Additionally, you should [http://maemo.org/community/wiki/howdoibecomeroot/ became a root] on your device.

In an X terminal On the tablet itself (NOT via ssh) do this:
cd /home/user/orbiter
export LD_LIBRARY_PATH=.
./Orbiter -r xxx.xxx.xxx.xxx -d yy -l orbiter.log
where xxx.xxx.xxx.xxx is the IP address of the DCE Router, and yy is the device number assigned to your new Orbiter.

If it complains about missing .so files, copy them over from your Scratchbox on the build machine into /home/user/orbiter on the tablet.

'''Notice:''' you need true type fonts on your Nokia770. The orbiter searches them here - '''/usr/share/truetype/msttcorefonts'''. Just copy this directory from your core to Nokia770 (the Debian package for Nokia is coming soon).

==Building Debian packages==
# Dependencies can be found [https://garage.maemo.org/frs/?group_id=162 here]
# The latest Orbiter binaries get [https://garage.maemo.org/frs/?group_id=162 here]
# Orbiter package - [https://garage.maemo.org/frs/?group_id=162 here]

=External references=

* [https://garage.maemo.org/frs/?group_id=162 Plutohome Nokia Orbiter on maemo garage]
* [http://smart-home-blog.com/writes/howto-build-plutohome-orbiter-for-nokia770/ Howto Build Plutohome Orbiter for Nokia770]
* [http://smart-home-blog.com/writes/nokia770-as-plutohome-orbiter-os2006/ Using Nokia770/N800 as Plutohome Orbiter]
* [http://smart-home-blog.com/archives/886 Tune Nokia770 to use as LinuxMCE Orbiter]
* [http://www.maemo.org/platform/docs/tutorials/Maemo_tutorial.html#settingup Maemo Tutorial]

Nokia 770

2007-12-21T20:58:00Z

Matthew: cleanup, fix lists

[[Category: Hardware]]
[[Category: WebPads]]
[[Category: Orbiters]]

[[Image:Nokia770.jpg|right]]

[http://europe.nokia.com/770 Official Site]

=About the device=
'''Microprocessor:''' 220-MHz, ARM9-based Texas Instruments (TI) OMAP 1710 
'''RAM:''' 64MB DDR 
'''On-board memory:''' 128 MB, more than 64 MB available to the user 
'''Memory slot:''' RS-MMC (Reduced size MultiMedia Card) 
'''Battery:''' Standard Li-ion BP-5L Battery 1500 mAh (3 hours browse, 7 hours standby) 
'''Screen:''' 800×480 touch screen with up to 65,536 colors 
'''WiFi:''' 802.11 b/g 
'''Bluetooth:''' Bluetooth 1.2 - dial-up networking, file transfer, generic access, SIM access, and serial port profiles 
'''Audio:''' Audio out 
'''PC connectivity:''' USB (slave mode only) via DKE-2 cable 
'''OS:''' Internet Tablet 2005 (Maemo-based) 
'''Linux specs:''' 2.6 kernel, GNOME-based GUI 
'''Dimensions:''' Dimensions: 5.5 inches x 3.1 inches x 0.70 inch 
'''Weight:''' 8.1 ounces 
'''Price''': $140

The Nokia 770 works pretty well as a LinuxMCE Orbiter.

The Orbiter package and all dependences can be found in the [https://garage.maemo.org/frs/?group_id=162 Maemo garage], for information on how to use it read "[http://smart-home-blog.com/writes/nokia770-as-plutohome-orbiter-os2006/ Using Nokia770/N800 as a Plutohome Orbiter]" on the [[SmartBlog]].

See also [[Tune_Nokia770 Tune Nokia770 to use it as LinuxMCE Orbiter]]

=Preparing the Tablet=
==Before you begin==
First of all this is work in progress so don't expect the orbiter to be fully functional at full speed on this tablet. There are some known bugs so far:
* It will only run on OS 2005 for now so don't try to install this on newer firmware versions
* TTF rendering is not working so you won't see any text when browsing you media files :(
* Crashing and working a little slow

Thanks to Michael "[[User:Nite man|Nite man]]" Stepanov from IPTRIPLEPLAY Ltd [[mailto:info@iptp.net info@iptp.net]] who ported Orbiter on maemo platform.

==Installing OS 2005 on Nokia 770==
Since LinuxMCE Orbiter won't run on firmware version newer that SO 2005, you'll need to get that firmware version installed before you begin.

To check you current firmware version you can go to : MainMenu -> Control Panel -> Device -> About Product. There it should say 'Version: 3.2005...". If you already have this version installed then you can skip to next paragraph, else follow up this steps to get it installed.

The next steps are copy pasted from [[http://maemo.org/maemowiki/HOWTO_FlashLatestNokiaImageWithLinux the maemo wiki]] and adapted to meet your needs :

Beware that flashing a new image on the Nokia 770 will remove all user changes to the system, including preferences, bookmarks, news feeds, user installed applications... Everything not on the memory card will be gone and the device will behave as if just purchased with the single exception that any previously-set lock code will be kept and not reset to the factory-default of "12345" (even the code is not preserved on some images).
#PC: Download the Linux flasher at [[http://maemo.org/downloads/d3.php maemo.org]].
#PC: In the same directory download the image you want: [[http://www.maemo.org/downloads/nokia_770 Nokia_770_3.2005.51-13.bin]]
#770: Unplug charger and switch off the Nokia 770. Connect it to your computer via USB.
#PC: Execute as root (or as a normal user with rights to use the USB port):
#:<pre>
#: ./flasher-2.0 -F Nokia_770_3.2005.51-13.bin -f -R
#:</pre>
#PC: "Suitable USB device not found, waiting" is displayed on the console.
#770: Now plug in the charger to switch on the 770 or switch it on using the power button WHILE holding the Home-button.
#PC: Watch the messages as the image loads to the 770 after which it reboots automatically -- you're done now!

=Configuring/Installing SW=

==Configuring the Core==
#Open up a web admin interface, go to Orbiter page and add a new device of type 'Orbiter'
#Locate the newly added device and change the resolution to 640x480 as the Nokia 770 won't support the default of 800x600
#Memorize the numeric id that LinuxMCE assigns to your new orbiter since you'll need it later, you can see it right of the 'Description' filed on the same page.
#Do a full regen of that orbiter and a quick reload router after that

==Configuring the Tablet==
#Setup you wireless connection. To use your tablet as an orbiter you'll need to make sure that the tablet is located within the internal network of the core.
#Upload the deb package to you tablet using the usb cable or by downloading it directly from our website. You can fetch the deb file [[http://plutohome.com/pluto-orbiter_0.1_arm.deb here]]
#Install it by double clicking the deb file from Nokia 770's File Manager.

==Starting the Orbiter==
#There is no easy way to start you orbiter yet, and you'll need an X terminal emulator to do this task. If you don't have it yet installed, download the osso-xterm deb package from [[http://770.fs-security.com/xterm/ fs-security.com]] and install it on you tablet the same way you installed the LinuxMCE orbiter package.
#Open up an xterminal using nokia 770's main menu: Extras -> X Terminal
#Make sure the network connection is available
#Type this in the terminal to start you orbiter
/var/lib/install/bin/startOrbiter.sh -r <ROUTER_INTERNAL_IP> -d <ORBITER_ID>
You can also start the orbiter with verbose logging to debug possible problems, but this will bring a slowdown in orbiter's screen changing :
/var/lib/install/bin/startOrbiterVerbose.sh -r <ROUTER_INTERNAL_IP> -d <ORBITER_ID>

==Getting Help==
For getting help and troubleshooting possible problems related to nokia 770 and LinuxMCE you can always talk to other users the [[http://plutohome.com/support/phpbb2/ forum]] and don't forget that this is still WiP.

=Building an Orbiter=
These are the instructions to build a version of [[Orbiter]] for the Nokia 770 internet platform. Nokia 770 has an ARM family processor, therefore you will need to cross-compile if your build machine is an Intel.

[[Image:Nokia-orbiter-small-400.jpg]]

==Requirements==
You will need:
* an Ubuntu box to host the build
* the Maemo 1.1 SDK for ARM ( http://repository.maemo.org/stable/1.1/arm/Maemo_Dev_Platform_RS_v1.1_arm.tgz )
* Scratchbox cross-compilation toolkit 0.9.8.5 (http://www.scratchbox.org/download/files/sbox-releases/0.9.8/deb/ )
scratchbox-core_0.9.8.5_i386.deb
scratchbox-devkit-debian_0.9.8.5_i386.deb
scratchbox-doctools_0.9.8.5_i386.deb
scratchbox-libs_0.9.8.5_i386.deb
scratchbox-toolchain-arm-glibc_0.9.8.5_i386.deb
scratchbox-toolchain-i686-glibc_0.9.8.5_i386.deb

==Preparing the Nokia tablet==
# Make sure it is connected to the network - check the Connection manager for a WiFi connection
# Open an X terminal on the tablet; make a directory in your home dir to hold the Orbiter binaries, say <tt>/home/user/orbiter</tt>
# You'll need a way to transfer files from the build machine to the tablet. Either have an HTTP server somewhere on your network, or install OpenSSH on the tablet. If you install OpenSSH, remember to also start it, by doing <tt>/etc/init.d/ssh start</tt>. To get a root prompt, use <tt>sudo gainroot</tt>.

==Preparing the build machine==
# Install Scratchbox debs on the build machine
# Add yourself as a Scratchbox user: <tt>'''/scratchbox/sbin/sbox_adduser ''username'''''</tt>
# Check out a fresh working copy of LinuxMCE from http://svn.plutohome.com/pluto/trunk/src/ into <tt>/scratchbox/users/username/pluto/trunk/src</tt> (username is assumed to be your user name on the build machine)
# Copy or symlink the Maemo SDK into <tt>/scratchbox/packages</tt>
# Log in to Scratchbox by typing <tt>'''scratchbox'''</tt>
# Configure Scratchbox cross-compile target:
#:<pre> > '''sbox-config -ct Nokia770'''
#:
#: Available compilers:
#: 0) arm-linux-gcc-3.3_3.3.4-glibc-2.3.2.ds1
#: 1) host-gcc
#: 2) i686-linux-gcc-3.3_3.3.4-glibc-2.3.2.ds1
#: Enter compiler number: '''0'''
#:
#: Available CPU-transparency methods:
#: sbrsh
#: qemu-arm
#: qemu-ppc
#:
#: Enter method name (qemu-arm): '''qemu-arm'''
#:
#: Available devkits:
#: debian
#:
#: Enter list of devkit names (none): '''debian'''
#:</pre>
# Select the new cross-compile target: <tt>'''sbox-config -st Nokia770'''</tt>
# Unpack the Maemo rootstrap: <tt>'''sbox-config -er /scratchbox/packages/Maemo_Dev_Platform_RS_v1.1_arm.tgz'''</tt>
# <tt>'''sbox-config -cc'''</tt>
# <tt>'''sbox-config -cf'''</tt>
# Update the package list inside Scratchbox by typing <tt>apt-get update</tt>
# Install the following build-time dependencies (with <tt>apt-get install</tt>)
#* libmysqlclient12-dev
#* libid3-dev
#* xlibmesa-gl-dev
# Before starting to compile Orbiter and its dependencies, type: export SNR_CPPFLAGS="-DMAEMO_NOKIA770" (add there -DDEBUG if you want to see all debug messages) and export SNR_LDFLAGS="". Also, apply that patch to Orbiter Makefile to remove GL and HID dependences:

<pre>
--- src-2.0.0.44/src/Orbiter/Makefile 2007-03-05 13:44:44.000000000 -0800
+++ tmp/Makefile 2007-06-07 08:02:09.000000000 -0700
@@ -23,9 +23,9 @@

CXXFLAGS += -g -O0
-CPPFLAGS += -I/usr/include/SDL -DORBITER -DCACHE_IMAGES -DENABLE_MOUSE_BEHAVIOR -I$(ROOT)/Splitter -I$(ROOT)/OrbiterGen -I$(ROOT)/SDL_Helpers -DHID_REMOTE
+CPPFLAGS += -I/usr/include/SDL -DORBITER -DCACHE_IMAGES -DENABLE_MOUSE_BEHAVIOR -I$(ROOT)/Splitter -I$(ROOT)/OrbiterGen -I$(ROOT)/SDL_Helpers
LDFLAGS += -L/usr/X11R6/lib
-XTRALDLIBS += -lDCECommon -lSDL -lSDL_ttf -lSDL_image -lSGE -lSDL_gfx -lXtst -lXext -lGL -lXrender -lGLU -lSDL_Helpers -lhid
+XTRALDLIBS += -lDCECommon -lSDL -lSDL_ttf -lSDL_image -lSGE -lSDL_gfx -lXtst -lXext -lXrender -lSDL_Helpers -lhid

# wmctrl wrapper
CPPFLAGS += -I/usr/X11R6/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
@@ -38,7 +38,6 @@
../utilities/linux/wrapper/wrapper_x11.cpp \
../utilities/linux/wrapper/image_file.cpp \
Linux/win_list_manager.cpp \
- Linux/HIDInterface.cpp \
Linux/OrbiterRenderer_Linux.cpp \
Linux/WindowContext.cpp \
DesignObj_Data.cpp \
</pre>

==Building Orbiter==
# While inside Scratchbox, go into /pluto/trunk/src/SerializeClass and type <tt>'''make'''</tt>
# Go into /pluto/trunk/src/PlutoUtils and type <tt>'''make'''</tt>
# Go into /pluto/trunk/src/DCE and type <tt>'''make'''</tt>
# Go into /pluto/trunk/src/SDL_Helpers and type <tt>'''make'''</tt>
# Go into /pluto/trunk/src/Orbiter and type <tt>'''make bin'''</tt>
# After a while, the following files will result in /pluto/trunk/src
#* lib/libDCECommon.so
#* lib/libSerializeClass.so
#* lib/libPlutoUtils.so
#* lib/libSDL_Helpers.so
#* bin/Orbiter
# Copy these files over to the tablet, in /home/user/orbiter
# Don't forget strip Orbiter binaries to save space:
#* strip lib/*
#* strip bin/*

==Running Orbiter==

Before starting Orbiter following applications and libraries should be installed:

* mysql-common
* libmysqlclient
* libhttpfetcher
* libhid (should be removed soon)
* libsdl-sge
* libsdl-gfx
* libsdl
* libgle
* libxmu
* libsdl-ttf
* libsdl-image
* libsm
* libice
* libxt
* xterm
* ssh

To do that just add additional repository repository.maemo.org and activate [http://wiki.snc.sapmi.net/doku.php?id=snc:nokia#red_pill_mode Red Pill Mode]. Additionally, you should [http://maemo.org/community/wiki/howdoibecomeroot/ became a root] on your device.

In an X terminal On the tablet itself (NOT via ssh) do this:
cd /home/user/orbiter
export LD_LIBRARY_PATH=.
./Orbiter -r xxx.xxx.xxx.xxx -d yy -l orbiter.log
where xxx.xxx.xxx.xxx is the IP address of the DCE Router, and yy is the device number assigned to your new Orbiter.

If it complains about missing .so files, copy them over from your Scratchbox on the build machine into /home/user/orbiter on the tablet.

'''Notice:''' you need true type fonts on your Nokia770. The orbiter searches them here - '''/usr/share/truetype/msttcorefonts'''. Just copy this directory from your core to Nokia770 (the Debian package for Nokia is coming soon).

==Building Debian packages==
# Dependencies can be found [https://garage.maemo.org/frs/?group_id=162 here]
# The latest Orbiter binaries get [https://garage.maemo.org/frs/?group_id=162 here]
# Orbiter package - [https://garage.maemo.org/frs/?group_id=162 here]

=External references=

* [https://garage.maemo.org/frs/?group_id=162 Plutohome Nokia Orbiter on maemo garage]
* [http://smart-home-blog.com/writes/howto-build-plutohome-orbiter-for-nokia770/ Howto Build Plutohome Orbiter for Nokia770]
* [http://smart-home-blog.com/writes/nokia770-as-plutohome-orbiter-os2006/ Using Nokia770/N800 as Plutohome Orbiter]
* [http://smart-home-blog.com/archives/886 Tune Nokia770 to use as LinuxMCE Orbiter]
* [http://www.maemo.org/platform/docs/tutorials/Maemo_tutorial.html#settingup Maemo Tutorial]

Nokia 770

2007-12-21T20:14:35Z

Matthew: Clean up section names

[[Category: Hardware]]
[[Category: WebPads]]
[[Category: Orbiters]]

[[Image:Nokia770.jpg|right]]

[http://europe.nokia.com/770 Official Site]

=About the device=
'''Microprocessor:''' 220-MHz, ARM9-based Texas Instruments (TI) OMAP 1710 
'''RAM:''' 64MB DDR 
'''On-board memory:''' 128 MB, more than 64 MB available to the user 
'''Memory slot:''' RS-MMC (Reduced size MultiMedia Card) 
'''Battery:''' Standard Li-ion BP-5L Battery 1500 mAh (3 hours browse, 7 hours standby) 
'''Screen:''' 800×480 touch screen with up to 65,536 colors 
'''WiFi:''' 802.11 b/g 
'''Bluetooth:''' Bluetooth 1.2 - dial-up networking, file transfer, generic access, SIM access, and serial port profiles 
'''Audio:''' Audio out 
'''PC connectivity:''' USB (slave mode only) via DKE-2 cable 
'''OS:''' Internet Tablet 2005 (Maemo-based) 
'''Linux specs:''' 2.6 kernel, GNOME-based GUI 
'''Dimensions:''' Dimensions: 5.5 inches x 3.1 inches x 0.70 inch 
'''Weight:''' 8.1 ounces 
Price: $140

The Nokia770 works pretty well as a LinuxMCE Orbiter.

The Orbiter package and all dependences can be found in the [https://garage.maemo.org/frs/?group_id=162 Maemo garage], for information on how to use it read "[http://smart-home-blog.com/writes/nokia770-as-plutohome-orbiter-os2006/ Using Nokia770/N800 as a Plutohome Orbiter]" on the [[SmartBlog]].

See also [[Tune_Nokia770 Tune Nokia770 to use it as LinuxMCE Orbiter]]

=Preparing the Tablet=
==Before you begin==
First of all this is work in progress so don't expect the orbiter to be fully functional at full speed on this tablet. There are some known bugs so far:
* It will only run on OS 2005 for now so don't try to install this on newer firmware versions
* TTF rendering is not working so you won't see any text when browsing you media files :(
* Crashing and working a little slow

Thanks to Michael "[[User:Nite man|Nite man]]" Stepanov from IPTRIPLEPLAY Ltd [[mailto:info@iptp.net info@iptp.net]] who ported Orbiter on maemo platform.

==Installing OS 2005 on Nokia 770==
Since LinuxMCE Orbiter won't run on firmware version newer that SO 2005, you'll need to get that firmware version installed before you begin.

To check you current firmware version you can go to : MainMenu -> Control Panel -> Device -> About Product. There it should say 'Version: 3.2005...". If you already have this version installed then you can skip to next paragraph, else follow up this steps to get it installed.

The next steps are copy pasted from [[http://maemo.org/maemowiki/HOWTO_FlashLatestNokiaImageWithLinux maemo wiki]] and adapted to meet you needs :

Beware that flashing a new image on the Nokia 770 will remove all user changes to the system, including preferences, bookmarks, news feeds, user installed applications, ... Everything not on the memory card will be gone and the device will behave as if just purchased with the single exception that any previously-set lock code will be kept and not reset to the factory-default of "12345" (even the code is not preserved on some images).

*PC: Download the Linux flasher at [[http://maemo.org/downloads/d3.php maemo.org]]
*PC: In the same directory download the image you want: [[http://www.maemo.org/downloads/nokia_770 Nokia_770_3.2005.51-13.bin]]
*770: Unplug charger and switch off the Nokia 770. Connect it to your computer via USB
*PC: Execute as root (or as a normal user with rights to use the USB port):
./flasher-2.0 -F Nokia_770_3.2005.51-13.bin -f -R
*PC: "Suitable USB device not found, waiting" is displayed on the console
*770: Now plug in the charger to switch on the 770 or switch it on using the power button WHILE holding the Home-button
*PC: Watch the messages as the image loads to the 770 after which it reboots automatically -- you're done now!

=Configuring/Installing SW=

==Configuring the Core==
#Open up a web admin interface, go to Orbiter page and add a new device of type 'Orbiter'
#Locate the newly added device and change the resolution to 640x480 as the Nokia 770 won't support the default of 800x600
#Memorize the numeric id that LinuxMCE assigns to your new orbiter since you'll need it later, you can see it right of the 'Description' filed on the same page.
#Do a full regen of that orbiter and a quick reload router after that

==Configuring the Tablet==
#Setup you wireless connection. To use your tablet as an orbiter you'll need to make sure that the tablet is located within the internal network of the core.
#Upload the deb package to you tablet using the usb cable or by downloading it directly from our website. You can fetch the deb file [[http://plutohome.com/pluto-orbiter_0.1_arm.deb here]]
#Install it by double clicking the deb file from Nokia 770's File Manager.

==Starting the Orbiter==
#There is no easy way to start you orbiter yet, and you'll need an X terminal emulator to do this task. If you don't have it yet installed, download the osso-xterm deb package from [[http://770.fs-security.com/xterm/ fs-security.com]] and install it on you tablet the same way you installed the LinuxMCE orbiter package.
#Open up an xterminal using nokia 770's main menu: Extras -> X Terminal
#Make sure the network connection is available
#Type this in the terminal to start you orbiter
/var/lib/install/bin/startOrbiter.sh -r <ROUTER_INTERNAL_IP> -d <ORBITER_ID>
You can also start the orbiter with verbose logging to debug possible problems, but this will bring a slowdown in orbiter's screen changing :
/var/lib/install/bin/startOrbiterVerbose.sh -r <ROUTER_INTERNAL_IP> -d <ORBITER_ID>

==Getting Help==
For getting help and troubleshooting possible problems related to nokia 770 and LinuxMCE you can always talk to other users the [[http://plutohome.com/support/phpbb2/ forum]] and don't forget that this is still WiP.

=Building an Orbiter=
These are the instructions to build a version of [[Orbiter]] for the Nokia 770 internet platform. Nokia 770 has an ARM family processor, therefore you will need to cross-compile if your build machine is an Intel.

[[Image:Nokia-orbiter-small-400.jpg]]

==Requirements==
You will need:
* an Ubuntu box to host the build
* the Maemo 1.1 SDK for ARM ( http://repository.maemo.org/stable/1.1/arm/Maemo_Dev_Platform_RS_v1.1_arm.tgz )
* Scratchbox cross-compilation toolkit 0.9.8.5 (http://www.scratchbox.org/download/files/sbox-releases/0.9.8/deb/ )
scratchbox-core_0.9.8.5_i386.deb
scratchbox-devkit-debian_0.9.8.5_i386.deb
scratchbox-doctools_0.9.8.5_i386.deb
scratchbox-libs_0.9.8.5_i386.deb
scratchbox-toolchain-arm-glibc_0.9.8.5_i386.deb
scratchbox-toolchain-i686-glibc_0.9.8.5_i386.deb

==Preparing the Nokia tablet==
# Make sure it is connected to the network - check the Connection manager for a WiFi connection
# Open an X terminal on the tablet; make a directory in your home dir to hold the Orbiter binaries, say <tt>/home/user/orbiter</tt>
# You'll need a way to transfer files from the build machine to the tablet. Either have an HTTP server somewhere on your network, or install OpenSSH on the tablet. If you install OpenSSH, remember to also start it, by doing <tt>/etc/init.d/ssh start</tt>. To get a root prompt, use <tt>sudo gainroot</tt>.

==Preparing the build machine==
# Install Scratchbox debs on the build machine
# Add yourself as a Scratchbox user: <tt>'''/scratchbox/sbin/sbox_adduser ''username'''''</tt>
# Check out a fresh working copy of LinuxMCE from http://svn.plutohome.com/pluto/trunk/src/ into <tt>/scratchbox/users/username/pluto/trunk/src</tt> (username is assumed to be your user name on the build machine)
# Copy or symlink the Maemo SDK into <tt>/scratchbox/packages</tt>
# Log in to Scratchbox by typing <tt>'''scratchbox'''</tt>
# Configure Scratchbox cross-compile target:
> '''sbox-config -ct Nokia770'''

Available compilers:
0) arm-linux-gcc-3.3_3.3.4-glibc-2.3.2.ds1
1) host-gcc
2) i686-linux-gcc-3.3_3.3.4-glibc-2.3.2.ds1

Enter compiler number: '''0'''

Available CPU-transparency methods:
sbrsh
qemu-arm
qemu-ppc

Enter method name (qemu-arm): '''qemu-arm'''

Available devkits:
debian

Enter list of devkit names (none): '''debian'''
# Select the new cross-compile target: <tt>'''sbox-config -st Nokia770'''</tt>
# Unpack the Maemo rootstrap: <tt>'''sbox-config -er /scratchbox/packages/Maemo_Dev_Platform_RS_v1.1_arm.tgz'''</tt>
# <tt>'''sbox-config -cc'''</tt>
# <tt>'''sbox-config -cf'''</tt>
# Update the package list inside Scratchbox by typing <tt>apt-get update</tt>
# Install the following build-time dependencies (with <tt>apt-get install</tt>)
#* libmysqlclient12-dev
#* libid3-dev
#* xlibmesa-gl-dev
# Before starting to compile Orbiter and its dependencies, type: export SNR_CPPFLAGS="-DMAEMO_NOKIA770" (add there -DDEBUG if you want to see all debug messages) and export SNR_LDFLAGS="". Also, apply that patch to Orbiter Makefile to remove GL and HID dependences:

<pre>
--- src-2.0.0.44/src/Orbiter/Makefile 2007-03-05 13:44:44.000000000 -0800
+++ tmp/Makefile 2007-06-07 08:02:09.000000000 -0700
@@ -23,9 +23,9 @@

CXXFLAGS += -g -O0
-CPPFLAGS += -I/usr/include/SDL -DORBITER -DCACHE_IMAGES -DENABLE_MOUSE_BEHAVIOR -I$(ROOT)/Splitter -I$(ROOT)/OrbiterGen -I$(ROOT)/SDL_Helpers -DHID_REMOTE
+CPPFLAGS += -I/usr/include/SDL -DORBITER -DCACHE_IMAGES -DENABLE_MOUSE_BEHAVIOR -I$(ROOT)/Splitter -I$(ROOT)/OrbiterGen -I$(ROOT)/SDL_Helpers
LDFLAGS += -L/usr/X11R6/lib
-XTRALDLIBS += -lDCECommon -lSDL -lSDL_ttf -lSDL_image -lSGE -lSDL_gfx -lXtst -lXext -lGL -lXrender -lGLU -lSDL_Helpers -lhid
+XTRALDLIBS += -lDCECommon -lSDL -lSDL_ttf -lSDL_image -lSGE -lSDL_gfx -lXtst -lXext -lXrender -lSDL_Helpers -lhid

# wmctrl wrapper
CPPFLAGS += -I/usr/X11R6/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
@@ -38,7 +38,6 @@
../utilities/linux/wrapper/wrapper_x11.cpp \
../utilities/linux/wrapper/image_file.cpp \
Linux/win_list_manager.cpp \
- Linux/HIDInterface.cpp \
Linux/OrbiterRenderer_Linux.cpp \
Linux/WindowContext.cpp \
DesignObj_Data.cpp \
</pre>

==Building Orbiter==
# While inside Scratchbox, go into /pluto/trunk/src/SerializeClass and type <tt>'''make'''</tt>
# Go into /pluto/trunk/src/PlutoUtils and type <tt>'''make'''</tt>
# Go into /pluto/trunk/src/DCE and type <tt>'''make'''</tt>
# Go into /pluto/trunk/src/SDL_Helpers and type <tt>'''make'''</tt>
# Go into /pluto/trunk/src/Orbiter and type <tt>'''make bin'''</tt>
# After a while, the following files will result in /pluto/trunk/src
#* lib/libDCECommon.so
#* lib/libSerializeClass.so
#* lib/libPlutoUtils.so
#* lib/libSDL_Helpers.so
#* bin/Orbiter
# Copy these files over to the tablet, in /home/user/orbiter
# Don't forget strip Orbiter binaries to save space:
#* strip lib/*
#* strip bin/*

==Running Orbiter==

Before starting Orbiter following applications and libraries should be installed:

* mysql-common
* libmysqlclient
* libhttpfetcher
* libhid (should be removed soon)
* libsdl-sge
* libsdl-gfx
* libsdl
* libgle
* libxmu
* libsdl-ttf
* libsdl-image
* libsm
* libice
* libxt
* xterm
* ssh

To do that just add additional repository repository.maemo.org and activate [http://wiki.snc.sapmi.net/doku.php?id=snc:nokia#red_pill_mode Red Pill Mode]. Additionally, you should [http://maemo.org/community/wiki/howdoibecomeroot/ became a root] on your device.

In an X terminal On the tablet itself (NOT via ssh) do this:
cd /home/user/orbiter
export LD_LIBRARY_PATH=.
./Orbiter -r xxx.xxx.xxx.xxx -d yy -l orbiter.log
where xxx.xxx.xxx.xxx is the IP address of the DCE Router, and yy is the device number assigned to your new Orbiter.

If it complains about missing .so files, copy them over from your Scratchbox on the build machine into /home/user/orbiter on the tablet.

'''Notice:''' you need true type fonts on your Nokia770. The orbiter searches them here - '''/usr/share/truetype/msttcorefonts'''. Just copy this directory from your core to Nokia770 (the Debian package for Nokia is coming soon).

==Building Debian packages==
# Dependencies can be found [https://garage.maemo.org/frs/?group_id=162 here]
# The latest Orbiter binaries get [https://garage.maemo.org/frs/?group_id=162 here]
# Orbiter package - [https://garage.maemo.org/frs/?group_id=162 here]

=External references=

* [https://garage.maemo.org/frs/?group_id=162 Plutohome Nokia Orbiter on maemo garage]
* [http://smart-home-blog.com/writes/howto-build-plutohome-orbiter-for-nokia770/ Howto Build Plutohome Orbiter for Nokia770]
* [http://smart-home-blog.com/writes/nokia770-as-plutohome-orbiter-os2006/ Using Nokia770/N800 as Plutohome Orbiter]
* [http://smart-home-blog.com/archives/886 Tune Nokia770 to use as LinuxMCE Orbiter]
* [http://www.maemo.org/platform/docs/tutorials/Maemo_tutorial.html#settingup Maemo Tutorial]

Nokia 770

2007-12-21T20:12:42Z

Matthew: Shift section degrees down to start at 1

[[Category: Hardware]]
[[Category: WebPads]]
[[Category: Orbiters]]

[[Image:Nokia770.jpg|right]]

[http://europe.nokia.com/770 Official Site]

=About the device=
'''Microprocessor:''' 220-MHz, ARM9-based Texas Instruments (TI) OMAP 1710 
'''RAM:''' 64MB DDR 
'''On-board memory:''' 128 MB, more than 64 MB available to the user 
'''Memory slot:''' RS-MMC (Reduced size MultiMedia Card) 
'''Battery:''' Standard Li-ion BP-5L Battery 1500 mAh (3 hours browse, 7 hours standby) 
'''Screen:''' 800×480 touch screen with up to 65,536 colors 
'''WiFi:''' 802.11 b/g 
'''Bluetooth:''' Bluetooth 1.2 - dial-up networking, file transfer, generic access, SIM access, and serial port profiles 
'''Audio:''' Audio out 
'''PC connectivity:''' USB (slave mode only) via DKE-2 cable 
'''OS:''' Internet Tablet 2005 (Maemo-based) 
'''Linux specs:''' 2.6 kernel, GNOME-based GUI 
'''Dimensions:''' Dimensions: 5.5 inches x 3.1 inches x 0.70 inch 
'''Weight:''' 8.1 ounces 
Price: $140

The Nokia770 works pretty well as a LinuxMCE Orbiter.

The Orbiter package and all dependences can be found in the [https://garage.maemo.org/frs/?group_id=162 Maemo garage], for information on how to use it read "[http://smart-home-blog.com/writes/nokia770-as-plutohome-orbiter-os2006/ Using Nokia770/N800 as a Plutohome Orbiter]" on the [[SmartBlog]].

See also [[Tune_Nokia770 Tune Nokia770 to use it as LinuxMCE Orbiter]]

=Setup guide 1=
==Before you begin==
First of all this is work in progress so don't expect the orbiter to be fully functional at full speed on this tablet. There are some known bugs so far:
* It will only run on OS 2005 for now so don't try to install this on newer firmware versions
* TTF rendering is not working so you won't see any text when browsing you media files :(
* Crashing and working a little slow

Thanks to Michael "[[User:Nite man|Nite man]]" Stepanov from IPTRIPLEPLAY Ltd [[mailto:info@iptp.net info@iptp.net]] who ported Orbiter on maemo platform.

==Installing OS 2005 on Nokia 770==
Since LinuxMCE Orbiter won't run on firmware version newer that SO 2005, you'll need to get that firmware version installed before you begin.

To check you current firmware version you can go to : MainMenu -> Control Panel -> Device -> About Product. There it should say 'Version: 3.2005...". If you already have this version installed then you can skip to next paragraph, else follow up this steps to get it installed.

The next steps are copy pasted from [[http://maemo.org/maemowiki/HOWTO_FlashLatestNokiaImageWithLinux maemo wiki]] and adapted to meet you needs :

Beware that flashing a new image on the Nokia 770 will remove all user changes to the system, including preferences, bookmarks, news feeds, user installed applications, ... Everything not on the memory card will be gone and the device will behave as if just purchased with the single exception that any previously-set lock code will be kept and not reset to the factory-default of "12345" (even the code is not preserved on some images).

*PC: Download the Linux flasher at [[http://maemo.org/downloads/d3.php maemo.org]]
*PC: In the same directory download the image you want: [[http://www.maemo.org/downloads/nokia_770 Nokia_770_3.2005.51-13.bin]]
*770: Unplug charger and switch off the Nokia 770. Connect it to your computer via USB
*PC: Execute as root (or as a normal user with rights to use the USB port):
./flasher-2.0 -F Nokia_770_3.2005.51-13.bin -f -R
*PC: "Suitable USB device not found, waiting" is displayed on the console
*770: Now plug in the charger to switch on the 770 or switch it on using the power button WHILE holding the Home-button
*PC: Watch the messages as the image loads to the 770 after which it reboots automatically -- you're done now!

=Setup Guide 2=

== Configuring the Core ==
#Open up a web admin interface, go to Orbiter page and add a new device of type 'Orbiter'
#Locate the newly added device and change the resolution to 640x480 as the Nokia 770 won't support the default of 800x600
#Memorize the numeric id that LinuxMCE assigns to your new orbiter since you'll need it later, you can see it right of the 'Description' filed on the same page.
#Do a full regen of that orbiter and a quick reload router after that

== Configuring the Tablet ==
#Setup you wireless connection. To use your tablet as an orbiter you'll need to make sure that the tablet is located within the internal network of the core.
#Upload the deb package to you tablet using the usb cable or by downloading it directly from our website. You can fetch the deb file [[http://plutohome.com/pluto-orbiter_0.1_arm.deb here]]
#Install it by double clicking the deb file from Nokia 770's File Manager.

== Starting the Orbiter ==
#There is no easy way to start you orbiter yet, and you'll need an X terminal emulator to do this task. If you don't have it yet installed, download the osso-xterm deb package from [[http://770.fs-security.com/xterm/ fs-security.com]] and install it on you tablet the same way you installed the LinuxMCE orbiter package.
#Open up an xterminal using nokia 770's main menu: Extras -> X Terminal
#Make sure the network connection is available
#Type this in the terminal to start you orbiter
/var/lib/install/bin/startOrbiter.sh -r <ROUTER_INTERNAL_IP> -d <ORBITER_ID>
You can also start the orbiter with verbose logging to debug possible problems, but this will bring a slowdown in orbiter's screen changing :
/var/lib/install/bin/startOrbiterVerbose.sh -r <ROUTER_INTERNAL_IP> -d <ORBITER_ID>

== Getting Help ==
For getting help and troubleshooting possible problems related to nokia 770 and LinuxMCE you can always talk to other users the [[http://plutohome.com/support/phpbb2/ forum]] and don't forget that this is still WiP.

=Setup Guide 3=
These are the instructions to build a version of [[Orbiter]] for the Nokia 770 internet platform. Nokia 770 has an ARM family processor, therefore you will need to cross-compile if your build machine is an Intel.

[[Image:Nokia-orbiter-small-400.jpg]]

==Requirements==
You will need:
* an Ubuntu box to host the build
* the Maemo 1.1 SDK for ARM ( http://repository.maemo.org/stable/1.1/arm/Maemo_Dev_Platform_RS_v1.1_arm.tgz )
* Scratchbox cross-compilation toolkit 0.9.8.5 (http://www.scratchbox.org/download/files/sbox-releases/0.9.8/deb/ )
scratchbox-core_0.9.8.5_i386.deb
scratchbox-devkit-debian_0.9.8.5_i386.deb
scratchbox-doctools_0.9.8.5_i386.deb
scratchbox-libs_0.9.8.5_i386.deb
scratchbox-toolchain-arm-glibc_0.9.8.5_i386.deb
scratchbox-toolchain-i686-glibc_0.9.8.5_i386.deb

==Preparing the Nokia tablet==
# Make sure it is connected to the network - check the Connection manager for a WiFi connection
# Open an X terminal on the tablet; make a directory in your home dir to hold the Orbiter binaries, say <tt>/home/user/orbiter</tt>
# You'll need a way to transfer files from the build machine to the tablet. Either have an HTTP server somewhere on your network, or install OpenSSH on the tablet. If you install OpenSSH, remember to also start it, by doing <tt>/etc/init.d/ssh start</tt>. To get a root prompt, use <tt>sudo gainroot</tt>.

==Preparing the build machine==
# Install Scratchbox debs on the build machine
# Add yourself as a Scratchbox user: <tt>'''/scratchbox/sbin/sbox_adduser ''username'''''</tt>
# Check out a fresh working copy of LinuxMCE from http://svn.plutohome.com/pluto/trunk/src/ into <tt>/scratchbox/users/username/pluto/trunk/src</tt> (username is assumed to be your user name on the build machine)
# Copy or symlink the Maemo SDK into <tt>/scratchbox/packages</tt>
# Log in to Scratchbox by typing <tt>'''scratchbox'''</tt>
# Configure Scratchbox cross-compile target:
> '''sbox-config -ct Nokia770'''

Available compilers:
0) arm-linux-gcc-3.3_3.3.4-glibc-2.3.2.ds1
1) host-gcc
2) i686-linux-gcc-3.3_3.3.4-glibc-2.3.2.ds1

Enter compiler number: '''0'''

Available CPU-transparency methods:
sbrsh
qemu-arm
qemu-ppc

Enter method name (qemu-arm): '''qemu-arm'''

Available devkits:
debian

Enter list of devkit names (none): '''debian'''
# Select the new cross-compile target: <tt>'''sbox-config -st Nokia770'''</tt>
# Unpack the Maemo rootstrap: <tt>'''sbox-config -er /scratchbox/packages/Maemo_Dev_Platform_RS_v1.1_arm.tgz'''</tt>
# <tt>'''sbox-config -cc'''</tt>
# <tt>'''sbox-config -cf'''</tt>
# Update the package list inside Scratchbox by typing <tt>apt-get update</tt>
# Install the following build-time dependencies (with <tt>apt-get install</tt>)
#* libmysqlclient12-dev
#* libid3-dev
#* xlibmesa-gl-dev
# Before starting to compile Orbiter and its dependencies, type: export SNR_CPPFLAGS="-DMAEMO_NOKIA770" (add there -DDEBUG if you want to see all debug messages) and export SNR_LDFLAGS="". Also, apply that patch to Orbiter Makefile to remove GL and HID dependences:

<pre>
--- src-2.0.0.44/src/Orbiter/Makefile 2007-03-05 13:44:44.000000000 -0800
+++ tmp/Makefile 2007-06-07 08:02:09.000000000 -0700
@@ -23,9 +23,9 @@

CXXFLAGS += -g -O0
-CPPFLAGS += -I/usr/include/SDL -DORBITER -DCACHE_IMAGES -DENABLE_MOUSE_BEHAVIOR -I$(ROOT)/Splitter -I$(ROOT)/OrbiterGen -I$(ROOT)/SDL_Helpers -DHID_REMOTE
+CPPFLAGS += -I/usr/include/SDL -DORBITER -DCACHE_IMAGES -DENABLE_MOUSE_BEHAVIOR -I$(ROOT)/Splitter -I$(ROOT)/OrbiterGen -I$(ROOT)/SDL_Helpers
LDFLAGS += -L/usr/X11R6/lib
-XTRALDLIBS += -lDCECommon -lSDL -lSDL_ttf -lSDL_image -lSGE -lSDL_gfx -lXtst -lXext -lGL -lXrender -lGLU -lSDL_Helpers -lhid
+XTRALDLIBS += -lDCECommon -lSDL -lSDL_ttf -lSDL_image -lSGE -lSDL_gfx -lXtst -lXext -lXrender -lSDL_Helpers -lhid

# wmctrl wrapper
CPPFLAGS += -I/usr/X11R6/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
@@ -38,7 +38,6 @@
../utilities/linux/wrapper/wrapper_x11.cpp \
../utilities/linux/wrapper/image_file.cpp \
Linux/win_list_manager.cpp \
- Linux/HIDInterface.cpp \
Linux/OrbiterRenderer_Linux.cpp \
Linux/WindowContext.cpp \
DesignObj_Data.cpp \
</pre>

==Building Orbiter==
# While inside Scratchbox, go into /pluto/trunk/src/SerializeClass and type <tt>'''make'''</tt>
# Go into /pluto/trunk/src/PlutoUtils and type <tt>'''make'''</tt>
# Go into /pluto/trunk/src/DCE and type <tt>'''make'''</tt>
# Go into /pluto/trunk/src/SDL_Helpers and type <tt>'''make'''</tt>
# Go into /pluto/trunk/src/Orbiter and type <tt>'''make bin'''</tt>
# After a while, the following files will result in /pluto/trunk/src
#* lib/libDCECommon.so
#* lib/libSerializeClass.so
#* lib/libPlutoUtils.so
#* lib/libSDL_Helpers.so
#* bin/Orbiter
# Copy these files over to the tablet, in /home/user/orbiter
# Don't forget strip Orbiter binaries to save space:
#* strip lib/*
#* strip bin/*

==Running Orbiter==

Before starting Orbiter following applications and libraries should be installed:

* mysql-common
* libmysqlclient
* libhttpfetcher
* libhid (should be removed soon)
* libsdl-sge
* libsdl-gfx
* libsdl
* libgle
* libxmu
* libsdl-ttf
* libsdl-image
* libsm
* libice
* libxt
* xterm
* ssh

To do that just add additional repository repository.maemo.org and activate [http://wiki.snc.sapmi.net/doku.php?id=snc:nokia#red_pill_mode Red Pill Mode]. Additionally, you should [http://maemo.org/community/wiki/howdoibecomeroot/ became a root] on your device.

In an X terminal On the tablet itself (NOT via ssh) do this:
cd /home/user/orbiter
export LD_LIBRARY_PATH=.
./Orbiter -r xxx.xxx.xxx.xxx -d yy -l orbiter.log
where xxx.xxx.xxx.xxx is the IP address of the DCE Router, and yy is the device number assigned to your new Orbiter.

If it complains about missing .so files, copy them over from your Scratchbox on the build machine into /home/user/orbiter on the tablet.

'''Notice:''' you need true type fonts on your Nokia770. The orbiter searches them here - '''/usr/share/truetype/msttcorefonts'''. Just copy this directory from your core to Nokia770 (the Debian package for Nokia is coming soon).

==Building Debian packages==
# Dependencies can be found [https://garage.maemo.org/frs/?group_id=162 here]
# The latest Orbiter binaries get [https://garage.maemo.org/frs/?group_id=162 here]
# Orbiter package - [https://garage.maemo.org/frs/?group_id=162 here]

=External references=

* [https://garage.maemo.org/frs/?group_id=162 Plutohome Nokia Orbiter on maemo garage]
* [http://smart-home-blog.com/writes/howto-build-plutohome-orbiter-for-nokia770/ Howto Build Plutohome Orbiter for Nokia770]
* [http://smart-home-blog.com/writes/nokia770-as-plutohome-orbiter-os2006/ Using Nokia770/N800 as Plutohome Orbiter]
* [http://smart-home-blog.com/archives/886 Tune Nokia770 to use as LinuxMCE Orbiter]
* [http://www.maemo.org/platform/docs/tutorials/Maemo_tutorial.html#settingup Maemo Tutorial]

Network Attached Storage

2007-12-21T17:50:09Z

Matthew: NAS on outside LAN

Include here a list of NAS that have been tested with LinuxMCE.

{| class="wikitable" width="300" style="text-align:center; background:#efefef; width:75%; border:1px solid black"
|+ NAS
|-
| [[Buffalo Terastation]]
|-
|-
| [[Buffalo Linkstation]]
|-
|-
| [[FreeNAS]]
|-
|}

=Troubleshooting=
#The files appear on the media directors, orbiters, and (while SSH'd) on /mnt/NAS_# and in the subdirectories of each user. But the files do not play. None of the music or video files play. All files stored on the core play fine. 
##(This solution comes from [http://forum.linuxmce.org/index.php?action=mlist;sa=search bliss01] on the forum. Needs more detailed instructions please...) Make sure you've mounted the device as the same name and dir and on the Core.
##Edit the /etc/exports file on the core, and the /etc/fstab on the MDs to fix this. But also to make the changes stay after reboot, edit the templates in /usr/pluto/templates/
##Also make sure the SMB drive is on the same network (ie. the 192.168.80.x) as the Core, which has a firewall which stops smb mounts, though there is a separate procedure for [[#Adding_NAS_to_LinuxMCE_Core.27s_.22Outside.22_LAN_Segment|attaching NAS to the outside LAN segment]].

=How Network Attached Storage (NAS) and Windows shares are made plug and play=
First, the detected event is fired.

For a detected NAS this event comes from dhcp monitor and has the ip/mac. The "plug and play" plugin figures out what it is, and fires an event like this:

/usr/pluto/bin/MessageSend dcerouter 0 -1001 2 65 52 3 53 2 5 "00:0D:0B:99:10:43" 28 "192.168.80.7"

For a detected Windows share, this event comes from the "scan the network for windows shares" utility that always runs in the background. It explicitly sends a "device detected" event with the device template "Generic File Server 1837", like this:

/usr/pluto/bin/MessageSend dcerouter 0 -1001 2 65 52 3 53 2 49 1837

Both the "generic file server" and the NAS devices like Maxtor & Buffalo have a device data called “Pre Pnp Script”, which is set to: /usr/pluto/bin/CheckNASForPasswords.sh. This means that before actually creating the device, this script will be run and is expected to send a command CMD_Pre_Pnp_Script_Done which includes additional parameters. In the script the key thing is the "182|'''1'''" parameter. Change that 1 to a 0 if no password is required. Maybe we will need a different script for different NAS devices.

After that script runs, if 182|1 was specified, the user will be prompted for the username and password, as per: Pnp_PreCreateOptions::OkayToCreateDevice with the screen: SCREEN_Get_Username_Password_For_Devices.

Once the device is created, its configure script will be run, for example: Configure_1794.sh for the Buffalo. This script will lookup the username and password for the device from the database and fire a "device detected" for each network share, as follows:

/usr/pluto/bin/MessageSend dcerouter <X> -1001 2 65 52 3 53 2 49 1768 55 "182|1"

That <X> must be the ID# of the device created above, since the file share will be a child of that device. 1768 is the template for a samba share, 1769 for nfs. If the share does not require a password, leave off the 55 "182|1". If the username and password already specified in the database are valid for the share, then instead of 55 "182|1" use 55 "127|username|128|password".

This message will create the child device for each share and prompt the user if the username or password are needed.

=Adding NAS to LinuxMCE Core's "Outside" LAN Segment=
The default configuration of LMCE supports NAS attached to the "inside" LAN segment (ie. inside the LMCE firewall, on the inside ethernet segment). But [http://forum.linuxmce.org/index.php?action=profile;u=38696 tkmedia] tested [http://forum.linuxmce.org/index.php?action=post;quote=17973;topic=3097.0;num_replies=6;sesc=16c0748221044872529fefa717ce4db6 reconfiguring LMCE to support the NAS on the outside LAN segment]:

#In the Web admin select "show devices tree".
#Select CORE from my devices.
#Create child device.
##Use the file server device template.
##Put in its IP Address, username and password, and save it.
#Now select the file server you just made and Create child device.
##Use the "Windows share" device template put in its sharename, username and password and save it.
##If you go the an Orbiter's KDE desktop, open Konqueror to /home/public/data/other , you should see something like "Windows Share [55]".
#Now let it automatically sync the files. Takes a while (even to get started, then syncing is slow)..................... You can go resync the files using the web admin but if you have a lot of files just let it sync overnight on its own.

In theory you may even be able to attach the NAS on the internal LAN segment, autodetect it, then change its IP address in the Web admin and reconnect it on the external LAN segment.

[[Category: Programmer's Guide]][[Category: Storage]]

Network Attached Storage

2007-12-21T17:37:18Z

Matthew: cleanup

Network Attached Storage

2007-12-21T16:45:09Z

Matthew: cleanup

Network Attached Storage

2007-12-21T16:23:37Z

Matthew: Shift section degrees down to start at 1

Cisco 7970

2007-12-21T06:45:32Z

Matthew: Fix instructions indent

[[Category: Hardware]]
[[Category: Phones]]
[[Category: Orbiters]]
[[Image:Cisco7909.JPG]]

LinuxMCE allows to use many devices as Orbiters. One of them is the Cisco 7970. You can use it to make calls and control your home as well. To add a new Cisco 7970 phone and Orbiter you should follow these simple instructions. Basically I got the information in the [http://forum.linuxmce.org/index.php?action=search2&search=Cisco+7970 LinuxMCE support forum]. But I think it's good to accumulate odd posts in one place. If you have some suggestions send me email - stepanov.michael [at] gmail [dot] com or leave a comment.

These instructions were adapted from [http://stepanoff.org/wordpress/works/smart-home/howto/how-to-setup-cisco-7970 How to setup CISCO 7970 in Plutohome].
There is also [http://forum.linuxmce.org/index.php?topic=3190.0 some discussion of upgrading Cisco 7970 firmware for using SIP instead of SCCP]. Complete info should be included in this wiki page.

=Preparation=
Cisco 7970 phone is plug-in-play device and LinuxMCE adds it automatically when it'll be plugged in the network. But to do it we have to make some preparations. Since the server must be prepared when the phone checks into it, the phone must be disconnected from the server until the server preparation is complete. But some info for the server must be copied from the phone first.

In short, you'll check that the phone is configured to use DHCP, and get its MAC address. Then you'll create a new LMCE device and set that device to recognize the phone's IP#, and restart the DCERouter.

#Get phone configs.
##Ensure the 7970 is unplugged from the network.
##Power up the phone but don't let it connect to a network server. If your phone is powered by PoE, you will have to ensure that no server cable is connected to the PoE source (eg. a PoE switch), or (harder) that no servers (ie. DHCPd) are up and responding to to queries from the phone.
##Wait for the phone to boot (Cisco splashscreen changes to a background image, then probably goes dark for a few seconds while the "doubled-square" button at the right end of the row of buttons below the screen lights, then the background image returns with a "Configuring IP" time wheel across the bottom).
##Press the settings button (checked box at lower right of round "?" button) to get a "7970(G) SETTINGS" menu ("G" depends on specific 7970/7970G model#).
##Use the down arrow side of the circular navigation button below the screen to select a submenu.
###Check DHCP setting on your phone.
####From the "7970(G) SETTINGS" main menu, select "Network Congfiguration" or enter with the phone's keypad the item's number (probably "2") next to that menu item to get the "Network Congfiguration" menu.
####Down the list is "DHCP Enabled" (probably item 22), which should say "Yes".
###Get the MAC address of your phone.
####Also in the "7970(G) SETTINGS" > "Network Congfiguration" menu, find the "MAC Address" item (probably item 3).
####The "MAC Address" item is the MAC address, though it lacks the conventional ":" field separators among its six pairs of (zero-padded) hexadecimal digits.
#####Insert the ":" separators (eg. 1234567890AB becomes 12:34:56:78:90:AB)
#####You will use those numbers to define the range of MAC addresses LMCE will recognize as Cisco 7970 phones in the LMCE device you are about to create in the LMCE Adminsite.
#Run an Orbiter (on an existing LMCE device, not the 7970).
##Click Orbiter Home -> LinuxMCE:More -> Advanced Options -> Pending Tasks for list.
##Be sure that no others task are pending.
#Go to Admin website, menu Home -> Advanced -> Configuration -> Devices.
##Click "Add a top level device" in either the device tree in the minor side panel, or in the main panel.
##For "Device Template", click the button "Pick Device Template", which will popup a new window.
###From "manufacturer" choose "Cisco". You can filter the Device Template list by using a Device Category like "Hard Phones < Phones < Peripherals" (or a subset of that compound category). You should see in the Device Template list at least two models: 7960 and 7970.
###From "Device Template" pick "7970".
###Press the button "Pick device template". The Orbiter will display "Configuring Cisco 7970". The popup window will close. Several seconds might pass while LMCE generates the new device configs, then the device tree will show under "CORE > Asterisk" a new "Cisco 7970" device (with a "Cisco 7970 Orbiter" subdevice collapsed/viewable through it), and reload the main panel with a details page titled "Device #<n>: Cisco 7970" (<n> is some device ID number previously unused by your LMCE).
##In the Device details panel insert the two decimal MAC addresses defining a range as "LO-HI" (eg. 29902132740096-29902149517311) into the "MAC Address" field
##Click the "Save" button.
##Reload the DCERouter
###Webadmin Home > Wizard > Restart
###Click "Quick Reload Router" button.

You can create the phone device in LMCE first, and then check the phone's DHCP config and MAC address, returning to the device to configure its MAC address range, just as long as you don't connect the phone to the nework with the LMCE DHCP server until after LMCE is prepared.

There is a possibility to have some problems with the phone installation related with its firmware. The firmware version should be the latest. I didn't have any problem with existing firmware on my Cisco 7970. But you should bear in mind, as some more recent SIP firmware has failed to register with LinuxMCE's Asterisk subsystem. See Asterisk's own documentation (separate project) for details.

=Installation=
#Power up the phone with it connected to the network. Note if you have two network cards in your core's machine you should plug network cable in the "inside" ethernet segment, with the LMCE DHCP server running on that inside interface.
#During boot of the phone it will after 2-3 minutes you register with the LMCE to download its Orbiter. You should see on the LMCE Orbiter a message about new device with your phone MAC address was detected.
#After that the phone should be registered with LinuxMCE's Asterisk subsystem and you can see a normal Cisco screen.
#However, it'll take another 2-3 minutes to generate a new Orbiter for the Cisco 7970.
#When this operation finishes you'll see a message on the LMCE Orbiter (not the 7970) screen. Run a quick reload of router (Adminsite Home > Wizard > Restart; Click "Quick Reload Router").
#Now go to the Services menu on the Cisco 7970 and chose "Orbiter".
#If the Cisco 7970 Services menu doesn't contain "Orbiter", reboot the phone (power cycle) and look again in the Services menu.

=Troubleshooting=
*Problem: Phone boots successfully in installation, but there isn't any message on the LMCE Orbiter's screen that it's registering.
Solution:Check the MAC address to ensure the phone's correct MAC address is in the specified range (Adminsite Home > Wizard > Devices; Phones; Cisco 790; Advanced; MAC Address)

=Useful tips=
#To reset a LMCE Network configuration of Cisco 7970 go to Admin website menu "Home -> Advanced -> Network Settings" (where you can change LMCE network settings) and press the following sequence of buttons on the phone: **#** (which will reset and reboot the phone).
#To check network communications between Cisco 7970 and CORE run tcpdump on the CORE: <code>tcpdump -i eth1 <Cisco 7970 IP Address></code>
#To see detailed packets information: <code>tcpdump -i -vv eth1 <Cisco 7970 IP Address></code>

=See also=
[[Orbiter]]

Cisco 7970

2007-12-21T06:31:47Z

Matthew: Instructions source citation

[[Category: Hardware]]
[[Category: Phones]]
[[Category: Orbiters]]
[[Image:Cisco7909.JPG]]

LinuxMCE allows to use many devices as Orbiters. One of them is the Cisco 7970. You can use it to make calls and control your home as well. To add a new Cisco 7970 phone and Orbiter you should follow these simple instructions. Basically I got the information in the [http://forum.linuxmce.org/index.php?action=search2&search=Cisco+7970 LinuxMCE support forum]. But I think it's good to accumulate odd posts in one place. If you have some suggestions send me email - stepanov.michael [at] gmail [dot] com or leave a comment.

These instructions were adapted from [http://stepanoff.org/wordpress/works/smart-home/howto/how-to-setup-cisco-7970 How to setup CISCO 7970 in Plutohome].
There is also [http://forum.linuxmce.org/index.php?topic=3190.0 some discussion of upgrading Cisco 7970 firmware for using SIP instead of SCCP]. Complete info should be included in this wiki page.

=Preparation=
Cisco 7970 phone is plug-in-play device and LinuxMCE adds it automatically when it'll be plugged in the network. But to do it we have to make some preparations. Since the server must be prepared when the phone checks into it, the phone must be disconnected from the server until the server preparation is complete. But some info for the server must be copied from the phone first.

In short, you'll check that the phone is configured to use DHCP, and get its MAC address. Then you'll create a new LMCE device and set that device to recognize the phone's IP#, and restart the DCERouter.

#Get phone configs.
##Ensure the 7970 is unplugged from the network.
##Power up the phone but don't let it connect to a network server. If your phone is powered by PoE, you will have to ensure that no server cable is connected to the PoE source (eg. a PoE switch), or (harder) that no servers (ie. DHCPd) are up and responding to to queries from the phone.
##Wait for the phone to boot (Cisco splashscreen changes to a background image, then probably goes dark for a few seconds while the "doubled-square" button at the right end of the row of buttons below the screen lights, then the background image returns with a "Configuring IP" time wheel across the bottom).
##Press the settings button (checked box at lower right of round "?" button) to get a "7970(G) SETTINGS" menu ("G" depends on specific 7970/7970G model#).
##Use the down arrow side of the circular navigation button below the screen to select a submenu.
###Check DHCP setting on your phone.
####From the "7970(G) SETTINGS" main menu, select "Network Congfiguration" or enter with the phone's keypad the item's number (probably "2") next to that menu item to get the "Network Congfiguration" menu.
####Down the list is "DHCP Enabled" (probably item 22), which should say "Yes".
###Get the MAC address of your phone.
####Also in the "7970(G) SETTINGS" > "Network Congfiguration" menu, find the "MAC Address" item (probably item 3).
####The "MAC Address" item is the MAC address, though it lacks the conventional ":" field separators among its six pairs of (zero-padded) hexadecimal digits.
#####Insert the ":" separators (eg. 1234567890AB becomes 12:34:56:78:90:AB)
#####You will use those numbers to define the range of MAC addresses LMCE will recognize as Cisco 7970 phones in the LMCE device you are about to create in the LMCE Adminsite.
#Run an Orbiter (on an existing LMCE device, not the 7970).
##Click Orbiter Home -> LinuxMCE:More -> Advanced Options -> Pending Tasks for list.
##Be sure that no others task are pending.
##Go to Admin website, menu Home -> Advanced -> Configuration -> Devices.
###Click "Add a top level device" in either the device tree in the minor side panel, or in the main panel.
###For "Device Template", click the button "Pick Device Template", which will popup a new window.
####From "manufacturer" choose "Cisco". You can filter the Device Template list by using a Device Category like "Hard Phones < Phones < Peripherals" (or a subset of that compound category). You should see in the Device Template list at least two models: 7960 and 7970.
####From "Device Template" pick "7970".
####Press the button "Pick device template". The Orbiter will display "Configuring Cisco 7970". The popup window will close. Several seconds might pass while LMCE generates the new device configs, then the device tree will show under "CORE > Asterisk" a new "Cisco 7970" device (with a "Cisco 7970 Orbiter" subdevice collapsed/viewable through it), and reload the main panel with a details page titled "Device #<n>: Cisco 7970" (<n> is some device ID number previously unused by your LMCE).
###In the Device details panel insert the two decimal MAC addresses defining a range as "LO-HI" (eg. 29902132740096-29902149517311) into the "MAC Address" field
###Click the "Save" button.
###Reload the DCERouter
####Webadmin Home > Wizard > Restart
####Click "Quick Reload Router" button.

You can create the phone device in LMCE first, and then check the phone's DHCP config and MAC address, returning to the device to configure its MAC address range, just as long as you don't connect the phone to the nework with the LMCE DHCP server until after LMCE is prepared.

There is a possibility to have some problems with the phone installation related with its firmware. The firmware version should be the latest. I didn't have any problem with existing firmware on my Cisco 7970. But you should bear in mind, as some more recent SIP firmware has failed to register with LinuxMCE's Asterisk subsystem. See Asterisk's own documentation (separate project) for details.

=Installation=
#Power up the phone with it connected to the network. Note if you have two network cards in your core's machine you should plug network cable in the "inside" ethernet segment, with the LMCE DHCP server running on that inside interface.
#During boot of the phone it will after 2-3 minutes you register with the LMCE to download its Orbiter. You should see on the LMCE Orbiter a message about new device with your phone MAC address was detected.
#After that the phone should be registered with LinuxMCE's Asterisk subsystem and you can see a normal Cisco screen.
#However, it'll take another 2-3 minutes to generate a new Orbiter for the Cisco 7970.
#When this operation finishes you'll see a message on the LMCE Orbiter (not the 7970) screen. Run a quick reload of router (Adminsite Home > Wizard > Restart; Click "Quick Reload Router").
#Now go to the Services menu on the Cisco 7970 and chose "Orbiter".
#If the Cisco 7970 Services menu doesn't contain "Orbiter", reboot the phone (power cycle) and look again in the Services menu.

=Troubleshooting=
*Problem: Phone boots successfully in installation, but there isn't any message on the LMCE Orbiter's screen that it's registering.
Solution:Check the MAC address to ensure the phone's correct MAC address is in the specified range (Adminsite Home > Wizard > Devices; Phones; Cisco 790; Advanced; MAC Address)

=Useful tips=
#To reset a LMCE Network configuration of Cisco 7970 go to Admin website menu "Home -> Advanced -> Network Settings" (where you can change LMCE network settings) and press the following sequence of buttons on the phone: **#** (which will reset and reboot the phone).
#To check network communications between Cisco 7970 and CORE run tcpdump on the CORE: <code>tcpdump -i eth1 <Cisco 7970 IP Address></code>
#To see detailed packets information: <code>tcpdump -i -vv eth1 <Cisco 7970 IP Address></code>

=See also=
[[Orbiter]]

Cisco 7970

2007-12-21T06:30:08Z

Matthew: cleanup

[[Category: Hardware]]
[[Category: Phones]]
[[Category: Orbiters]]
[[Image:Cisco7909.JPG]]

LinuxMCE allows to use many devices as Orbiters. One of them is the Cisco 7970. You can use it to make calls and control your home as well. To add a new Cisco 7970 phone and Orbiter you should follow these simple instructions. Basically I got the information in the [http://forum.linuxmce.org/index.php?action=search2&search=Cisco+7970 LinuxMCE support forum]. But I think it's good to accumulate odd posts in one place. If you have some suggestions send me email - stepanov.michael [at] gmail [dot] com or leave a comment.

There is also [http://forum.linuxmce.org/index.php?topic=3190.0 some discussion of upgrading Cisco 7970 firmware for using SIP instead of SCCP]. Complete info should be included in this wiki page.

=Preparation=
Cisco 7970 phone is plug-in-play device and LinuxMCE adds it automatically when it'll be plugged in the network. But to do it we have to make some preparations. Since the server must be prepared when the phone checks into it, the phone must be disconnected from the server until the server preparation is complete. But some info for the server must be copied from the phone first.

In short, you'll check that the phone is configured to use DHCP, and get its MAC address. Then you'll create a new LMCE device and set that device to recognize the phone's IP#, and restart the DCERouter.

#Get phone configs.
##Ensure the 7970 is unplugged from the network.
##Power up the phone but don't let it connect to a network server. If your phone is powered by PoE, you will have to ensure that no server cable is connected to the PoE source (eg. a PoE switch), or (harder) that no servers (ie. DHCPd) are up and responding to to queries from the phone.
##Wait for the phone to boot (Cisco splashscreen changes to a background image, then probably goes dark for a few seconds while the "doubled-square" button at the right end of the row of buttons below the screen lights, then the background image returns with a "Configuring IP" time wheel across the bottom).
##Press the settings button (checked box at lower right of round "?" button) to get a "7970(G) SETTINGS" menu ("G" depends on specific 7970/7970G model#).
##Use the down arrow side of the circular navigation button below the screen to select a submenu.
###Check DHCP setting on your phone.
####From the "7970(G) SETTINGS" main menu, select "Network Congfiguration" or enter with the phone's keypad the item's number (probably "2") next to that menu item to get the "Network Congfiguration" menu.
####Down the list is "DHCP Enabled" (probably item 22), which should say "Yes".
###Get the MAC address of your phone.
####Also in the "7970(G) SETTINGS" > "Network Congfiguration" menu, find the "MAC Address" item (probably item 3).
####The "MAC Address" item is the MAC address, though it lacks the conventional ":" field separators among its six pairs of (zero-padded) hexadecimal digits.
#####Insert the ":" separators (eg. 1234567890AB becomes 12:34:56:78:90:AB)
#####You will use those numbers to define the range of MAC addresses LMCE will recognize as Cisco 7970 phones in the LMCE device you are about to create in the LMCE Adminsite.
#Run an Orbiter (on an existing LMCE device, not the 7970).
##Click Orbiter Home -> LinuxMCE:More -> Advanced Options -> Pending Tasks for list.
##Be sure that no others task are pending.
##Go to Admin website, menu Home -> Advanced -> Configuration -> Devices.
###Click "Add a top level device" in either the device tree in the minor side panel, or in the main panel.
###For "Device Template", click the button "Pick Device Template", which will popup a new window.
####From "manufacturer" choose "Cisco". You can filter the Device Template list by using a Device Category like "Hard Phones < Phones < Peripherals" (or a subset of that compound category). You should see in the Device Template list at least two models: 7960 and 7970.
####From "Device Template" pick "7970".
####Press the button "Pick device template". The Orbiter will display "Configuring Cisco 7970". The popup window will close. Several seconds might pass while LMCE generates the new device configs, then the device tree will show under "CORE > Asterisk" a new "Cisco 7970" device (with a "Cisco 7970 Orbiter" subdevice collapsed/viewable through it), and reload the main panel with a details page titled "Device #<n>: Cisco 7970" (<n> is some device ID number previously unused by your LMCE).
###In the Device details panel insert the two decimal MAC addresses defining a range as "LO-HI" (eg. 29902132740096-29902149517311) into the "MAC Address" field
###Click the "Save" button.
###Reload the DCERouter
####Webadmin Home > Wizard > Restart
####Click "Quick Reload Router" button.

You can create the phone device in LMCE first, and then check the phone's DHCP config and MAC address, returning to the device to configure its MAC address range, just as long as you don't connect the phone to the nework with the LMCE DHCP server until after LMCE is prepared.

There is a possibility to have some problems with the phone installation related with its firmware. The firmware version should be the latest. I didn't have any problem with existing firmware on my Cisco 7970. But you should bear in mind, as some more recent SIP firmware has failed to register with LinuxMCE's Asterisk subsystem. See Asterisk's own documentation (separate project) for details.

=Installation=
#Power up the phone with it connected to the network. Note if you have two network cards in your core's machine you should plug network cable in the "inside" ethernet segment, with the LMCE DHCP server running on that inside interface.
#During boot of the phone it will after 2-3 minutes you register with the LMCE to download its Orbiter. You should see on the LMCE Orbiter a message about new device with your phone MAC address was detected.
#After that the phone should be registered with LinuxMCE's Asterisk subsystem and you can see a normal Cisco screen.
#However, it'll take another 2-3 minutes to generate a new Orbiter for the Cisco 7970.
#When this operation finishes you'll see a message on the LMCE Orbiter (not the 7970) screen. Run a quick reload of router (Adminsite Home > Wizard > Restart; Click "Quick Reload Router").
#Now go to the Services menu on the Cisco 7970 and chose "Orbiter".
#If the Cisco 7970 Services menu doesn't contain "Orbiter", reboot the phone (power cycle) and look again in the Services menu.

=Troubleshooting=
*Problem: Phone boots successfully in installation, but there isn't any message on the LMCE Orbiter's screen that it's registering.
Solution:Check the MAC address to ensure the phone's correct MAC address is in the specified range (Adminsite Home > Wizard > Devices; Phones; Cisco 790; Advanced; MAC Address)

=Useful tips=
#To reset a LMCE Network configuration of Cisco 7970 go to Admin website menu "Home -> Advanced -> Network Settings" (where you can change LMCE network settings) and press the following sequence of buttons on the phone: **#** (which will reset and reboot the phone).
#To check network communications between Cisco 7970 and CORE run tcpdump on the CORE: <code>tcpdump -i eth1 <Cisco 7970 IP Address></code>
#To see detailed packets information: <code>tcpdump -i -vv eth1 <Cisco 7970 IP Address></code>

=See also=
[[Orbiter]]

Cisco 7970

2007-12-21T06:29:25Z

Matthew: Test and revise instructions

[[Category: Hardware]]
[[Category: Phones]]
[[Category: Orbiters]]
[[Image:Cisco7909.JPG]]

LinuxMCE allows to use many devices as Orbiters. One of them is the Cisco 7970. You can use it to make calls and control your home as well. To add a new Cisco 7970 phone and Orbiter you should follow these simple instructions. Basically I got the information in the [http://forum.linuxmce.org/index.php?action=search2&search=Cisco+7970 LinuxMCE support forum]. But I think it's good to accumulate odd posts in one place. If you have some suggestions send me email - stepanov.michael [at] gmail [dot] com or leave a comment.

There is also [http://forum.linuxmce.org/index.php?topic=3190.0 some discussion of upgrading Cisco 7970 firmware for using SIP instead of SCCP]. Complete info should be included in this wiki page.

=Preparation=
Cisco 7970 phone is plug-in-play device and LinuxMCE adds it automatically when it'll be plugged in the network. But to do it we have to make some preparations. Since the server must be prepared when the phone checks into it, the phone must be disconnected from the server until the server preparation is complete. But some info for the server must be copied from the phone first.

In short, you'll check that the phone is configured to use DHCP, and get its MAC address. Then you'll create a new LMCE device and set that device to recognize the phone's IP#, and restart the DCERouter.

#Get phone configs.
##Ensure the 7970 is unplugged from the network.
##Power up the phone but don't let it connect to a network server. If your phone is powered by PoE, you will have to ensure that no server cable is connected to the PoE source (eg. a PoE switch), or (harder) that no servers (ie. DHCPd) are up and responding to to queries from the phone.
##Wait for the phone to boot (Cisco splashscreen changes to a background image, then probably goes dark for a few seconds while the "doubled-square" button at the right end of the row of buttons below the screen lights, then the background image returns with a "Configuring IP" time wheel across the bottom).
##Press the settings button (checked box at lower right of round "?" button) to get a "7970(G) SETTINGS" menu ("G" depends on specific 7970/7970G model#).
##Use the down arrow side of the circular navigation button below the screen to select a submenu.
###Check DHCP setting on your phone.
####From the "7970(G) SETTINGS" main menu, select "Network Congfiguration" or enter with the phone's keypad the item's number (probably "2") next to that menu item to get the "Network Congfiguration" menu.
####Down the list is "DHCP Enabled" (probably item 22), which should say "Yes".
###Get the MAC address of your phone.
####Also in the "7970(G) SETTINGS" > "Network Congfiguration" menu, find the "MAC Address" item (probably item 3).
####The "MAC Address" item is the MAC address, though it lacks the conventional ":" field separators among its six pairs of (zero-padded) hexadecimal digits.
#####Insert the ":" separators (eg. 1234567890AB becomes 12:34:56:78:90:AB)
#####You will use those numbers to define the range of MAC addresses LMCE will recognize as Cisco 7970 phones in the LMCE device you are about to create in the LMCE Adminsite.
#Run an Orbiter (on an existing LMCE device, not the 7970).
##Click Orbiter Home -> LinuxMCE:More -> Advanced Options -> Pending Tasks for list.
##Be sure that no others task are pending.
##Go to Admin website, menu Home -> Advanced -> Configuration -> Devices.
###Click "Add a top level device" in either the device tree in the minor side panel, or in the main panel.
###For "Device Template", click the button "Pick Device Template", which will popup a new window.
####From "manufacturer" choose "Cisco". You can filter the Device Template list by using a Device Category like "Hard Phones < Phones < Peripherals" (or a subset of that compound category). You should see in the Device Template list at least two models: 7960 and 7970.
####From "Device Template" pick "7970".
####Press the button "Pick device template". The Orbiter will display "Configuring Cisco 7970". The popup window will close. Several seconds might pass while LMCE generates the new device configs, then the device tree will show under "CORE > Asterisk" a new "Cisco 7970" device (with a "Cisco 7970 Orbiter" subdevice collapsed/viewable through it), and reload the main panel with a details page titled "Device #<n>: Cisco 7970" (<n> is some device ID number previously unused by your LMCE).
###In the Device details panel insert the two decimal MAC addresses defining a range as "LO-HI" (eg. 29902132740096-29902149517311) into the "MAC Address" field
###Click the "Save" button.
###Reload the DCERouter
####Webadmin Home > Wizard > Restart
####Click "Quick Reload Router" button.

####A MAC address is six pairs of hexadecimal digits, separated by hyphens (-) or colon (:). The first three pairs identify a maker. You use them and fill the rest with either three "00" or "FF" pairs to define each of the start and the end of the range. For example, if MAC is 00:16:78:CD:01:D8 its range will be 00:16:78:00:00:00 - 00:16:78:FF:FF:FF.
####Convert those two range delimiting values into LinuxMCE representation.
#####Run the script /usr/pluto/bin/convert_mac, passing the hexadecimal values as parameters: <code>/usr/pluto/bin/convert_mac 00:16:78:00:00:00 ; /usr/pluto/bin/convert_mac 00:16:78:FF:FF:FF</code>
#####You will get two big decimal numbers, one from each conversion of a hexadecimal MAC address.
#####Or use some other method to convert the hexadecimal MAC Addresses (as if they were just long hexadecimal numbers, by omitting the ":" separators) into their decimal equivalents.
#####You will use those numbers to define the range of MAC addresses LMCE will recognize as Cisco 7970 phones in the LMCE device you are about to create in the LMCE Adminsite.

You can create the phone device in LMCE first, and then check the phone's DHCP config and MAC address, returning to the device to configure its MAC address range, just as long as you don't connect the phone to the nework with the LMCE DHCP server until after LMCE is prepared.

There is a possibility to have some problems with the phone installation related with its firmware. The firmware version should be the latest. I didn't have any problem with existing firmware on my Cisco 7970. But you should bear in mind, as some more recent SIP firmware has failed to register with LinuxMCE's Asterisk subsystem. See Asterisk's own documentation (separate project) for details.

=Installation=
#Power up the phone with it connected to the network. Note if you have two network cards in your core's machine you should plug network cable in the "inside" ethernet segment, with the LMCE DHCP server running on that inside interface.
#During boot of the phone it will after 2-3 minutes you register with the LMCE to download its Orbiter. You should see on the LMCE Orbiter a message about new device with your phone MAC address was detected.
#After that the phone should be registered with LinuxMCE's Asterisk subsystem and you can see a normal Cisco screen.
#However, it'll take another 2-3 minutes to generate a new Orbiter for the Cisco 7970.
#When this operation finishes you'll see a message on the LMCE Orbiter (not the 7970) screen. Run a quick reload of router (Adminsite Home > Wizard > Restart; Click "Quick Reload Router").
#Now go to the Services menu on the Cisco 7970 and chose "Orbiter".
#If the Cisco 7970 Services menu doesn't contain "Orbiter", reboot the phone (power cycle) and look again in the Services menu.

=Troubleshooting=
*Problem: Phone boots successfully in installation, but there isn't any message on the LMCE Orbiter's screen that it's registering.
Solution:Check the MAC address to ensure the phone's correct MAC address is in the specified range (Adminsite Home > Wizard > Devices; Phones; Cisco 790; Advanced; MAC Address)

=Useful tips=
#To reset a LMCE Network configuration of Cisco 7970 go to Admin website menu "Home -> Advanced -> Network Settings" (where you can change LMCE network settings) and press the following sequence of buttons on the phone: **#** (which will reset and reboot the phone).
#To check network communications between Cisco 7970 and CORE run tcpdump on the CORE: <code>tcpdump -i eth1 <Cisco 7970 IP Address></code>
#To see detailed packets information: <code>tcpdump -i -vv eth1 <Cisco 7970 IP Address></code>

=See also=
[[Orbiter]]

Cisco 7970

2007-12-20T21:46:45Z

Matthew: Link by search query to forum discussion

Single to Double NIC

2007-12-20T06:54:53Z

Matthew: DHCPd interface = eth1

[[Category: Tutorials]]
[[Category: Networking]]

When switching from a Single NIC setup to using dual NICs, Changes need to be made in several places. Order of these operations is important.

* Web Admin: Show devices tree/My Devices/CORE > Device data/Network Interfaces
** Change: ''eth0,dhcp|'''eth0:0''',192.168.80.1,255.255.255.0'' to: ''eth0,dhcp|'''eth1''',192.168.80.1,255.255.255.0''
* ''/etc/network/interfaces'' (can be edited from the launch manager).
** Comment out eth0:0 related entries:
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0
#
#
# Set eth0 to use DHCP to connect to cable/DSL/etc automatically.
auto eth0
iface eth0 inet dhcp
#
#auto eth0:0
#iface eth0:0 inet static
# address 192.168.80.1
# netmask 255.255.255.0
#
# Set eth1 to use the internal network.
auto eth1
iface eth1 inet static
address 192.168.80.1
netmask 255.255.255.0

* Ensure /etc/default/dhcp3-server contains (only) INTERFACES="eth1" for the internal network.
* You may need to edit ''/etc/iftab'' as well and add a line similar to the eth0 one for your new eth1 with it's own unique MAC address. See '''man iftab''' for more details on this file.
* Web Admin: Advanced menu > Network > Network Settings (more or less optional)
* Check the /etc/exports file, if it looks like this (Please note that these are just examples, your file will likely be somewhat different):
# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes hostname1(rw,sync) hostname2(ro,sync)
#
# Example for NFSv4:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt)
# /srv/nfs4/homes gss/krb5i(rw,sync)
#

## BEGIN : InternalStorageDevices

/mnt/device/81 '''192.168.80'''/255.255.255.0''' eth0'''(rw,no_root_squash,no_all_squash,async,nohide,no_subtree_check)
## END : InternalStorageDevices

## BEGIN : CommonDiskless

/home '''192.168.80'''/255.255.255.0''' eth0'''(rw,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/orbiter '''192.168.80'''/255.255.255.0''' eth0'''(rw,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/keys '''192.168.80'''/255.255.255.0''' eth0'''(ro,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/deb-cache '''192.168.80'''/255.255.255.0''' eth0'''(ro,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/var '''192.168.80'''/255.255.255.0''' eth0'''(rw,no_root_squash,no_all_squash,sync,no_subtree_check)

## END : CommonDiskless

## BEGIN : DisklessMDRoots

/usr/pluto/diskless/108 '''192.168.80'''/255.255.255.0''' eth0'''(rw,no_root_squash,no_all_squash,sync,no_subtree_check)
## END : DisklessMDRoots

:Then it should be changed to look like this:

# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes hostname1(rw,sync) hostname2(ro,sync)
#
# Example for NFSv4:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt)
# /srv/nfs4/homes gss/krb5i(rw,sync)
#

## BEGIN : InternalStorageDevices

/mnt/device/81 '''192.168.80.0'''/255.255.255.0(rw,no_root_squash,no_all_squash,async,nohide,no_subtree_check)
## END : InternalStorageDevices

## BEGIN : CommonDiskless

/home '''192.168.80.0'''/255.255.255.0(rw,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/orbiter '''192.168.80.0'''/255.255.255.0(ro,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/keys '''192.168.80.0'''/255.255.255.0(ro,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/deb-cache '''192.168.80.0'''/255.255.255.0(ro,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/var '''192.168.80.0'''/255.255.255.0(rw,no_root_squash,no_all_squash,sync,no_subtree_check)

## END : CommonDiskless

## BEGIN : DisklessMDRoots

/usr/pluto/diskless/108 '''192.168.80.0'''/255.255.255.0(rw,no_root_squash,no_all_squash,sync,no_subtree_check)
## END : DisklessMDRoots

Single to Double NIC

2007-12-20T06:53:38Z

Matthew: DHCPd interface = eth0

[[Category: Tutorials]]
[[Category: Networking]]

When switching from a Single NIC setup to using dual NICs, Changes need to be made in several places. Order of these operations is important.

* Web Admin: Show devices tree/My Devices/CORE > Device data/Network Interfaces
** Change: ''eth0,dhcp|'''eth0:0''',192.168.80.1,255.255.255.0'' to: ''eth0,dhcp|'''eth1''',192.168.80.1,255.255.255.0''
* ''/etc/network/interfaces'' (can be edited from the launch manager).
** Comment out eth0:0 related entries:
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0
#
#
# Set eth0 to use DHCP to connect to cable/DSL/etc automatically.
auto eth0
iface eth0 inet dhcp
#
#auto eth0:0
#iface eth0:0 inet static
# address 192.168.80.1
# netmask 255.255.255.0
#
# Set eth1 to use the internal network.
auto eth1
iface eth1 inet static
address 192.168.80.1
netmask 255.255.255.0

* Ensure /etc/default/dhcp3-server contains (only) INTERFACES="eth0"
* You may need to edit ''/etc/iftab'' as well and add a line similar to the eth0 one for your new eth1 with it's own unique MAC address. See '''man iftab''' for more details on this file.
* Web Admin: Advanced menu > Network > Network Settings (more or less optional)
* Check the /etc/exports file, if it looks like this (Please note that these are just examples, your file will likely be somewhat different):
# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes hostname1(rw,sync) hostname2(ro,sync)
#
# Example for NFSv4:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt)
# /srv/nfs4/homes gss/krb5i(rw,sync)
#

## BEGIN : InternalStorageDevices

/mnt/device/81 '''192.168.80'''/255.255.255.0''' eth0'''(rw,no_root_squash,no_all_squash,async,nohide,no_subtree_check)
## END : InternalStorageDevices

## BEGIN : CommonDiskless

/home '''192.168.80'''/255.255.255.0''' eth0'''(rw,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/orbiter '''192.168.80'''/255.255.255.0''' eth0'''(rw,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/keys '''192.168.80'''/255.255.255.0''' eth0'''(ro,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/deb-cache '''192.168.80'''/255.255.255.0''' eth0'''(ro,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/var '''192.168.80'''/255.255.255.0''' eth0'''(rw,no_root_squash,no_all_squash,sync,no_subtree_check)

## END : CommonDiskless

## BEGIN : DisklessMDRoots

/usr/pluto/diskless/108 '''192.168.80'''/255.255.255.0''' eth0'''(rw,no_root_squash,no_all_squash,sync,no_subtree_check)
## END : DisklessMDRoots

:Then it should be changed to look like this:

# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes hostname1(rw,sync) hostname2(ro,sync)
#
# Example for NFSv4:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt)
# /srv/nfs4/homes gss/krb5i(rw,sync)
#

## BEGIN : InternalStorageDevices

/mnt/device/81 '''192.168.80.0'''/255.255.255.0(rw,no_root_squash,no_all_squash,async,nohide,no_subtree_check)
## END : InternalStorageDevices

## BEGIN : CommonDiskless

/home '''192.168.80.0'''/255.255.255.0(rw,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/orbiter '''192.168.80.0'''/255.255.255.0(ro,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/keys '''192.168.80.0'''/255.255.255.0(ro,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/deb-cache '''192.168.80.0'''/255.255.255.0(ro,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/var '''192.168.80.0'''/255.255.255.0(rw,no_root_squash,no_all_squash,sync,no_subtree_check)

## END : CommonDiskless

## BEGIN : DisklessMDRoots

/usr/pluto/diskless/108 '''192.168.80.0'''/255.255.255.0(rw,no_root_squash,no_all_squash,sync,no_subtree_check)
## END : DisklessMDRoots

Single to Double NIC

2007-12-20T06:44:28Z

Matthew: Revise operations order to tested sequence

[[Category: Tutorials]]
[[Category: Networking]]

When switching from a Single NIC setup to using dual NICs, Changes need to be made in several places. Order of these operations is important.

* Web Admin: Show devices tree/My Devices/CORE > Device data/Network Interfaces
** Change: ''eth0,dhcp|'''eth0:0''',192.168.80.1,255.255.255.0'' to: ''eth0,dhcp|'''eth1''',192.168.80.1,255.255.255.0''
* ''/etc/network/interfaces'' (can be edited from the launch manager).
** Comment out eth0:0 related entries:
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0
#
#
# Set eth0 to use DHCP to connect to cable/DSL/etc automatically.
auto eth0
iface eth0 inet dhcp
#
#auto eth0:0
#iface eth0:0 inet static
# address 192.168.80.1
# netmask 255.255.255.0
#
# Set eth1 to use the internal network.
auto eth1
iface eth1 inet static
address 192.168.80.1
netmask 255.255.255.0

* You may need to edit ''/etc/iftab'' as well and add a line similar to the eth0 one for your new eth1 with it's own unique MAC address. See '''man iftab''' for more details on this file.
* Web Admin: Advanced menu > Network > Network Settings (more or less optional)
* Check the /etc/exports file, if it looks like this (Please note that these are just examples, your file will likely be somewhat different):
# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes hostname1(rw,sync) hostname2(ro,sync)
#
# Example for NFSv4:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt)
# /srv/nfs4/homes gss/krb5i(rw,sync)
#

## BEGIN : InternalStorageDevices

/mnt/device/81 '''192.168.80'''/255.255.255.0''' eth0'''(rw,no_root_squash,no_all_squash,async,nohide,no_subtree_check)
## END : InternalStorageDevices

## BEGIN : CommonDiskless

/home '''192.168.80'''/255.255.255.0''' eth0'''(rw,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/orbiter '''192.168.80'''/255.255.255.0''' eth0'''(rw,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/keys '''192.168.80'''/255.255.255.0''' eth0'''(ro,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/deb-cache '''192.168.80'''/255.255.255.0''' eth0'''(ro,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/var '''192.168.80'''/255.255.255.0''' eth0'''(rw,no_root_squash,no_all_squash,sync,no_subtree_check)

## END : CommonDiskless

## BEGIN : DisklessMDRoots

/usr/pluto/diskless/108 '''192.168.80'''/255.255.255.0''' eth0'''(rw,no_root_squash,no_all_squash,sync,no_subtree_check)
## END : DisklessMDRoots

:Then it should be changed to look like this:

# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes hostname1(rw,sync) hostname2(ro,sync)
#
# Example for NFSv4:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt)
# /srv/nfs4/homes gss/krb5i(rw,sync)
#

## BEGIN : InternalStorageDevices

/mnt/device/81 '''192.168.80.0'''/255.255.255.0(rw,no_root_squash,no_all_squash,async,nohide,no_subtree_check)
## END : InternalStorageDevices

## BEGIN : CommonDiskless

/home '''192.168.80.0'''/255.255.255.0(rw,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/orbiter '''192.168.80.0'''/255.255.255.0(ro,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/keys '''192.168.80.0'''/255.255.255.0(ro,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/deb-cache '''192.168.80.0'''/255.255.255.0(ro,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/var '''192.168.80.0'''/255.255.255.0(rw,no_root_squash,no_all_squash,sync,no_subtree_check)

## END : CommonDiskless

## BEGIN : DisklessMDRoots

/usr/pluto/diskless/108 '''192.168.80.0'''/255.255.255.0(rw,no_root_squash,no_all_squash,sync,no_subtree_check)
## END : DisklessMDRoots

Single to Double NIC

2007-12-20T06:43:46Z

Matthew: Revise operations order to tested sequence

[[Category: Tutorials]]
[[Category: Networking]]

When switching from a Single NIC setup to using dual NICs, Changes need to be made in several places.

* Web Admin: Show devices tree/My Devices/CORE > Device data/Network Interfaces
** Change: ''eth0,dhcp|'''eth0:0''',192.168.80.1,255.255.255.0'' to: ''eth0,dhcp|'''eth1''',192.168.80.1,255.255.255.0''
* ''/etc/network/interfaces'' (can be edited from the launch manager).
** Comment out eth0:0 related entries:
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0
#
#
# Set eth0 to use DHCP to connect to cable/DSL/etc automatically.
auto eth0
iface eth0 inet dhcp
#
#auto eth0:0
#iface eth0:0 inet static
# address 192.168.80.1
# netmask 255.255.255.0
#
# Set eth1 to use the internal network.
auto eth1
iface eth1 inet static
address 192.168.80.1
netmask 255.255.255.0

* You may need to edit ''/etc/iftab'' as well and add a line similar to the eth0 one for your new eth1 with it's own unique MAC address. See '''man iftab''' for more details on this file.
* Web Admin: Advanced menu > Network > Network Settings (more or less optional)
* Check the /etc/exports file, if it looks like this (Please note that these are just examples, your file will likely be somewhat different):
# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes hostname1(rw,sync) hostname2(ro,sync)
#
# Example for NFSv4:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt)
# /srv/nfs4/homes gss/krb5i(rw,sync)
#

## BEGIN : InternalStorageDevices

/mnt/device/81 '''192.168.80'''/255.255.255.0''' eth0'''(rw,no_root_squash,no_all_squash,async,nohide,no_subtree_check)
## END : InternalStorageDevices

## BEGIN : CommonDiskless

/home '''192.168.80'''/255.255.255.0''' eth0'''(rw,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/orbiter '''192.168.80'''/255.255.255.0''' eth0'''(rw,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/keys '''192.168.80'''/255.255.255.0''' eth0'''(ro,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/deb-cache '''192.168.80'''/255.255.255.0''' eth0'''(ro,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/var '''192.168.80'''/255.255.255.0''' eth0'''(rw,no_root_squash,no_all_squash,sync,no_subtree_check)

## END : CommonDiskless

## BEGIN : DisklessMDRoots

/usr/pluto/diskless/108 '''192.168.80'''/255.255.255.0''' eth0'''(rw,no_root_squash,no_all_squash,sync,no_subtree_check)
## END : DisklessMDRoots

:Then it should be changed to look like this:

# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes hostname1(rw,sync) hostname2(ro,sync)
#
# Example for NFSv4:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt)
# /srv/nfs4/homes gss/krb5i(rw,sync)
#

## BEGIN : InternalStorageDevices

/mnt/device/81 '''192.168.80.0'''/255.255.255.0(rw,no_root_squash,no_all_squash,async,nohide,no_subtree_check)
## END : InternalStorageDevices

## BEGIN : CommonDiskless

/home '''192.168.80.0'''/255.255.255.0(rw,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/orbiter '''192.168.80.0'''/255.255.255.0(ro,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/keys '''192.168.80.0'''/255.255.255.0(ro,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/deb-cache '''192.168.80.0'''/255.255.255.0(ro,no_root_squash,no_all_squash,sync,no_subtree_check)
/usr/pluto/var '''192.168.80.0'''/255.255.255.0(rw,no_root_squash,no_all_squash,sync,no_subtree_check)

## END : CommonDiskless

## BEGIN : DisklessMDRoots

/usr/pluto/diskless/108 '''192.168.80.0'''/255.255.255.0(rw,no_root_squash,no_all_squash,sync,no_subtree_check)
## END : DisklessMDRoots