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 - rocketlynx

Pages: 1 2 [3] 4 5 ... 10
31
Installation issues / Re: Starting Core Only - LinuxMCE 810-Alpha2.36
« on: October 01, 2009, 09:16:44 am »
Thanks Emil.

Regards,
Charles

32
Installation issues / Starting Core Only - LMCE 810-Alpha2.36
« on: October 01, 2009, 07:06:07 am »
For some time now, for many of us, the Core Media Director's Orbiter has been a real "Pain in the you know what" and, so far, no one seems to have a handle on it.

I don't need the Core's Orbiter because my Core sits in a closet, not connected to anything more than a VGA monitor, not needing the Media Director's functions.  I've asked this question before and got no responses.

How do I modify the start procedure to start the Core ONLY!  The Alpha2.36 stated under one of it's updates, (lmce-launch-manager (298,299)) "Fixing startup mode for running core only", so, How do you do it?

Thanks,
Charles

33
Installation issues / Re: Hauppauge BT878 ImpactVCB problem
« on: October 01, 2009, 04:54:21 am »
**************************************************************
http://store.bluecherry.net/Provideo_PV_149_p/pv-149.htm
**************************************************************
Ok. Thanks for the help. I had found this in the wiki. I actually looked for this board and had a little trouble finding it at a reasonable price. I guess I thought that since mine had the same chipset it would work. Anyways, I appreciate the help. Now, where to go to get this?  Do these all support simultaneous video feeds to record from? I assume so.  I'll look into the 143  Thanks!!

**Actually found the answer. Does anyone know where I can get a PV149 for cheap? :)

Ok. Maybe someone knows what type of card that I will be able to buy that will definitely work in linux mce. One that I can plug and play with.
OK, Just because the BT878 (Brooktree) chipset on your board is the same as what Bulecherry uses, it doesn't mean the board's design will use the same drivers successfully.  The following Bluecherry capture boards are Linux compatible and known to work in LinuxMCE:

From the LinuxMCE Wiki...
http://wiki.linuxmce.org/index.php/Bluecherry_PV-143
http://wiki.linuxmce.org/index.php/Bluecherry_PV-149
http://wiki.linuxmce.org/index.php/Bluecherry_PV-155


I have the PV-143 working just fine!  Hope this helps.

Regards,
Charles

34
Installation issues / Re: Hauppauge BT878 ImpactVCB problem
« on: September 30, 2009, 08:26:25 pm »
Ok. Maybe someone knows what type of card that I will be able to buy that will definitely work in linux mce. One that I can plug and play with.
OK, Just because the BT878 (Brooktree) chipset on your board is the same as what Bulecherry uses, it doesn't mean the board's design will use the same drivers successfully.  The following Bluecherry capture boards are Linux compatible and known to work in LinuxMCE:

From the LinuxMCE Wiki...
http://wiki.linuxmce.org/index.php/Bluecherry_PV-143
http://wiki.linuxmce.org/index.php/Bluecherry_PV-149
http://wiki.linuxmce.org/index.php/Bluecherry_PV-155


I have the PV-143 working just fine!  Hope this helps.

Regards,
Charles

35
Installation issues / Re: Still having WebDT366 networking issues
« on: September 28, 2009, 10:03:08 pm »
Hi,

I am still having networking problems with my WebDT 366. It now boots again, but the orbiter is not loaded since there is no proper IP address. I tried all network protection schemes, including "none", but nothing works. Often, the reported access point (using iwconfig) is 'invalid', but sometimes a valid MAC address appears. I'm probably on the right track when that happens, but I have no idea why the network does not get started properly.

A few key points with the configuration:
  • network name is CASE sensitive
  • WEP encryption key is actually key1 on my wireless router, not the pass phrase (is this case sensitive though?)
  • A nokia n800 works on the same wireless network, no problem.

Once the webdt finds a valid access point, what happens then? Somewhere between finding the AP and receiving an IP address, something goes wrong.

There's this great orbiter, sitting in its charger, and I cannot use it.   :(  Does anyone have an idea how to get this going, or how to prove defective hardware if such is the case?

Cheers

Mark


Have you gone to LinuxMCE Admin-->Devices-->Orbiters-->Standard Roaming Orbiters-->(the one for your WebDT 366) and looked at the advanced tab to see if your WebDT 366's correct MAC is entered and saved there?

I have not found the WEP to be case sensitive, It's hexadecimal, 0-9 & a-f, and have entered it in upper or lower case and it works.

If you want, email me at my email in my profile and I'll send you a image of my WebDT 366's LinuxMCE setup to compare.

Good Luck,
Charles

36
Users / Re: WAYNE-DALTON Z-WAVE® THERMOSTAT
« on: September 23, 2009, 09:34:00 pm »
I've added temp readouts recently, the proper events should be sent now. Did anybody test the latest version on 0810?

Hari, I've got one of my Wayne Daltons set to Celsius and bound to my Z-Wave mesh and LinuxMCE recognizes it properly as a standard thermostat.  I've tested the My Scenario buttons and they all command the thermostat properly and it responds as requested.  However, the scenario buttons for +1 and -1 degree fail and both set the thermostat immediatley to 2.0C when pressed.  

Also, the Climate Floorplan never shows a change, it shows the thermostat at On/Cool (25) no matter what the setting or the thermostat is really set for or currently reading.  Is the floorplan display and functions still not finished?

Charles

Charles,
I know that Hari told me at one point that only absolute values have been programmed at this point ie: 23, 42, 12. relative values have not yet been implemented, +1, -1 etc.

Donpaul,
Hari has done some work on the zwave driver for the thermostat and it can be turned on/off, switched between heat/cool, and you can set it to an absolute temperature (for temp adjustment the thermostat must be in Celsius mode, and the temp sent must be in Celsius). Hari has no desire to do the work to convert from C to F as he is in Europe and doesn't need it. SO, long story short... the ground work has been laid and currently the thermostat is partially functional, all we need now is someone with some programming experience to step up and tie up the loose ends. Unfortunately no one as of yet has been able to tackle this project.
-Krys

OK Guys, Thanks for all of the responses.  I've got some programming experience so I'll be able to help as soon as I get time from my real job to set up my Development system.  I'm already using my Wayne-Daltons in the Fahrenheit mode, albeit, a little crippled.  I've got them set in the "F", Fahrenheit modes and I can send them Celsius commands and they respond with the appropriate Fahrenheit temp.  This is not the greatest way of doing things but it keeps all of the household from going "Bonkers".  

Now, for example if I want the downstairs thermostat to go to around 80F degrees at night, because all of our bedrooms are upstairs, I set up a timed event for the downstairs thermostat at 11:00pm, with a Set-Temperature of 27.  When the command goes out, the thermostat immediately responds and changes the target temp to "81F which is a rounded equivalent from 27.22C the equal of 81F".  

Since there is no exact conversion from two-digit Celsius  to two-digit Fahrenheit, you cannot get the exact temp you might want with this work-around.

The unit and LinuxMCE will round it to the closest Fahrenheit setting, hence, 25C = 77F, 26C gets you 79F and 27C responds with 81F on the thermostat.  Theoretically, to set 78 degrees Fahrenheit, you would need to send the command of 25.55C but this gets ignored and rounded down to 25C and the result is 77F.  

This results in many desired target temps being unachievable but this is only a temporary fix and I admit, this is a very awkward way of things behaving but it lets me use the Wayne-Dalton units temporarily in the Fahrenheit mode.

Also, since the +1 and -1 temp sets do not work in either Celsius or Fahrenheit modes, I have just created and array of many "My Scenarios" Orbiter buttons with many different temp settings for both my Upstairs and Downstairs Wayne-Dalton Thermostats.

This gets me by and I will hopefully be set up and working on a final fix with you guys by this weekend.  When I got my Thermoststs, I guess I thought the Orbiter templates read out the correct current temperatures when in the Celsius mode but when I saw that that also wasn't completed, I said, screw it, I'll stay in the crippled, Fahrenheit mode until we get it right for all who need it in either mode!

Charles

37
Installation issues / Re: Double orbiter and other strange things - Try this
« on: September 19, 2009, 08:05:23 am »
Hello,

whoever is experiencing the double orbiter launch on the core/hybrid, please  put the following lines on top of your /etc/init.d/core.sh

Code: [Select]
#!/bin/bash
exit 0

and let me know, if that helps.

Guys, hold off on the bashing because I'm still fairly new to Linux and LinuxMCE but I don't have a file specifically name core.sh in my /etc/init.d directory.  I have a text file named core without the .sh extension.  Here is the code:

Code: [Select]
#!/bin/sh

case "$1" in
start)
/usr/pluto/bin/startCore.sh
;;
stop)

/usr/pluto/bin/StopCoreServices.sh
;;

*)
echo "Usage: /etc/init.d/core {start|stop}"
exit 1
;;
esac

exit 0

I modified this file, "core", with the code exit 0 at the top, rebooted the Core and got the same results as before.

Is this the file you were referring to or am I missing a file exactly named core.sh?  

Charles

38
Installation issues / Re: Double orbiter and other strange things - Try this
« on: September 18, 2009, 03:44:25 am »
it will just stop the core.sh script from running at startup

if it doesn't help you, you can just remove those lines again and reboot, it won't effect anything else...
Thanks, will do.

39
Installation issues / Re: Double orbiter and other strange things - Try this
« on: September 17, 2009, 06:07:17 pm »
Hello,

whoever is experiencing the double orbiter launch on the core/hybrid, please  put the following lines on top of your /etc/init.d/core.sh

Code: [Select]
#!/bin/bash
exit 0

and let me know, if that helps.

So far, I've been able to work around this problem without re-installing my core.  Can you be more specific about what this does because I don't want to just seat-of-the-pants experiment on my working system.  I don't want to attempt anything that my not allow my LMCE Core to at least boot up if this doesn't correct the orbiter problem. 

As usual, thanks to you and all for the LinuxMCE Project!

Charles

40
:D
Hey all,

Been a while since I have posted. But after this latest update, I needed to compare notes.....

My DirecTV boxes are controlled by the core with a USB-UIRT, and they are hooked into a PVR 500 and daughter card. Now the issue I am having is this:

I lose the orbiter on the core.

Hi Seth: I know you are having trouble with your Core's Orbiter, many of us are, but I only quoted a portion of your comment as I am interested in how you are using your DirecTV receivers throught LMCE.  I have several Dish Network Sat Receivers and would like to intergrate them directly into my core so I was wondering how you have your DirecTV sats hooked to a PVR-950 and available to the system (MDs)?

I don't want to Hi-Jack this threads purpose so we can do this on another topic or you can email me at my email address in my profile.

Thanks again and hang in there on the Core Orbiter's problem.  I just was astounded that last evening, my Core's Orbiter began working properly and I even checked it again this morning and it still was functioning as it should.  I'm thinking, if I reboot, the old evil 2 orbiters will appear again on the Core so I'm hoping I don't have to for a while.

Best Regards,
Charles

41
Maybe this is the answer we've been looking for...

I am thinking that it will be very similar to the 20P combined with the ICM.  

I'm pretty sure the 21iP still needs the vista icm to work with lmce. From what I can tell, its ip capabilities were designed for alarmnet integration only. Honeywell phone support is pretty good - give them a call and see what they say.

:Matt

This is from the Vista-21ip Installation Manual:

Code: [Select]
∗29 Menu Mode for IP and GSM Module Programming
This mode is for programming the Internet connection (IP) and optional GSM Module configuration,
collectively referred to as the Internal Device.
NOTE: The Internal Device is automatically set to address 3 and cannot be changed.
The following section describes the programming of the Internal Device using an alpha keypad.
Alternatively, these options can be programmed via the AlarmNet Direct website. After programming is
complete, the control must be registered with AlarmNet via the Internet connection. Refer to the
Registration with AlarmNet section for procedures.
IMPORTANT: The use of the IP connection or the VISTA-GSM module requires an AlarmNet–I account.
Please obtain the account information from the central station prior to programming this module.

Note the following from above:
IMPORTANT: The use of the IP connection or the VISTA-GSM module requires an AlarmNet–I account.
Please obtain the account information from the central station prior to programming this module.


Regards,
Charles

42
Installation issues / Re: Resolved - This orbiter will be closed message.
« on: September 15, 2009, 06:39:53 pm »
as an aside, i also go all the way back to the 8-bit micro space, my first personal computer being a TRS-80 Model I (although most of my code was for 6502 based micros, mostly the Atari 800)

-Thom

I understand your pain and agree, It's Alpha!

Thom, I'm living with this for now rather than reinstalling because I don't use my core as an MD. 

Can I stop/kill the MD on the Core/Hybrid after the core reboots which will also of course, kill the orbiter, with a command from the terminal?

Thanks,
Charles

P.S. Check your spam filter for a personal email I sent you about some plans I have for the WebDT 366 Orbiter.

43
Users / Re: WAYNE-DALTON Z-WAVE® THERMOSTAT
« on: September 14, 2009, 11:29:33 pm »
I've added temp readouts recently, the proper events should be sent now. Did anybody test the latest version on 0810?

Hari, I've got one of my Wayne Daltons set to Celsius and bound to my Z-Wave mesh and LinuxMCE recognizes it properly as a standard thermostat.  I've tested the My Scenario buttons and they all command the thermostat properly and it responds as requested.  However, the scenario buttons for +1 and -1 degree fail and both set the thermostat immediatley to 2.0C when pressed. 

Also, the Climate Floorplan never shows a change, it shows the thermostat at On/Cool (25) no matter what the setting or the thermostat is really set for or currently reading.  Is the floorplan display and functions still not finished?

Charles

44
Users / Re: WAYNE-DALTON Z-WAVE® THERMOSTAT
« on: September 14, 2009, 07:27:11 pm »
ok, cool, get your env prepared. I'm just adding a "unit" parameter to the set temp command. Merkur offered help with extending the web admin:
18:20 < merkur2k> im sure i can handle the web admin side, i just cant test it

br, Hari

Thanks, hopefully by tomorrow, my test core will be up and running.  In the mean time, I'll switch my 2 Thermostats on my working system to Celsius to test your added temp readouts.  Also, as I said before, I'll be glad to open my system up to a developer to dig into if they so desire, especially if I get into trouble.
 
Thanks, Charles

45
Users / Re: WAYNE-DALTON Z-WAVE® THERMOSTAT
« on: September 14, 2009, 06:51:38 pm »
I've added temp readouts recently, the proper events should be sent now. Did anybody test the latest version on 0810?

Hari, although I need Fahrenheit, I'll set my temps for Celsius and rebind them today and check it out.

Charles
don't get me wrong, no offense, but everybody uses the metric system.. besides.. you get it. So I don't really feel like adding fahrenheit support, I have no use for it. I will assist by doing the z-wave dce device side. But somebody needs to extend the DCE command set temperature, the web admin, the orbiter and add a system wide option for it.

br, Hari
No offense taken Hari, and thanks for getting back to me.  Yes you are correct, I do get it.  But no one else in the house does without confusion.  Here in the US, and quite possibly we're behind the rest of the world, everybody grew up referencing temperatures using the Fahrenheit table.  So the "Celsius" world for most folks that I know is annoying because there exists constant translation, it doesn’t happen naturally for them.

I've done programming in the past so I don't mind getting my hands dirty if need be.  I've been preparing to set up a development core for LinuxMCE anyway and this will just give me the reason to not put it off any longer.

Again, I appreciate all that you and many others have contributed to the LinuxMCE project.  It's a wonderful and feature rich product.

Best Regards,
Charles

Pages: 1 2 [3] 4 5 ... 10