Hi.
I have Connected my It-100 with a serial to usb adapter into a Vera 3. Installed the app and configured the serial port and that i have the it-100 module.
I can now Arm,disarm,set time but i don?t get the zone names and i can?t see any status on zones and partitions? The setup is 9600 baud. Is that right?
I have searched the forum for two days now and tried a lot of things. Do any have an idea what could be the problem?
More info.
I have the latest firmware on my vera3 1.6.641. I have tried two different usb to rs232 and two different cables with DB9 connectors. I have tried to reinstall the dec plugin several times. Today i connected my computer to the it-100 and opened the hyperterminal and went in front of the ir detectors and armed,disarmed the alarm from the panel. I don?t get any information at all in the vera app from the alarmsystem but i can control it. Do i need to do any programing in the dsc panel to activate something?
Please help!
I attach a picture from the test witch hyperterminal
.
/Niclas
9600 baud is correct (listed in the Help/Wiki install instructions, which are here and here).
Check the “used-by-device” is set to have the Serial device used by/associated with the DSC Plugin. If this UI isn’t there at all, then it’s likely that the USB-Serial device isn’t recognized by Vera.
I no longer have a UI6 box to test against, nor an IT100, but the first thing to look at is the USB-Serial adapter you’re using. There are many that will work on your PC/Mac, but won’t work on Vera, so that’s the first thing to check.
If it’s missing, there’s a long, pinned, thread on USB-Serial compat, and how to diagnose. In many cases, it’s just simpler to buy one of the supported ones (listed on wiki.micasaverde.com)
Many people have simply reverted to UI5, since UI6 has many issues. I did do an early trial of it, using the Envisalink EVL2, and it was functioning fine (albeit, with minor UI-Layout issues due to incompatibilities introduced by UI6 itself)
I have done everything and read the guides but still the same result.
I attach i picture on my converter. It?s a converter with the FTDI chip. Do you think it still can possibly be something wrong with this or should i order the wizenet module RS232 to RJ45?
Going to be hard to tell. Run through the standard procedure (Pinned in Programming):
http://forum.micasaverde.com/index.php/topic,1471.0.html
You haven’t indicated whether the Serial Port shows up in Vera or not, nor whether it’s attached/associated “used-by-device” to the DSC Plugin.
It might be easier if you provide the counterpart screenshots, from your environment, that map to the ones in the [DSC] install instructions.
Once you have it recognized by Vera, and Associated with the DSC Plugin, then the next thing to work out is whether the RS-232 needs to be cross-over, null-modem, (etc). I remember when I originally used it, it took a while to work out the right combo (I have several gender-benders for exactly this purpose)
BTW: The picture isn’t of much use, there are FTDI adapters that also aren’t recognized by Vera (see the USB-Serial thread above for examples). There are also some nasty-a$$ clones that look like FTDI, but really aren’t.
Vera finds converter. I Also tried to connect IT-100 to my Global Cache GC-100. But i?ve got the same result. Before i bought my Vera i had the DSC and Global Cache with Irule. and status feedback worked fine. So i think the cable is correct. Now with the Global cache connected i can control everything but no status. I attach a picture of the serial setup.
I’ve never tried a GC-100 on Vera.
If you want to see the datastream that an attached plugin sees, enable log levels “51” and “52” in the file:
/etc/cmh/cmh.conf
The log configuration will look like this:
LogLevels = 1,2,3,4,5,6,7,8,9,50,51,52
Log level 52 is incoming serial data (from the IT100), and 51 is outgoing (to the IT100).
The output will look like this:
grep ^5[012] LuaUPnP.log
52 08/12/14 13:19:21.106 0x36 0x35 0x30 0x31 0x43 0x43 (6501CC) <0x2d87e680>
50 08/12/14 13:19:21.106 luup_log:3: DSCAlarmPanel: debug processIncoming:: Command=650, Data='1', Checksum=CC <0x2d87e680>
50 08/12/14 13:19:21.107 luup_log:3: DSCAlarmPanel: debug Partition::Ready 650 partition: 1 <0x2d87e680>
52 08/12/14 13:19:53.599 0x35 0x35 0x30 0x31 0x36 0x32 0x30 0x30 0x38 0x31 0x32 0x31 0x34 0x39 0x33 (550162008121493) <0x2d87e680>
50 08/12/14 13:19:53.599 luup_log:3: DSCAlarmPanel: debug processIncoming:: Command=550, Data='1620081214', Checksum=93 <0x2d87e680>
50 08/12/14 13:19:53.601 luup_log:3: DSCAlarmPanel: debug Panel::Time/Date Broadcast (1620081214) <0x2d87e680>
52 08/12/14 13:23:30.619 0x35 0x31 0x31 0x31 0x30 0x46 0x38 (51110F8) <0x2d87e680>
50 08/12/14 13:23:30.619 luup_log:3: DSCAlarmPanel: debug processIncoming:: Command=511, Data='10', Checksum=F8 <0x2d87e680>
50 08/12/14 13:23:30.622 luup_log:3: DSCAlarmPanel: debug Panel::Keypad LED Flash State - Partition 1 only (10) <0x2d87e680>
52 08/12/14 13:23:30.623 0x38 0x34 0x39 0x30 0x35 0x30 0x41 (849050A) <0x2d87e680>
50 08/12/14 13:23:30.624 luup_log:3: DSCAlarmPanel: debug processIncoming:: Command=849, Data='05', Checksum=0A <0x2d87e680>
50 08/12/14 13:23:30.626 luup_log:3: DSCAlarmPanel: debug Verbose Trouble Status 849 <0x2d87e680>
52 08/12/14 13:23:31.119 0x35 0x31 0x30 0x38 0x30 0x46 0x45 (51080FE) <0x2d87e680>
50 08/12/14 13:23:31.120 luup_log:3: DSCAlarmPanel: debug processIncoming:: Command=510, Data='80', Checksum=FE <0x2d87e680>
If you’re not seeing that, then there’s a problem upstream somewhere (Panel, Wiring, GC100, GC100 Plugin, etc). I’ve seen cases in the past, with regular USB-Serial, where one of the wires is broken and so either TX or RX isn’t working.
I will try this tomorrow. Thank you for your time!!
I attach two pictures more. Should the three buttons in zone settings work? get this when i press them.
Poll methods aren’t implemented, since they don’t need to be. Serial is attached to the parent node (Panel) not the children.
I?ve got this from the log. It does not say much to me. But i?ve got tjis when i opened the front door and closed it.
You have your Panel configured to prefix each line with a Timestamp. This is not the default, and is going to break the code.
The line that currently reads:
18:07:00 60900433
should read:
60900433
It might be the Time Stamp Control command (055), but you’d have to play around with it to see since it’s not in the format described in the IT100 programmer/API guide.
It?s Working!!! Thank you ;D
I set the time stamp to 0
Best Home Automation shopping experience. Shop at Ezlo!
© 2024 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules