Messages

16

Users / Re: Where is some info on how to connect a windows computer to the network?

« on: October 30, 2008, 12:13:27 am »

William

I assume you have a standard set up - ie 2 NICs, an internal and external network?

In which case, you just plug the XP machine into the internal network, it will get an IP and then you have full access to the Internet through the core machine. What is not working with this?

Yes I have the 2 nic setup but I haven't seen the hybrid recognize it yet even after reloading the router.

17

Users / Where is some info on how to connect a windows computer to the network?

« on: October 30, 2008, 12:03:32 am »

I need to connect a windows xp computer to the linuxmce network for internet access. I have been looking at the wiki and the forums but can't find anything. Any help would be apprecaited.
Thanks

18

Users / Re: Installing insteon and X10

« on: October 07, 2008, 02:42:51 am »

Anyone have any luck getting the template to work correctly? X10?
I will be trying this again this weekend and I post the results.
Thanks

19

Installation issues / Re: Media Director question - VGA monitor as display instead of TV out?

« on: October 07, 2008, 02:23:32 am »

You can use a VGA monitor but I don't think the touchscreen option will work.
Thanks

20

Users / Re: Does anyone use insteon and X10?

« on: September 21, 2008, 01:49:28 am »

Does anyone just use Insteon? I could sure use your help! Please see post:

http://forum.linuxmce.org/index.php?topic=5931.0

Thanks

21

Users / Re: Core/Hybrid Locking up: Possible Solution?

« on: September 21, 2008, 01:46:24 am »

Post your computer hardware!

22

Users / Re: Up and running with minor issues

« on: September 21, 2008, 01:44:47 am »

To start with your computer is more of a MD than core or hybrid.


Don't seem to get MythTV running for some reason. The PVR-150 Hauppage is recognised in the admin website. It starts up and after that the screen turns black. When using the Menu button on the remote, the text in the upper bar says: not available. - Go to the KDE Desktop and setup Mythtv.

Hope this helps.

23

Users / Re: Getting my feet wet!

« on: September 21, 2008, 01:39:58 am »

You can go look at the example setups on the wiki that have worked for others but to comment on your proposal:

# 1.8GHz Intel Celeron Processor w/ 800MHz FSB & 512K L2 Cache - Upgradeable up to Core 2 Duo - at least a core 2 duo

# 512MB Kingston DDR2 RAM - Upgradeable - 1 Gb or higher

# 10/100 Integrated LAN - 1Gb for a core

  * VGA:
          o Integrated Graphics, up to 256MB shared memory
          o Support max. resolution to 1920 x 1440 (@75Hz) - Nvidia 6200 or higher

Hope this helps.

24

Users / Re: Installing insteon and X10

« on: September 21, 2008, 01:34:48 am »

I got a few Insteon light switches 2466DW. I went back through and deleted my X10 light switches and changed the "COM Port on PC" to pciXXXXX. I the follow log posted this:

 (***):receive timeout=3
(***):Third attempt, Failing Command!
(***):in RemoveCurrentCommand
(***):Current Command:{"Parameter1"=>"A2", "Parameter2"=>"00", "Parameter3"=>"00", "Parameter4"=>"0F", "Command"=>"InsStdMsg", "Parameter5"=>"10", "Parameter6"=>"00"}
(***):ID=A2.00.00
(***):Removing A2.00.00 from child database
(***):Removing from plm
(***):DEBUG:45 32 30 31 41 32 30 30 30 30 30 31 30 31 46 46 Length:16
(***):Found Record, Deleting
(***):{"Parameter1"=>"80", "Parameter2"=>"E2", "Parameter3"=>"01", "Parameter4"=>"A2", "Command"=>"MngLnk", "Parameter5"=>"00", "Parameter6"=>"00", "Parameter7"=>"01", "Parameter8"=>"01", "Parameter9"=>"FF"}
(***):Command Completed.
(***):SndIns:Queue:1
(***):out:02 6F 80 E2 01 A2 00 00 01 01 FF Length:11
(***):IN:02 6F 80 E2 01 A2 00 00 01 01 FF 06 Length:12
(***):MngLnk => ACK
(***):Command Completed.
(***):Queue Empty.
(***):RERUN=TRUE, RESTARTING
(***):Queue Empty.
(***):RERUN Not needed
(***):Reporting Child Devices
(***):

Then I got this on the follow log:

 (***):SndIns:Queue:1
(***):out:02 69 Length:2
(***):IN:02 69 15 Length:3
(***):GetLnk NACKED
(***):Command Completed.
(***):Entered CheckChildRecordsinPLM
(***):Queue Empty.
(***):RERUN Not needed
(***):Reporting Child Devices
(***):

Then to double check I changed the "COM Port on PC" back to /dev/ttyS0 and I got this same as before, wasn't communicating. I then changed the "COM Port on PC" back to the pci setting and I get this on the follow log:

 (***):Command Stalled!  resetting and retrying
(***):Current Command:0
(***):SndIns:Queue:3
(***):out:02 62 00 00 00 0F 19 00 Length:8
(***):IN:02 62 00 00 00 0F 19 00 06 Length:9
(***):receive timeout=1
(***):receive timeout=2
(***):receive timeout=3
(***):Command Stalled!  resetting and retrying
(***):Current Command:25
(***):SndIns:Queue:3
(***):out:02 62 00 00 00 0F 19 00 Length:8
(***):IN:02 62 00 00 00 0F 19 00 06 Length:9

JQE what do you have in your setup for the "COM Port on PC"? Also please post as much info about how you got Insteon to work.
Would it be possible to link up in the forum Linuxmce, and go over the settings?
Thanks

25

Developers / Re: How's Insteon working?

« on: September 15, 2008, 06:06:14 pm »

I'm having trouble getting the 2412s to communicate with a X10 light switch (maybe ws467). See more detail at this post:
http://forum.linuxmce.org/index.php?topic=5931.0

Thanks

26

Users / Does anyone use insteon and X10?

« on: September 13, 2008, 10:07:06 pm »

If you do please see this topic:

http://forum.linuxmce.org/index.php?topic=5931.0

We need help!
Thanks

27

Marketplace / Re: Fiire Chief Remote + 3 USB Dongles for sale

« on: September 13, 2008, 02:07:08 am »

I'll buy all for $100 + shipping.
Thanks

28

Users / Re: Installing insteon and X10

« on: September 12, 2008, 03:09:06 am »

I just tried something....I unplugged the AC from the PLM and the follow log still keeps giving me the same data as I posted earlier....is this normal? Or is this a possible problem of communication with the X10 light switch?
Thanks

29

Users / Re: Installing insteon and X10

« on: September 12, 2008, 02:51:07 am »

I pressed and held the button on the PLM and the led stayed on solid. I also used and extension cord connected on the same circuit and I get the same result:

(***):Current Command:0
(***):SndIns:Queue:18
(***):out:02 6B 40 Length:3
(***):receive timeout=1
05   09/11/08 20:36:51.036      GSDMessageTranslator isCmdImplemented = false <0x42003950>
05   09/11/08 20:36:51.038      #### Pre-Process Queue = 1 <0x42003950>
05   09/11/08 20:36:51.041      _QueueProc Pre - 193 : 0 <0x40800950>
05   09/11/08 20:36:51.041      GSD-Sleep Pre 193 : 0 <0x40800950>
05   09/11/08 20:36:51.041      Process Queue = 1 <0x40800950>
(***):------dce--- cmdID:193, cmdFrom:0, cmdTo:41, cmdType:1, Priority:1
(***):------dce--- X10 DEVICE!!!
(***):DeviceID=A2
(***):X10 Byte1:6E
(***):X-----------SndIns: Waiting for response to:SetCfg
(***):X-----------SndIns: Current Queue Length:20
(***):From:41
(***):current State:100
(***):Wanted State:0
(***):ReportStatus: device:41 Status:0
05   09/11/08 20:36:51.188      GSDMessageTranslator isCmdImplemented = false <0x42003950>
05   09/11/08 20:36:51.189      #### Pre-Process Queue = 1 <0x42003950>
05   09/11/08 20:36:51.189      GSD-Sleep Post 193 : 0 <0x40800950>
05   09/11/08 20:36:51.189      _QueueProc Post - 193 : 0 <0x40800950>
05   09/11/08 20:36:51.189      _QueueProc Pre - 193 : 0 <0x40800950>
05   09/11/08 20:36:51.189      GSD-Sleep Pre 193 : 0 <0x40800950>
05   09/11/08 20:36:51.190      Process Queue = 1 <0x40800950>
(***):------dce--- cmdID:193, cmdFrom:41, cmdTo:41, cmdType:1, Priority:1
(***):Detected Command sent to Self!
05   09/11/08 20:36:51.193      GSD-Sleep Post 193 : 0 <0x40800950>
05   09/11/08 20:36:51.193      _QueueProc Post - 193 : 0 <0x40800950>
(***):receive timeout=2
(***):receive timeout=1
(***):receive timeout=2
(***):receive timeout=3
(***):Command Stalled!  resetting and retrying
(***):Current Command:0
(***):SndIns:Queue:20
(***):out:02 6B 40 Length:3
(***):receive timeout=1
(***):receive timeout=2
(***):receive timeout=3
(***):Command Stalled!  resetting and retrying

Did everyone follow this step in the setup instructions?

 Adding a Code Group

        * Click 'Edit Ruby Codes' ( loads Edit Ruby Codes Popup)

            * In the field to the LEFT of 'Create new group', type in 'Insteon PLM'
            * click 'Create new group'

b4 is broken have to run sql manually to add new group close 'Edit Ruby codes' page. Look at 'Edit Device Template' popup page and note Device_Category and Manufacturer you will need to set them in sql code below

INSERT INTO InfraredGroup (FK_DeviceCategory,FK_Manufacturer,Description,FK_CommMethod,psc_id,psc_batch,psc_user,psc_frozen,psc_mod,psc_restrict) VALUES (Device_Category,Manufacturer,"Insteon PLM",2,NULL,NULL,NULL,NULL,NULL,NULL);

run this sql and reload 'Edit Ruby codes' page and you should see 'Insteon PLM' in 'Uses Group/Codeset'

            * If the 'Uses Group/Codeset' does not change to 'Insteon PLM', repeat the previous 2 steps again.
            * Once the 'Uses Group/Codeset' says 'Insteon PLM' Check 'Discoverable Interfaces'
            * Check 'Ruby Internal Commands'
            * click Update

When I did this:

            * In the field to the LEFT of 'Create new group', type in 'Insteon PLM'
            * click 'Create new group

The 'Uses Group/Codeset' said 'Insteon PLM' and I didn't edit the sql. Is this ok?
Thanks

30

Users / Re: Installing insteon and X10

« on: September 11, 2008, 02:52:20 pm »

what kind of switch are you using?

X10 WS467 ( I think)

Did you link at least one device to the PLM?

Yes just the x10 switch.

Are the PLM and the devices on the same phase of your electrical circuit?

Yes on the same circuit.

I'm using PLM 2412S and 3 insteon wall switches.

in one of my attempts I had a similar problem.
First I had no linked the plm and the devises. Non of the switches were recognized by the system.
Later when I link them (push the set button on the plm for 10 sec, led should blink, then push the top switch button until the PLM stop blinking) they were recognized by the system but every time I restart the router they disappear. The problem is that the first time the driver boots it looks for devices on the internal plm data base, when it boots again it tries to find the devises by ping them or something similar to a ping, if they are not found it tries to delete them from the data base. In my case I think it was caused by the poor communication between the PLM and the devises I solved by changing the electrical outlet that I was using (had to use a extension cord to put it as far as possible from the computer)
Once I chage the plm outlet the

(***):receive timeout=1
(***):receive timeout=2
(***):receive timeout=3
(***):Command Stalled!  resetting and retrying

desappear from the logs and the devices stay on the system

hope this helps you.
Let me know if you have any questions.

Cesar

Ok...I didn't realize that the plm button had to be depressed. Also I will try the extention cord.
Also I'm using a serial to usb convertor. Did anyone change the setup for the plm to accommodate this? or does it matter?
Thanks