Home› AMX User Forum› NetLinx Modules & Duet Modules

Wolfvision Duet

jdcraigjdcraig Posts: 3
in NetLinx Modules & Duet Modules
I have come across a situation where the VZ9+ document cameras and EYE12 units are not being linked consistantly, there are times when the units are discovered and appear in the online tree and therefore respond to commands, but otherwise the units do not appear in the online tree and invariably do not respond to commands. Here is the code I use to initialize the link;

-Define Device
vdvDocCam201 = 41001:1:701 //
vdvDocCam203 = 41002:1:701 // The virtual device use for communication between the COMM module
vdvDocCam207 = 41003:1:701 // interface and User Interface (UI) module interface
vdvDocCam300 = 41004:1:701 //

-Define Variable
// Touch panel (UI) module
DEFINE_MODULE 'WolfVision_VZ-9plus_UI' ui201(vdvDocCam201, nBtns, nLvls, dv201TP3)
DEFINE_MODULE 'WolfVision_VZ-9plus_UI' ui203(vdvDocCam203, nBtns, nLvls, dv203TP3)
DEFINE_MODULE 'WolfVision_VZ-9plus_UI' ui207(vdvDocCam207, nBtns, nLvls, dv207TP3)
DEFINE_MODULE 'WolfVision_VZ-9plus_UI' ui300(vdvDocCam300, nBtns, nLvls, dv300TP3)

-Define Start
DYNAMIC_APPLICATION_DEVICE(vdvDocCam201, DUET_DEV_TYPE_DOCUMENT_CAMERA, 'WolfVision VZ')
DYNAMIC_APPLICATION_DEVICE(vdvDocCam203, DUET_DEV_TYPE_DOCUMENT_CAMERA, 'WolfVision VZ')
DYNAMIC_APPLICATION_DEVICE(vdvDocCam207, DUET_DEV_TYPE_DOCUMENT_CAMERA, 'WolfVision VZ')
DYNAMIC_APPLICATION_DEVICE(vdvDocCam300, DUET_DEV_TYPE_DOCUMENT_CAMERA, 'WolfVision VZ')

-DATA_EVENT[vdvDocCam203]
{
ONLINE:
{
Send_Command vdvDocCam203,"'PROPERTY-IP_Address,10.242.212.104'"
Send_Command vdvDocCam203,"'reinit'"
}
}

Any insight to this would be much appreciated, the clients are not impressed when they choose document camera and the touch panel controls get no responce from the document camera. And yes I have debugged and watched the button codes get passed in and get lost as the code attempts to hand off to the duet module.

Thanks

JD
ACE MCSA VCP
Chemeketa College

Comments

  • Joe HebertJoe Hebert Posts: 2,159
    jdcraig wrote: »
    -DATA_EVENT[vdvDocCam203]
    {
    ONLINE:
    {
    Send_Command vdvDocCam203,"'PROPERTY-IP_Address,10.242.212.104'"
    Send_Command vdvDocCam203,"'reinit'"
    }
    }
    Shouldn't it be REINIT not reinit? I haven't used this device before but the DUET modules I've seen use all caps for that command.
  • ericmedleyericmedley Posts: 4,177
    jdcraig wrote: »
    I have come across a situation where the VZ9+ document cameras and EYE12 units are not being linked consistantly, there are times when the units are discovered and appear in the online tree and therefore respond to commands, but otherwise the units do not appear in the online tree and invariably do not respond to commands. Here is the code I use to initialize the link;

    -Define Device
    vdvDocCam201 = 41001:1:701 //
    vdvDocCam203 = 41002:1:701 // The virtual device use for communication between the COMM module
    vdvDocCam207 = 41003:1:701 // interface and User Interface (UI) module interface
    vdvDocCam300 = 41004:1:701 //

    -Define Variable
    // Touch panel (UI) module
    DEFINE_MODULE 'WolfVision_VZ-9plus_UI' ui201(vdvDocCam201, nBtns, nLvls, dv201TP3)
    DEFINE_MODULE 'WolfVision_VZ-9plus_UI' ui203(vdvDocCam203, nBtns, nLvls, dv203TP3)
    DEFINE_MODULE 'WolfVision_VZ-9plus_UI' ui207(vdvDocCam207, nBtns, nLvls, dv207TP3)
    DEFINE_MODULE 'WolfVision_VZ-9plus_UI' ui300(vdvDocCam300, nBtns, nLvls, dv300TP3)

    -Define Start
    DYNAMIC_APPLICATION_DEVICE(vdvDocCam201, DUET_DEV_TYPE_DOCUMENT_CAMERA, 'WolfVision VZ')
    DYNAMIC_APPLICATION_DEVICE(vdvDocCam203, DUET_DEV_TYPE_DOCUMENT_CAMERA, 'WolfVision VZ')
    DYNAMIC_APPLICATION_DEVICE(vdvDocCam207, DUET_DEV_TYPE_DOCUMENT_CAMERA, 'WolfVision VZ')
    DYNAMIC_APPLICATION_DEVICE(vdvDocCam300, DUET_DEV_TYPE_DOCUMENT_CAMERA, 'WolfVision VZ')

    -DATA_EVENT[vdvDocCam203]
    {
    ONLINE:
    {
    Send_Command vdvDocCam203,"'PROPERTY-IP_Address,10.242.212.104'"
    Send_Command vdvDocCam203,"'reinit'"
    }
    }

    Any insight to this would be much appreciated, the clients are not impressed when they choose document camera and the touch panel controls get no responce from the document camera. And yes I have debugged and watched the button codes get passed in and get lost as the code attempts to hand off to the duet module.

    Thanks

    JD
    ACE MCSA VCP
    Chemeketa College

    Nothing seems obvious in the code presented. I suppose one thing might be that typically the DEFINE_MODULE statements goe just prior to the DEFINE_EVENT section rather than below the DEFINE_VAR section where you have it. However, since NS doesn't mind having nested DEFINE_Whatever statements it might be okay.

    You might try moving them and see if it's happier.

    I didn't see any code for the other Wolfvisions. Do they have different IPs and if so, what are they and where are they handled in code?
  • jdcraigjdcraig Posts: 3
    Improving but not totally fixed...

    I changed the 'reinit' to 'REINIT' as suggested by Joe Hebert and it did not seem to make a difference, then I added the lines;
    // WolfVision Visualizer (COMM) module
    DEFINE_MODULE 'WolfVision_VZ_Comm_dr2_0_0' comm201(vdvDocCam201, dvVis201)
    DEFINE_MODULE 'WolfVision_VZ_Comm_dr2_0_0' comm203(vdvDocCam203, dvVis203)
    DEFINE_MODULE 'WolfVision_VZ_Comm_dr2_0_0' comm207(vdvDocCam207, dvVis207)
    DEFINE_MODULE 'WolfVision_VZ_Comm_dr2_0_0' comm300(vdvDocCam300, dvVis300)
    according to Wolfvision instructions these lines are only needed when connected via serial port. All of the units being controlled by the NI4100 are working again, however the units being controlled by the NI3100 are still not loading. The environment here is a workspace with 2 systems.
    0:1:700 (NI4100) 1st floor control 5 rooms
    0:1:701 (NI3100) 2nd/3rd floor control 2.5 rooms and 1 respectivly
    1 module instance per room, each controller runs core code virtually identical, with unique interface code to match room configuration. I should also mention that I also found that the comm modules need to be before the UI modules.
    e.g.;
    0:1:700 code excerpt
    (***********************************************************)
    (* SUBROUTINE/FUNCTION DEFINITIONS GO BELOW *)
    (***********************************************************)
    (* EXAMPLE: DEFINE_FUNCTION <RETURN_TYPE> <NAME> (<PARAMETERS>) *)
    (* EXAMPLE: DEFINE_CALL '<NAME>' (<PARAMETERS>) *)
    DEFINE_MODULE 'WolfVision_VZ_Comm_dr2_0_0' comm101(vdvDocCam101, dvVIS101) (****************************************)
    DEFINE_MODULE 'WolfVision_VZ_Comm_dr2_0_0' comm102(vdvDocCam102, dvVIS102) (* *)
    DEFINE_MODULE 'WolfVision_VZ_Comm_dr2_0_0' comm103(vdvDocCam103, dvVIS103) (* WolfVision Visualizer (COMM) module *)
    DEFINE_MODULE 'WolfVision_VZ_Comm_dr2_0_0' comm106(vdvDocCam106, dvVis106) (* *)
    DEFINE_MODULE 'WolfVision_VZ_Comm_dr2_0_0' comm115(vdvDocCam115, dvVIS115) (* *)
    DEFINE_MODULE 'WolfVision_VZ_Comm_dr2_0_0' comm115B(vdvDocCam115B, dvVIS115B)
    (****************************************)
    DEFINE_MODULE 'WolfVision_VZ-9plus_UI' ui101(vdvDocCam101, nBtns, nLvls, dv101TP3) (********************************)
    DEFINE_MODULE 'WolfVision_VZ-9plus_UI' ui102(vdvDocCam102, nBtns, nLvls, dv102TP3) (* *)
    DEFINE_MODULE 'WolfVision_VZ-9plus_UI' ui103(vdvDocCam103, nBtns, nLvls, dv103TP3) (* Touch panel (UI) module *)
    DEFINE_MODULE 'WolfVision_VZ-9plus_UI' ui106(vdvDocCam106, nBtns, nLvls, dv106TP3) (* *)
    DEFINE_MODULE 'WolfVision_VZ-9plus_UI' ui115(vdvDocCam115, nBtns, nLvls, dv115TP3) (* *)
    DEFINE_MODULE 'WolfVision_VZ-9plus_UI' ui115B(vdvDocCam115B, nBtns, nLvls, dv115TP3) (********************************)

    (***********************************************************)
    (* STARTUP CODE GOES BELOW *)
    (***********************************************************)
    DEFINE_START
    DYNAMIC_APPLICATION_DEVICE(vdvDocCam101, DUET_DEV_TYPE_DOCUMENT_CAMERA, 'WolfVision VZ')
    DYNAMIC_APPLICATION_DEVICE(vdvDocCam102, DUET_DEV_TYPE_DOCUMENT_CAMERA, 'WolfVision VZ')
    DYNAMIC_APPLICATION_DEVICE(vdvDocCam103, DUET_DEV_TYPE_DOCUMENT_CAMERA, 'WolfVision VZ')
    DYNAMIC_APPLICATION_DEVICE(vdvDocCam106, DUET_DEV_TYPE_DOCUMENT_CAMERA, 'WolfVision VZ')
    DYNAMIC_APPLICATION_DEVICE(vdvDocCam115, DUET_DEV_TYPE_DOCUMENT_CAMERA, 'WolfVision VZ')
    DYNAMIC_APPLICATION_DEVICE(vdvDocCam115B, DUET_DEV_TYPE_DOCUMENT_CAMERA, 'WolfVision VZ')
    DEFINE_EVENT
    DATA_EVENT[vdvDocCam101]
    {
    ONLINE:
    {
    Send_Command vdvDocCam101,'PROPERTY-IP_Address,10.242.212.65'
    Send_Command vdvDocCam101,"'REINIT'"
    }
    }
    ...
    DATA_EVENT[vdvDocCam102]
    {
    ONLINE:
    {
    Send_Command vdvDocCam102,'PROPERTY-IP_Address,10.242.212.66'
    Send_Command vdvDocCam102,"'REINIT'"
    }
    }
    ...
    DATA_EVENT[vdvDocCam103]
    {
    ONLINE:
    {
    Send_Command vdvDocCam103,'PROPERTY-IP_Address,10.242.212.67'
    Send_Command vdvDocCam103,"'REINIT'"
    }
    }
    ...
    DATA_EVENT[vdvDocCam106]
    {
    ONLINE:
    {
    Send_Command vdvDocCam106,'PROPERTY-IP_Address,10.242.212.68'
    Send_Command vdvDocCam106,"'REINIT'"
    }
    }
    ...
    DATA_EVENT[vdvDocCam115]
    {
    ONLINE:
    {
    Send_Command vdvDocCam115,'PROPERTY-IP_Address,10.242.212.69'
    Send_Command vdvDocCam115,"'REINIT'"
    }
    }
    DATA_EVENT[vdvDocCam115B]
    {
    ONLINE:
    {
    Send_Command vdvDocCam115B,'PROPERTY-IP_Address,10.242.212.95'
    Send_Command vdvDocCam115B,"'REINIT'"
    }
    }
    ...

    0:1:701
    code is the same, other than room numbers and IP addresses being different.

    JD
    ACE MCSA VCP
  • Joe HebertJoe Hebert Posts: 2,159
    jdcraig wrote:
    All of the units being controlled by the NI4100 are working again, however the units being controlled by the NI3100 are still not loading.
    Is the DUET memory partition the same on both the NI-4100 and NI-3100?
    If you have more DUET modules in the NI-3100 than the NI-4100 you may need a bigger DUET memory partition.
  • jdcraigjdcraig Posts: 3
    Less

    The NI3100 is only handling 4 units while the NI4100 is handling 6 units.
    The code shown in my most recent post is a sample off the NI4100 1st floor controller.

    JD
  • Joe HebertJoe Hebert Posts: 2,159
    If you are running the same code on both the NI-4100 and the NI-3100 it sure sounds like it may be a memory issue.
    The DUET partition on the NI-3100 is big enough?
Sign In or Register to comment.