RPi 3 pre-built issues

[mflembeck]

I ran a continuity test on all the wires and they are good. i can telnet into the ad2pi at port 10000 and see the output messages coming off the panel (when i arm/disarm or pull the battery connection). So I went back into webapp setup and found that the configuration is not being saved on the ad2pi. The address had returned to 18. That also jibes with the time out for "saving device configuration" on the diagnostic page. Does that give you any sort of clue? It sounds like the ad2pi just isn't listening?

[kevin]

Please confirm you can go through manual configuration of the ad2pi through ser2sock by issuing a ! key and following the prompts - make sure to set the proper address and confirm if you can arm and disarm through ser2sock

[mflembeck]

I'm not sure exactly how to access ser2sock directly unless that is the interface accessed via telnet IP 10000? if that is the case, no commands (!\r, C\r, V\r, XXXX2, XXXX1, etc) are being responded to on the telnet interface. but, as reported above, i only receive unprompted status messages on the telnet interface.

[kevin]

Well, that's just the oddest thing I've ever seen - well, if you could email ad2usb@support.nutech.com we can certainly set up an exchange. Sorry for the hassle, just trying to rule as much out as possible so we don't end up in the same place with a new unit.

[mflembeck]

Really appreciate your help. Given your statistics (no failures), and the newness of the RPI 3 operating over wifi, it seems like something in the receive end of the serial interface (either hardware or software) on the Pi would more likely be at fault. The Pi in turn is not passing data to the ad2pi, but receiving ok. I'm not a unix guru (yet), but would there be a way to see what the Pi thinks its receiving on ser2sock before it pushes it over to the ad2pi? BTW, i did put a logic analyzer on the DI/DO interface and see traffic from the ademco, but nothing going over from the ad2pi.

[kevin]

You can stop the ser2sock process as well as the gunicorn process (sudo /etc/init.d/gunicorn stop, sudo /etc/init.d/ser2sock stop) and then attach directly to the "serial port" with something like screen while ssh'd in. (sudo screen /dev/serial0 115200) - that should, if the ad2pi is hooked to the gpio correctly as well as the panel correctly give you direct access to the ad2pi. If you are unable to issue commands to the pi from the terminal directly, then it is likely the ad2pi, if not, something else is going on - and would definitely like you to email support and perhaps give access to the system to me or another available engineer on monday to investigate via TeamViewer or other remote access program.

[mflembeck]

sounds good. i'll try that and then email support. thanks very much.

[mflembeck]

Tried your suggestion. SSH'ed into the pi via wifi from my Mac. Stopped gunicorn and ser2sock. Started screen and tried to send some commands (!, C, =, V) to no avail. Sending email to support now. Thanks again for your patience in working through this with me.

[mflembeck]

Tried using your contact us page to email for additional support help, but, alas, the page responds that it is unable to verify i am a human. i'm thinking, therefore i am!

[kevin]

There should be a captcha there - you may have to enable scripts on the page to enable it. Anyway, it's equivalent to emailing ad2usb@support.nutech.com so just send an email there and you'll get a ticket created - leave your phone number and on Monday I'll call you and we'll see what we can do and then replace the unit if we have to.

Also, in the ticket it would be helpful if you attached pictures of all connections to the panel and ad2pi as well as how the pi is connected to the ad2pi just to be sure.