Hitachi projector status parsing
gregr
Posts: 54
I don't use a lot of Hitachi's, but was enticed because of the built-in TCP/IP ports.
But the protocol seems like a holdover from the 60's. The commands are verbose (13 bytes to do anything including on/off).
I can deal with that, but my difficulty is how do you parse the responses, which don't seem have any exclusivity. For example, the response for power on is "01 00". The response for cover error is "01 00".
Am I missing something? The Sanyo's that we normally use have responses which in addition to being human readable ASCII, are for the most part exclusive-very easy to parse.
I have set flags before on the Hitachi when requesting status, but this seems to be a kludgy way to do things.
Is there a better way to parse responses from the Hitachi's, or similar devices whose feedback is so generic?
Thanks much.
But the protocol seems like a holdover from the 60's. The commands are verbose (13 bytes to do anything including on/off).
I can deal with that, but my difficulty is how do you parse the responses, which don't seem have any exclusivity. For example, the response for power on is "01 00". The response for cover error is "01 00".
Am I missing something? The Sanyo's that we normally use have responses which in addition to being human readable ASCII, are for the most part exclusive-very easy to parse.
I have set flags before on the Hitachi when requesting status, but this seems to be a kludgy way to do things.
Is there a better way to parse responses from the Hitachi's, or similar devices whose feedback is so generic?
Thanks much.
0
Comments
I also queue all my strings to the projector. When I'm expecting a reply, I ensure that I do not send more strings until the first reply has been dealt with, or a reasonable timeout has occurred.
Roger McLean
Swinburne University