1. Manuals
  2. Brands
  3. Christie Manuals
  4. Projector
  5. LW400
  6. Reference manual

Christie LW400 Reference Manual

Hide thumbs Also See for LW400:
Table of Contents

Advertisement

Quick Links

See also: User Manual
NetLinx Module Interface Specification
for a
Christie Digital
LW400 Projector
Also works with LX501/LW401/LWU421/
LX601i/LW551i/LWU501i

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the LW400 and is the answer not in the manual?

Questions and answers

Related Manuals for Christie LW400

Summary of Contents for Christie LW400

  • Page 1 NetLinx Module Interface Specification for a Christie Digital LW400 Projector Also works with LX501/LW401/LWU421/ LX601i/LW551i/LWU501i...

  • Page 2: Table Of Contents

    TABLE OF CONTENTS Introduction ..............................3 Overview ..............................3 Implementation ............................3 Channels ..............................4 Levels ................................. 4 Command Interface ............................ 6 String Feedback ............................8 Device Notes .............................. 9 Programming Notes ........................... 9 Adding Functions to Modules ........................9 Commands to the device ........................

  • Page 3: Introduction

    The COMM module translates between the standard interface described below and the LW400 serial protocol. It parses the buffer for responses from the LW400, sends strings to control the LW400, and receives commands from the UI module or telnet sessions.

  • Page 4: Channels

    // Place define_module calls to the very end of the define_start section. // Comm module DEFINE_MODULE 'Christie Digital_LW400_Comm' mdlLW400_APP(vdvLW400, dvLW400) Upon initialization the AMX Comm module will communicate with the Christie Digital LW400 and information will be exchanged. Channels The channels supported by the COMM module are listed below. These channels are associated with the virtual device(s) and are independent of the channels associated with the touch panel device.
  • Page 5 associated with the virtual device(s) and are independent of the levels associated with the touch panel device. Level Description Lamp-Hours used Professional Control Solutions LLC  3804 Parchment Circle  Henrico, VA  23233-7034 804-677-6794  info@professionalcontrolsolutions.com www.professionalcontrolsolutions.com...

  • Page 6: Command Interface

    Command Interface The UI module controls the LW400 via command events (NetLinx command send_command) sent to the COMM module. The commands supported by the COMM module are listed below. NOTE: AMX has not defined a standard API for LW400 devices.
  • Page 7 Allows user the capability of sending commands directly to the LW400 without processing by the NetLinx module. User must be aware of the protocol implemented by the unit to use this command. This gives the user access to features which may not be directly supported by the module.

  • Page 8: String Feedback

    String Feedback The NetLinx COMM module provides feedback to the User Interface module for LW400 changes via string events. The strings supported are listed below. String Description Reports the current aspect ratio. <value>: 1 = Normal (All modes) 2 = Wide (All modes) ASPECT=<value>...

  • Page 9: Device Notes

    Device Notes Commands implemented by this interface include those that are commonly used and shared between various LW400 devices. Several of the LW400 commands have been omitted and may be executed using the PASSTHRU command. A periodic poll will return the power state and the total number of hours used by the device. Should the LW400 shift into sleep mode, it will be automatically shifted back into power-on mode.

  • Page 10: Additional Feedback From The Device

    the device through the module. (The module documentation will indicate any processing that will be automatically done to the PASSTHRU string like checksum calculation.) Additional Feedback from the device The module documentation indicates what feedback is provided. If additional feedback is required, a CREATE_BUFFER for the device must be implemented in the user code to process the strings from the device manually.

Table of Contents