Open geetee24 opened 4 years ago
Did you ever get this resolved? I hooked mine up yesterday, and I’m seeing the exact same issue. Power LED is on and the bus LED is blinking. The RS232 LED is off, at least when I’m looking.
The concord express absolutely 100% does not work with that unit
It does not have the firmware to communicate with it
The only way to solve the problem is to do what I did throw out the Concord express and in my case I bought a used Concord 4 which can communicate with the unit
On Sat, Jan 1, 2022 at 6:50 AM Dave Dupre @.***> wrote:
Did you ever get this resolved? I hooked mine up yesterday, and I’m seeing the exact same issue. Power LED is on and the bus LED is blinking. The RS232 LED is off, at least when I’m looking.
— Reply to this email directly, view it on GitHub https://github.com/JasonCarter80/concord232/issues/20#issuecomment-1003568877, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABS6UT7LF6ZMEAPTHER44HTUT4IDBANCNFSM4TVK7RHA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>
Hmm. I don’t have a concord express. I have a SuperBus 2000 automation module. In theory, this is the recommended unit.
Never mind. You meant the main unit. Looks like mine is a Concord Express. Bummer.
I own ge concord express sw version 0500 and a new home automation module. wired in the automation unit. powered up both. see on auto unit the power led on and the blinking BUSS red LED. So auto unit looks good.
PROBLEM: The Concord shows no indication of recognizing the automation unit. The panel should be beeping with a unknown new device. It is not.
I run the concord232server in debug mode and get:
2020-11-13 21:32:49,391 _internal INFO * Running on http://0.0.0.0:5007/ (Press CTRL+C to quit) 2020-11-13 21:32:49,861 concord DEBUG Sending message (retry=1) '022022' 2020-11-13 21:33:09,399 concord DEBUG Looping 20 2020-11-13 21:33:29,439 concord DEBUG Looping 40 2020-11-13 21:33:49,477 concord DEBUG Looping 60 2020-11-13 21:34:09,516 concord DEBUG Looping 80 ^[[4~^[[1~^[[1~^[[1~^[[1~^[[1~^[[1~^[[5~^[[5~^[[5~^[[5~^[[5~^[[5~^[[5~^[[5~^[[5~^[[5~^[[5~^[[5~^[[5~^[[5~^[[5~^[[5~^[[5~2020-11-13 21:34:29,554 concord DEBUG Looping 100 2020-11-13 21:34:49,592 concord DEBUG Looping 120 2020-11-13 21:35:09,632 concord DEBUG Looping 140 2020-11-13 21:35:29,670 concord DEBUG Looping 160 2020-11-13 21:35:49,708 concord DEBUG Looping 180 2020-11-13 21:36:09,747 concord DEBUG Looping 200 2020-11-13 21:36:29,786 concord DEBUG Looping 220 2020-11-13 21:36:49,830 concord DEBUG Looping 240 2020-11-13 21:37:09,873 concord DEBUG Looping 260 2020-11-13 21:37:29,917 concord DEBUG Looping 280 2020-11-13 21:37:49,959 concord DEBUG Looping 300 2020-11-13 21:38:10,002 concord DEBUG Looping 320 2020-11-1
I then plug the serial (usb) cable into miniterm and send a ControlJ 020204 command and get a hex 6 form the auto unit. This is the unit replying with an ACK.
It appears that the concord alarm is just not seeing the auto panel.
Anyone have ideas?
Thank you.