From: Troy C. <tr...@ca...> - 2007-02-27 15:18:07
|
Ok, I am actively troubleshooting this problem, but I thought I would post to see if anyone can give any pointers in the meantime. I finally bit the bullet and upgraded my system from its semi-frozen post 102 SVN state to the latest SVN snapshot. I have two main issues, but the first seems to have resolved itself (MH was not seeing my W800 signals, but that seems to be working now). The BIG problem I am having is with my DSC5401. It just will not talk to Misterhouse after the upgrade (well, it did work one time, but that was it). Starting up I see the following (edited superfluous lines): Loading other modules Starting setup - creating DSC5401 port on /dev/ttyS3 - creating W800 port on /dev/ttyS2 - creating Lynx10PLC port on /dev/ttyS0 Debug level: /dev/ttyS0 = 0 at /pub/misterhouse/bin/../lib/Lynx10PLC.pm line 291 Done with setup 02/27/07 09:57:29 AM Calling Serial_match_add_hook 02/27/07 09:57:29 AM Starting DSC 5401 computer interface module 02/27/07 09:57:29 AM Sending to DSC panel Poll (000) with argument () 02/27/07 09:57:29 AM Sending to DSC panel StatusReport (001) with argument () 02/27/07 09:57:29 AM Sending to DSC panel VerboseArmingControl (050) with argument (1) 02/27/07 09:57:29 AM Sending to DSC panel TimeBroadcastControl (056) with argument (1) Good code saved 02/27/07 09:57:32 AM Command Error : Unknown 02/27/07 09:57:32 AM System Error : RS-232 Receive Buffer Overrun 02/27/07 09:57:32 AM Setting time on DSC panel to 0957022707 02/27/07 09:57:32 AM Sending to DSC panel SetDateTime (010) with argument (0957022707) ----- After this I would normally see the a zone status updated message from the DSC logging, plus I never get any updates from the system about zones opening and closing, nor do I get arm/disarm events. I am concerned with the "Command Error" and "System Errors" that are occurring during the startup (they come from the DSC5401 library code). I have not seen those before upgrading. I do not remember making any kernel changes or serial port configuration changes in the past few months. As a final bit, here's my DSC5401.2007_02.log file from startup: Tue 02/27/07 10:03:17 ========= DSC5401.pm Initialized ========= Tue 02/27/07 10:03:18 >>> Sending to DSC panel Poll (000) with argument () [00090] Tue 02/27/07 10:03:18 >>> Sending to DSC panel StatusReport (001) with argument () [00191] Tue 02/27/07 10:03:19 >>> Sending to DSC panel VerboseArmingControl (050) with argument (1) [0501C6] Tue 02/27/07 10:03:19 >>> Sending to DSC panel TimeBroadcastControl (056) with argument (1) [0561CC] Tue 02/27/07 10:03:19 501 Command Error Unknown Tue 02/27/07 10:03:19 500 Command Acknowledge StatusReport Tue 02/27/07 10:03:19 502 System Error RS-232 Receive Buffer Overrun Tue 02/27/07 10:03:19 610 Zone Restored zone Front Door (001) Tue 02/27/07 10:03:19 610 Zone Restored zone Media Room Windows (002) Tue 02/27/07 10:03:19 610 Zone Restored zone Family Room Windows (003) Tue 02/27/07 10:03:19 610 Zone Restored zone Garage Entry Door (004) Tue 02/27/07 10:03:19 610 Zone Restored zone Kitchen Door or Windows (005) Tue 02/27/07 10:03:19 610 Zone Restored zone Music Room Windows (006) Tue 02/27/07 10:03:19 610 Zone Restored zone Basement Door or Windows (007) Tue 02/27/07 10:03:19 610 Zone Restored zone Fire Alarm (008) Tue 02/27/07 10:03:19 610 Zone Restored zone 009 (009) Tue 02/27/07 10:03:19 610 Zone Restored zone 010 (010) Tue 02/27/07 10:03:19 610 Zone Restored zone 011 (011) Tue 02/27/07 10:03:19 610 Zone Restored zone 012 (012) Tue 02/27/07 10:03:19 610 Zone Restored zone 013 (013) Tue 02/27/07 10:03:19 610 Zone Restored zone 014 (014) Tue 02/27/07 10:03:19 610 Zone Restored zone 015 (015) Tue 02/27/07 10:03:19 610 Zone Restored zone 016 (016) Tue 02/27/07 10:03:19 610 Zone Restored zone 017 (017) Tue 02/27/07 10:03:19 610 Zone Restored zone 018 (018) Tue 02/27/07 10:03:19 610 Zone Restored zone 019 (019) Tue 02/27/07 10:03:19 610 Zone Restored zone 020 (020) Tue 02/27/07 10:03:19 610 Zone Restored zone 021 (021) Tue 02/27/07 10:03:19 610 Zone Restored zone 022 (022) Tue 02/27/07 10:03:20 Setting time on DSC panel to 1003022707 Tue 02/27/07 10:03:20 >>> Sending to DSC panel SetDateTime (010) with argument (1003022707) [010100302270787] Troy |
From: Troy C. <tr...@ca...> - 2007-02-27 15:25:53
|
On Tuesday 27 February 2007 10:17:40 am Troy Carpenter wrote: > Ok, I am actively troubleshooting this problem, but I thought I would post > to see if anyone can give any pointers in the meantime. > > I finally bit the bullet and upgraded my system from its semi-frozen post > 102 SVN state to the latest SVN snapshot. I have two main issues, but the > first seems to have resolved itself (MH was not seeing my W800 signals, but > that seems to be working now). > > The BIG problem I am having is with my DSC5401. It just will not talk to > Misterhouse after the upgrade (well, it did work one time, but that was > it). Starting up I see the following (edited superfluous lines): > > Loading other modules > Starting setup > - creating DSC5401 port on /dev/ttyS3 > - creating W800 port on /dev/ttyS2 > - creating Lynx10PLC port on /dev/ttyS0 > Debug level: /dev/ttyS0 = 0 at /pub/misterhouse/bin/../lib/Lynx10PLC.pm > line 291 > > Done with setup > > 02/27/07 09:57:29 AM Calling Serial_match_add_hook > 02/27/07 09:57:29 AM Starting DSC 5401 computer interface module > 02/27/07 09:57:29 AM Sending to DSC panel Poll (000) with argument () > 02/27/07 09:57:29 AM Sending to DSC panel StatusReport (001) with argument > () 02/27/07 09:57:29 AM Sending to DSC panel VerboseArmingControl (050) > with argument (1) > 02/27/07 09:57:29 AM Sending to DSC panel TimeBroadcastControl (056) with > argument (1) > Good code saved > 02/27/07 09:57:32 AM Command Error : Unknown > 02/27/07 09:57:32 AM System Error : RS-232 Receive Buffer Overrun > 02/27/07 09:57:32 AM Setting time on DSC panel to 0957022707 > 02/27/07 09:57:32 AM Sending to DSC panel SetDateTime (010) with argument > (0957022707) > ----- > > After this I would normally see the a zone status updated message from the > DSC logging, plus I never get any updates from the system about zones > opening and closing, nor do I get arm/disarm events. > > I am concerned with the "Command Error" and "System Errors" that are > occurring during the startup (they come from the DSC5401 library code). I > have not seen those before upgrading. > > I do not remember making any kernel changes or serial port configuration > changes in the past few months. > > As a final bit, here's my DSC5401.2007_02.log file from startup: > Tue 02/27/07 10:03:17 ========= DSC5401.pm Initialized ========= > Tue 02/27/07 10:03:18 >>> Sending to DSC panel Poll (000) with argument () > [00090] > Tue 02/27/07 10:03:18 >>> Sending to DSC panel StatusReport (001) with > argument () [00191] > Tue 02/27/07 10:03:19 >>> Sending to DSC panel VerboseArmingControl (050) > with argument (1) [0501C6] > Tue 02/27/07 10:03:19 >>> Sending to DSC panel TimeBroadcastControl (056) > with argument (1) [0561CC] > Tue 02/27/07 10:03:19 501 Command Error Unknown > Tue 02/27/07 10:03:19 500 Command Acknowledge StatusReport > Tue 02/27/07 10:03:19 502 System Error RS-232 Receive Buffer Overrun > Tue 02/27/07 10:03:19 610 Zone Restored zone Front Door (001) > Tue 02/27/07 10:03:19 610 Zone Restored zone Media Room Windows (002) > Tue 02/27/07 10:03:19 610 Zone Restored zone Family Room Windows (003) > Tue 02/27/07 10:03:19 610 Zone Restored zone Garage Entry Door (004) > Tue 02/27/07 10:03:19 610 Zone Restored zone Kitchen Door or Windows > (005) Tue 02/27/07 10:03:19 610 Zone Restored zone Music Room Windows > (006) Tue 02/27/07 10:03:19 610 Zone Restored zone Basement Door or > Windows (007) Tue 02/27/07 10:03:19 610 Zone Restored zone Fire Alarm > (008) > Tue 02/27/07 10:03:19 610 Zone Restored zone 009 (009) > Tue 02/27/07 10:03:19 610 Zone Restored zone 010 (010) > Tue 02/27/07 10:03:19 610 Zone Restored zone 011 (011) > Tue 02/27/07 10:03:19 610 Zone Restored zone 012 (012) > Tue 02/27/07 10:03:19 610 Zone Restored zone 013 (013) > Tue 02/27/07 10:03:19 610 Zone Restored zone 014 (014) > Tue 02/27/07 10:03:19 610 Zone Restored zone 015 (015) > Tue 02/27/07 10:03:19 610 Zone Restored zone 016 (016) > Tue 02/27/07 10:03:19 610 Zone Restored zone 017 (017) > Tue 02/27/07 10:03:19 610 Zone Restored zone 018 (018) > Tue 02/27/07 10:03:19 610 Zone Restored zone 019 (019) > Tue 02/27/07 10:03:19 610 Zone Restored zone 020 (020) > Tue 02/27/07 10:03:19 610 Zone Restored zone 021 (021) > Tue 02/27/07 10:03:19 610 Zone Restored zone 022 (022) > Tue 02/27/07 10:03:20 Setting time on DSC panel to 1003022707 > Tue 02/27/07 10:03:20 >>> Sending to DSC panel > SetDateTime (010) with argument (1003022707) [010100302270787] > > Troy Also, when I turn on serial debugging, I see the following continually: 50202029 --- serial name=DSC5401 type=raw data2= --- serial name=DSC5401 type=raw data2= 50196 --- serial name=DSC5401 type=raw data2= --- serial name=DSC5401 type=raw data2= 50196 --- serial name=DSC5401 type=raw data2= --- serial name=DSC5401 type=raw data2= 50202029 |
From: Matthew W. <mat...@us...> - 2007-02-27 17:50:25
|
Troy Carpenter wrote: > Ok, I am actively troubleshooting this problem, but I thought I would post to > see if anyone can give any pointers in the meantime. Try setting debug=DSC5401 to get more debug info. Also, try changing the select timeouts in &DSC5401::new from 250ms to 1000ms. Matt |
From: Troy C. <tr...@ca...> - 2007-02-27 18:48:37
|
Matthew Williams wrote: > Troy Carpenter wrote: > >> Ok, I am actively troubleshooting this problem, but I thought I would post to >> see if anyone can give any pointers in the meantime. >> > > > Try setting debug=DSC5401 to get more debug info. Also, try changing the > select timeouts in &DSC5401::new from 250ms to 1000ms. > 02/27/07 01:34:54 PM DSC5401:check_for_data DscString=502 002 29 02/27/07 01:34:54 PM DSC5401:IsChecksumOK DscString=[50200229] CksValue=[29] CksCalc=[29] 02/27/07 01:34:54 PM System Error : RS-232 Receive Buffer Overflow 02/27/07 01:34:54 PM DSC5401:check_for_data DscString=500 001 26 02/27/07 01:34:54 PM DSC5401:IsChecksumOK DscString=[50000126] CksValue=[26] CksCalc=[26] 02/27/07 01:34:54 PM DSC5401:check_for_data DscString=502 001 28 02/27/07 01:34:54 PM DSC5401:IsChecksumOK DscString=[50200128] CksValue=[28] CksCalc=[28] 02/27/07 01:34:54 PM System Error : RS-232 Receive Buffer Overrun 02/27/07 01:34:54 PM DSC5401:check_for_data DscString=610 001 28 02/27/07 01:34:54 PM DSC5401:IsChecksumOK DscString=[61000128] CksValue=[28] CksCalc=[28] 02/27/07 01:34:54 PM DSC5401:check_for_data DscString=610 002 29 02/27/07 01:34:54 PM DSC5401:IsChecksumOK DscString=[61000229] CksValue=[29] CksCalc=[29] 02/27/07 01:34:54 PM DSC5401:check_for_data DscString=610 003 2A 02/27/07 01:34:54 PM DSC5401:IsChecksumOK DscString=[6100032A] CksValue=[2A] CksCalc=[2A] 02/27/07 01:34:54 PM DSC5401:check_for_data DscString=610 004 2B 02/27/07 01:34:54 PM DSC5401:IsChecksumOK DscString=[6100042B] CksValue=[2B] CksCalc=[2B] 02/27/07 01:34:54 PM DSC5401:check_for_data DscString=610 005 2C 02/27/07 01:34:54 PM DSC5401:IsChecksumOK DscString=[6100052C] CksValue=[2C] CksCalc=[2C] 02/27/07 01:34:54 PM DSC5401:check_for_data DscString=610 006 2D 02/27/07 01:34:54 PM DSC5401:IsChecksumOK DscString=[6100062D] CksValue=[2D] CksCalc=[2D] 02/27/07 01:34:54 PM DSC5401:check_for_data DscString=610 007 2E 02/27/07 01:34:54 PM DSC5401:IsChecksumOK DscString=[6100072E] CksValue=[2E] CksCalc=[2E] 02/27/07 01:34:54 PM DSC5401:check_for_data DscString=610 008 2F 02/27/07 01:34:54 PM DSC5401:IsChecksumOK DscString=[6100082F] CksValue=[2F] CksCalc=[2F] 02/27/07 01:34:54 PM DSC5401:check_for_data DscString=610 009 30 02/27/07 01:34:54 PM DSC5401:IsChecksumOK DscString=[61000930] CksValue=[30] CksCalc=[30] 02/27/07 01:34:54 PM DSC5401:check_for_data DscString=610 010 28 02/27/07 01:34:54 PM DSC5401:IsChecksumOK DscString=[61001028] CksValue=[28] CksCalc=[28] 02/27/07 01:34:54 PM DSC5401:check_for_data DscString=610 011 29 02/27/07 01:34:54 PM DSC5401:IsChecksumOK DscString=[61001129] CksValue=[29] CksCalc=[29] 02/27/07 01:34:54 PM DSC5401:check_for_data DscString=610 012 2A 02/27/07 01:34:54 PM DSC5401:IsChecksumOK DscString=[6100122A] CksValue=[2A] CksCalc=[2A] 02/27/07 01:34:54 PM DSC5401:check_for_data DscString=610 013 2B 02/27/07 01:34:54 PM DSC5401:IsChecksumOK DscString=[6100132B] CksValue=[2B] CksCalc=[2B] 02/27/07 01:34:54 PM DSC5401:check_for_data DscString=610 014 2C 02/27/07 01:34:54 PM DSC5401:IsChecksumOK DscString=[6100142C] CksValue=[2C] CksCalc=[2C] 02/27/07 01:34:54 PM DSC5401:check_for_data DscString=610 015 2D 02/27/07 01:34:54 PM DSC5401:IsChecksumOK DscString=[6100152D] CksValue=[2D] CksCalc=[2D] 02/27/07 01:34:54 PM DSC5401:check_for_data DscString=610 016 2E 02/27/07 01:34:54 PM DSC5401:IsChecksumOK DscString=[6100162E] CksValue=[2E] CksCalc=[2E] 02/27/07 01:34:54 PM DSC5401:check_for_data DscString=610 017 2F 02/27/07 01:34:54 PM DSC5401:IsChecksumOK DscString=[6100172F] CksValue=[2F] CksCalc=[2F] 02/27/07 01:34:54 PM DSC5401:check_for_data DscString=610 018 30 02/27/07 01:34:54 PM DSC5401:IsChecksumOK DscString=[61001830] CksValue=[30] CksCalc=[30] 02/27/07 01:34:54 PM DSC5401:check_for_data DscString=610 019 31 02/27/07 01:34:54 PM DSC5401:IsChecksumOK DscString=[61001931] CksValue=[31] CksCalc=[31] 02/27/07 01:34:54 PM DSC5401:check_for_data DscString=610 020 29 02/27/07 01:34:54 PM DSC5401:IsChecksumOK DscString=[61002029] CksValue=[29] CksCalc=[29] 02/27/07 01:34:54 PM DSC5401:check_for_data DscString=610 021 2A 02/27/07 01:34:54 PM DSC5401:IsChecksumOK DscString=[6100212A] CksValue=[2A] CksCalc=[2A] 02/27/07 01:34:54 PM DSC5401:check_for_data DscString=610 022 2B 02/27/07 01:34:54 PM DSC5401:IsChecksumOK DscString=[6100222B] CksValue=[2B] CksCalc=[2B] ---------- There are more commands that are issued to the DSC after the above output, but there are no more debug statements. However, if I also turn on serial debug, I see a number of 500x* messages coming from the serial driver, but are not reflected in the DSC5401 debug logs. I have already increased that time to 500ms, so I don't think another 500ms will make a difference. When I can physically access the system, I am going to move both the W800 and DSC5401 to the built-in serial ports (I'm using a LAVA PCI card right now) to try to rule out the LAVA card. Troy |
From: Troy C. <tr...@ca...> - 2007-02-28 02:58:36
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 27 February 2007 08:11:23 pm Troy Carpenter wrote: > Troy Carpenter wrote: > > Matthew Williams wrote: > >> Troy Carpenter wrote: > > > > I have already increased that time to 500ms, so I don't think another > > 500ms will make a difference. > > > > When I can physically access the system, I am going to move both the > > W800 and DSC5401 to the built-in serial ports (I'm using a LAVA PCI card > > right now) to try to rule out the LAVA card. > > I have tried all my serial devices on all serial ports. Here's the lowdown > as it stands: > > I have two built-in serial ports ttyS0-ttyS1. I have a Lava card providing > ttyS2-ttyS5. > > I have a modem connected to a callerID collector daemon. I can put that > daemon/modem on any of the ports and it works. > > I have a Lynx10PLC. I can put that on any of the ports and MH can use it. > > I have a W800 which before the MH upgrade was connected to ttyS2. It will > not work on any port now (built-in or Lava card). The W800 did work one > time after the upgrade, but after a MH restart, it has not worked. I did > get MH one time to tell me it was "flushing incomplete data". Serial debug > shows nothing from the W800. > > I have a DSC5401 which before the MH upgrade was connected to ttyS3. It > will not work on any port now (built-in or Lava card). If I turn on > DSC5401 debugging, I see the commands go out, I see the zone report come > back. I will get two errors on startup, but as to what they are at any > time is a crap shoot. Messages I have seen include "API syntax errors", > "RS232 receive buffer overflow" and "unknown". There appear to be nothing > coming from the DSC after that. However, if instead I turn on serial > debug, I see an endless string of encoded error messages from the DSC. > > Since I can run the Lynx10 and external modem from any port, I do not > believe the Lava card is malfunctioning. I'm left with a failure of the MH > code, the physical units, or both as the only possible explanations. > > Stupid me didn't preserve my MH code directory so I could revert back to my > previous code base if there was a problem. During the upgrade process I > hosed my installation and got tons of perl errors. What I have now, is the > latest SVN code (checked out into it's own directory, so it's clean), along > with my customized code sub-directory. > > Is there any way to check out a specific MH release from SVN? The lineup I > had before upgrading was in the high 900's, but less than 1000. I don't > want to go all the way back to the v102 release because I know there were > many changes from that one to get my system to work (I know because I > submitted a few of them). Ok, just like that, it's over. After all day of restarts, reconfigurations, power cycles on all components, etc, I finally hit on something that worked. I don't know why it worked, but it did. Of course, I tried powering down my DSC system to reset the 5401 card. That made no difference. However, one time during a power down, I changed the baud rate of the card from 9600 to 19200. Changed MH config, restarted, and it worked. I now get a checksum error at startup: "DSC5401:check_for_data Invalid checksum from 6100250001026 (1F)" but in spite of that, the 5401 now is sending and receiving system updates. And just an inexplicable, I took the W800 off the PC to another to test it, but never got around to it. I put it back on the MH system and it too started working. Likewise I had done a number of power cycles on the unit throughout the day to solve the problem to no avail. In the end, I have no idea what caused the problem, nor really why it is solved (if it really is). I have done a number of restarts on MH since then and both the W800 and the DSC5401 have come back every time. Troy -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.2 (GNU/Linux) iD8DBQFF5O/KuVQoOU+V4YYRAr5xAJ4k5bC8G9x8dgZfjV+z8hTJNku4FgCePQG3 URT/1qXjmxA0Jo2GMYZtJE4= =aznL -----END PGP SIGNATURE----- |
From: Matthew W. <mat...@us...> - 2007-02-28 13:45:58
|
Troy Carpenter wrote: >> Is there any way to check out a specific MH release from SVN? The lineup I >> had before upgrading was in the high 900's, but less than 1000. I don't >> want to go all the way back to the v102 release because I know there were >> many changes from that one to get my system to work (I know because I >> submitted a few of them). The answer is yes. Normally an "update" will get you to the "HEAD" revision of the current URL, however it can be also be used to get to any revision, forwards or backwards from the current revision of your working copy. If you run the command line version of svn, take a look at "svn help update". If you want to "update" to revision 999, you would do "svn update -r 999" from the root of your working directory. If you run this command from a subdirectory, then only that subdirectory and its children will be "updated". This is normally a very bad thing as it is likely that some revisions changed files in multiple subdirectories. The same thing will work from TortoiseSVN as well with the "Update to revision" command. > Of course, I tried powering down my DSC system to reset the 5401 card. That > made no difference. However, one time during a power down, I changed the > baud rate of the card from 9600 to 19200. Changed MH config, restarted, and > it worked. I now get a checksum error at startup: > "DSC5401:check_for_data Invalid checksum from 6100250001026 (1F)" > but in spite of that, the 5401 now is sending and receiving system updates. I'm glad that it is working for you but that is very wacky. I can't see anything in the recent mh revisions that would cause this sort of behaviour. Oh well, do report if the problems reoccur and we can add some more debugs to figure this out. Matt |
From: Troy C. <tr...@ca...> - 2007-02-28 01:11:38
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Troy Carpenter wrote: > Matthew Williams wrote: >> Troy Carpenter wrote: >> > I have already increased that time to 500ms, so I don't think another > 500ms will make a difference. > > When I can physically access the system, I am going to move both the > W800 and DSC5401 to the built-in serial ports (I'm using a LAVA PCI card > right now) to try to rule out the LAVA card. > I have tried all my serial devices on all serial ports. Here's the lowdown as it stands: I have two built-in serial ports ttyS0-ttyS1. I have a Lava card providing ttyS2-ttyS5. I have a modem connected to a callerID collector daemon. I can put that daemon/modem on any of the ports and it works. I have a Lynx10PLC. I can put that on any of the ports and MH can use it. I have a W800 which before the MH upgrade was connected to ttyS2. It will not work on any port now (built-in or Lava card). The W800 did work one time after the upgrade, but after a MH restart, it has not worked. I did get MH one time to tell me it was "flushing incomplete data". Serial debug shows nothing from the W800. I have a DSC5401 which before the MH upgrade was connected to ttyS3. It will not work on any port now (built-in or Lava card). If I turn on DSC5401 debugging, I see the commands go out, I see the zone report come back. I will get two errors on startup, but as to what they are at any time is a crap shoot. Messages I have seen include "API syntax errors", "RS232 receive buffer overflow" and "unknown". There appear to be nothing coming from the DSC after that. However, if instead I turn on serial debug, I see an endless string of encoded error messages from the DSC. Since I can run the Lynx10 and external modem from any port, I do not believe the Lava card is malfunctioning. I'm left with a failure of the MH code, the physical units, or both as the only possible explanations. Stupid me didn't preserve my MH code directory so I could revert back to my previous code base if there was a problem. During the upgrade process I hosed my installation and got tons of perl errors. What I have now, is the latest SVN code (checked out into it's own directory, so it's clean), along with my customized code sub-directory. Is there any way to check out a specific MH release from SVN? The lineup I had before upgrading was in the high 900's, but less than 1000. I don't want to go all the way back to the v102 release because I know there were many changes from that one to get my system to work (I know because I submitted a few of them). Troy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF5Na7uVQoOU+V4YYRAvQrAJ9tMH2/cTDGheI9j/h8heGBZN3e/ACfQpxD BtMdvDQYdg6/fpsk3+Lh1lE= =pT4w -----END PGP SIGNATURE----- |
From: Noah S. <ns...@ho...> - 2007-12-11 16:51:59
|
Were you ever able to get this to work? I'm still having the same problem nothing ever comes back. 12/11/07 11:07:33 AM: >>> Sending to DSC panel SetDateTime (010) with argument (1107121107) [010110712110786] 12/11/07 10:59:56 AM: >>> Sending to DSC panel TimeBroadcastControl (056) with argument (1) [0561CC] 12/11/07 10:59:55 AM: >>> Sending to DSC panel VerboseArmingControl (050) with argument (1) [0501C6] 12/11/07 10:59:55 AM: >>> Sending to DSC panel StatusReport (001) with argument () [00191] > Ok, I am actively troubleshooting this problem, but I thought I would post > to > see if anyone can give any pointers in the meantime. > > I finally bit the bullet and upgraded my system from its semi-frozen post > 102 > SVN state to the latest SVN snapshot. I have two main issues, but the > first > seems to have resolved itself (MH was not seeing my W800 signals, but that > seems to be working now). > > The BIG problem I am having is with my DSC5401. It just will not talk to > Misterhouse after the upgrade (well, it did work one time, but that was > it). > Starting up I see the following (edited superfluous lines): > > Loading other modules > Starting setup > - creating DSC5401 port on /dev/ttyS3 > - creating W800 port on /dev/ttyS2 > - creating Lynx10PLC port on /dev/ttyS0 > Debug level: /dev/ttyS0 = 0 at /pub/misterhouse/bin/../lib/Lynx10PLC.pm > line > 291 > > Done with setup > > 02/27/07 09:57:29 AM Calling Serial_match_add_hook > 02/27/07 09:57:29 AM Starting DSC 5401 computer interface module > 02/27/07 09:57:29 AM Sending to DSC panel Poll (000) with argument () > 02/27/07 09:57:29 AM Sending to DSC panel StatusReport (001) with argument > () > 02/27/07 09:57:29 AM Sending to DSC panel VerboseArmingControl (050) with > argument (1) > 02/27/07 09:57:29 AM Sending to DSC panel TimeBroadcastControl (056) with > argument (1) > Good code saved > 02/27/07 09:57:32 AM Command Error : Unknown > 02/27/07 09:57:32 AM System Error : RS-232 Receive Buffer Overrun > 02/27/07 09:57:32 AM Setting time on DSC panel to 0957022707 > 02/27/07 09:57:32 AM Sending to DSC panel SetDateTime (010) with argument > (0957022707) > ----- > > After this I would normally see the a zone status updated message from the > DSC > logging, plus I never get any updates from the system about zones opening > and > closing, nor do I get arm/disarm events. > > I am concerned with the "Command Error" and "System Errors" that are > occurring > during the startup (they come from the DSC5401 library code). I have not > seen those before upgrading. > > I do not remember making any kernel changes or serial port configuration > changes in the past few months. > > As a final bit, here's my DSC5401.2007_02.log file from startup: > Tue 02/27/07 10:03:17 ========= DSC5401.pm Initialized ========= > Tue 02/27/07 10:03:18 >>> Sending to DSC panel Poll (000) with argument () > [00090] > Tue 02/27/07 10:03:18 >>> Sending to DSC panel StatusReport (001) with > argument () [00191] > Tue 02/27/07 10:03:19 >>> Sending to DSC panel VerboseArmingControl (050) > with > argument (1) [0501C6] > Tue 02/27/07 10:03:19 >>> Sending to DSC panel TimeBroadcastControl (056) > with > argument (1) [0561CC] > Tue 02/27/07 10:03:19 501 Command Error Unknown > Tue 02/27/07 10:03:19 500 Command Acknowledge StatusReport > Tue 02/27/07 10:03:19 502 System Error RS-232 Receive Buffer Overrun > Tue 02/27/07 10:03:19 610 Zone Restored zone Front Door (001) > Tue 02/27/07 10:03:19 610 Zone Restored zone Media Room Windows (002) > Tue 02/27/07 10:03:19 610 Zone Restored zone Family Room Windows (003) > Tue 02/27/07 10:03:19 610 Zone Restored zone Garage Entry Door (004) > Tue 02/27/07 10:03:19 610 Zone Restored zone Kitchen Door or Windows > (005) > Tue 02/27/07 10:03:19 610 Zone Restored zone Music Room Windows (006) > Tue 02/27/07 10:03:19 610 Zone Restored zone Basement Door or Windows > (007) > Tue 02/27/07 10:03:19 610 Zone Restored zone Fire Alarm (008) > Tue 02/27/07 10:03:19 610 Zone Restored zone 009 (009) > Tue 02/27/07 10:03:19 610 Zone Restored zone 010 (010) > Tue 02/27/07 10:03:19 610 Zone Restored zone 011 (011) > Tue 02/27/07 10:03:19 610 Zone Restored zone 012 (012) > Tue 02/27/07 10:03:19 610 Zone Restored zone 013 (013) > Tue 02/27/07 10:03:19 610 Zone Restored zone 014 (014) > Tue 02/27/07 10:03:19 610 Zone Restored zone 015 (015) > Tue 02/27/07 10:03:19 610 Zone Restored zone 016 (016) > Tue 02/27/07 10:03:19 610 Zone Restored zone 017 (017) > Tue 02/27/07 10:03:19 610 Zone Restored zone 018 (018) > Tue 02/27/07 10:03:19 610 Zone Restored zone 019 (019) > Tue 02/27/07 10:03:19 610 Zone Restored zone 020 (020) > Tue 02/27/07 10:03:19 610 Zone Restored zone 021 (021) > Tue 02/27/07 10:03:19 610 Zone Restored zone 022 (022) > Tue 02/27/07 10:03:20 Setting time on DSC panel to 1003022707 > Tue 02/27/07 10:03:20 >>> Sending to DSC panel > SetDateTime (010) with argument (1003022707) [010100302270787] > > Troy > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > ________________________________________________________ > To unsubscribe from this list, go to: > http://sourceforge.net/mail/?group_id=1365 > > |
From: Noah S. <ns...@ho...> - 2007-12-12 17:20:28
|
I commented the first line and uncommented the second in DSC5401startup.pl. I'm back in business. #set $serial_out_2 "ati0q0v0e0l3m2x4\r\n"; set $serial_out_2 "ate1\r\n"; # If debug is enable... > Were you ever able to get this to work? > > I'm still having the same problem nothing ever comes back. > > > 12/11/07 11:07:33 AM: >>> Sending to DSC panel SetDateTime (010) with > argument (1107121107) [010110712110786] > 12/11/07 10:59:56 AM: >>> Sending to DSC panel TimeBroadcastControl (056) > with argument (1) [0561CC] > 12/11/07 10:59:55 AM: >>> Sending to DSC panel VerboseArmingControl (050) > with argument (1) [0501C6] > 12/11/07 10:59:55 AM: >>> Sending to DSC panel StatusReport (001) with > argument () [00191] > > > >> Ok, I am actively troubleshooting this problem, but I thought I would >> post >> to >> see if anyone can give any pointers in the meantime. >> >> I finally bit the bullet and upgraded my system from its semi-frozen >> post >> 102 >> SVN state to the latest SVN snapshot. I have two main issues, but the >> first >> seems to have resolved itself (MH was not seeing my W800 signals, but >> that >> seems to be working now). >> >> The BIG problem I am having is with my DSC5401. It just will not talk >> to >> Misterhouse after the upgrade (well, it did work one time, but that was >> it). >> Starting up I see the following (edited superfluous lines): >> >> Loading other modules >> Starting setup >> - creating DSC5401 port on /dev/ttyS3 >> - creating W800 port on /dev/ttyS2 >> - creating Lynx10PLC port on /dev/ttyS0 >> Debug level: /dev/ttyS0 = 0 at /pub/misterhouse/bin/../lib/Lynx10PLC.pm >> line >> 291 >> >> Done with setup >> >> 02/27/07 09:57:29 AM Calling Serial_match_add_hook >> 02/27/07 09:57:29 AM Starting DSC 5401 computer interface module >> 02/27/07 09:57:29 AM Sending to DSC panel Poll (000) with argument () >> 02/27/07 09:57:29 AM Sending to DSC panel StatusReport (001) with >> argument >> () >> 02/27/07 09:57:29 AM Sending to DSC panel VerboseArmingControl (050) >> with >> argument (1) >> 02/27/07 09:57:29 AM Sending to DSC panel TimeBroadcastControl (056) >> with >> argument (1) >> Good code saved >> 02/27/07 09:57:32 AM Command Error : Unknown >> 02/27/07 09:57:32 AM System Error : RS-232 Receive Buffer Overrun >> 02/27/07 09:57:32 AM Setting time on DSC panel to 0957022707 >> 02/27/07 09:57:32 AM Sending to DSC panel SetDateTime (010) with >> argument >> (0957022707) >> ----- >> >> After this I would normally see the a zone status updated message from >> the >> DSC >> logging, plus I never get any updates from the system about zones >> opening >> and >> closing, nor do I get arm/disarm events. >> >> I am concerned with the "Command Error" and "System Errors" that are >> occurring >> during the startup (they come from the DSC5401 library code). I have >> not >> seen those before upgrading. >> >> I do not remember making any kernel changes or serial port configuration >> changes in the past few months. >> >> As a final bit, here's my DSC5401.2007_02.log file from startup: >> Tue 02/27/07 10:03:17 ========= DSC5401.pm Initialized ========= >> Tue 02/27/07 10:03:18 >>> Sending to DSC panel Poll (000) with argument >> () >> [00090] >> Tue 02/27/07 10:03:18 >>> Sending to DSC panel StatusReport (001) with >> argument () [00191] >> Tue 02/27/07 10:03:19 >>> Sending to DSC panel VerboseArmingControl >> (050) >> with >> argument (1) [0501C6] >> Tue 02/27/07 10:03:19 >>> Sending to DSC panel TimeBroadcastControl >> (056) >> with >> argument (1) [0561CC] >> Tue 02/27/07 10:03:19 501 Command Error Unknown >> Tue 02/27/07 10:03:19 500 Command Acknowledge StatusReport >> Tue 02/27/07 10:03:19 502 System Error RS-232 Receive Buffer Overrun >> Tue 02/27/07 10:03:19 610 Zone Restored zone Front Door (001) >> Tue 02/27/07 10:03:19 610 Zone Restored zone Media Room Windows (002) >> Tue 02/27/07 10:03:19 610 Zone Restored zone Family Room Windows >> (003) >> Tue 02/27/07 10:03:19 610 Zone Restored zone Garage Entry Door (004) >> Tue 02/27/07 10:03:19 610 Zone Restored zone Kitchen Door or Windows >> (005) >> Tue 02/27/07 10:03:19 610 Zone Restored zone Music Room Windows (006) >> Tue 02/27/07 10:03:19 610 Zone Restored zone Basement Door or Windows >> (007) >> Tue 02/27/07 10:03:19 610 Zone Restored zone Fire Alarm (008) >> Tue 02/27/07 10:03:19 610 Zone Restored zone 009 (009) >> Tue 02/27/07 10:03:19 610 Zone Restored zone 010 (010) >> Tue 02/27/07 10:03:19 610 Zone Restored zone 011 (011) >> Tue 02/27/07 10:03:19 610 Zone Restored zone 012 (012) >> Tue 02/27/07 10:03:19 610 Zone Restored zone 013 (013) >> Tue 02/27/07 10:03:19 610 Zone Restored zone 014 (014) >> Tue 02/27/07 10:03:19 610 Zone Restored zone 015 (015) >> Tue 02/27/07 10:03:19 610 Zone Restored zone 016 (016) >> Tue 02/27/07 10:03:19 610 Zone Restored zone 017 (017) >> Tue 02/27/07 10:03:19 610 Zone Restored zone 018 (018) >> Tue 02/27/07 10:03:19 610 Zone Restored zone 019 (019) >> Tue 02/27/07 10:03:19 610 Zone Restored zone 020 (020) >> Tue 02/27/07 10:03:19 610 Zone Restored zone 021 (021) >> Tue 02/27/07 10:03:19 610 Zone Restored zone 022 (022) >> Tue 02/27/07 10:03:20 Setting time on DSC panel to 1003022707 >> Tue 02/27/07 10:03:20 >>> Sending to DSC panel >> SetDateTime (010) with argument (1003022707) [010100302270787] >> >> Troy >> >> ------------------------------------------------------------------------- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to share >> your >> opinions on IT & business topics through brief surveys-and earn cash >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >> ________________________________________________________ >> To unsubscribe from this list, go to: >> http://sourceforge.net/mail/?group_id=1365 >> >> > > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > ________________________________________________________ > To unsubscribe from this list, go to: > http://sourceforge.net/mail/?group_id=1365 > > |
From: Jocelyn B. <joc...@vi...> - 2007-12-12 21:31:52
|
Hi, These lignes are not realy required with DSC5401. #set $serial_out_2 "ati0q0v0e0l3m2x4\r\n"; set $serial_out_2 "ate1\r\n"; # If debug is enable... This is work around to communicate to a DSC Escort/Thermostat module to switch from Day to Night mode by using touch tone phone ligne. The DSC5401 serial can't communicate to the Escort module by DSC bus. Jocelyn ----- Original Message ----- From: "Noah Swint" <ns...@ho...> To: <ns...@ho...>; "The main list for the MisterHouse home automation program" <mis...@li...> Sent: Wednesday, December 12, 2007 11:10 AM Subject: Re: [mh] Problems with DSC5401 after upgrade >I commented the first line and uncommented the second in > DSC5401startup.pl. I'm back in business. > > #set $serial_out_2 "ati0q0v0e0l3m2x4\r\n"; > > > set $serial_out_2 "ate1\r\n"; # If debug is enable... > > > >> Were you ever able to get this to work? >> >> I'm still having the same problem nothing ever comes back. >> >> >> 12/11/07 11:07:33 AM: >>> Sending to DSC panel SetDateTime (010) with >> argument (1107121107) [010110712110786] >> 12/11/07 10:59:56 AM: >>> Sending to DSC panel TimeBroadcastControl (056) >> with argument (1) [0561CC] >> 12/11/07 10:59:55 AM: >>> Sending to DSC panel VerboseArmingControl (050) >> with argument (1) [0501C6] >> 12/11/07 10:59:55 AM: >>> Sending to DSC panel StatusReport (001) with >> argument () [00191] >> >> >> >>> Ok, I am actively troubleshooting this problem, but I thought I would >>> post >>> to >>> see if anyone can give any pointers in the meantime. >>> >>> I finally bit the bullet and upgraded my system from its semi-frozen >>> post >>> 102 >>> SVN state to the latest SVN snapshot. I have two main issues, but the >>> first >>> seems to have resolved itself (MH was not seeing my W800 signals, but >>> that >>> seems to be working now). >>> >>> The BIG problem I am having is with my DSC5401. It just will not talk >>> to >>> Misterhouse after the upgrade (well, it did work one time, but that was >>> it). >>> Starting up I see the following (edited superfluous lines): >>> >>> Loading other modules >>> Starting setup >>> - creating DSC5401 port on /dev/ttyS3 >>> - creating W800 port on /dev/ttyS2 >>> - creating Lynx10PLC port on /dev/ttyS0 >>> Debug level: /dev/ttyS0 = 0 at /pub/misterhouse/bin/../lib/Lynx10PLC.pm >>> line >>> 291 >>> >>> Done with setup >>> >>> 02/27/07 09:57:29 AM Calling Serial_match_add_hook >>> 02/27/07 09:57:29 AM Starting DSC 5401 computer interface module >>> 02/27/07 09:57:29 AM Sending to DSC panel Poll (000) with argument () >>> 02/27/07 09:57:29 AM Sending to DSC panel StatusReport (001) with >>> argument >>> () >>> 02/27/07 09:57:29 AM Sending to DSC panel VerboseArmingControl (050) >>> with >>> argument (1) >>> 02/27/07 09:57:29 AM Sending to DSC panel TimeBroadcastControl (056) >>> with >>> argument (1) >>> Good code saved >>> 02/27/07 09:57:32 AM Command Error : Unknown >>> 02/27/07 09:57:32 AM System Error : RS-232 Receive Buffer Overrun >>> 02/27/07 09:57:32 AM Setting time on DSC panel to 0957022707 >>> 02/27/07 09:57:32 AM Sending to DSC panel SetDateTime (010) with >>> argument >>> (0957022707) >>> ----- >>> >>> After this I would normally see the a zone status updated message from >>> the >>> DSC >>> logging, plus I never get any updates from the system about zones >>> opening >>> and >>> closing, nor do I get arm/disarm events. >>> >>> I am concerned with the "Command Error" and "System Errors" that are >>> occurring >>> during the startup (they come from the DSC5401 library code). I have >>> not >>> seen those before upgrading. >>> >>> I do not remember making any kernel changes or serial port configuration >>> changes in the past few months. >>> >>> As a final bit, here's my DSC5401.2007_02.log file from startup: >>> Tue 02/27/07 10:03:17 ========= DSC5401.pm Initialized ========= >>> Tue 02/27/07 10:03:18 >>> Sending to DSC panel Poll (000) with argument >>> () >>> [00090] >>> Tue 02/27/07 10:03:18 >>> Sending to DSC panel StatusReport (001) with >>> argument () [00191] >>> Tue 02/27/07 10:03:19 >>> Sending to DSC panel VerboseArmingControl >>> (050) >>> with >>> argument (1) [0501C6] >>> Tue 02/27/07 10:03:19 >>> Sending to DSC panel TimeBroadcastControl >>> (056) >>> with >>> argument (1) [0561CC] >>> Tue 02/27/07 10:03:19 501 Command Error Unknown >>> Tue 02/27/07 10:03:19 500 Command Acknowledge StatusReport >>> Tue 02/27/07 10:03:19 502 System Error RS-232 Receive Buffer Overrun >>> Tue 02/27/07 10:03:19 610 Zone Restored zone Front Door (001) >>> Tue 02/27/07 10:03:19 610 Zone Restored zone Media Room Windows (002) >>> Tue 02/27/07 10:03:19 610 Zone Restored zone Family Room Windows >>> (003) >>> Tue 02/27/07 10:03:19 610 Zone Restored zone Garage Entry Door (004) >>> Tue 02/27/07 10:03:19 610 Zone Restored zone Kitchen Door or Windows >>> (005) >>> Tue 02/27/07 10:03:19 610 Zone Restored zone Music Room Windows (006) >>> Tue 02/27/07 10:03:19 610 Zone Restored zone Basement Door or Windows >>> (007) >>> Tue 02/27/07 10:03:19 610 Zone Restored zone Fire Alarm (008) >>> Tue 02/27/07 10:03:19 610 Zone Restored zone 009 (009) >>> Tue 02/27/07 10:03:19 610 Zone Restored zone 010 (010) >>> Tue 02/27/07 10:03:19 610 Zone Restored zone 011 (011) >>> Tue 02/27/07 10:03:19 610 Zone Restored zone 012 (012) >>> Tue 02/27/07 10:03:19 610 Zone Restored zone 013 (013) >>> Tue 02/27/07 10:03:19 610 Zone Restored zone 014 (014) >>> Tue 02/27/07 10:03:19 610 Zone Restored zone 015 (015) >>> Tue 02/27/07 10:03:19 610 Zone Restored zone 016 (016) >>> Tue 02/27/07 10:03:19 610 Zone Restored zone 017 (017) >>> Tue 02/27/07 10:03:19 610 Zone Restored zone 018 (018) >>> Tue 02/27/07 10:03:19 610 Zone Restored zone 019 (019) >>> Tue 02/27/07 10:03:19 610 Zone Restored zone 020 (020) >>> Tue 02/27/07 10:03:19 610 Zone Restored zone 021 (021) >>> Tue 02/27/07 10:03:19 610 Zone Restored zone 022 (022) >>> Tue 02/27/07 10:03:20 Setting time on DSC panel to 1003022707 >>> Tue 02/27/07 10:03:20 >>> Sending to DSC panel >>> SetDateTime (010) with argument (1003022707) [010100302270787] >>> >>> Troy >>> >>> ------------------------------------------------------------------------- >>> Take Surveys. Earn Cash. Influence the Future of IT >>> Join SourceForge.net's Techsay panel and you'll get the chance to share >>> your >>> opinions on IT & business topics through brief surveys-and earn cash >>> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >>> ________________________________________________________ >>> To unsubscribe from this list, go to: >>> http://sourceforge.net/mail/?group_id=1365 >>> >>> >> >> >> ------------------------------------------------------------------------- >> SF.Net email is sponsored by: >> Check out the new SourceForge.net Marketplace. >> It's the best place to buy or sell services for >> just about anything Open Source. >> http://sourceforge.net/services/buy/index.php >> ________________________________________________________ >> To unsubscribe from this list, go to: >> http://sourceforge.net/mail/?group_id=1365 >> >> > > > ------------------------------------------------------------------------- > SF.Net email is sponsored by: > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > ________________________________________________________ > To unsubscribe from this list, go to: > http://sourceforge.net/mail/?group_id=1365 > |