Multiple modules
Ahmed
Posts: 4
Dear All,
Have a nice day.
We are facing a big problem now when finalizing our code, firstly we can control each device by the module downloaded from AMX website.
When we try to put two modules in the main code we have a conflict between each module’s variables.
Example:
For Cisco VC:
DEFINE_VARIABLE
DEV vdvDev[] = {vdvCiscoC60}
DEV vdvDev4[] = {vdvCiscoC60,vdvCiscoC602,vdvCiscoC603,vdvCiscoC60 4}
//
// CURRENT DEVICE NUMBER ON TP NAVIGATION BAR
INTEGER nCiscoC60 = 1
//
// DEFINE THE PAGES THAT YOUR COMPONENTS ARE USING IN THE
// SUB NAVIGATION BAR HERE
INTEGER nVideoConferencerPages[] = { 1 }
INTEGER nDialerPages[] = { 2 }
INTEGER nCameraPages[] = { 3,4,5 }
INTEGER nPhonebookPages[] = { 6 }
INTEGER nPowerPages[] = { 1 }
INTEGER nSourceSelectPages[] = { 8 }
INTEGER nVolumePages[] = { 9 }
INTEGER nMenuPages[] = { 10,11,12 }
INTEGER nModulePages[] = { 13 }
For Samsung Screen:
DEV vdvDev[] = {vdvSamsungME46B,vdvSamsungME46B_PIP}
//
// CURRENT DEVICE NUMBER ON TP NAVIGATION BAR
INTEGER nSamsungME46B = 1
//
// DEFINE THE PAGES THAT YOUR COMPONENTS ARE USING IN THE
// SUB NAVIGATION BAR HERE
INTEGER nDisplayPages[] = { 1,2,3 }
INTEGER nLampPages[] = { 7 }
INTEGER nSourceSelectPages[] = { 8 }
INTEGER nVolumePages[] = { 9 }
INTEGER nModulePages[] = { 12 }
INTEGER nTunerStationPages[] = { 10 }
Regarding above example we have some questions to support us in our code:
• Should we define all this variables or we can ignore?
• If no, As you see from above example that (DEV vdvDev[] , nVolumePages[] , ….) has two definitions which is not acceptable. How to solve this conflict to make both modules working well?
• Also what is the meaning of (CURRENT DEVICE NUMBER ON TP NAVIGATION BAR - DEFINE THE PAGES THAT YOUR COMPONENTS ARE USING IN THE SUB NAVIGATION BAR HERE)? And what is their effect in the code and TPDesign?
• In the TPDesign example touchpanel which is downloaded with the module, what is navigation and sub navigation bars?
And what is the channel & port codes for their buttons refer to? (Cisco C60 button in Navigation bar ‘1:500’ – Volume in Sub navigation bar ‘1:528’ - …..)
• What is the include file “componentInclude file” which is exist in all modules? Can we rename this files to get rid of the conflict?
• Also if we have two screens all we do is defining them in ‘Define Device’ and add Communication modules for both of them, or must we define this variables twice?
• Is there any technical papers describe the module components and the effect of any change? (as we see from many modules they have the same form, description, variables and components)
Waiting for your fast reply ASAP.
Best regards,,,
Have a nice day.
We are facing a big problem now when finalizing our code, firstly we can control each device by the module downloaded from AMX website.
When we try to put two modules in the main code we have a conflict between each module’s variables.
Example:
For Cisco VC:
DEFINE_VARIABLE
DEV vdvDev[] = {vdvCiscoC60}
DEV vdvDev4[] = {vdvCiscoC60,vdvCiscoC602,vdvCiscoC603,vdvCiscoC60 4}
//
// CURRENT DEVICE NUMBER ON TP NAVIGATION BAR
INTEGER nCiscoC60 = 1
//
// DEFINE THE PAGES THAT YOUR COMPONENTS ARE USING IN THE
// SUB NAVIGATION BAR HERE
INTEGER nVideoConferencerPages[] = { 1 }
INTEGER nDialerPages[] = { 2 }
INTEGER nCameraPages[] = { 3,4,5 }
INTEGER nPhonebookPages[] = { 6 }
INTEGER nPowerPages[] = { 1 }
INTEGER nSourceSelectPages[] = { 8 }
INTEGER nVolumePages[] = { 9 }
INTEGER nMenuPages[] = { 10,11,12 }
INTEGER nModulePages[] = { 13 }
For Samsung Screen:
DEV vdvDev[] = {vdvSamsungME46B,vdvSamsungME46B_PIP}
//
// CURRENT DEVICE NUMBER ON TP NAVIGATION BAR
INTEGER nSamsungME46B = 1
//
// DEFINE THE PAGES THAT YOUR COMPONENTS ARE USING IN THE
// SUB NAVIGATION BAR HERE
INTEGER nDisplayPages[] = { 1,2,3 }
INTEGER nLampPages[] = { 7 }
INTEGER nSourceSelectPages[] = { 8 }
INTEGER nVolumePages[] = { 9 }
INTEGER nModulePages[] = { 12 }
INTEGER nTunerStationPages[] = { 10 }
Regarding above example we have some questions to support us in our code:
• Should we define all this variables or we can ignore?
• If no, As you see from above example that (DEV vdvDev[] , nVolumePages[] , ….) has two definitions which is not acceptable. How to solve this conflict to make both modules working well?
• Also what is the meaning of (CURRENT DEVICE NUMBER ON TP NAVIGATION BAR - DEFINE THE PAGES THAT YOUR COMPONENTS ARE USING IN THE SUB NAVIGATION BAR HERE)? And what is their effect in the code and TPDesign?
• In the TPDesign example touchpanel which is downloaded with the module, what is navigation and sub navigation bars?
And what is the channel & port codes for their buttons refer to? (Cisco C60 button in Navigation bar ‘1:500’ – Volume in Sub navigation bar ‘1:528’ - …..)
• What is the include file “componentInclude file” which is exist in all modules? Can we rename this files to get rid of the conflict?
• Also if we have two screens all we do is defining them in ‘Define Device’ and add Communication modules for both of them, or must we define this variables twice?
• Is there any technical papers describe the module components and the effect of any change? (as we see from many modules they have the same form, description, variables and components)
Waiting for your fast reply ASAP.
Best regards,,,
0
Comments
Unfortunately, there is not enough information to accurately answer your questions. However you are in luck! Since you are working with an AMX module you can get all the help you need directly from tech support. Just give them a call during normal business hours and you'll be running in no time! Make sure to have your dealer ID handy when you call.