LinuxMCE - User contributions [en]

Zavio M510E

2010-03-11T21:38:37Z

Murcel:

[[Category: Cameras]]
[[Category: IP Cameras]]

[[Image:M511EWeb_180_opt.jpg|right]]

= Status =
The Zavio M510E device template can be derived from the D-Link DCS-5300G Template. It is fully plug and play and supports pan and tilt.

= Features =
* Browser based
* PAN Range +/- 135°, TILT Range +90°/ -45°
* 10/100mbit LAN
* 2x I/O Port, 1x Sensor Input, 1x Relay Output
* 1x mic input, 1x A/V Connector
* 30fps max
* active motion detector
* MPEG4 compression
* UPnP, DynDNS
* Real-Time Live Video & Audio Streaming

= Ruby Code =
<pre>
RCODE:
0:require 'Ruby_Generic_Serial_Device'
1:class Command < Ruby_Generic_Serial_Device::RubyCommandWrapper
2:end
3:class Device_95 < Ruby_Generic_Serial_Device::RubySerialIOWrapper
4:#### 84 ####################################################################
5:def cmd_84(data, format, disable_aspect_lock, streamid, width, height, cmd=nil)
6:@returnParamArray.clear
7:conn_.Reconnect()
8:auth_s=device_.devdata_[114]+":"+device_.devdata_[115]
9:auth_a=Array.new;
10:auth_s.each{|c| auth_a.push(c)}
11:
12:fix_path=device_.devdata_[2];
13:fix_path='/'+fix_path if(fix_path[0]!='/'[0]);
14:
15:s = "GET "+fix_path+" HTTP/1.0\r\n"
16:s+= "Accept: */*\r\n"
17:s+= "Authorization: Basic "+auth_a.pack("m").chop+"\r\n"
18:s+= "\r\n"
19:
20:conn_.Send(s)
21:recv=""
22:while(true)
23: buff=conn_.Recv(16384, 5000)
24: if(buff.length() == 0)
25: break
26: end
27: recv = recv + buff
28:end
29:if (recv=~ /^HTTP[^\r\n]+200\sOK.+?\r\n\r\n(.+)$/m)
30: fileName="/tmp/ip_camera_img"+device_.devid_.to_s
31: imageFile=File.new(fileName+".jpg",'w')
32: imageFile.print $1
33: imageFile.close()
34: system("/usr/bin/convert "+fileName+".jpg "+fileName+".png");
35: size=File.stat(fileName+".png").size
36: imageFile=File.new(fileName+".png",'r')
37: img = imageFile.read(size);
38: imageFile.close()
39: data_set(img)
40: format_set('png')
41:end
42:return @returnParamArray
43:end
44:#### 200 ####################################################################
45:def cmd_200(cmd=nil)
46:@returnParamArray.clear
47:conn_.Reconnect()
48:auth_s=device_.devdata_[114]+":"+device_.devdata_[115]
49:auth_a=Array.new;
50:auth_s.each{|c| auth_a.push(c)}
51:s = "GET /cgi-bin/camctrl.cgi?move=up HTTP/1.0\r\n"
52:s+= "Accept: */*\r\n"
53:s+= "Authorization: Basic "+auth_a.pack("m").chop+"\r\n"
54:s+= "\r\n"
55:
56:conn_.Send(s)
57:recv=""
58:while(true)
59:buff=conn_.Recv(256, 5000)
60:if(buff.length() == 0)
61:break
62:end
63:recv = recv + buff
64:end
65:return @returnParamArray
66:end
67:#### 201 ####################################################################
68:def cmd_201(cmd=nil)
69:@returnParamArray.clear
70:conn_.Reconnect()
71:auth_s=device_.devdata_[114]+":"+device_.devdata_[115]
72:auth_a=Array.new;
73:auth_s.each{|c| auth_a.push(c)}
74:s = "GET /cgi-bin/operator/ptzset?move=down HTTP/1.0\r\n"
75:s+= "Accept: */*\r\n"
76:s+= "Authorization: Basic "+auth_a.pack("m").chop+"\r\n"
77:s+= "\r\n"
78:
79:conn_.Send(s)
80:recv=""
81:while(true)
82:buff=conn_.Recv(256, 5000)
83:if(buff.length() == 0)
84:break
85:end
86:recv = recv + buff
87:end
88:return @returnParamArray
89:end
90:#### 202 ####################################################################
91:def cmd_202(cmd=nil)
92:@returnParamArray.clear
93:conn_.Reconnect()
94:auth_s=device_.devdata_[114]+":"+device_.devdata_[115]
95:auth_a=Array.new;
96:auth_s.each{|c| auth_a.push(c)}
97:s = "GET /cgi-bin/operator/ptzset?move=left HTTP/1.0\r\n"
98:s+= "Accept: */*\r\n"
99:s+= "Authorization: Basic "+auth_a.pack("m").chop+"\r\n"
100:s+= "\r\n"
101:
102:conn_.Send(s)
103:recv=""
104:while(true)
105:buff=conn_.Recv(256, 5000)
106:if(buff.length() == 0)
107:break
108:end
109:recv = recv + buff
110:end
111:return @returnParamArray
112:end
113:#### 203 ####################################################################
114:def cmd_203(cmd=nil)
115:@returnParamArray.clear
116:conn_.Reconnect()
117:auth_s=device_.devdata_[114]+":"+device_.devdata_[115]
118:auth_a=Array.new;
119:auth_s.each{|c| auth_a.push(c)}
120:s = "GET /cgi-bin/operator/ptzset?move=down HTTP/1.0\r\n"
121:s+= "Accept: */*\r\n"
122:s+= "Authorization: Basic "+auth_a.pack("m").chop+"\r\n"
123:s+= "\r\n"
124:
125:conn_.Send(s)
126:recv=""
127:while(true)
128: buff=conn_.Recv(256, 5000)
129: if(buff.length() == 0)
130: break
131: end
132: recv = recv + buff
133:end
134:return @returnParamArray
135:end
136:#### START SETTERS ####################################################################
137:def initialize()
138:super
139:@returnParamArray=Array.new
140:end
141:def data_set(value)
142:@returnParamArray[19]=value
143:end
144:def format_set(value)
145:@returnParamArray[20]=value
146:end
147:#### END SETTERS ####################################################################
148:end
</pre>

Path has to be changed to /jpg/image.jpg

Zavio M510E

2010-03-11T21:37:27Z

Murcel:

[[Category: Hardware]]
[[Category: Cameras]]

[[Image:M511EWeb_180_opt.jpg|right]]

= Status =
The Zavio M510E device template can be derived from the D-Link DCS-5300G Template. It is fully plug and play and supports pan and tilt.

= Features =
* Browser based
* PAN Range +/- 135°, TILT Range +90°/ -45°
* 10/100mbit LAN
* 2x I/O Port, 1x Sensor Input, 1x Relay Output
* 1x mic input, 1x A/V Connector
* 30fps max
* active motion detector
* MPEG4 compression
* UPnP, DynDNS
* Real-Time Live Video & Audio Streaming

= Ruby Code =
<pre>
RCODE:
0:require 'Ruby_Generic_Serial_Device'
1:class Command < Ruby_Generic_Serial_Device::RubyCommandWrapper
2:end
3:class Device_95 < Ruby_Generic_Serial_Device::RubySerialIOWrapper
4:#### 84 ####################################################################
5:def cmd_84(data, format, disable_aspect_lock, streamid, width, height, cmd=nil)
6:@returnParamArray.clear
7:conn_.Reconnect()
8:auth_s=device_.devdata_[114]+":"+device_.devdata_[115]
9:auth_a=Array.new;
10:auth_s.each{|c| auth_a.push(c)}
11:
12:fix_path=device_.devdata_[2];
13:fix_path='/'+fix_path if(fix_path[0]!='/'[0]);
14:
15:s = "GET "+fix_path+" HTTP/1.0\r\n"
16:s+= "Accept: */*\r\n"
17:s+= "Authorization: Basic "+auth_a.pack("m").chop+"\r\n"
18:s+= "\r\n"
19:
20:conn_.Send(s)
21:recv=""
22:while(true)
23: buff=conn_.Recv(16384, 5000)
24: if(buff.length() == 0)
25: break
26: end
27: recv = recv + buff
28:end
29:if (recv=~ /^HTTP[^\r\n]+200\sOK.+?\r\n\r\n(.+)$/m)
30: fileName="/tmp/ip_camera_img"+device_.devid_.to_s
31: imageFile=File.new(fileName+".jpg",'w')
32: imageFile.print $1
33: imageFile.close()
34: system("/usr/bin/convert "+fileName+".jpg "+fileName+".png");
35: size=File.stat(fileName+".png").size
36: imageFile=File.new(fileName+".png",'r')
37: img = imageFile.read(size);
38: imageFile.close()
39: data_set(img)
40: format_set('png')
41:end
42:return @returnParamArray
43:end
44:#### 200 ####################################################################
45:def cmd_200(cmd=nil)
46:@returnParamArray.clear
47:conn_.Reconnect()
48:auth_s=device_.devdata_[114]+":"+device_.devdata_[115]
49:auth_a=Array.new;
50:auth_s.each{|c| auth_a.push(c)}
51:s = "GET /cgi-bin/camctrl.cgi?move=up HTTP/1.0\r\n"
52:s+= "Accept: */*\r\n"
53:s+= "Authorization: Basic "+auth_a.pack("m").chop+"\r\n"
54:s+= "\r\n"
55:
56:conn_.Send(s)
57:recv=""
58:while(true)
59:buff=conn_.Recv(256, 5000)
60:if(buff.length() == 0)
61:break
62:end
63:recv = recv + buff
64:end
65:return @returnParamArray
66:end
67:#### 201 ####################################################################
68:def cmd_201(cmd=nil)
69:@returnParamArray.clear
70:conn_.Reconnect()
71:auth_s=device_.devdata_[114]+":"+device_.devdata_[115]
72:auth_a=Array.new;
73:auth_s.each{|c| auth_a.push(c)}
74:s = "GET /cgi-bin/operator/ptzset?move=down HTTP/1.0\r\n"
75:s+= "Accept: */*\r\n"
76:s+= "Authorization: Basic "+auth_a.pack("m").chop+"\r\n"
77:s+= "\r\n"
78:
79:conn_.Send(s)
80:recv=""
81:while(true)
82:buff=conn_.Recv(256, 5000)
83:if(buff.length() == 0)
84:break
85:end
86:recv = recv + buff
87:end
88:return @returnParamArray
89:end
90:#### 202 ####################################################################
91:def cmd_202(cmd=nil)
92:@returnParamArray.clear
93:conn_.Reconnect()
94:auth_s=device_.devdata_[114]+":"+device_.devdata_[115]
95:auth_a=Array.new;
96:auth_s.each{|c| auth_a.push(c)}
97:s = "GET /cgi-bin/operator/ptzset?move=left HTTP/1.0\r\n"
98:s+= "Accept: */*\r\n"
99:s+= "Authorization: Basic "+auth_a.pack("m").chop+"\r\n"
100:s+= "\r\n"
101:
102:conn_.Send(s)
103:recv=""
104:while(true)
105:buff=conn_.Recv(256, 5000)
106:if(buff.length() == 0)
107:break
108:end
109:recv = recv + buff
110:end
111:return @returnParamArray
112:end
113:#### 203 ####################################################################
114:def cmd_203(cmd=nil)
115:@returnParamArray.clear
116:conn_.Reconnect()
117:auth_s=device_.devdata_[114]+":"+device_.devdata_[115]
118:auth_a=Array.new;
119:auth_s.each{|c| auth_a.push(c)}
120:s = "GET /cgi-bin/operator/ptzset?move=down HTTP/1.0\r\n"
121:s+= "Accept: */*\r\n"
122:s+= "Authorization: Basic "+auth_a.pack("m").chop+"\r\n"
123:s+= "\r\n"
124:
125:conn_.Send(s)
126:recv=""
127:while(true)
128: buff=conn_.Recv(256, 5000)
129: if(buff.length() == 0)
130: break
131: end
132: recv = recv + buff
133:end
134:return @returnParamArray
135:end
136:#### START SETTERS ####################################################################
137:def initialize()
138:super
139:@returnParamArray=Array.new
140:end
141:def data_set(value)
142:@returnParamArray[19]=value
143:end
144:def format_set(value)
145:@returnParamArray[20]=value
146:end
147:#### END SETTERS ####################################################################
148:end
</pre>

Path has to be changed to /jpg/image.jpg

TV Card Comparison

2009-07-29T16:44:14Z

Murcel:

{{stub}}
[[Category: Hardware ]]
[[Category: Video Capture Boards]]
[[Category: TV Cards ]]

The purpose of this page is to summarize the currently supported / tested TV cards. This is intended to allow a quick comparison for those who are not necessarily familiar with all the available models.

Please get involved and update as appropriate!

{| border="1" cellspacing="0" cellpadding="5" align="center" class = "sortable"
! Model
! Make / Manufacturer
! Connection Type
! DVB-S
! DVB-S2
! DVB-T
! DVB-C
! Analog
! Composite
! 710
! 810
! MythTV
! VDR
|-
| [[Hauppauge_WinTV_Nova-SE2|WinTV Nova-SE2]]
| Hauppauge
| PCI
| Yes
| Yes
| No
| No
| No
| No
| bgcolor="red"| Unknown
| Supported
| Yes
| bgcolor="red"| Unknown
|-
| [[Hauppauge_WinTV-Nova-HD-S2|WinTV Nova-HD-S2]]
| Hauppauge
| PCI
| Yes
| Yes
| No
| No
| No
| No
| Working
| bgcolor="red"| Unknown
| bgcolor="red"| Unknown
| bgcolor="red"| Unknown
|-
| [[Hauppauge_WinTV-PVR-150_MCE|WinTV PVR-150 MCE]]
| Hauppauge
| PCI
| No
| No
| No
| No
| Yes
| Yes
| Supported
| Supported
| Yes, OOB, choose MPEG2 encoder. Also UPNP under Sarah setup
| bgcolor="red"| Unknown
|-
| [[Hauppauge_WinTV-PVR-250|WinTV PVR-250]]
| Hauppauge
| PCI
| No
| No
| No
| No
| Yes
| Yes
| bgcolor="red"| Unknown
| bgcolor="red"| Unknown
| bgcolor="red"| Unknown
| bgcolor="red"| Unknown
|-
| Pinnacle PCTV 310i
| Pinnacle
| PCI
| No
| No
| Yes
| No
| Yes
| No
| Working
| Working
| bgcolor="red"| Unknown
| Working
|-
| [[Kworld_KW-DVB-T_399U|KWorld U399]]
| KWorld
| USB
| No
| No
| Yes x2
| No
| No
| No
| Working
| In development
| bgcolor="red"| Unknown
| bgcolor="red"| Unknown
|-
| [[DViCO_FusionHDTV7_Dual_Express|FusionHDTV7 Dual Express]]
| DViCO
| PCI Express x1
| No
| No
| No (2x ATSC)
| No
| Yes NTSC
| Yes
| bgcolor="red"| Unknown
| bgcolor="red"| Unknown
| bgcolor="red"| Unknown
| bgcolor="red"| Unknown
|-
| [[TT-Budget/WinTV-NOVA-CI]]
| TechnoTrend
| PCI
| Yes
| No
| No
| No
| No
| No
| Supported
| Supported
| bgcolor="red"| Unknown
| Supported
|-
| [[Silicondust HDHomeRun]]
| Silicondust
| Device
| bgcolor="red"| Unknown
| bgcolor="red"| Unknown
| bgcolor="red"| Unknown
| Yes
| No
| bgcolor="red"| Unknown
| Supported
| Supported
| Yes
| bgcolor="red"| Unknown
|-
| [[Technisat SkyStar2]]
| Technisat
| PCI
| Yes
| No
| No
| No
| No
| No
| Supported
| Supported
| bgcolor="red"| Unknown
| Supported
|}

Statuses:
{| border="1" cellspacing="0" cellpadding="5" align="center"
! Status
! Meaning
|-
| bgcolor="red"| Unknown
| The status of this card with this version is not known to whoever added this card. If you know otherwise, '''PLEASE UPADTE!'''
|-
| Unsupported
| No work has yet been done integrating on this version
|-
| Working
| Works with this version, but requires manual configuration / driver updates etc.
|-
| In development
| As Working, but development work is in progress to add this card and make it PNP
|-
| Supported
| Works "Out of the box" so a good choice for newbies :-)
|}

ADT Safewatch Pro 3000

2009-07-17T13:15:42Z

Murcel:

[[Category: Hardware]]
[[Category: Security]]
[[Category: Works without caveats on 0710]]
[[Category: Works without caveats on 0810]]

== This security panel is fully supported via the VistaICM from In2 Networks. ==

ACT Homepro ZRW230

2009-07-17T13:15:09Z

Murcel:

[[Category: Hardware]]
[[Category: ZWave]]
[[Category: Works without caveats on 0710]]
[[Category: Works without caveats on 0810]]

= Status =
working.

= Links =
[http://www.act-solutions.com/HomePro/pdfs/HomePro/Inst/ZRW230_instr.pdf Installation]

[http://www.act-solutions.com/HomePro/pdfs/HomePro/Specs/ZRW230_spec.pdf Specification]

ACT Homepro ZDW230

2009-07-17T13:14:57Z

Murcel:

[[Category: Hardware]]
[[Category: ZWave]]
[[Category: Works without caveats on 0710]]
[[Category: Works without caveats on 0810]]

= Status =
working.

= About =
This is the 3-wire version, there is also a 2-wire version (ZDW232) available.

= Links =
[http://www.act-solutions.com/HomePro/pdfs/HomePro/Inst/ZDW230_instr.pdf Installation]

[http://www.act-solutions.com/HomePro/pdfs/HomePro/Specs/ZDW230_spec.pdf Specification]

ACT Homepro ZCU010

2009-07-17T13:14:32Z

Murcel:

ACT Homepro ZCU000

2009-07-17T13:14:21Z

Murcel:

ACT Homepro ZCS201

2009-07-17T13:13:52Z

Murcel:

[[Category: Hardware]]
[[Category: RF Control]]
[[Category: ZWave]]
[[Category: Works without caveats on 0710]]
[[Category: Works without caveats on 0810]]

= Status =
working.

= About =
This is the serial EU variant of the ACT HomePro Interface, new version

= Available from =

UK - Techstyle UK Ltd.
[http://www.techstyleuk.co.uk/index_files/zcs201.htm ACT ZCS201 Z-Wave Controller, RS232 to Z-Wave Interface (EU)]

ACT Homepro ZCS101

2009-07-17T13:13:40Z

Murcel:

ACT Homepro ZCS010

2009-07-17T13:13:27Z

Murcel:

ACT Homepro ZCS000

2009-07-17T13:13:16Z

Murcel:

ACT Homepro ZIR010

2009-07-17T13:13:01Z

Murcel:

{| align="right"
| __TOC__
|}
[[Category: Hardware]]
[[Category: Security]]
[[Category: ZWave]]
[[Category: Works without caveats on 0710]]
[[Category: Works without caveats on 0810]]

= ACT Homepro Passive Infrared Motion Detector (Binary Sensor) =

PIR (Passive Infra Red) sensor, a type of motion detector which uses invisible infra red light to detect movement in a room.
PIR is sending "Sensor Tripped" events, so that you can use it in security scenarios.

All the tests were made using [[HomePro ZIR010]] (RF Transmitter PIR) model.

=== HowTo install PIR ===
# Open the PIR box so that you have access to Z-Wave button, it is used to remove/add (reset) the PIR from/to Z-Wave network
# Use your Z-Wave Master Controller to add PIR
# Copy the new Z-Wave network configuration to your Z-Wave USB device (see command "Download Configuration")
# Reload Router
# You should see the PIR device available as a child device of ZWave (see [[LinuxMCE Admin Website]]), but the setup isn't ready yet.
# Power off PIR, then power on again (remove a battery for few seconds). Close the PIR box.
## This step is important because PIR is in awake state only for 10 min after it's powered up.
# After 2-3 min from step 6, PIR will send the wake up notification and PIR will be able to set its configuration.
# You should receive the events from PIR

=== Device configuration ===

The PIR supports three modes, they can be set with the device parameter #17:

* Lighting (configuration value 0): Sends ON/OFF to associations in group 1, sends ON to devices associated to group 2 when housing is opened
* Alarm mode (configuration value 1): Sends ALARM to associations in group 1, sends ALARM to group 2 when housing is opened
* Sensor mode (configuration value 2): Sends a binary sensor report to group 1, sends update to group 2 when housing is opened

Battery reports are sent to all devices associated to group 3 of the PIR.

The OFF/IDLE delay can be set via parameter #18. The values 0-255 represent 0-255 minutes.

The device can be temporary disabled by setting parameter #19 to 0. Setting it to 1 will re-enable the PIR.

The wake-up time can be adjusted with parameter #22. The values 15 - 45 represent 15 to 45 seconds.

=== Notes ===

* PIR needs 2 min of 'silence' to get to Trigger Off
* Z-Wave has some new commands to support PIR :
**- Assign Return Route
**- Set Association
**- Set Configuration Parameter
**- Set Wake Up
**The configuration commands are sent automatically by LinuxMCE's [[Z-Wave]] device. But if you are using a different PIR device and you need another setup parameters, you can use the new commands.
*The PIR wake up notification is important, no commands are sent to PIR if the notification wasn't received.
** We must be sure that PIR is able to communicate with Z-Wave network.

= Specifications =
* Power: 4 AAA batteries
* Dimensions (mounted): 10.47cm x 6.6cm x 7.8cm

= Command Classes =
* BASIC_TYPE_ROUTING_SLAVE
* GENERIC_TYPE_SENSOR_BINARY

== Supports ==
* COMMAND_CLASS_SENSOR_BINARY
* COMMAND_CLASS_ALARM
* COMMAND_CLASS_WAKE_UP
* COMMAND_CLASS_ASSOCIATION
* COMMAND_CLASS_CONFIGURATION
* COMMAND_CLASS_BATTERY
* COMMAND_CLASS_MANUFACTURER_SPECIFIC
* COMMAND_CLASS_VERSION

== Controls ==
*COMMAND_CLASS_BASIC

= Links =
http://www.elekhomica.nl/product_info.php?cPath=91&products_id=589

http://www.act-solutions.com/HomePro/HomePro.shtml

Available in the UK - Techstyle UK Ltd.
[http://www.techstyleuk.co.uk/index_files/zir010.htm ACT ZIR010 Z-Wave Passive Infra-Red detector (PIR) Motion Detector]

ACT Homepro Lamp Plug

2009-07-17T13:12:14Z

Murcel:

[[Category: Hardware]]
[[Category: RF Control]]
[[Category: ZWave]]
[[Category: Works without caveats on 0710]]
[[Category: Works without caveats on 0810]]
= Status =

Supported.

= Links =
http://www.elekhomica.nl/product_info.php?cPath=91&products_id=326

http://www.act-solutions.com/HomePro/HomePro.shtml

UK Version Lamp/Appliance Module - Techstyle UK Ltd.
[http://www.techstyleuk.co.uk/index_files/act_zrp210.htm ACT ZRP210 Z-Wave 10A Plug-in Appliance Module (UK Plug type)]

UK Version Lamp Dimmer Module - Techstyle UK Ltd.
[http://www.techstyleuk.co.uk/index_files/act_zdp210.htm ACT ZDP210 Z-Wave 300W Plug-in Dimmer Module (UK Plug type)]

3ware RAID Controller

2009-07-17T13:10:42Z

Murcel:

{| align="right"
| __TOC__
|}
[[category: Hardware]]
[[category: Controller]]
[[Category: RAID Controller]]
[[category: Works without caveats on 0710]]
[[Category: Works without caveats on 0810]]

3ware RAID controllers are supported by default under Linux, but if you want to manage them from Linux instead of the RAID BIOS (3BM) you have to download some things from the 3ware website first.

==== Note for setting up system with over 2 Terabytes of space ====
In order to install LinuxMCE on a RAID with more than 2 terabytes of space, you need to set up the Boot Volume Size to be somewhere around 40 GB. After you install the system on that drive, follow the directions in [[GPT]] to set up the rest of the RAID for media.

=== CLI and Web interface ===
==== Installation ====
===== Automatic installation =====
The 3ware 9560 controller is now automatically recognized by LinutMCE and the 3dm2 software is installed automatically (introduced after 0710 beta 4). There's is no need for manually installing the software.
===== Manual installation =====
'''Using APT'''

apt-get install 3ware-3dm2

'''From 3ware's website '''

3ware download page: http://www.3ware.com/support/download.asp
*Select "Latest Official Release".
This way you'll have just on option to select instead of a whole bunch.
*Choose your product.
I selected "3ware 9650SE" (the suffix doesn't matter, its the same software)
*Scroll down to "Combined 3DM2 and CLI"
*Click on the 32bit or 64bit Linux link, depending on your architecture
*Read the license and press the "Agree" button, which will start the download.
*Unpack the downloaded archive
*Run ./setupLinux_x86.bin (32bit) or ./setupLinux_x64.bin (64bit) in a X terminal.
This will start an InstallShield. You can go with the defaults.

There is a chance that the 3dm2 daemon won't get started by the installer (it will tell you if it fails). You can run it manually by typing "3dm2" in a console.

==== Web interface ====
For some reason, accessing the web interface remotely doesn't work. The browser gets redirected to the wrong place. It only works for local access, for me at least.

After you started the 3dm2 daemon, start a firefox on the machine with the controller and go to [https://localhost:888 https://localhost:888]. Login as "Administrator". The default password is "3ware".

==== Documentation ====
The installer also installs some documentation which you can browse by using this URL: file://localhost/opt/AMCC/Documentation/index.html (if you used the default path, /opt/AMCC)

=== Extending a RAID 5's capacity by adding a new disk ===
If you have a working RAID 5 array and want to expand it with one or more drives so you have more space, you can use the 3ware web interface (3DM) to do this.

Here are the steps:
*Login as "Administrator" (default password "3ware")
*In the top menu, select Management/Maintenance
*Mark the checkbox corresponding to the unit that you want to expand
*Click "Migrate Unit"
*A popup appears. Mark the checkbox(es) corresponding the the disks that you want added to the array and click "OK". Keep the RAID level the same.
At this point, the array will switch to migration mode and it will show this. In the summary page, the controller will say "Warning" in yellow. If you select the controller, the unit you started to expand will display its status in the "Status" column in yellow and a completion percentage.

After the migration is complete, you'll have to increase your partition and filesystem size or create new partition(s) and filesystem(s) from Linux.

==== Power failure notes ====
The manual doesn't say a word about what happens if a power failure happens during array migration/expansion.

Extrapolating the information in the manual, chances are that the migration/expansion will continue after power gets back.

Information extrapolated to get the high chances:
*If you have a BBU (Backup Battery Unit) enabled, the controller memory will contain its data for up to 72 hours in case of an unexpected shutdown
*The array is usuable during the migration. All you get is a performance hit.

Category:RAID Controller

2009-07-17T13:09:31Z

Murcel: New page: category: Hardware category: Controller

[[category: Hardware]]
[[category: Controller]]

3ware RAID Controller

2009-07-17T13:09:18Z

Murcel:

{| align="right"
| __TOC__
|}
[[category: Hardware]]
[[category: Controller]]
[[Category: RAID Controller]]
3ware RAID controllers are supported by default under Linux, but if you want to manage them from Linux instead of the RAID BIOS (3BM) you have to download some things from the 3ware website first.

==== Note for setting up system with over 2 Terabytes of space ====
In order to install LinuxMCE on a RAID with more than 2 terabytes of space, you need to set up the Boot Volume Size to be somewhere around 40 GB. After you install the system on that drive, follow the directions in [[GPT]] to set up the rest of the RAID for media.

=== CLI and Web interface ===
==== Installation ====
===== Automatic installation =====
The 3ware 9560 controller is now automatically recognized by LinutMCE and the 3dm2 software is installed automatically (introduced after 0710 beta 4). There's is no need for manually installing the software.
===== Manual installation =====
'''Using APT'''

apt-get install 3ware-3dm2

'''From 3ware's website '''

3ware download page: http://www.3ware.com/support/download.asp
*Select "Latest Official Release".
This way you'll have just on option to select instead of a whole bunch.
*Choose your product.
I selected "3ware 9650SE" (the suffix doesn't matter, its the same software)
*Scroll down to "Combined 3DM2 and CLI"
*Click on the 32bit or 64bit Linux link, depending on your architecture
*Read the license and press the "Agree" button, which will start the download.
*Unpack the downloaded archive
*Run ./setupLinux_x86.bin (32bit) or ./setupLinux_x64.bin (64bit) in a X terminal.
This will start an InstallShield. You can go with the defaults.

There is a chance that the 3dm2 daemon won't get started by the installer (it will tell you if it fails). You can run it manually by typing "3dm2" in a console.

==== Web interface ====
For some reason, accessing the web interface remotely doesn't work. The browser gets redirected to the wrong place. It only works for local access, for me at least.

After you started the 3dm2 daemon, start a firefox on the machine with the controller and go to [https://localhost:888 https://localhost:888]. Login as "Administrator". The default password is "3ware".

==== Documentation ====
The installer also installs some documentation which you can browse by using this URL: file://localhost/opt/AMCC/Documentation/index.html (if you used the default path, /opt/AMCC)

=== Extending a RAID 5's capacity by adding a new disk ===
If you have a working RAID 5 array and want to expand it with one or more drives so you have more space, you can use the 3ware web interface (3DM) to do this.

Here are the steps:
*Login as "Administrator" (default password "3ware")
*In the top menu, select Management/Maintenance
*Mark the checkbox corresponding to the unit that you want to expand
*Click "Migrate Unit"
*A popup appears. Mark the checkbox(es) corresponding the the disks that you want added to the array and click "OK". Keep the RAID level the same.
At this point, the array will switch to migration mode and it will show this. In the summary page, the controller will say "Warning" in yellow. If you select the controller, the unit you started to expand will display its status in the "Status" column in yellow and a completion percentage.

After the migration is complete, you'll have to increase your partition and filesystem size or create new partition(s) and filesystem(s) from Linux.

==== Power failure notes ====
The manual doesn't say a word about what happens if a power failure happens during array migration/expansion.

Extrapolating the information in the manual, chances are that the migration/expansion will continue after power gets back.

Information extrapolated to get the high chances:
*If you have a BBU (Backup Battery Unit) enabled, the controller memory will contain its data for up to 72 hours in case of an unexpected shutdown
*The array is usuable during the migration. All you get is a performance hit.

Hauppauge WinTV Nova-SE2

2009-07-17T13:04:37Z

Murcel:

[[Category: Hardware]]
[[Category: Video]]
[[Category: TV Cards]]
[[category: Works without caveats on 0810]]

The Hauppauge WinTV-Nova-SE2 is a single tuner DVB-S & S2 PCI card.
It works out of the box with Linuxmce 0810 alpha

MSI Wind PC

2009-07-17T13:02:22Z

Murcel:

[[Category: Hardware]]
[[Category: Media Directors]]
[[Category: Barebones]]
[[Category: Nettops]]
[[category: To be tested]]

The MSI Wind PC is a very small, ultra low power consumption Intel Atom based PC that can be used as an MD. This is a low end, very low cost barebones PC that already includes a CPU. So for MD useage, you just need to add a stick of RAM and you're done!

The cheapest I have seen it is at NewEgg (they do not ship internationally) for US$139.99, [http://www.newegg.com/Product/Product.aspx?Item=N82E16856167032&Tpk=msi%20wind%20pc here].

[[Image:MSI_Wind_PC.jpg|thumb|right|300px|MSI Wind PC]]

== Advantages ==

* Small foot print - 300x260x65mm
* Support UI2 with overlay and 1080p (HD) video playback - VGA out only (note it supports 1080p resolutions, but will struggle with UI2 or HD media at this resolution, 720p is best, and avoid high bitrate/advanced codecs like H264)
* 7.1 Surround sound - analogue minijacks
* Almost noiseless
* Low energy consumption - less than 40w at full speed, this is probably including a HDD which isn't needed for LMCE
* Low price

== Disadvantages ==

* Video is analogue - no DVI or HDMI
* Audio is analogue - no SPDIF out

== Known Issues ==

* Photo Screen Saver sometimes causes issues with the Intel graphics chipset - this causes the unit to lock up. Resolution: disable PSS. It is possible in the next version (0810) of LMCE the driver updates will fix this.
* There is an issue with the NIC drivers that means the unit can't PXE boot properly. Resolution: follow [http://wiki.linuxmce.org/index.php/R8168 this] article to correct the drivers. Probable that the next version of LMCE (0810) will correct this.

Tricklestar 300ZW-US-W

2009-07-17T13:00:21Z

Murcel:

[[Category: Hardware]]
[[Category: RF Control]]
[[Category: ZWave]]
[[Category: Works with caveats on 0710]]
[[Category: Works without caveats on 0810]]

[[Image:300ZW-XX-W-(HI-RES).jpg|thumb|200px|Tricklestar 300ZW-EU-W]]

= Status =
Received sample from manufacturer. Will be full Plug and play with the next release (0810). Works on 0710 with some easy tweaks (either manually create the device or add the usb id's to the #1754 device template: [[ZWave_DeviceTemplate_PlugAndPlay]]).

'''This highly recommended dongle is available in US and EU frequencies and has the latest Zensys library version'''

= About =
The Tricklestar 300ZW-US-W is a USB Z-Wave Controller based on a Zensys chip. It uses US frequency. There is also an EU version: [[Tricklestar 300ZW-EU-W]]. It uses the latest Z-Wave software, 4.27 from October 2008, with support for all the new command classes, and supports both high speed (4x 40kbps) and standard speed Z-Wave devices.

= USB =
uses the pl2303 chipset and the same manuf./prod. ids.

= Links =
http://www.tricklestar.com

Everspring SP103

2009-07-17T12:58:25Z

Murcel:

[[Category: Hardware]]
[[Category: RF Control]]
[[Category: ZWave]]
[[Category: Security]]
[[Category: Works without caveats on 0810]]
[[Image:SP103-s.jpg|thumb|200px|SP103]]

= Status =
Tested (and working) with the latest svn Z-Wave driver (will be included in 0810).

The Everspring SP103 is a basic PIR supporting on/off. One of the disadvantages is the energy consumpton "Eats batteries like there is no tomorrow"

= About =
The Everspring SP103 is a battery powered Z-Wave PIR sensor. It uses a frequency of 868MHz. There is also a US version.

Manuf ID1: 0x0 ID2: 0x60, Prod Typ1: 0x2 Typ2: 0x2, Prod ID1: 0x0 ID2: 0x1

= Command Classes =
* BASIC_TYPE_ROUTING_SLAVE
* GENERIC_TYPE_SENSOR_BINARY

== Supports ==
* COMMAND_CLASS_SENSOR_BINARY
* COMMAND_CLASS_WAKE_UP
* COMMAND_CLASS_ASSOCIATION
* COMMAND_CLASS_CONFIGURATION
* COMMAND_CLASS_BATTERY
* COMMAND_CLASS_MANUFACTURER_SPECIFIC
* COMMAND_CLASS_VERSION

== Controls ==
*COMMAND_CLASS_BASIC
= Links =
http://www.everspring.com

[http://www.techstyleuk.co.uk/index_files/sp103.htm For sale at Techstyle UK Ltd.]

Everspring SM103

2009-07-17T12:57:47Z

Murcel:

[[Category: Hardware]]
[[Category: RF Control]]
[[Category: ZWave]]
[[Category: Security]]
[[Category: Works without caveats on 0810]]
[[Image:SM103-s.jpg|thumb|200px|SM103]]

= Status =
Tested with the latest svn Z-Wave driver (will be included in 0810).

= About =
The Everspring SM103 is a battery powered Z-Wave door/window sensor. It uses a frequency of 868MHz. There is also a US version.

= Links =
http://www.everspring.com

[http://www.techstyleuk.co.uk/index_files/sm103.htm For sale at Techstyle UK Ltd.]

Tricklestar 300ZW-EU-W

2009-07-17T12:56:56Z

Murcel:

[[Category: Hardware]]
[[Category: RF Control]]
[[Category: ZWave]]
[[Category: Works with caveats on 0710]]
[[Category: Works without caveats on 0810]]

[[Image:300ZW-XX-W-(HI-RES).jpg|thumb|200px|Tricklestar 300ZW-EU-W]]

= Status =
'''May 2009 - This dongle is not recommended at the moment as it does not provide stable ZWave enviroment. See also the ZWave driver thread in the forum for more'''

In Europe use this instead : [[Seluxit viaSENS Homecontroller]]

Received sample from manufacturer. Will be full Plug and play with the next release (0810). Works on 0710 with some easy tweaks (either manually create the device or add the usb id's (067b2303) to the #1754 device template: [[ZWave_DeviceTemplate_PlugAndPlay]]).

'''This dongle is available in US and EU frequencies and has the latest Zensys library version'''

To get your zwave devices included into the 300ZW-EU-W or 300ZW-US-W for Linuxmce 710 to control, you will also need a remote like TrickleStar 200ZW-US-W - 2-Button Z-Wave Remote/Inclusion Controller. The alternative and free way would be to download the MAC Widget for a MAC, this has the abiltiy to include your divices into the 300ZW and then the wizard in Linuxmce 710 will see them and auto configure them for you.

'''MAC Widget'''
http://www.tricklestar.com/html/s02_article/article_view.asp?art_id=210&nav_cat_id=150&nav_top_id=57

= About =
The Tricklestar 300ZW-EU-W is a USB Z-Wave Controller based on a Zensys chip. It uses a frequency of 868MHz. There is also a US version.
It uses the latest Z-Wave software, 4.27 from October 2008, with support for all the new command classes, and supports both high speed (4x 40kbps) and standard speed Z-Wave devices.

= USB =
uses the pl2303 chipset and the same manuf./prod. ids.

= Links =
http://www.tricklestar.com

Tricklestar 200ZW-EU-W

2009-07-17T12:55:30Z

Murcel:

[[Category: Hardware]]
[[Category: RF Control]]
[[Category: ZWave]]
[[Category: Works without caveats on 0710]]
[[Category: Works without caveats on 0810]]
[[Image:200ZW-XX-W-ii-(HI-RES).jpg|thumb|200px|Tricklestar 200ZW-EU-W]]

= Status =
Tested with the latest svn Z-Wave driver (will be included in 0810). Also works as inclusion controller when LinuxMCE runs as SIS.
Runs also fine with stock 0710 as primary or secondary controller.

'''This is the recommended inclusion controller'''

= About =
The Tricklestar 200ZW-EU-W is a Z-Wave Remote Controller based on a Zensys chip. It uses a frequency of 868MHz. There is also a US version.

= Configuration Switch =
The product has a slide switch under the Rubber end piece (next to the USB connector), which can set the product in “Operation Mode” and “Configuration Mode”.

= How to reset the Remote (from the Manual) =

Resetting the Controller
# Put the Configuration Switch in “Configuration Mode”.
# Press-and-hold “Up” Operation button for 2 seconds to enter Configuration Mode. LED Indicator will illuminate Green.
# Press-and-hold “Up” Operation button for 10 seconds - this will initiate a reset of the Controller. LED Indicator will alternate Red, Yellow and Green while remote is being reset.
# LED Indicator on the Remote will illuminate Green when Reset is successfully completed and illuminate Red if the operation is unsuccessful.

= Links =
http://www.tricklestar.com

How to Select Components for Your LinuxMCE Computers

2009-07-17T10:09:38Z

Murcel:

The selection of the mainboard is probably the most crucial decision when building a LinuxMCE computer. An entire [[How to Select Mainboards for Your LinuxMCE System|guide is dedicated to just to mainboard selection]]. ''This'' guide is meant to help you select the other components that go into a LinuxMCE computer.

Many aspects of building LinuxMCE computers are no different from building any other PC. There are plenty of resources on the internet to help you select, purchase, and assemble the components of your LinuxMCE computers. There are even guides [http://electronics.howstuffworks.com/how-to-tech/build-a-computer.htm on how to build a computer] if you have never done that before.

For any component you are contemplating, read as much information as you can about it. Oftentimes the most useful information about a component is posted in the form of a review -- either by another purchaser of the same component (like the reviews on product pages at [http://www.newegg.com/Product/ProductReview.aspx?Item=N82E16822148337 newegg], [http://www.amazon.com/Seagate-Barracuda-7200-11-Cache-ST31500341AS/product-reviews/B00066IJPQ/ref=dp_top_cm_cr_acr_txt?ie=UTF8&showViewpoints=1 amazon], or [http://www.ncix.com/products/?sku=33167&vpn=ST31500341AS&manufacture=Seagate&promoid=1046#CustomerReviews NCIX]), or by a web site ([http://www.silentpcreview.com/article772-page1.html like this]) or blogger that has candidly reviewed the component.

Google is your friend when researching components.

You might consider a [[:Category:Nettops|nettop]] computer for use as a [[Core|core]] or [[Media Director|media director]]. Nettop computers are usually purchased fully integrated. This means that what you buy is actually a mainboard with a power supply, hard drive, memory, case et cetera all put together and ready to use. If you are considering a nettop computer, you should still scrutinize all of its components to assess its appropriateness for your LinuxMCE installation.

===Audible Noise===
''Note: Cores and centralized media directors are often kept in a closet, utility room, or basement where their noise emission does not matter. If that is the case for the computer you are building, we recommend selecting components for better cooling rather than low noise.''

[[Media Director|Media directors]] will be in your living space unless they are centralized, so it is important that they are not so loud that they are distracting or disturbing. Generally, cooling fans are the biggest noise makers. Fans can be found on CPU coolers, power supplies, graphics cards, and integrated into cases. We recommend that you find reviews that comment on the noise generated by any components with fans that you are considering.

Note that fans are designed into components for a reason: To keep them cool. This is also an important aspect of component selection. Expect to compromise between cooling capability and low audible noise when selecting components.

===Mainboards, RAM, CPUs, GPUs, Network Adapters, and Audio Chips===
The selection of mainboards, RAM, CPUs, GPUs, network adapters, and audio chips are closely related to one another and crucial to a successful LinuxMCE installation. Their selection is covered in detail in [[How to Select Mainboards for Your LinuxMCE System|the mainboard selection article]].

===Optical Drives===
We recommend an [http://en.wikipedia.org/wiki/Optical_disc_drive optical drive] that is connected to your mainboard using either [http://en.wikipedia.org/wiki/SATA SATA] or [http://en.wikipedia.org/wiki/Parallel_ATA PATA]. SATA and PATA optical drives generally work with LinuxMCE out-of-the-box. If you are considering an optical drive connected over [http://en.wikipedia.org/wiki/USB USB] or [http://en.wikipedia.org/wiki/FireWire firewire] be sure to verify that other linux users have had success with the model you are considering.

The optical drive that you select should at least support reading [http://en.wikipedia.org/wiki/Compact_Disc compact discs] and [http://en.wikipedia.org/wiki/DVD DVDs]. Optical disc writing capabilities are not used by LinuxMCE so an optical drive capable of burning discs offers little advantage over read-only drives under normal use. You might, however, want to include an optical drive capable of writing on your core computer in case you want to copy data for maintenance or backup purposes.

[http://en.wikipedia.org/wiki/Blu-ray_Disc Blu-ray] playback is [http://forum.linuxmce.org/index.php?topic=7346.msg46555#msg46555 not supported from optical drives built-in to media directors]. Blu-ray support can still be integrated into your LinuxMCE system in other ways. The blu-ray playback limitation is inherited from linux itself. That is, once linux supports blu-ray playback, LinuxMCE will likely support it soon after.

===Storage===
For purposes of hardware selection, it is helpful to divide the [http://en.wikipedia.org/wiki/Hard_disk storage] of a LinuxMCE system into two categories:
*'''System Hard Drive''' - This is the hard drive that the [[Core|core]] boots from. All system files in the entire LinuxMCE system are stored on the system hard drive.
*'''Media Storage''' - These are hard drives used to store media like videos and music.

====System Hard Drive====
We recommend that you include a hard drive in your core that will be used only for storing the LinuxMCE system and the operating system it is running on. This drive should be a physically separate drive from any drive that is used to store your media. It should be connected to your mainboard using a SATA or PATA connection.

When you install or upgrade LinuxMCE, the process will normally require overwriting the entire partition where LinuxMCE is installed. If you keep media on that partition it will be deleted. Keeping your media on a partition separate from your system drive allows your media to survive upgrading and reinstallation of LinuxMCE.

Media kept on a separate partition from the system drive on the same physical hard disk can survive re-installation of LinuxMCE. However, the risk of permanently losing access to the media on the media partition is much higher than if it were on a physically separate hard drive. Because of this, we recommend that media be stored on a physically separate hard drive from the system.

The system hard drive on the core will store the operating system and LinuxMCE software for both the core itself and each of the media directors. This has two effects worth noting:
*<u>No hard drive is needed in media directors.</u> Hard drives can be connected to media directors to store media but will not be used to host LinuxMCE system files.
*Each media director you include in your LinuxMCE system will require its own space on the core's system hard drive.

An [http://forum.linuxmce.org/index.php?topic=4684.msg27410#msg27410 accepted rule of thumb] for calculating the size of the system drive required for your LinuxMCE core (or [[Hybrid|hybrid]]) is 20 GB plus 7 GB for each additional media director.

====Media Storage====
Any hard drive connected to either the core or any of the media directors can be used by LinuxMCE to store media. In addition, any network attached storage on the INTERNAL network can also be used by LinuxMCE for media storage. The best way to store your media depends on a variety of factors.

The following are common locations for media storage used by other users:
*hard drives connected by SATA or PATA to media directors or the core (in either [http://en.wikipedia.org/wiki/JBOD#Concatenation_.28SPAN.29 JBOD] or [http://en.wikipedia.org/wiki/RAID RAID] configurations)
*hard drives in external enclosures connected via USB to media directors or the core
*networked attached storage devices

===Case===
Most [http://en.wikipedia.org/wiki/Computer_case computer cases]that can physically contain all of the components of your LinuxMCE computers will work just fine. We do recommend that you select the appropriate style or form factor of case for the location where the computer will reside. There are four different styles of case that are commonly used to house LinuxMCE computers:
*'''Tower''' - A normal desktop PC case. These are typically used for cores and centralized media directors and kept out-of-sight in utility rooms, closets, and basements.
*'''[http://en.wikipedia.org/wiki/19-inch_rack Rackmount]''' - Also used for cores and centralized media directors and kept out-of-sight. The advantage of rackmount cases is that they can be neatly mounted in a rack alongside other computer and network equipment.
*'''[http://en.wikipedia.org/wiki/Home_theater_PC HTPC]''' - Used for hybrids and media directors where the esthetics are important and there is room for home theater components. These cases generally look like other home theater components.
*'''[[:Category:Nettops|Nettop]]''' - Small form factor used mainly as media directors where hiding or unobtrusive mounting of the media director is important. Nettops can often be mounted completely out-of-sight behind the display.

===TV Tuner Cards===
The [[Hauppauge_WinTV-PVR-150_MCE|Hauppauge PVR-150]], [[Hauppauge_WinTV-PVR-250|PVR-250]], and [[Hauppauge_WinTV-PVR-500_MCE|PVR-500]] are the [http://forum.linuxmce.org/index.php?topic=6369.msg38610#msg38610 officially supported] TV tuner cards. They work out-of-the-box with LinuxMCE. These are all standard definition TV tuner cards. Some of these cards are difficult to find new, however, they are widely available used.

There are also officially-supported external TV tuners: The standard definition [[Hauppauge_WinTV-PVR-USB2|Hauppauge PVR-USB2]], and the high definition [[Silicondust_HDHomeRun|Silicondust HDHomeRun]].

Many LinuxMCE systems incorporate multiple TV tuners. This is because each tuner can only be tuned to one channel at a time. The number of tuners you need is the sum of the following:
*the maximum number of media directors you want to be able to simultaneously watch different channels
*the number of channels you want to be able to record simultaneously
If you intend to record two programs in adjacent time slots on different channels you should budget two tuners for that task. This because the beginning of the second program may start before the end of the first.

Suppose, for example, you have two media directors. Using four TV tuners would allow you to simultaneously record two channels and watch different channels on each of the media directors.

TV tuner cards can be incorporated into the core and any media directors. They are shared throughout the system regardless of where they are physically located.

===See Also===
[[How to Select Mainboards for Your LinuxMCE System]]
[[Category: Hardware | Hardware ]]

Swann IP-3G ConnectCam 500

2009-07-17T09:45:44Z

Murcel:

[[Category: Hardware]]
[[Category: Cameras]]
[[Category: IP Cameras]]
'''Swann IP-3G ConnectCam 500
'''

[[Image:Swann3g.jpg]]

The Swann 3G Connect Cam 500 is a basic IP camera. It is Wireless, with a 802.11g functionality, and can run over Ethernet. It is perfect for a budget indoor IP camera that is compatible with Linux MCE.

Once you have plugged the camera and you know the IP address and Mac address, it is very simple to setup.
Just browse to the admin system. At the bottom of the left hand pane, click "Show Devices Tree".
Click CORE on the left, then click "Create child device".

Enter a common name for the camera, eg "Swann 500"

Enter the IP address and Mac address.

[[Image:childdevices.jpg]]

Then click "Pick Device Template"

You then select "Generic IP Camera" from the device templates dropdown. (This is in 810, Not sure if 710 has this template?)
Once selected, click "Pick Device Template"

Another window will now appear, you can safely ignore the top half of page and scroll to the bottom.

In the "Path" field, enter the following :

/cgi/jpg/image.cgi

Leave PK_FloorplanObjectType and Alert blank.

TCP Port : 80
AuthUser : admin
AuthPassword : admin (assuming you have not changed it from default )
IP : IP of Camera
MAC : MAC address of camera

Click Save

[[Image:Devicedata.JPG]]

Now reload your DCE Router and you should see the camera in "Show Cameras" in the admin system.

The Swann IP 3G Camera is available in the EU from :

http://www.hightechpad.com

Phone Lines

2009-07-17T09:42:27Z

Murcel:

[[Category: Documentation]]
[[Category: Tutorials]]
[[Category: Admin Website]]
<p>Here is where you add all the phone lines you have in your house. LinuxMCE supports the regular, old fashioned type of phone line (aka POTS), as well as ISDN, T1 and VOIP. VOIP, for Voice Over IP, is the most flexible and usually the lowest cost. It uses the Internet to place and receive calls, however you can still call regular phone numbers like you always did, and most VOIP providers will still give you a regular incoming number like you have now.</p>
<p>If you have VOIP lines, your LinuxMCE Core will automatically manage your internet connection for you, giving priority to the phone calls so that they have a clear connection.</p>
<p>Even if you have no phone lines at all, you can always call other LinuxMCE users for free. On your Orbiter just choose "Call LinuxMCE User" and dial their LinuxMCE username.</p>
<p>To add a phone line, choose the type of line and then supply the parameters. There are more documents under this one which explain how to configure the various types of phone lines.</p>

* Make phone calls using a VOIP provider. Currently the follow Providers are supported with minimal setup.
** [[Broadvoice]]
** [[E-Fon_(Switzerland)]]
** [[Inphonex]]
** [[NuFone]]
** [[Sipgate]]
** [[Teliax]]
** [[VoiceEclipse]]
** [[Manual Phones Configuration | How to Configure Phone Lines Manually]]

Panasconic BL-C10

2009-07-17T09:39:53Z

Murcel:

[[category: hardware]]
[[category: cameras]]
[[category: IP Cameras]]
[http://panasonic.co.jp/pcc/products/en/netwkcam/lineup/c10a.html Panasonic BL-C10 website.]

Motorola DCT6416

2009-07-17T09:37:15Z

Murcel:

{{delete}}
It's a DVR/Cable box

How to set up as an input device via firewire:

Dlna

2009-07-17T09:33:36Z

Murcel:

[[category: documentation]]
[[category: glossary]]
= DLNA =

== Summary ==
The Digital Living Network Alliance is an international, cross-industry collaboration of consumer electronics, computing industry and mobile device companies. Members of DLNA share a vision of wired and wireless interoperable networks where digital content such as photos, music, and videos can be shared through consumer electronics (CE), personal computers (PCs), and mobile devices in and beyond the home. DLNA is focused on delivering an interoperability framework of design guidelines based on internationally recognized open industry standards together with a certification and logo program to officially verify and validate the conformance and interoperability of compliant products for consumers.

DLNA published its first set of Interoperability Guidelines in June 2004, and the first set of DLNA Certified products began appearing in the market soon thereafter. The latest version of the DLNA Interoperability Guidelines, version 1.5, was published in March 2006 and then expanded in October 2006. The current guidelines expand the capabilities of the DLNA-defined network to include more device classes and functional capabilities – including printers, mobile devices, controllers, uploaders and downloaders.

== How does it work ==
First of all we need some kind of network. It might be LAN, WAN, wifi, wimax, gprs, 3g etc.
As long as it can talk TCP/IP and handle multicast it should work in theory.
Next you need a couple of dlna compatible devices. For example a Playstation 3 and a DMS. For example Fuppes or MediaTomb.
As soon as you power up your PS3 you should see a the DMS under each of the three categories (Pic, Audio, Video).

=== Device Classes ===
*DMS
Digital Media Server:
Store media content and makes it available to DMP and DMRs.

*DMP
Digital Media Player:
Plays content stored on DMRs and render its output to a screen, audio amplifier etc.

*DMR
Digital Media Renderer:
Plays content received from DMC which get its media from a DMS.

*DMC.
Digital Media Controller:
Gets content from DMS and plays it on a DMR.
Its like a remote control. Just control stuff.
For example: Internet Tablets etc.

*DMP
Digital Media Printer:
Provides printing capabilities to a dlna enabled network.

*Other device classes:
MHDx
P: Player
U: Uploader
D: Downloader
C: Controller

HID:
M-NCF: Mobile Network Connectivity Function
MIU: Media Interoperability Unit

== Supported media formats (DLNA approved formats) ==
*Video:
MPEG-1, MPEG-2
H.263, MPEG-4 Part 2, MPEG-4 Part 10
WMV9, VC-1

*Audio:
LPCM
MPEG-1/2 L2, MPEG-1/2 L3
MPEG-4 AAC LC, MPEG-4 AAC LTP, MPEG-4 HE AAC, MPEH-4 BSAC
AC-3, ATRAC3plus, WMA, WMA Professional, AMR, AMR-WB+, G.726

*Pictures:
JPEG, PNG, GIF, TIFF

=== Media Format Profile ===
A format profile define a combination of media formats that create a media object.
MPEG-2 video + AC-3 sound, make up a DVB PS stream.

Profile example:
*MPEG_PS_NTSC:
Video: MPEG-2 (NTSC constraints)
Audio: Encoded using either AC-3, LPCM, or MPEG 1/2 L2
System: Program Streams

=== DRM ===
DRM exist in DLNA world too.
It consist of serveral DRM technologies together with something calle Link Proctection.
Basically you by the right to use a media and you are able to transport it to any of your dlna devices.
They DMR handle encryption, decryption and re-encryption.
Above is a oversimplified.

== LMCE implementation status ==
As of today LMCE use Fuppes as its UPnP/DLNA server.
There is a proposed change to MediaTomb since it is more complete in terms of functionality and maintenance/maturity.

== Usage Scenarios ==

*2-box push:
In this scenarion only two boxes (might be software or hardware boxes) interact.
We have DMS and one DMP.
The DMP fetch content from DMS and render it and plays it.

DMS->DMP

*3-box push:
This scenario involve three components.
One DMS. A DMC and a DMP.
In this scenarion we can use the DMC to control what is played on the DMP.

DMS---->DMP
| ^
| |
|->DMC-|

== Links ==
http://www.cybergarage.org/net/upnp/c/index.html

Difference between 710 RC1 and 710 RC2

2009-07-17T09:31:23Z

Murcel:

[[category: versions]]
When we first shipped RC1 it happened to coincide with an Ubuntu release. Ubuntu's servers were under very heavy load and downloads took a while to complete. We later discovered that we were missing a few debs in the downloads from Ubuntu, in our deb cache.

If you installed RC1 at any other time, however, these missing packages were automatically downloaded during your installation. You don't need the RC2 disc to obtain them.

RC2 includes minor changes in the ZWave Driver, which is currently under active development. If you are using RC1 and need the most recent ZWave Driver, you can get it by directly installing the debian package:

For i386:

wget http://linuxmce.org/710rc1_update/pluto-zwave-lighting_2.0.0.44.0804202200_i386.deb
sudo dpkg -i pluto-zwave-lighting_2.0.0.44.0804202200_i386.deb

For AMD64:

wget http://linuxmce.org/710rc1_update/pluto-zwave-lighting_2.0.0.44.0804202200_amd64.deb
sudo dpkg -i pluto-zwave-lighting_2.0.0.44.0804202200_amd64.deb

Bug Reporting

2009-07-17T09:30:41Z

Murcel:

[[category: tutorials]]
==Introduction==
In oder to focus the efforts of a software project, it is essential to have a clear understanding of the current status of all defects. This document outlines LinuxMCE's policies on bug reporting.

==Importance of Reporting Bugs==
There are several reasons to track defects strictly:
*If a bug is not tracked, it may be overlooked and never fixed
*If a bug is not tracked, members of the development team may not know it exists
*Tracking bugs provides a way to determine the functional status of the project
*The bug list provides development team members a place to look for things to contribute
*The bug list provides users a place to formally report issues
*The bug tracking system provides a way to divide up work among the development team
*The bug tracking system provides a way for people to check the status of particular issues and present workarounds or fixes in an organized and manageable way

==What Bugs Should Be Reported==
Follow these steps:
===Step 1: Determine if the issue is worth reporting===
If the answer to any of these questions is '''"yes"''', then this issue probably '''does not warrant a bug report''':
*Can the issue be phrased as a support request? (for examples: "How do I...", "Is it possible to...", "How do I configure...", "Where is documentation on..."
*Is the issue related to future development? (for examples: "Add a feature for...", "Restructure system so...")
*Is the issue caused by an unrelated software package that doesn't directly affect our project? (for example, say we are making a phone system based in Linux that has a Gnome desktop. Our issue is: "I cannot open text documents in gedit because the Gnome project has provided a broken package". This would not be a bug for our phone system at all, as it doesn't affect our project - though it may be an annoyance to people using our applications)

If the answer to any of the following questions is '''"yes"''', then it may be time to '''consider reporting a bug''':
*Is a feature completely unusable?
*Is a feature that used to work not working as expected?
*Is an important feature missing that is hindering the usefulness of another feature?

===Step 2: Determine if the bug is actually expected behavior===
In many cases, software is designed to do things that the user doesn't expect. To avoid reporting bugs when no bug exists, a thorough check of the functionality of the affected component is required. Make sure you have answered the following questions before reporting a bug:
*Do I have a complete understanding of what is happening to produce the bug? (consider checking documentation)
*Have other people experienced this issue and been shown that it is by design? (consider checking forums, IRC channels)
*Is this component under heavy development right now? Perhaps there has been a change in how it works.

===Step 3: Determine if the bug has already been reported===
Reporting duplicate bugs wastes everyone's time. The reporter takes time to compile their thoughts, the reviewer takes time to mark it as a duplicate, future bug investigators take time to redirect to the proper bug, and the list goes on. To maintain everyone's efficiency, duplicate bugs should be avoided. Make sure you have followed the previous two steps and done significant searching in the bug database before reporting a new bug.

If a bug ticket already exists for the issue you are trying to report, make sure there is enough information in the ticket. Add any new information you have. Useful information is discussed in the next section.

===Step 4: Report the bug===
Assuming all of the previous steps have suggested the issue is worth reporting, it's time to make a bug report. The details that go into the report are discussed in the next section.

==What Data Should Be In The Report==
An uninformative bug report is a waste of time. To make a good bug report, the following items are essential:
*'''A clear title/subject''' - describe what is broken and in what way. This goes in the "Short summary" field in LinuxMCE Trac tickets.
**''Good example'': Unable to adjust screen brightness using hotkeys - works otherwise
**''Bad example'': Brightness doesn't work
*'''Clear description of the issue''' - describe all symptoms of the issue in the body of the report without trailing off into other features. Be sure to explain exactly what you expect to happen, exactly what is happening, and exactly how to make it happen.
**''Good example'': When the hotkeys associated with screen brightness are pressed, the screen brightness should change, but the screen brightness does not change. The expected brightness notification appears in the top right of the screen, but it displays the wrong brightness level.
**''Bad example'': I push the hotkey and nothing happens.
*'''If there is more than one way to perform a task, state exactly which way you did it, and whether the other way works'''
**''Good example'': (taking a break from the brightness examples) Select File --> Load to load the file. Loading the file by double clicking in the file explorer works.
**''Bad example'': Load the file.
*'''When was the last time it worked the way you expected?''' - Is this something that broke recently? When, precisely, did it stop working?
**''Good example'': This worked out of the box in versions 7.04 through 8.10. Using the most recent development packages, it does not work
**''Bad example'': It used to work, now it doesn't.
*'''Step by step instructions to reproduce the issue''' - the more detailed, the better. Do not leave steps out, do not assume any prior knowledge of the issue, even if it is widely known
**''Good example'': While logged into Gnome in an X session, press Fn+F5 or Fn+F6 several times. Notice that the brightness doesn't change, but the brightness notification appears
*'''Note any configuration that may impact this issue''' - If you have configured something differently than expected, be sure to note this.
**''Good example'': I am using the out-of-the box configuration.
**''Good example'': I have changed xorg.conf to try to increase my screen resolution. The lines I changed were...
*'''Hardware description''' - If hardware could affect the issue, be sure to include all relevant information
**''Good example'': I am using a Sony VGN-S480 with nVidia 6200Go graphics card
*'''Workarounds''' - If you've found a way around the issue, add that in to help people who are suffering the same issue and to provide a better picture of what is actually broken
**''Good example'': It is possible to adjust screen brightness using the ''smartdimmer'' command
*'''''MOST IMPORTANTLY: RE-READ THE REPORT BEFORE YOU SEND IT''''' - Re-reading gives you a chance to collect your thoughts, make sure you haven't missed anything, correct typographical errors that make reading difficult, and clarifying your ideas. Be sure your writing is clear and concise. Read the report as if you know nothing about the issue. Look for places where you may have assumed certain knowledge or a certain process.

When writing your report, be mindful of the following:
*'''Avoid the use of general terms like "it" or "the window".''' Instead, use specifics like "the brightness notification dialog at the top right of the screen"
*'''Give any information that could be related.''' It is generally acceptable to provide too much information, but leaving something out will make the issue harder to address
*This can't be stressed enough: '''''RE-READ THE REPORT BEFORE YOU SEND IT''''' for all the reasons stated above.

==Fill in Additional Bug Report Fields==
This information is specific to LinuxMCE and the Trac ticket system.
===Your email or username===
Put something here so we know who you are! If we can't identify you as the original reporter, we can't follow up to make sure the bug is fixed.
===Type===
Pick a type so we know what this bug is all about.
*''defect'' - There is a feature in the version you are using that is not working properly
*''defect_patch'' - There is a feature in the version you are using that is not working properly, and you are providing a patch that fixes it. '''This is the standard way to submit a fix patch''' (see also - [[Bug_Reporting#Submitting a Patch|Submitting a Patch]])
*''feature_request'' - Something is missing from the version you are using that should be added
*''feature_patch'' - Something is missing, and you are providing a patch that adds it. '''This is the standard way to submit a feature patch''' (see also - [[Bug_Reporting#Submitting a Patch|Submitting a Patch]])
*''task'' - Something needs doing, but nothing is broken
===Priority===
Pick a priority so we know how serious the issue is.
*''blocker'' - LinuxMCE cannot exist without this bug being addressed
*''critical'' - Functionality of the whole system or a critical component is significantly impaired by this bug
*''major'' - Functionality of a specific component is significantly impaired by this bug
*''normal'' - Functionality of a specific component is slightly impaired by this bug
*''minor'' - Functionality is impaired, but not significantly
*''trivial'' - Functionality may slightly affected, or this bug may simply cause user confusion
===Component===
Determine what area of LinuxMCE is most directly affected.
===Milestone===
When is a reasonable target time for this bug to be addressed? (Most people who are not involved with the development process will leave this blank)
===Version===
What is the most recent version of LinuxMCE that is affected by this bug?
===Keywords===
Key words and phrases to allow others to search for this bug easier. Keywords are important to avoid bug duplications.
===Cc===
Names of people who should be notified of this bug. (Most people who are not involved with the development process will leave this blank)

==Attaching Files to the Bug Report==
*Log files are essential to understanding issues. Attach any log files that may be interesting.
*The output of certain programs may demonstrate the issue well. Attach any interesting output in text files if more than a few lines to avoid filling the bug report with complex text.

==Submitting a Patch==
If you're attaching a patch, be sure to mention it in the report. Attach it as a separate file - not inline.
*Explain how the patch addresses the problem and any other components that the changes might affect.
*Explain the procedure you went through to test the functionality of the patch
*Explain what you've done to make sure the patch does not break other functionalities.
*Make sure the ''type'' field is set to ''feature_patch'' if your patch is adding a new feature or ''defect_patch'' if your patch is fixing a defect

==Following Bug Progress==
If you are the original reporter of the bug you have a responsibility to make sure it is addressed. Check the bug ticket regularly. If more information is requested, you should provide it in a timely manner.

It is generally not acceptable to post additional comments on a bug report asking for the bug to be fixed faster, so do not do that. Only post additional comments if you have come up with new information that will help resolve the bug.

==References==
*This page originally adapted from [http://jimbodude.net/wiki/Bug_Reporting jimbodude's wiki]
*[http://www.chiark.greenend.org.uk/~sgtatham/bugs.html Simon Tatham, "How to Report Bugs Effectively"]
*[http://www.debian.org/Bugs/Reporting Debian BTS, "reporting bugs"]
*[https://help.ubuntu.com/community/ReportingBugs Ubuntu Community Documentation, "Reporting Bugs"]

Category:Glossary

2009-07-17T09:27:56Z

Murcel: New page: Category: Documentation

[[Category: Documentation]]

Child devices

2009-07-17T09:27:45Z

Murcel:

[[Category: Documentation]]
[[Category: Glossary]]
Orbiter relates to more devices which adds more functionality like:

- [[Photo Screen Saver]] - OpenGL based screen saver

- using a remote to control it Orbiter instead a keyboard

- Other devices

Creating a Device Template for a Remote that uses the kernel input subsystem

2009-07-17T09:25:10Z

Murcel:

[[Category: Tutorials]]
== Criteria for using The Generic HID Interface ==

The Remote in question must:

* Expose itself as an input device, and have a file entry in /dev/input as eventX where X is the order in which the kernel discovered the device.
* Must emit EV_KEY packets, as specified by the Linux Input subsystem.

Following these criteria, creating a device template is simple.

== Adding Support for a new Remote ==

=== Before you start ===

Press Keys on the remote, make note of which keys work, and which ones do not. '''You will only need to specify keys for the keys that do not work in your template.'''

=== Step 1: Plug in device ===

With orbiter started, plug in the device, and quick reload the router.

=== Step 2: Find the Device # of the On-Screen Orbiter you are using. ===

In the web admin, go to Advanced > Configuration > Devices.

Select your media director from the top of the device tree. For the Core Hybrid, select Core/Hybrid under CORE.

Select the On Screen Orbiter child. Get its device #. You will need this.

=== Step 3: Tail the Orbiter Log looking for Generic HID events ===

Open a shell on the media director on which you have the remote connected.

Due to the sheer volume of data generated by the Orbiter log, we will need to filter it, looking specifically for GenericHIDInterface messages. This is simple with a grep command.

tail -f /var/log/pluto/XX_LaunchOrbiter.sh.log | grep "GenericHIDInterface"

You will start seeing GenericHIDInterface messages.

=== Step 4: Press the keys that do not work ===

Press the keys that do not work. If the Generic HID Interface is able to decode them, you will see messages similar to the following:

10 06/27/09 22:00:33.856 GenericHIDInterface::DecodeEventInFD() Begin <0xb3232b90>
10 06/27/09 22:00:33.856 GenericHIDInterface::DecodeEventInFD code 20114 value 1. <0xb3232b90>
10 06/27/09 22:00:33.856 GenericHIDInterface::DecodeEventInFD() End <0xb3232b90>
10 06/27/09 22:00:34.048 GenericHIDInterface::DecodeEventInFD() Begin <0xb3232b90>
10 06/27/09 22:00:34.048 GenericHIDInterface::DecodeEventInFD code 20114 value 0. <0xb3232b90>
10 06/27/09 22:00:34.048 GenericHIDInterface::DecodeEventInFD() End <0xb3232b90>

If you recieve the code, Make note of the code. Match this with the button you're intending to press, in your notes.

Repeat this for all the buttons that do not work.

=== Step 5: Open a notepad and write Configuration Device Data ===

Open a notepad and take the codes you have written down, and pair them with buttons in the [[Remote Mapping Table]].

The Lines should be like this:

VolUp,20114,R[,Y]

and should be one per line. Where the:

* first value, is the symbol in the [[Remote Mapping Table]]
* second value, is the key code you determined by looking at the logs.
* third value is a key state, where:
** U = Button Up
** D = Button Down
** H = Button Held Down
** R = Button Repeats when Held Down.
* fourth value (optional) means that this key code should be honored even on screens which yield to the OS, examples of this screen include:
** DVD Menu
** Web Browser
** On-Screen navigation (think MythTV menus, etc.)

=== Step 6: Write the Mapping Device Data ===

Press enter a few times, and enter the mapping device data.

This device data is used to map one key code, to another.

According to the 1812: Gyration Go Mouse template:

new line delimited list of events to replace with other events in the format: Event Type,ID=EventType,id

To give an example:

The Gyration 3101 emits a key code, 97, when the Windows button is pressed. This needs to be changed so the system interprets it as the key code for F7.

so we add a mapping for it:

2,97=2,73
3,97=3,73

The code, 73, for F7, is coincidentally the xkeysym for F7. X Key symbols can be found using the '''xev''' utility, and reading the "code:" value when a key is pressed.

==== Wait, what are the 2, and 3, values? ====

These are the Event Types.

According to Orbiter.h:
<pre>
typedef enum _EventType {
QUIT,
NOT_PROCESSED,
BUTTON_DOWN, // keyboard
BUTTON_UP,
REGION_DOWN, // mouse
REGION_UP,
MOUSE_MOVE,
MOUSE_RELATIVE_MOVE,
HID,
NONE
} EventType;
</pre>
Since this is an enumerated type, starting from 0, 2 = BUTTON_DOWN, and 3 = BUTTON_UP.

=== Step 7: Make a New template, with all the compiled information ===

Please read the general information on [[Device Templates]] before continuing.

Go to the web admin, Advanced > Configuration > Device Templates.

Select the appropriate Manufacturer. If it does not exist, make one.

Select Remote Controls from the device category, or Gestural Remotes if it is a gyro-mouse. Basically, use an appropriate category.

Select [Add Device]

Select that this is a device that does not require any programming. Name it appropriately.

====Controlled By Category====
This device needs to be controlled by category '''Orbiters -> Standard Orbiter'''. So add that as a controlled by Device Category. Orbiter uses this relation to not only make the remote a child of the on-screen orbiter, but Orbiter expects to find remote controls in this category so it knows to appropriate them.

====Configuration Device data====
add the following, with the Use Master List Defaults checked for all:

* Configuration. Paste the Configuration device data from your notepad, here.
* Mapping. Paste the Mapping Device data from your notepad, here.
* Only One Per PC, set this to 1
* Auto Assign This to Parents Room, set this to 1
* PNP Create Without Prompting, set this to 1
* Immediate Reload isn't Necessary, set this to 1.

''Please be sure to put appropriate comments into the comments field. This is required.''

====Plug and Play====

This is how LinuxMCE will detect the device. Since this is most likely, a USB device, you will need to put 0 in both the beginning and end MAC, as they will not be used.

You will then need to fill out the Vendor/Model ID appropriately. You can grab this information using '''lsusb'''

For example: The Gyration Go Mouse and MCR Remote use a USB ID of 0c16:0002, where 0c16 is the vendor number, and 0002 is the model number. Enter this without the colon: '''0c160002'''. Write a suitable comment, and click the add button.

You can then press the Save button, and the device template will be saved. You can then check this in anonymously, by using the sqlCVS functions in the web admin to check in your '''dce''' and '''ir''' repositories. Use the default credentials for an anonymous check in, and let us know in a trac ticket that you've checked in a template.

MythTV, xmltv and channels

2009-07-16T10:55:33Z

Murcel:

CONCEPT

To get MythTV set up fairly easily with xmltv, I use the following steps. It works with multiple grabbers and sources. The approach should work with LMCE 0704 (stable) as well as all beta versions for 0710.

#If LMCE already offers a good tv_grab_* for your situation, skip this step. If there is a grabber available that is not yet listed in mythtv-setup, download your favorite version(s). In my case (Holland), these are tv_grab_nl_upc and tv_grab_nl_py. Make them executable and copy them to /usr/bin. In mythtv-setup, these grabbers will now show up automagically.
#Go through mythtv-setup as usual (when in doubt, see generic Mythtv documentation).
#'''Make sure your system timezone and LMCE timezone are correct!''' For your system timezone, you could use the command tzselect at the command line, for the LMCE timezone, go to http://192.168.80.1/pluto-admin/ -> basic info -> installation.
#Run tv_grab_<the one you use> --configure. Pay attention, it will probably generate a config file in .xmltv, but you will need to copy it to .mythtv. The name will depend on what you used in mythtv-setup. I find it convenient to just do a test-run of mythfilldatabase. It will complain about a missing config file: that will be the name and location you need to use. It will look something like this: /home/linuxmce/.mythtv/UPC-analog.xmltv (I used the name UPC-analog in mythtv-setup).
#Assuming you finished mythtv-setup properly, you can now run mythfilldatabase --manual. You will ''have'' to fill in the channel numbers when asked, if you leave them blank, the channels are not added to the database! Just use the suggested names. Press enter at every other question.
#Once done, go to http://192.168.80.1/mythweb/settings/channels. You will see a list of all channels, as shown below. Do NOT edit xmltvid (3rd column). You can change the 4th to 6th column as you see fit. Column 4 determines the order in which the guide data is shown on screen. The important column is 7. In my case, this has many 6-digits numbers. This is the frequency at which the channel is coming in. This information is usually readily available from your cable provider.
[[Image:Channels.jpg]]
One last remark: The example image above is from a setup with two sources. Column 2 shows the source number. If your source is ''digital'', you will have to use an ir-blaster (probably a usb-uirt) to change the channels on the cable box. Leave the frequency empty, but make sure column 4 contains the correct channel number.

--[[User:Domodude|Domodude]] 14:27, 21 March 2008 (PDT)
[[category: Tutorials]]

Make things happen at set times or intervals

2009-07-16T10:52:08Z

Murcel:

<p><h1>How to set it up</h1></p>
<p> In LinuxMCE admin, choose wizard, events, timed events. Give your event handler a description, like "7 a.m. wake-up call", and then choose the type of timed event that most closely matches what you want, and click add. Then add all the commands that you want to occur at that time.</p>

<p> The event Wizard gives you very basic event control, but without requiring any programming or technical skills. Click the advanced link if you want to program a sophisticated event handler using the embedded ruby language interpreter. The snippet of code will be executed whenever the event is triggered. This way you can create a very sophisticated event,such as "start watering the lawn at 7 a.m. only if there has been no rain in the last 24 hours and the weather report indicates a clear day". </p>

<p><h1>How to use it</h1></p>
<p>N/A</p>

<p><h1>Programmer's guide</h1></p>
[[category: Tutorials]]

How to Select Components for Your LinuxMCE Computers

2009-07-16T10:44:12Z

Murcel:

The selection of the mainboard is probably the most crucial decision when building a LinuxMCE computer. An entire [[How to Select Mainboards for Your LinuxMCE System|guide is dedicated to just to mainboard selection]]. ''This'' guide is meant to help you select the other components that go into a LinuxMCE computer.

Many aspects of building LinuxMCE computers are no different from building any other PC. There are plenty of resources on the internet to help you select, purchase, and assemble the components of your LinuxMCE computers. There are even guides [http://electronics.howstuffworks.com/how-to-tech/build-a-computer.htm on how to build a computer] if you have never done that before.

For any component you are contemplating, read as much information as you can about it. Oftentimes the most useful information about a component is posted in the form of a review -- either by another purchaser of the same component (like the reviews on product pages at [http://www.newegg.com/Product/ProductReview.aspx?Item=N82E16822148337 newegg], [http://www.amazon.com/Seagate-Barracuda-7200-11-Cache-ST31500341AS/product-reviews/B00066IJPQ/ref=dp_top_cm_cr_acr_txt?ie=UTF8&showViewpoints=1 amazon], or [http://www.ncix.com/products/?sku=33167&vpn=ST31500341AS&manufacture=Seagate&promoid=1046#CustomerReviews NCIX]), or by a web site ([http://www.silentpcreview.com/article772-page1.html like this]) or blogger that has candidly reviewed the component.

Google is your friend when researching components.

You might consider a [[:Category:Nettops|nettop]] computer for use as a [[Core|core]] or [[Media Director|media director]]. Nettop computers are usually purchased fully integrated. This means that what you buy is actually a mainboard with a power supply, hard drive, memory, case et cetera all put together and ready to use. If you are considering a nettop computer, you should still scrutinize all of its components to assess its appropriateness for your LinuxMCE installation.

===Audible Noise===
''Note: Cores and centralized media directors are often kept in a closet, utility room, or basement where their noise emission does not matter. If that is the case for the computer you are building, we recommend selecting components for better cooling rather than low noise.''

[[Media Director|Media directors]] will be in your living space unless they are centralized, so it is important that they are not so loud that they are distracting or disturbing. Generally, cooling fans are the biggest noise makers. Fans can be found on CPU coolers, power supplies, graphics cards, and integrated into cases. We recommend that you find reviews that comment on the noise generated by any components with fans that you are considering.

Note that fans are designed into components for a reason: To keep them cool. This is also an important aspect of component selection. Expect to compromise between cooling capability and low audible noise when selecting components.

===Mainboards, RAM, CPUs, GPUs, Network Adapters, and Audio Chips===
The selection of mainboards, RAM, CPUs, GPUs, network adapters, and audio chips are closely related to one another and crucial to a successful LinuxMCE installation. Their selection is covered in detail in [[How to Select Mainboards for Your LinuxMCE System|the mainboard selection article]].

===Optical Drives===
We recommend an [http://en.wikipedia.org/wiki/Optical_disc_drive optical drive] that is connected to your mainboard using either [http://en.wikipedia.org/wiki/SATA SATA] or [http://en.wikipedia.org/wiki/Parallel_ATA PATA]. SATA and PATA optical drives generally work with LinuxMCE out-of-the-box. If you are considering an optical drive connected over [http://en.wikipedia.org/wiki/USB USB] or [http://en.wikipedia.org/wiki/FireWire firewire] be sure to verify that other linux users have had success with the model you are considering.

The optical drive that you select should at least support reading [http://en.wikipedia.org/wiki/Compact_Disc compact discs] and [http://en.wikipedia.org/wiki/DVD DVDs]. Optical disc writing capabilities are not used by LinuxMCE so an optical drive capable of burning discs offers little advantage over read-only drives under normal use. You might, however, want to include an optical drive capable of writing on your core computer in case you want to copy data for maintenance or backup purposes.

[http://en.wikipedia.org/wiki/Blu-ray_Disc Blu-ray] playback is [http://forum.linuxmce.org/index.php?topic=7346.msg46555#msg46555 not supported from optical drives built-in to media directors]. Blu-ray support can still be integrated into your LinuxMCE system in other ways. The blu-ray playback limitation is inherited from linux itself. That is, once linux supports blu-ray playback, LinuxMCE will likely support it soon after.

===Storage===
For purposes of hardware selection, it is helpful to divide the [http://en.wikipedia.org/wiki/Hard_disk storage] of a LinuxMCE system into two categories:
*'''System Hard Drive''' - This is the hard drive that the [[Core|core]] boots from. All system files in the entire LinuxMCE system are stored on the system hard drive.
*'''Media Storage''' - These are hard drives used to store media like videos and music.

====System Hard Drive====
We recommend that you include a hard drive in your core that will be used only for storing the LinuxMCE system and the operating system it is running on. This drive should be a physically separate drive from any drive that is used to store your media. It should be connected to your mainboard using a SATA or PATA connection.

When you install or upgrade LinuxMCE, the process will normally require overwriting the entire partition where LinuxMCE is installed. If you keep media on that partition it will be deleted. Keeping your media on a partition separate from your system drive allows your media to survive upgrading and reinstallation of LinuxMCE.

Media kept on a separate partition from the system drive on the same physical hard disk can survive re-installation of LinuxMCE. However, the risk of permanently losing access to the media on the media partition is much higher than if it were on a physically separate hard drive. Because of this, we recommend that media be stored on a physically separate hard drive from the system.

The system hard drive on the core will store the operating system and LinuxMCE software for both the core itself and each of the media directors. This has two effects worth noting:
*<u>No hard drive is needed in media directors.</u> Hard drives can be connected to media directors to store media but will not be used to host LinuxMCE system files.
*Each media director you include in your LinuxMCE system will require its own space on the core's system hard drive.

An [http://forum.linuxmce.org/index.php?topic=4684.msg27410#msg27410 accepted rule of thumb] for calculating the size of the system drive required for your LinuxMCE core (or [[Hybrid|hybrid]]) is 20 GB plus 7 GB for each additional media director.

====Media Storage====
Any hard drive connected to either the core or any of the media directors can be used by LinuxMCE to store media. In addition, any network attached storage on the INTERNAL network can also be used by LinuxMCE for media storage. The best way to store your media depends on a variety of factors.

The following are common locations for media storage used by other users:
*hard drives connected by SATA or PATA to media directors or the core (in either [http://en.wikipedia.org/wiki/JBOD#Concatenation_.28SPAN.29 JBOD] or [http://en.wikipedia.org/wiki/RAID RAID] configurations)
*hard drives in external enclosures connected via USB to media directors or the core
*networked attached storage devices

===Case===
Most [http://en.wikipedia.org/wiki/Computer_case computer cases]that can physically contain all of the components of your LinuxMCE computers will work just fine. We do recommend that you select the appropriate style or form factor of case for the location where the computer will reside. There are four different styles of case that are commonly used to house LinuxMCE computers:
*'''Tower''' - A normal desktop PC case. These are typically used for cores and centralized media directors and kept out-of-sight in utility rooms, closets, and basements.
*'''[http://en.wikipedia.org/wiki/19-inch_rack Rackmount]''' - Also used for cores and centralized media directors and kept out-of-sight. The advantage of rackmount cases is that they can be neatly mounted in a rack alongside other computer and network equipment.
*'''[http://en.wikipedia.org/wiki/Home_theater_PC HTPC]''' - Used for hybrids and media directors where the esthetics are important and there is room for home theater components. These cases generally look like other home theater components.
*'''[[:Category:Nettops|Nettop]]''' - Small form factor used mainly as media directors where hiding or unobtrusive mounting of the media director is important. Nettops can often be mounted completely out-of-sight behind the display.

===TV Tuner Cards===
The Hauppauge PVR-150, PVR-250, and PVR-500 are the [http://forum.linuxmce.org/index.php?topic=6369.msg38610#msg38610 officially supported] TV tuner cards. They work out-of-the-box with LinuxMCE. These are all standard definition TV tuner cards. Some of these cards are difficult to find new, however, they are widely available used.

There are also officially-supported external TV tuners: The standard definition Hauppauge PVR-USB2, and the high definition Silicondust HDHomeRun.

Many LinuxMCE systems incorporate multiple TV tuners. This is because each tuner can only be tuned to one channel at a time. The number of tuners you need is the sum of the following:
*the maximum number of media directors you want to be able to simultaneously watch different channels
*the number of channels you want to be able to record simultaneously
If you intend to record two programs in adjacent time slots on different channels you should budget two tuners for that task. This because the beginning of the second program may start before the end of the first.

Suppose, for example, you have two media directors. Using four TV tuners would allow you to simultaneously record two channels and watch different channels on each of the media directors.

TV tuner cards can be incorporated into the core and any media directors. They are shared throughout the system regardless of where they are physically located.

===See Also===
[[How to Select Mainboards for Your LinuxMCE System]]
[[Category: Hardware | Hardware ]]

Category:Internet Streaming

2009-07-16T10:38:57Z

Murcel:

This section contains articles relevant to streaming media from internet sources such as internet radio or television.
[[Category: Tutorials]]

Category:Telecom

2009-07-16T10:38:05Z

Murcel:

Pluto's phone system

Category:News

2009-07-16T10:37:38Z

Murcel: Removing all content from page

Category:LinuxAdmin

2009-07-16T10:37:04Z

Murcel:

LinuxMCE Admin Documentation

[[Category: Documentation]]

Category:Automation

2009-07-16T10:34:55Z

Murcel:

[[Category: Hardware]]

Also see this list of widely available [[Automation|home automation systems]].

If you would like to add to this section, please add the relevant subcategory as listed below with <nowiki>[[Category: Infrared]]</nowiki> for example to the top of a page you wish to have listed here.

I'm a Linux user already. Should I use LinuxMCE's distribution

2009-07-16T09:38:07Z

Murcel:

{{delete}}__NOTOC__

Strictly speaking LinuxMCE is a package. A very big package. The distribution it runs on is standard Kubuntu Linux.

Only the PC running as the Core is required to run Kubuntu and use the LinuxMCE package.

Any PC used as a Media Director can [[netboot]] from the Core, without the requirement for an OS at all. Of course, you can always boot whatever OS is already stored on the hard drive of each Media Director PC and use that PC separately from the LinuxMCE system. Play the games (or whatever) that are stored on the hard drive (using whichever OS is already installed there) there, and when you're ready to use that PC as a Media Director again, you just go back to netbooting from the Core.

For the Core, you should use Kubuntu and our packages.

LinuxMCE is based on the standard Kubuntu Linux distribution. While you could try to run LinuxMCE on another distribution, it's not recommended. LinuxMCE has lots of scripts and utilities to facilitate various tasks. Plus, LinuxMCE embeds many other open source projects, like Xine, Asterisk, etc., with our own "wrappers" that allows them to work together seamlessly. These wrappers are only tested against the versions we maintain in our Ubuntu mirror.

Before we upgrade anything on our mirror, we thoroughly test the new packages in our system to be sure it still works.

We didn't take any modules away from the Kubuntu distribution, we only added some. You can still use your Core as a normal Kubuntu Linux PC. In fact, our additions can be bypassed if they get in your way, as is explained below. But in general, DCERouter and other devices, like the home automation modules, all run in the background and won't interfere in screen sessions.

''Here's what we changed:''

====Configuration scripts====
LinuxMCE includes a lot of scripts that automate all aspects of maintaining a Linux system. For example, when you add a new user from the LinuxMCE Admin site, it automatically creates a new media directory, exports a samba share, creates an email and voicemail accounts, and so on. There's also scripts to do lots of low-level things like setup ip network prioritizing, so your VOIP calls are always clear. By default, LinuxMCE overwrites and re-creates many Linux config files at each boot. In this regard LinuxMCE acts like a black box appliance. However, once you install LinuxMCE you can go to the [[LinuxMCE Admin Website]]-->Advanced-->Boot Scripts and disable any or all of these scripts. Then you can still maintain your LinuxMCE Core like any other Linux PC and it won't overwrite your config files.

====Our Ubuntu mirror====
We maintain our own mirror based on Ubuntu. The reason is that we have "wrappers" for many open source projects like Xine, Asterisk, etc., allowing them to work together seamlessly. Whenever updates are posted to Ubuntu's repository, we test the new versions to be sure the changes did not break anything in our wrappers and that the auto-configuration scripts still work. In very rare cases, we need to make our own version of a package that replaces the one in Ubuntu. We avoid that whenever possible, and instead re-work our wrappers so that we can stay current with the "stock" version. Such changes are generally trivial, and you should see no difference between LinuxMCE's Ubuntu mirror and the official one.

====Window manager====
The Media Directors use our own modified version of the Ratpoison window manager. All applications appear as full-screen, with no borders. Our Orbiter GUI becomes the XWindows desktop. This is the desired behavior in an appliance-like set-top box; we completely isolate the user from anything computer-like. However, you will likely not want this as your main desktop. It is possible to run 2 versions of X on separate terminals: one with LinuxMCE's window manager, and the other with your own preferred choice of desktop.

====Software Module Overview====

[[Overview of the software modules]]

I'm a Linux user already. Should I use LinuxMCE's distribution

2009-07-16T09:37:28Z

Murcel:

Known Issues

2009-07-16T08:51:52Z

Murcel:

[[Category: Known Issues]]
{| align="right"
| __TOC__
|}

== Known issues with LinuxMCE 0710 ==
*[[Known_Issues_0710|Known issues with 0710 RC2]]
*[[Known_Issues_0710_RC1|Known issues with 0710 RC1]]
*[[Known_Issues_0710_Beta4|Known issues with 0710 Beta4]]
*[[Known_Issues_0710_Beta3|Known issues with 0710 Beta3]]

== Known issues with LinuxMCE 0704 ==

*[[Known_Issues_0704|Known issues with 0704]]

== Known issues with LinuxMCE 1.1 ==

*[[Known_Issues_11Beta|Known issues with LinuxMCE 1.1 Beta]]

== Known issues with LinuxMCE 1.0 ==

*[[Known_Issues_LinuxMCE10|Known issues with LinuxMCE 1.0]]

KnownIssues 0710 RC1

2009-07-16T08:50:39Z

Murcel: KnownIssues 0710 RC1 moved to Known Issues 0710 RC1

#REDIRECT [[Known Issues 0710 RC1]]

Known Issues 0710 RC1

2009-07-16T08:50:39Z

Murcel: KnownIssues 0710 RC1 moved to Known Issues 0710 RC1

[[Category: Known Issues]]
No known issues.

KnownIssues 0710 Beta4

2009-07-16T08:50:22Z

Murcel: KnownIssues 0710 Beta4 moved to Known Issues 0710 Beta4

#REDIRECT [[Known Issues 0710 Beta4]]

Known Issues 0710 Beta4

2009-07-16T08:50:22Z

Murcel: KnownIssues 0710 Beta4 moved to Known Issues 0710 Beta4

[[Category: Known Issues]]
{{delete}}
* "Failed to get IVTV video driver" message on status window on Orbiter. This is because IVTV package fails to install.This can be safely ignored as the IVTV driver is now built into the Linux kernel.

* VIA video support is a bit lame at the moment: Cursor leaves dandruff with OpenChrome drivers (fix is to enable SWCursor in xorg.conf, need to make default), MythTV menu text not always drawn with VIA proprietary drivers

* nVidia 7150 + and some 6150 and 7050 systems have high cpu problem. This causes high Xorg usage with MythTV + Xine, unless V-Sync disabled. On machines with SSE (most modern CPUs), the solution is to install nvidia drivers 169.12 and add
Option "UseEvents" "true"
to the video device section of the /etc/xorg.conf file. Then you can fully enable v-sync in nvidia-settings without drowning the CPU. A fix for this has been committed.

* Zwave children have the device data's and room reset after reload router. A fix was committed (svn rev #19914) to the General Info Plugin for this. To fix this on your machine, follow these steps:
''- cd /usr/pluto/bin''

''- mv General_Info_Plugin.so General_Info_Plugin.so.orig''

''- wget -c ftp://builder32.linuxmce.com/Download/GIP-beta4-fix/i386/General_Info_Plugin.so '' (for i386)

''or''

''- wget -c ftp://builder32.linuxmce.com/Download/GIP-beta4-fix/x86_64/General_Info_Plugin.so '' (for amd64)

''- reload router''

* Sorting by genre, performed etc. doesn't work correctly. A fix was committed (svn rev #19953) for the Media Plugin for this. Also, now you can rip an audio CD and play it in track order (the track number attribute will be attach to audio files). To fix this on your machine, follow these steps:

''- cd /usr/pluto/bin''

''- mv Media_Plugin.so Media_Plugin.so.orig''

''- wget -c ftp://builder32.linuxmce.com/Download/Media_Plugin-beta4-fix/i386/Media_Plugin.so '' (for i386)

''or''

''- wget -c ftp://builder32.linuxmce.com/Download/Media_Plugin-beta4-fix/x86_64/Media_Plugin.so '' (for amd64)

''- reload router''

* MythTV affects performance of system because of too verbose logging, sometimes even freezing. The fix has been commited (svn rev #19965). To fix it on your machine, follow the steps

''- cd /usr/pluto/bin''

''- mv MythTV_Player MythTV_Player.orig''

''- wget -c ftp://builder32.linuxmce.com/Download/MythTV_Player-beta4-fix/i386/MythTV_Player '' (for i386)

''or''

''- wget -c ftp://builder32.linuxmce.com/Download/MythTV_Player-beta4-fix/x86_64/MythTV_Player '' (for amd64)

''- chmod +x MythTV_Player''

''- reload router''

* Asterisk/FreePBX (automatic) configuration seems to be broken. It fails to accept incoming calls, the following error is logged:
[Mar 6 23:11:25] WARNING[19471] pbx.c: Channel 'SIP/0878700000-081dffa8' sent into invalid extension '102' in context 'custom-linuxmce', but no invalid handler
See http://forum.linuxmce.org/index.php?topic=4850.msg28369#msg28369 on how to fix this.

* Support disked MD was dropped completely in 0710

* DVDs fail to play on the M/D but play OK on the Core.
This is caused by the bug in the mounting script which is fixed in svn. See the instruction how to patch your M/Ds in this post: http://forum.linuxmce.org/index.php?topic=4585.msg27572#msg27572

* CM11A fixes:

'' - download TAR file [http://www.mediafire.com/?lkzl4ddwniz for AMD64] or [http://www.k-net.eu.org/lmce/cm11a-x86.tgz here for i386]

'' - copy libSerial.so to /usr/pluto/lib

'' - copy CM11A and Lighting_Plugin.so to /usr/pluto/bin

'''DO NOT FORGET BACKUP ORIGINAL FILES!'''

'' - reload router