G3 keyboard issue
Darkside
Posts: 345
I have a G3 CA10 with f/w 5.11L connected to an NI3000 running f/w 3.21.254
On the panel I have a button that pops the onboard keyboard (KB), and I have a data_event for dvTouch to capture incoming KB strings. The data_event string: does not receive anything punched in on the KB, yet when the system boots and dvTouuch comes online, it does report the startup and wake string via this same string handler!
Line 92 (22:11:59):: This system TP sending text >> STARTUP <<
Upon testing, diagnostics shows
Line 100 (22:12:21):: String From [128:1:1]-[KEYB-TESTING]
Line 102 (22:12:21):: String From [33000:1:1]-[KEYB-TESTING]
yet the string handler sees nothing (send_string 0,"data.text")
Also, if I 'control a device' and send sleep or wake, the panel responds, diagnostics sees it, but the data_event string: doesn't.
Maybe there is a firmware issue I can't find...
If anyone had some input I would appreciate it..
On the panel I have a button that pops the onboard keyboard (KB), and I have a data_event for dvTouch to capture incoming KB strings. The data_event string: does not receive anything punched in on the KB, yet when the system boots and dvTouuch comes online, it does report the startup and wake string via this same string handler!
Line 92 (22:11:59):: This system TP sending text >> STARTUP <<
Upon testing, diagnostics shows
Line 100 (22:12:21):: String From [128:1:1]-[KEYB-TESTING]
Line 102 (22:12:21):: String From [33000:1:1]-[KEYB-TESTING]
yet the string handler sees nothing (send_string 0,"data.text")
Also, if I 'control a device' and send sleep or wake, the panel responds, diagnostics sees it, but the data_event string: doesn't.
Maybe there is a firmware issue I can't find...
If anyone had some input I would appreciate it..
0
Comments
With respect to "control a device", your AMX processor won't see the commands you're sending out, because all you're doing is... get this... controlling the device. You want "emulate a device" if you want to fake feedback FROM the device TO the processor.
Thanks Dave, I hadn't changed that back to the virtual after some other testing - therefore the string handler would see the 'startup' and 'wakeup' strings clearly because the combine had not occured yet. Threw me off the trail I must admit.
Appreciate your help guys..
Note to self...stop programming in th middle of the night :-)