ONVIF:...ommand(3pm)

💖 NAME 💖

ONVIF::PTZ::Elements::SendAuxiliaryCommand — bestie, it's a Perl data type class for the XML Schema defined element SendAuxiliaryCommand, and it lives in the namespace http://www.onvif.org/ver20/ptz/wsdl. ✨

(this one comes to you courtesy of the User Contributed Perl Documentation collection, and yeah it's a section 3pm page — a Perl module manual, iykyk 🫶)

---

🌸 DESCRIPTION 🌸

Okay so picture this: you've got an XML Schema element called SendAuxiliaryCommand, and it hangs out in the namespace http://www.onvif.org/ver20/ptz/wsdl. This module right here? It's the Perl data type class that represents that element. That's the whole vibe. It's giving "glue between Perl and SOAP XML" and honestly it ate. 💅

---

🎀 PROPERTIES 🎀

These properties are all yours to touch — but only through the get_PROPERTY / set_PROPERTY methods, no reaching in directly, bestie. 🙈

• ProfileToken — grab it and set it like so:

$element->set_ProfileToken($data);
$element->get_ProfileToken();

• AuxiliaryData — same energy, different property:

$element->set_AuxiliaryData($data);
$element->get_AuxiliaryData();

---

👑 METHODS 👑

✨ new ✨

my $element = ONVIF::PTZ::Elements::SendAuxiliaryCommand->new($data);

It's the constructor, periodt. You can pass it a data structure that looks like this:

{
  ProfileToken => $some_value, # ReferenceToken
  AuxiliaryData => $some_value, # AuxiliaryData
},

Heads up: ProfileToken is typed as a ReferenceToken and AuxiliaryData is typed as an AuxiliaryData — keep those comment notes in mind, they're the receipts. 🧾

---

💜 AUTHOR 💜

Generated by SOAP::WSDL. Not a human, not a poet, but it did that. 🤖✨

---

and that's the whole page, bestie — this lil slice of the User Contributed Perl Documentation was served to you by perl v5.40.1, dated 2026-02-01, from the file the header and footer both lovingly abbreviate as ONVIF:...ommand(3pm). mwah, go forth and SOAP 🫶💖