Please enable JavaScript.
Coggle requires JavaScript to display documents.
Troubleshootinng (Philosophies (make the user self-sufficient, Extron…
Troubleshootinng
Philosophies
make the user self-sufficient
Extron should not be a bottleneck
make a control system solution, not just a product solution
event message emitter is the host itself
Event messages we want to see
Hardware
#
AV Products
like dataviewer and non-secure connections
Control Products
eBUS IO
TLPs
Program
GC/Automation
monitors
Macros
Drivers
User Trace
#
Control Script (print)
User stuff
usually wants to look at multiple devices at a time
Might troubleshoot across subnets or locally
Ways to see/get the message
different tools
locally, remotely (across subnets)
Emulation
data injection (both ways)
Short Term needs
Non Primary Controller Trace
TLPs
Secondary Controllers
eBUS
NAV
NBPs
Other AVInterface devices