TinyGSM-SMS for Arduino/esp8266, KeypadInterface send LCD msg and support PC2550 keypad, KeybusReader fits on Uno

[kricon]

Added TinyGSM-SMS Arduino and ESP8266 examples:

• Tested on PC5020 and Arduino Uno/NodeMCU with SIM800L GSM module
• I was needed to drop baud rate to 9600, as on 115200 it wasn't communicating correctly with SIM800L module. It can be just on my module or 30cm long wires from ESP/Uno to SIM800L module was just too long, maybe it will work on some other baud rate in between, I don't know.
• Works and send SMS messages fine, but on Arduino it will often trigger "buffer overflow" when more messages is send at once, or when there's a lot of keybus activity. On esp8266 I didn't have any "keybus buffer overflow" issues.
• Based on ESP32 TinyGSM-SMS example by @jvitkauskas

PS: In wiring, Bell+ and COM/Aux- isn't a typo. Bell- triggers only in alarm state but Bell+ is always active and can provide 2-3A short term (from backup battery) as requied by SIM800L module.

KeypadInterface changes:

• Support for Fire, Program, Zone 7 and Zone 8 lights on DSC Classic PC2550 keypads
• Setting LCD messages according to printPanelMessages list with entering HEX input (starting with 0x) into serial console (which gets send on cmd 0x05/byte3).
• It doesn't fully match printPanelMessages list, but first dozen statuses seems right.
• Change function keys 1-5 with entering 0x70 - 0x74. Have in mind that setting will get saved but LCD message won't change.
• Change LCD keypad time by entering 0x2A (slight delay before LCD will ask to input data, as it tries to receive current date/time from panel and then timeout)
• Change LCD brightness/contrast/buzzer level by entering 0x29 and scrolling to desired setting then pressing just as you would do it from 6 menu.

KeybusReader changes:

• Redo the 0xC3 cmd used for dialer with more information (I've tested it with both phone line connected and disconnected)
• Started including messages of 0x8D, 0x94 and Module_0x94 commands used for module programming, as decoded in #188.
• Sketch now fit into Arduino, but for module program request/response messages it will show just basic info without additonal decoded data to save program space.

[taligentx]

Hi @kricon - this is still marked as being in "Draft" status, are there any other changes to make to this PR? I know it's been a while but I'd like to make sure your work is included in the next release, thanks!

[kricon]

Hi @taligentx ! Sorry that it took so long - life things got in, doing some housework... I need somebody to review TinyGSM-SMS examples as I'm not sure that dropping baud rate was right thing to do. Also I'm not sure if I choose good pins, the examples works fine (except "buffer overflow" thing on Arduino) but needs more testing and feedback before merging into master branch.

KeybusInterface/KeybusReader are now ready to be merged. I've started doing some 0x8D and 0x94 decoding locally but got stuck with nibbles and bitshifting, and with all requied checks I need to make (for different modules, versions, etc) it would be one hell of a mess, I'm sure that it can be made in more optimised way. I'll look into it when having some spare time.

I have some Teensy 3.1 boards laying around (they have Arduino IDE support with teensyduino), I will see and try to convert some examples onto it, atleast that's the plan. I don't have compatible ethernet module yet, just SIM800L and basic examples (local serial only) stuff. Better than nothing.

[taligentx]

Hi @kricon,

Sorry that it took so long - life things got in, doing some housework...

No worries at all, thanks for your work on this and all of your previous work, especially protocol decoding work can be very time consuming, merged! (but just now getting a chance to comment)

I need somebody to review TinyGSM-SMS examples as I'm not sure that dropping baud rate was right thing to do.

For TinyGSM-SMS, I'm fine with merging as-is because I don't have the hardware for testing and rely on folks who need to use these features to post any issues that crop up. It's great to have the examples in place for Arduino and esp8266.

I've started doing some 0x8D and 0x94 decoding locally but got stuck with nibbles and bitshifting, and with all requied checks I need to make (for different modules, versions, etc) it would be one hell of a mess

Thanks for the logs on those commands, especially 0x8D is extensive - it's great to see parts of the protocol for these modules. Also thanks for flagging those functions in dscKeybusPrintData.cpp to skip Arduino/AVR, it's been an interesting challenge to try and keep the KeybusReader sketch size small enough to fit on all platforms but at this point it's fair to take advantage of the esp8266, esp32, etc to decode more of the protocol.

I have some Teensy 3.1 boards laying around (they have Arduino IDE support with teensyduino), I will see and try to convert some examples onto it

More architectures are always welcome - it should mostly be a matter of setting up the timer interrupts in the library code and adding Teensy wherever there's currently code selecting for different architectures between AVR, esp8266, and esp32. From a quick look at Teensyduino, IntervalTimer should work to trigger dscDataInterrupt() in src/dscKeybusInterface.cpp. The example sketches ideally would be simple to update, just need updated documentation for whichever pins work best for wiring on that microcontroller and networking configuration.