Best Of
Re: communication between MUSE controller and NX-xxxx controller
I did a small sample to basically show the possibilities passing channel, level, string and command forth and back. Hope this will give a little idea about usage.
Re: Televic D-Cerno CUR Conferencer integration with Muse 2300
Televic D-Cerno CUR API example: to send a command to connect to Televic D-Cerno CUR from JavaScript (from iRidi):
connectCommand = {
typ: "Application", // Application type
nam: "DU", // Application name
ver: "1.01", // Application version
inf: "0", // Additional information
svr: 0 // Server flag (0 — client)
};
commandBody = JSON.Stringify(connectCommand);
header = "02:con0000029O00000C00000000000000";
fullCommand = header + ":" + commandBody;
IR.Log("SENDING connect command: "+fullCommand);
this.dev.Send([0x02, fullCommand, 0x03]);
And the answer will come:
☻02:rep0000020C00000O00000000000000:{
"sta": 0,
"inf": "Connected to D-Cerno",
"con": {
"typ": "D-Cerno",
"nam": "CU",
"ver": "0.12.02",
"svr": 0
}
}♥
The smiley at the beginning is 0x02, the heart at the end is 0x03. This is how the iRidi server emulator outputs to the console.
Bagunda
Re: communication between MUSE controller and NX-xxxx controller
I only know that there are some bigger new things in the pipe for Muse, next release I think will be to Infocomm
Re: communication between MUSE controller and NX-xxxx controller
in general this works, our solution center is running "hybrid". The existing parts of control still work on NetLinx, and the AV part we reworked to N2600 series is controlled by Muse with Automator, with interaction thru such Muse-generated NetLinx devices, to join the two controller worlds.
Let me see if I can do a little sample with NetLinx and Muse side.
Re: communication between MUSE controller and NX-xxxx controller
It's not possible to access the NX ports directly from Muse. So you may have at least to pass control and response between the NX device and the device created from the MU, it is not working without any programming on the NetLinx side.
Maybe this helps: from the NetLinx perspective, I imagine a MU NetLinx device more or less as kind of a "module" device, and in a NetLinx module, you have all options open to use channels, levels, strings and commands for your needs.
Re: Symetrix Module Request
By the naming, but being a .tko, I would say it is a Duet file used. You may check by Studio on the controller if you can find the related jar file.
Connect Studio to the controller, then Tools -> File Transfer -> Receive.
Her click "add", select "Receive non-system, JAR or XDD files", click "Add", then you will get listed any other file type on the controller loaded, that is not one of the direct options.
Maybe you can find here the "Symetrix_SymNet_dr3_0_0.jar" Module File.
Re: Symetrix Module Request
Something weird going on there. There use to be more modules. If you search for Manufacturer is 'Symetrix' you only get 2 devices, but if you also click in the 'Device Model' field, you can see the other devices that used to be there. So they are removed for some reason of something else went wrong. Probably need support from AMX for this
