Anybody have any success in externally (via M1XEP ethernet) sending new rules to the M1G, similar to how you would use ElkRP2 for updating rules?
My use case is that I have a complex series of rules that change on a regular basis. I have a program I use that makes defining my requirements really easy, and it outputs all the rules necessary for the M1G to do it's magic. However, I'm still left with the tedious task of manually entering those rules. I was hoping to send those new rules directly to the M1G from my program.
So far I've tried:
- Looking at the serial protocol documentation for M1G, but no mention of managing the rules
- Opening the ElkAccts2.mdb file directly (Access in Office 365, as well as direct via ODBC) but get a permissions error that I've failed to figure out how to get around. Perhaps need a much older version of Access?
- Examining the export file format, but it is a long CSV file with tons of numbers and not obvious how to work with it
I've not yet attempted to monitor the serial connection between the XEP and M1G to see if I can "reverse engineer" the ElkRP2 protocol - but I guess that's an option, but would likely be more work than it's worth.
Any hints on how to break through on any of the above, or other ideas to do it? Or is this a dead-end with the M1G?
Thanks!
Chris
My use case is that I have a complex series of rules that change on a regular basis. I have a program I use that makes defining my requirements really easy, and it outputs all the rules necessary for the M1G to do it's magic. However, I'm still left with the tedious task of manually entering those rules. I was hoping to send those new rules directly to the M1G from my program.
So far I've tried:
- Looking at the serial protocol documentation for M1G, but no mention of managing the rules
- Opening the ElkAccts2.mdb file directly (Access in Office 365, as well as direct via ODBC) but get a permissions error that I've failed to figure out how to get around. Perhaps need a much older version of Access?
- Examining the export file format, but it is a long CSV file with tons of numbers and not obvious how to work with it
I've not yet attempted to monitor the serial connection between the XEP and M1G to see if I can "reverse engineer" the ElkRP2 protocol - but I guess that's an option, but would likely be more work than it's worth.
Any hints on how to break through on any of the above, or other ideas to do it? Or is this a dead-end with the M1G?
Thanks!
Chris