Parasound Z-Tuner Rs232
ondrovic
Posts: 217
I am currently working on the feedback for a parasound z-tuner, but i am a little stuck atm. Everything seems to be working execpt you have to push the button to go to the preset twice for it to display the feedback correctly. Anyone had any success on this? Or any ideas on how to fix it?
i attached the source file
thanks for taking a look
Chris Ondrovic
i attached the source file
thanks for taking a look
Chris Ondrovic
0
Comments
From my little_bird(), you should expect to see a new ZTuner in not too long. The next version supposedly supports unsolicited feedback, and supposedly the RS-232 structure will be different. A module is supposedly in the works to be hopefuly released when the new ZTuner is out.
Thanks for the reply I will give that a shot when I get to the office in the morning. I will keep you posted.
Good to know about the new Ztuner we shall see about it features
Thanks again
Chris Ondrovic
I had to comment out the modules for it to compile, BTW.
The TEXT command only supports addresses up to 255. Try using ^TXT instead.
But you said you were getting feedback before? How can that bee if the TEXT command only supports addresses up to 255?
trying what you said about the ^TXT
still not getting the stations vars to populate
well that is just strange
i have 2 ztuners on this job and i switch over to the second one and it worked fine maybe my 1st tuner is fubared LOL thanks again
Okay . . . I was going to ask you to monitor the responses from the ZTuner, but you beat me to the punch. When the ZTuner freaks out, it's normally because strings were sent to it too quickly. There must be at least a 200ms delay between strings sent to the device. There seems to be two types of respones protocols in the ZTuner, which I've had to put a band-aid on my code to fix it.
If it's not sending you the documented protocl, it's more than likely sending you an INTEGER based protocol - much easier to parse. Here's the code I use when it flips out.
Since the ZTuner can send you "'1',CR" for different querry requests, you should keep track of what you asked it.
Of course there's variables and constants defined above the data_event, but this code block should be pretty straight forward. This code is closely based off of parsing the documented protocol, so thanks the Programming Master in the Chicago area for help with the documented prptocol parsing.
As you should already know, if you unplug it, and then power it back up - all will be fine.
One last thing - this code took maybe 10-20 minutes to write, so I'll be sending a hefty bill to all who use it.