Can't get control modules to work...

mrd · Post by **mrd** » Thu Jun 25, 2009 2:03 am

Has anyone been able to use the existing Visca.pm control module in 1.24? I can't seem to get it to work and also can;t seem to debug it very well. As far as I can tell the old issue of a missing perl load module isn;t the problem.

Any hints on how to set debugging in the Visca.pm module?

I should also point out that I am using the zmarch installed version of ZM.

zappen · Post by **zappen** » Thu Jun 25, 2009 3:43 pm

open zmcontrol.pl and change the DEBUG flag to 1, then try tail -f /tmp/zmcontrol.log and see the output while moving your camera.
i had problems with PTZ controls because of wrong speeds and bad permissions on the serial ports, some stty, a chmod 777 and a chmod a+w on them fixed it

mrd · Post by **mrd** » Thu Jun 25, 2009 5:14 pm

Can you be more specific about how to set the DEBUG parameter in the newer perl modules.

use ZoneMinder::Debug qw(:all);

I should also point out that the path where the control modules seems to have changed (at least on my zmarch install):

zmarch = /usr/share/perl5/site_perl/5.10.0/ZoneMinder/Control

1.23 Ubuntu = /usr/share/perl5/ZoneMinder/Control

I know that older versions of the control scripts had the option change the DEBUG value within the script as below, but it's different in the modules.

use constant DBG_ID => "zmctrl-ptel"; # Tag that appears in debug to identify source
use constant DBG_LEVEL => 1; # 0 is errors, warnings and info only, > 0 for debug

zappen · Post by **zappen** » Thu Jun 25, 2009 5:39 pm

sorry i meant open zmcontrol.pl and change the DEBUG bit to 1
*edited my prev post

mrd · Post by **mrd** » Thu Jun 25, 2009 6:24 pm

OK.. I'll give it a shot tonight an see if Ican get it to work.

mrd · Post by **mrd** » Fri Jun 26, 2009 10:27 pm

Well, I got the Visca.pm module to work and as it turns out I had both a camera problem and a cable problem. However, I am still not able to debug the module and there are issues that need to be fixed and features that need to be added that are specific to the EVI-D30. I can do all of this, but I need to understand how to run debugging on and where to view the Debug ("blah blah") statements in the code.

I've struggled with this for a long time and it sure would be nice to find out how it works so that I can be more productive here.

Thanks,
Michael