bitfocus / companion-module-requests

Repository for tracking module requests
96 stars 10 forks source link

PTZ Camera AVer PTZ310, PTC310, DL10, DL 10 #789

Open vmax140 opened 2 years ago

vmax140 commented 2 years ago

Hello,

Can someone do camera control, first of all I mean presets using IP VISCA protocol?

Here are the control codes and specifications for the mentioned models:

AVer PTZ310 - https://www.averusa.com/pro-av/downloads/user-manual/PTZ310,330,310N,330N%20UM_20200316.pdf AVer PTC 310 - https://www.averusa.com/pro-av/downloads/user-manual/PTZ310,330,310N,330N%20UM_20200316.pdf DL10 - https://presentation.aver.com/DownloadFile.aspx?n=5577%7C5ED51453-145D-494F-AC59-9CAFD3A11F14&t=ServiceDownload DL 30 - https://presentation.aver.com/DownloadFile.aspx?n=5577%7C5ED51453-145D-494F-AC59-9CAFD3A11F14&t=ServiceDownload

AronHetLam commented 2 years ago

Visca over IP is available in two modules. I've used the PTZOptics one before, but thers also a Sony one. However, the Visca commands should be the same (at least for the PTZOptics one from quickly glancing over one of your links).

vmax140 commented 2 years ago

@AronHetLam, so, you think it will work for Aver cameras too (based on documentation with control codes that I attached before) ?

AronHetLam commented 2 years ago

Visca over IP should be the same across devices for all the common features (ptz, presets and so on), so yes.

However, i ran into an issue recently where some cameras need an additional header when using visca over IP, (which ptzoptics doesn't need, but probably should implement).

The AVer manual doesn't mention the header, but it's in the DL manual.

Give it a try with both modules. I've only used the ptzopticsone, which I assume doen't have the header. Maybe the Sony one does.

vlada140 commented 1 year ago

I think some of existing module will work, but only for basic commands like move, presets, zoom and so on. Aver cameras have Auto framing, Auto tracking and similar features. That features don't have for PTZ optics and other modules.

ExtremGladiator commented 1 year ago

I need also the possibility to turn on and off the Auto tracking from the Aver. The Sony Visca model work well for PTZ and Presets.

vlada140 commented 1 year ago

I need also the possibility to turn on and off the Auto tracking from the Aver. The Sony Visca model work well for PTZ and Presets.

Which camere do you use?

ExtremGladiator commented 1 year ago

I use the AVer ptc310h

vlada140 commented 1 year ago

I use the AVer ptc310h

So, Sony Visca codes work for you? Did you try other modules? For auto tracking on/off you can add custom command.

ExtremGladiator commented 1 year ago

How i can ad this command? :)

vlada140 commented 1 year ago

How i can ad this command? :)

First I need to know which module do you use and did you try other modules? Becouse I think in some modules have auto tracking on/off.

UrbelTap commented 1 year ago

You can use Presets to turn ON and OFF the Autotrack Function (and other Functions). Default: Preset 168= ON, 169=Off. You can change this on the Web UI off the Camera (System -> VISCA Costumized Function)

ExtremGladiator commented 1 year ago

I use the Sony visca Modul. What Modul have this Tracking on/off button?

@UrbelTap i will try this :)

Colbix commented 1 year ago

I've tried the Aver TR323NV2 which uses the same VISCA commands as the other models. Current environment for testing, MacOS with Bitfocus 2.4.2. I tried both the Sony and PTZOptics module.

For the Sony module it indicated a successful connection however the presets didn't function with pan/tilt as my test buttons. PTZOptics indicated an error while trying to connect so I wasn't able to test the button configuration.

I used PacketSender to send VISCA commands and found the camera does need the IP packet header^1 for it to work. ie: 01 00 00 09 00 00 00 00 for command.

Colbix commented 1 year ago

I switched to using Bitfocus Companion v3.0 beta and decided to develop the Aver module[^1]. I've performed testing on the TR323NV2 with success of most features in Windows 10 and MacOS. To use the repo you'll need to use Bitfocus Companion v3 and follow the module development wiki[^2] to create the needed associated files and environment.

You won't need a git or Visual Studio Code if you don't plan to develop any further. Just having Node.js and fnm should be enough. I used Windows 10 as my dev environment and powershell to execute the commands from the wiki.

[^1]: Aver Visca over IP [^2]: Companion Module Wiki

Colbix commented 1 year ago

The module has been added to the Bitfocus repository and renamed to Aver PTZ[^1].

[^1]: Aver PTZ

Colbix commented 1 year ago

For me Sony visca works (Dl30 and Cam540). Does your module have presets for features like auto tracking, zone mode etc?

Yes, Aver follows the VISCA protocol and I basically added what was included with the Aver documentation. So ai tracking and mode control such as zone, presenter, and hybrid have been added. I've also included the ability to add your own custom commands.

Edit: To clarify the features are available however they are not set to the presets. A preset is just a shortcut to minimize button configuration. I considered the features required no significant configuration and to leave adding the buttons to the user. I can add the features as presets fairly easy if needed.

vmax140 commented 1 year ago

@Colbix , I cant find module on companion.

Colbix commented 1 year ago

@vmax140

@Colbix , I cant find module on companion.

I'm working on having it included into the searchable repository. In the mean time, and I checked today, it can still be used by downloading the repo as a zip file and install as a developer module described in the Companion module wiki linked previously.

My primary environment is Windows, so I'll describe a very basic setup in that context. The following presumes you've downloaded Companion version 3 stable or beta and installed NPM and YARN.

1) Download the Aver repo as a zip. 2) Create a folder called companion-module-dev. 3) Unzip the Aver repo into the companion-module-dev folder. 4) Run the Yarn command from the Aver repo folder which will download all the necessary files. 5) Run Companion and access the developer settings. 6) Change the Developer modules path in Companion to companion-module-dev folder. 7) The module should now show up in the Add Connection search area, Aver: PTZ.

Colbix commented 1 year ago

The module has been added as of 3.0.0+6017 released on 05Jul2023. Search for Aver in Add Connection.

vmax140 commented 1 year ago

Great! Thank you!

I tested it and it works for pan, tilt but I have Cam570 camera and it has audio tracking and there is no button for that. Also, there is no preset button for preset position. Can you add option to add custom commands so I can add for audio tracking and presets?

Colbix commented 1 year ago

When you create a button under Press Action, click add press action, select Preset. I didn't find a command for audio tracking but if you can locate the hex command for it let me know or provide a link to the document. Also there is a Custom Command where you can add any command in hex.

Edit: I was able to find an Aver support article ^1 for the audio command however I don't have a way to test. Try using a custom command with the audio command message to see if it works.

vmax140 commented 1 year ago

I will test it and let you know if hex custom command works.

vlada140 commented 9 months ago

@Colbix, I tried Aver module but it works very well but Custom Command button dosent work. I tried pan, tilt, zoom etc but it dosent work. I need for audio tracking 8x01047D0400FF with space between and without. Can you add audio tracking button or show me how Custom Command works?

Colbix commented 9 months ago

@Colbix, I tried Aver module but it works very well but Custom Command button dosent work. I tried pan, tilt, zoom etc but it dosent work. I need for audio tracking 8x01047D0400FF with space between and without. Can you add audio tracking button or show me how Custom Command works?

@vlada140 For the custom command field it can contain spaces or no spaces. The x represents the camera ID number, typically it will be 1 for camera 1. For your example it would be 81 01 04 7D 04 00 FF . I've used custom command with the standard visca commands and it worked on my end.

I have a description in the repo for using an open source program where you can send commands directly to a device without the need for Bitfocus Companion. If you do use Packet Sender you'll need to include the packet header which is automatically included with the Aver module.