Virtual device ports in module.

From NetLinx Keyword Help

SET_VIRTUAL_PORT_COUNT
Lets the programmer override the default number of ports that a virtual device maintains.

By default every virtual device maintains the state of a single port (port 1).

Syntax:

SET_VIRTUAL_PORT_COUNT(DEV Device, INTEGER Count)

Parameters:

Device - the virtual device to modify.

Count - the number of ports that the specified virtual device should maintain.

Returns: None

Example:

SET_VIRTUAL_PORT_COUNT (dvVirtual,2) // 2 ports

With regards to TRANSLATE_DEVICE, set_virtual_port_count needs to be applied to the dynamic virtual device and then translate_device applied to each port on the virtual device pair.

Edge of the envelope is writing NetLinx programs with no defined devices and populating device arrays from configuration file data...

Yup - that's a thing :-)

@HARMAN_icraigie said:
Edge of the envelope is writing NetLinx programs with no defined devices and populating device arrays from configuration file data...

Yup - that's a thing :-)

Yep, it's the basis of CineTouch. Same for UI, Rooms, Users, features. All defined in data... the program is the same in every system, and the panels are the same for every room in every system... data rules.

Depending how or where its used you might have to also rebuild_event() after the SVPC. Normally its done in define start but not always. My memories of such things are very faded.

This is how I did it (in a module):

(vdvDevice is the virtual that's passed into the module)

DEFINE_DEVICE

vdvCam = DYNAMIC_VIRTUAL_DEVICE

DEFINE_FUNCTION fnBuildDeviceArray()
{
    STACK_VAR INTEGER nCount
    SET_VIRTUAL_PORT_COUNT(vdvDevice,PORT_COUNT)
    SET_VIRTUAL_PORT_COUNT(vdvCam,PORT_COUNT)
    FOR(nCount = 1; nCount <= PORT_COUNT; nCount++)
    {
    vdvCamArray[nCount] = vdvCam.NUMBER:nCount:vdvCam.SYSTEM
    TRANSLATE_DEVICE(vdvDevice.NUMBER:nCount:vdvDevice.SYSTEM,vdvCam.NUMBER:nCount:vdvCam.SYSTEM)
    }
    SET_LENGTH_ARRAY(vdvCamArray,PORT_COUNT)
    REBUILD_EVENT()
}

As '@JasonS' noted, using TRANSLATE_DEVICE can be a bit tricky. Still hoping for some explanation about this, like some internal AMX document that magically appears. Hint... it's all a bit trail and error now.

@vining said:
I believe if you do your SVPC in define_start or in a function called by define start with out any wait delays you don't need to rebuild the event table because the event tables aren't yet built but if you do it anywhere else in code after the event tables are built that's when you have to use rebuilt_event() otherwise you won't get what you want.

If any named element (device, channel, level, etc) referenced in an event trigger is not defined (DEFINE_DEVICE, DEFINE_CONSTANT, DEFINE_VARIABLE) the event table will not be built and REBUILD_EVENT is required.

This channel event never happens:

(***********************************************************)
(*               VARIABLE DEFINITIONS GO BELOW             *)
(***********************************************************)
DEFINE_VARIABLE
    volatile dev vdvTEST_3;

(***********************************************************)
(*                 STARTUP CODE GOES BELOW                 *)
(***********************************************************)
DEFINE_START
    vdvTEST_3 = 33003:1:0;

(***********************************************************)
(*                  THE EVENTS GO BELOW                    *)
(***********************************************************)
DEFINE_EVENT

channel_event[vdvTEST_3,0]
{
    on:
    {
    amx_log(AMX_ERROR,"'channel_event[',itoa(channel.device.number),',',itoa(channel.channel),']'");
    }
}