Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - nite_man

Pages: 1 ... 66 67 [68]
Users / Re: Squeezebox
« on: July 24, 2007, 11:45:55 am »
As I know Squeezebox is integrated with LinuxMCE in following manner. You add it to the system. The system recognizes it, assigns it to the specific room (that room should have any MD) and install SlimServer. After quick reload router when you choose the room with Sqeezebox on Orbiter, go to audio section  and choose some song to play the system automatically will transfer request to the Squeezebox and it starts play the music. Theoretically, you should be able to control Squeezebox from its remote but I'm not sure in case of LinuxMCE.

You can try SlimServer web ineterface - http://you_core_ip:9000. But be sure that you add port 9000 on the Firewall page.

Developers / Re: Movie database ( vs. for lookups)
« on: July 24, 2007, 08:49:23 am »
Agree with Eirik. IMDB is much appropriate place to take movie information. Especially, there is a Perl module - IMDB::Film with can be used for that. I'll try to create a command-line script and integrate it with LinuxMCE web interface.


I'm very interested to have Marantz in LinuxMCE. If it's possible let's add it and other contributions as well.

Users / Re: Generic Serial Device - (New user)
« on: July 23, 2007, 11:57:50 am »
You're very welcome, Martin :)

Users / Re: Building a core ideas?
« on: July 19, 2007, 09:56:05 am »
As I already wrote in other post in Pluthome only nVidia 6XXX (Asus на 6200LE, for example) works well with UI2 Alpha Blended and HDTV. Also I head that VIA UniChrome is supported under Linux but I didn't make any real tests yet.

Users / Re: What Hardware are you using?
« on: July 19, 2007, 09:52:07 am »
I'm not sure about LinuxMCE but for Plutohome UI2 and HDTV only nVidia 6XXX works well (not sure about S3 UniChrome card. It also should work).
If you're going to build HTPC by yourself the best noiseless processor coolers (CNPS8000 for AMD, for example) and power supplies are from Zalman, case - Silverstone LC16M or LC20M - I managed to configure VFD display to work with MythTV, remote control also works fine. UI2 can be used comfortable with wireless mouse and keyboard (actually is not needed) from Gyration.

Users / Re: Generic Serial Device - (New user)
« on: July 19, 2007, 09:39:35 am »
Yes - I had looked at this, but unless I am missing something I am not able to understand how to define the interface correctly and then how to send and receive the ascii text through the interface.

The steps are following:
1. Be sure that you have installed GSD package -
Code: [Select]
dpkg -l 'pluto-generic-serial-device' (it should be there).
2. Created a device template for your system and specify that it should use GSD. Add it under category lighting interfaces if you want to control lighting devices only. To control all kind of devices (security, climate etc) it's better to use Interface::Specialize. Also, you should specify a communication type - RS232, Ethernet etc.
3. After you save a new template a new interface will be added automatically. You can see it under Wizard --> Devices --> Interfaces. Also, there is a GSD page - Wizard --> Devices --> Generic Serial Devices. On that page you'll able to add/modify Ruby commands. To do that you should specify a group and tick box 'internal Ruby Command'. After you quick reload router you should see GSD process in console:
Code: [Select]
# ps -elf|grep Generic_Serial_Device
Code: [Select]
5 S root     10085     1  0  76   0 -   683 -      Jul17 ?        00:00:00 SCREEN -d -m -S LinCon_8000-30 /usr/pluto/bin/ 30 localhost Generic_Serial_Device
4 S root     10086 10085  0  75   0 -   646 wait   Jul17 pts/8    00:00:00 /bin/bash /usr/pluto/bin/ 30 localhost Generic_Serial_Device
0 S root     31800 10086  0  79   0 - 123146 295621 Jul17 pts/8   00:00:00 ./Generic_Serial_Device -d 30 -r localhost -l /var/log/pluto/30_Generic_Serial_Device.log

Have a look into GSD log: /var/log/pluto/<GSD LinuxMCE ID>_Generic_Serial_Device.log. You can find here all Ruby errors, connection status and other useful information.

4. There are 6 base functions which you need:
    - Private Method Listing - you may place here all common functionality and use it from the others functions.
    - Process IDLE - method executed each one - two seconds, maybe useful to check a connection between your device and LinuxMCE.
    - Process Incoming Data - called when some data come from your device:
Code: [Select]
recv = conn_.Recv(100,500);recv contains now the data received from the physical device (some switch is OFF). You can parse it to update a status of that switch in LinuxMCE:
Code: [Select]
cmd =, -1001, 1, 2, 48)
cmd.params_[10] = 0
    - Process Receive Command For Child - called when the child device (in your case it's a dimmer of switch) gets some command: ON, OFF or SET LEVEL. Actually, those commands are routed to the parent device (your GSD interface) and it send the commands in desired format to the physical device:
Code: [Select]
cmdId           = cmd.id_                                                         # Command ID: ON, OFF, SET LEVEL
cmdTo           = cmd.devidto_                                                # Device ID in LinuxMCE
devPort         = device_.childdevices_[cmdTo].devdata_[12] # 12 contains a port/channel
childType       = device_.childdevices_[cmdTo].devtemplid_   # Template ID to know type of device: switch or dimmer

case cmdId
      when 192 #192 is ON                       
           command = '<your ON command format>'             
      when 193 #193 is OFF                       
           command = '<your OFF command format>'
      when 184 #184 is Level of dimmer
           command = '<your SET LEVEL command format>'                   


In my case the command includes following parameters: LinuxMCE ID - to update the status in LinuxMCE, Port Number - to know where send actual command, command type - ON, OFF, SET LEVEL, level value for SET LEVEL. Plus, I generate an unique ID for each command to check its status. It might be good idea to push unsuccessful commands into array in the GSD device to run them one again.

    - Process Initialize - called when GSD device is starting. It's good point to initialize common variables and start logging for example:
Code: [Select]
time =
$logFile        ="/var/log/pluto/ICPDAS-" + time.strftime("%Y%m%d%H%M") + ".log", "w")
$bFlush        = true          # flash output buffer
$waitTime    = 4000          # wait time in comunication

I use that log approach just for test purpose. When you go live it's better do not use time stamp.

Also, I use that method to get actual status real child devices and update their statuses  in the LinuxMCE. Because some switch can be OFF manually during GSD device was down.

    - Process Release - called when GSD device is closing. I don't use at all.

Note that you should quick reload router each time when you modify your Ruby code! Because LinuxMCE caches it.

Hope it help you to bring up your GSD device.

i have an AMD Athlon X2 and i managed to install LMCE without any problem.

If I understand correctly you installed only LinucMCE server without additional media directors, right? The problem is not to install LinuxMCE on core duo processor. The problem is to add core duo MD to the one core server. In my case (with Plutohome) the MD couldn't find appropriate kernel (SMP). So, since I got that problem with Plutohome I worry about the same situation with LinuxMCE.

Installation issues / Re: iMon from Soundgraph.
« on: July 17, 2007, 10:45:49 am »
Is iMon supported in LinuxMCE?

Can this driver be used?

Can the VFD be used for anything?

Since Plutohome supports iMON remote LinuxMCE should do the same. But VFD display driver you should manually according to Venky's howto. It works fine with MythTV.

Did you install Kubuntu with the default kernel?  I was under the impression that the default kernel detects whether the PC has SMP capabilities.  This way, you don't need to specify a particular kernel depending on the number of processors/cores.

Not I'm just going to do that. I have Plutohome installation with similar case. When I install server I chose the kernel type manually (there is a choice between usual and SMP kernel). But when I installed MD with core duo the system didn't give me a chance to specify kernel for MD. It detected processor automatically and tried to boot SMP kernel but since the server had usual kernel the installation was crashed. So, I'm worry about similar problem with LinuxMCE. That's why I asked people about success installation of core duo MD with one core server.

Installation issues / One core server and core duo processor MD issue
« on: July 16, 2007, 08:52:27 pm »

I'm going to try LinuxMCE with one core processor server and MD with core duo processor. I couldn't manage to setup core duo MD. It couldn't find SMP kernel.

So, did somebody success install MD with Core Duo processor under LnuxMCE server with one Core processor?

Thanks in advance.


Users / Re: camera and linuxmce for access control and security!
« on: June 08, 2007, 11:20:08 am »
another way (I'm thinking of) is to have doorphone that is FXS compatible (like normal analog phone) and then have ATA or Sipura VOIP adapter, so doorphone makes proper call to Asterisk PBX in LMCE. Quite some time ago I proposed such setup on Pluto forums but it went by....
You normally get "Incoming call screen" on all Pluto Orbiters on call from doorphone, the only addition that should be made is to make incoming call screen that would also show snapshots from related camera and there you go... Talk over plain phone and see it over camera...

Good solution. I'm waiting for delivering of three analog doorphones from USA. So, probably I'll start implement this under Pluto next week.

Users / Avoid sending push messages to the Cisco7970
« on: June 08, 2007, 11:14:41 am »

There is a problem with Cisco7970 Orbiter functionality. The Proxy Orbiter sends push messages to the Cisco7970 to display some messages on its display. It's useful but it doesn't allow to switch phone display OFF if it's not in use. This is not good in case if you have Cisco7970 in your bedroom or Home Theater. So, I suggest to make pushing optional (it can be option on the phone or Orbiter page). In that case Orbiter will work only if somebody press button 'Services' on the phone.

Users / Bug with ignore command OFF in GSD interface
« on: June 08, 2007, 11:05:04 am »
There is a serious bug in the Plutohome GSD interface. Command OFF is ignored 'because it is useless'. Does this bug exist in LinuxMCE?


Pages: 1 ... 66 67 [68]