Vantage Controls Module & help
jjames
Posts: 2,908
Does anyone have the Vantage Module de-compiled, the AXS file. All there seems to be is the TKO in the InConcert area. I'm new to all this, so if anyone could help me out with the essentials in getting AMX talking with Vantage, that would be great. Just need to send out serial commands to Vantage from AMX.
Thanks in advance
Thanks in advance
0
Comments
You don't need the AXS source file for the module in order to communicate with and control the Vantage system. Most of the AMX (or manufacturer) modules posted on the InConcert site do not provide source code - only the binary compiled TKO or token file. While this is a pain for those that wish to customize the module, we don't have a lot of choice. AMX says that many of the manufacturers do not permit the source to be released (or for the external control protocol to be published).
You can however import the TKO token file into your Studio 1.2 or 2.2 project and then interface to the module for control purposes as described in the Interface Specification document. This document is typically included as part of the module package on the InConcert site. It describes the command strings to send to the control module as well as the feedback strings you can expect from it. The package also typically includes a sample touchpanel file as well as a main program sample with device definitions and a module declaration example. So, unless you absolutely require source code, build a project and incorporate the TKO file to do what you want to do.
AMX does not release the source code to their modules (although it would be great if they did.) All you need is the .tko file to get up and running. The module zip contains a file called VantageQ.doc which explains how to implement the AMX module.
If you want to talk to Vantage directly and bypass using the module completely then you will need the Vantage protocol.
Cheers,
Joe
With any NetLinx module, there is nothing preventing you from sending strings directly to the device, bypassing the module altogether, and likewise for processing feedback - as long as the module doesn't override commands when it sees something unexpected happening.
Isn't it best practice to use the Pass-Thru command vs. sending directly to the device when using a module? I'm thinking of cases where the module might be queuing commands, or polling on a timed basis, or might implement retries and a command direct to the device could produce undesirable side-effects.
Joe
Hi guys
What is exact string to send?
I tried
DATA_EVENT [dvVANTAGE]
{
ONLINE:
{
SEND_COMMAND dvVANTAGE, "'SET BAUD 19200,N,8,1 485 DISABLE'"
}
}
BUTTON_EVENT [dvTP_LIGHT,100]
{
PUSH:
{
SEND_COMMAND dvVANTAGE, "'VSW 1 67 1 1 [CR]'"
}
}
The command don't execute and NI seem don't send command on port where I connected my Vantage controler
I use NI3000 and Vantage CBox LE
Tanks for any clue
You'll need to set it up like so:
BUTTON_EVENT[dvTP_LIGHT,100]
{
PUSH:
{
SEND_STRING dvVANTAGE, "'VSW 1 67 1 1',13"
}
}
Tanks JJames
Tanks for quickly answer. I tried it and it's work nice
I'm begining in this world ( Vanatge and AMX) and I have somme little problems to understanding difference between strig and command
Regards
Denis