Not able to connect

[ghost]

Hello, I'm having trouble connecting to the panel through the code. When I try to connect I see

Resending message, attempt 2: '03020308'
Resending message, attempt 2: '022022'
Resending message, attempt 3: '022022'
Unable to send message (timeout), too many attempts (3): '022022'

in my terminal. I used the concordtester app I found in another form to make sure my module and wires are good, I can control/view the system just fine so I don't think thats the problem.

I get the same responses when I try to do the concord232_server with my serial port.

Thank you for any help!!

[JasonCarter80]

What happens when you enable debug? What do you see?

[ghost]

This is what I get back...
2018-02-03 13:27:44,515 main INFO Ready
2018-02-03 13:27:45,531 concord WARNING Resending message, attempt 2: '03020308'
2018-02-03 13:27:47,559 concord WARNING Resending message, attempt 2: '022022'
2018-02-03 13:27:48,575 concord WARNING Resending message, attempt 3: '022022'
2018-02-03 13:27:49,529 _internal INFO * Running on http://0.0.0.0:5007/ (Press CTRL+C to quit)
2018-02-03 13:27:49,584 concord ERROR Unable to send message (timeout), too many attempts (3): '022022'
^CRobins-MacBook-Pro:~ robinisrael$ concord232_server --debug
2018-02-03 13:28:03,788 main INFO Ready
2018-02-03 13:28:03,788 main ERROR Serial and baudrate are required
Robins-MacBook-Pro:~ robinisrael$ concord232_server --debug --serial /dev/cu.usbserial
2018-02-03 13:28:14,603 main INFO Ready
2018-02-03 13:28:14,603 concord DEBUG SerialInterface Starting
2018-02-03 13:28:14,609 concord DEBUG Starting
2018-02-03 13:28:14,610 concord DEBUG Message Loop Starting
2018-02-03 13:28:14,612 concord DEBUG Sending message (retry=1) '03020308'
2018-02-03 13:28:15,621 concord WARNING Resending message, attempt 2: '03020308'
2018-02-03 13:28:16,127 concord DEBUG {'display_text': 'UNIT - ID\n2 - 06786024', 'timestamp': datetime.datetime(2018, 2, 3, 13, 28, 16, 127436), 'partition_number': 1, 'message_type': 'Broadcast', 'area_number': 0, 'command_id': 'TOUCHPAD'}
2018-02-03 13:28:16,384 concord DEBUG {'display_text': '*TUE OCT 17\n07:00 AM P1\n', 'timestamp': datetime.datetime(2018, 2, 3, 13, 28, 16, 384336), 'partition_number': 1, 'message_type': 'Broadcast', 'area_number': 0, 'command_id': 'TOUCHPAD'}
2018-02-03 13:28:16,384 concord DEBUG Sending message (retry=1) '022022'
2018-02-03 13:28:17,434 concord WARNING Resending message, attempt 2: '022022'
2018-02-03 13:28:18,192 concord DEBUG Handling command 0x02 EVENT_LOST, cmd_automation_event_lost
2018-02-03 13:28:18,444 concord DEBUG Handling command 0x01 PANEL_TYPE, cmd_panel_type
2018-02-03 13:28:18,444 concord DEBUG {'hardware_revision': 'G1', 'software_revision': 9302, 'panel_type': 'Concord', 'serial_number': 25362, 'is_concord': True, 'command_id': 'PANEL_TYPE'}
2018-02-03 13:28:18,445 concord WARNING Resending message, attempt 3: '022022'
2018-02-03 13:28:18,696 concord DEBUG Handling command 0x20 CLEAR_IMAGE, cmd_clear_image
2018-02-03 13:28:19,460 concord ERROR Unable to send message (timeout), too many attempts (3): '022022'
2018-02-03 13:28:19,619 _internal INFO * Running on http://0.0.0.0:5007/ (Press CTRL+C to quit)
2018-02-03 13:28:34,843 concord DEBUG Looping 20
2018-02-03 13:28:35,347 concord DEBUG {'display_text': '*TUE OCT 17\n07:01 AM P1\n', 'timestamp': datetime.datetime(2018, 2, 3, 13, 28, 35, 347829), 'partition_number': 1, 'message_type': 'Broadcast', 'area_number': 0, 'command_id': 'TOUCHPAD'}
2018-02-03 13:28:55,035 concord DEBUG Looping 40
2018-02-03 13:29:09,834 _internal INFO 127.0.0.1 - - [03/Feb/2018 13:29:09] "GET /command?cmd=arm&level=stay HTTP/1.1" 200 -
2018-02-03 13:29:09,917 concord DEBUG Sending message (retry=1) '054001000248'
2018-02-03 13:29:10,927 concord WARNING Resending message, attempt 2: '054001000248'
2018-02-03 13:29:15,211 concord DEBUG Looping 60
2018-02-03 13:29:35,416 concord DEBUG Looping 80
2018-02-03 13:29:35,456 concord DEBUG {'display_text': '*TUE OCT 17\n07:02 AM P1\n', 'timestamp': datetime.datetime(2018, 2, 3, 13, 29, 35, 456721), 'partition_number': 1, 'message_type': 'Broadcast', 'area_number': 0, 'command_id': 'TOUCHPAD'}
2

I think the display text means its at least reading the panel so thats good! lower down is where I tried to arm stay from another terminal.

[ghost]

Also, when I arm from the keypad itself, it will run pop up in the terminal immediately with what is showing on the keypad screen.

[belmendo]

Has anyone figured this out? Seeing same issue trying to "Refresh Dynamic State" using Indigo on OSX to talk to Concord 4.

Thanks!

[ghost]

I can’t remember exactly what I did, but I think it was reinstalling the code completely. Either that or something with the parity. I know I have had issues before with the panel due to the wrong parity setting (it’s supposed to be odd parity), but I think it’s preconfigured in this code.

I’d definitely try deleting it and reinstalling it completely through pip.