Vaddio ProductionView lockup

Kenny

Has anyone controlled a ProductionView via RS232?
The unit my customer has keeps locking up for no reason. It seems that when the unit is not ready for a command and gets anything via RS232 it will lockup.
I can't query the unit to see if it is ready because it will lockup if it's not ready.
Vaddio TS is of no help. They have tried to help and are excellent at doing everything they can but so far nothing has helped.

Hedberg

I had a similar experience with a Vaddio. It's been quite a while and I don't recall the exact sequence, but certain interactions with the physical device and with RS232 could lock it up and would require a hard reset of the device itself. I seem to recall that it goes through an initialization sequence when it's powered up and that sending RS232 commands during that sequence, or when it is unexpected by the Vaddio, will lock it up. I don't believe there is a fix for this. If your problem is the same as what I saw, it's a Vaddio feature.

Kenny

That is exactly my problem.
My client is furious with me since it works fine unless he uses the AMX system.
I just hope someone is able to reply with an actual fix. Vaddio seems to want to not addess this as a problem.

Colzie

I concur.

My solution is a workaround, but does the job. The Vaddio spits out a string with 'Power On' in it when it turns on...I wait 1 minute after I see this before I send anything to it. Similarly, 'Power Off' is sent when it is turning off - I only wait 10 seconds after seeing this string.

Also noteworthy, the SuperJoystick terminates some data strings with "$0D, $0A" and some with "$0A, $0D". Yay!

Hope this helps.

filpee

As mentioned the Vaddio WILL lockup its rs232 port if you send some data during its initialization sequence.

All you can do is work around it. My module prevents strings from being sent to it until it receives a command after the init (from memory its "Preview On" or something to that effect).

I'm not 100% convinced that this is the only time the port locks up but I have been unable to replicate a port lockup at any other time.



Yes. Watch the line terminations.

Kenny

Unfortunately my customer likes to turn the unit on and off. So he will try to use the AMX to control it and finds that he has turned the unit off then he turns it on tries to use the AMX again.
I have noticed that when the power on command is sent from the Vaddio is still needs a few seconds before it is really ready.

filpee

active (find_string(lower_string(strCamBufferTmp),"'power off',$0a,$0d,$3e",1)):{
	vaddioPowerUp = false;
	validCmd = true;
}
active (find_string(lower_string(strCamBufferTmp),"'power on',$0a,$0d,$3e",1)):{
	vaddioPowerUp = true;
	validCmd = true;
}
active (find_string(lower_string(strCamBufferTmp),"'display preview',$0a,$0d,$3e",1)):{
	vaddioPowerUp = false;
	validCmd = true;
}

If vaddioPowerUp = true then comms is disabled (or buffered, depends on the command)

Its not bulletproof but has reduced alot of the locking up errors.

kbeattyAMX

Vaddio Protocol

I'm looking for the protocol for the ProductionView. Can anyone Help? Is the Vaddio still having lockup problems with the 232?

filpee

kbeattyAMX wrote: »

I'm looking for the protocol for the ProductionView. Can anyone Help? Is the Vaddio still having lockup problems with the 232?

You can get the protocol from the user manual. Just go to their website.

And yes I am still having problems but I think mine are heat related.

You can, without fail, lock up the data port by sending it something during its warmup phase.

Lawrieav

Vaddio ProductionView FX lockup

I found the most lockups occur with repeat manual focus near/far commands or sending strings when the unit is initialising. Worked around the initialisation lockups by storing the default preset in cam using the '6 in cam - 6 in unit' setting.

Has anyone found a firmware version that actually outputs 'Focus Manual' when toggling the Auto Focus button on the unit. The led display reads 'Focus Auto'/'Focus Manual' but the string output is always 'Focus Auto' ?? I've loaded 4 firmware versions and they all do the same.