I was wondering if I could query what memory was recalled on a MLE on the Acuity. I know I can query for cross point and others, but I didn’t see memory listed as an option and using MEM ?:2 didn’t give me any result.
What Version of Acuity are you running? That was added in v7.1j(specific customer patch) v9.0a general release.
Confirmed in v9.2b..
Manually recalled the memories… Then sent the query command… Returned a response… Manually changed the memory again.. Repeat.
9.1i, guessing I was pulling an ID-10-T error… I’ll play around with it and if I can’t get it to work I’ll reach back out. Thanks for confirming it is a function Les!
Well I gave it another go with no success, tried out most of the other commands and got results just nothing for the memory query. Script as follows:
function callbackFunction(success, cmd, result, exception)
{
ogscript.debug(result);
}
rosstalk.sendMessage(%const[‘hosts’][‘ACUITY.host’]%, %const[‘hosts’][‘ACUITY.port’]%, ‘MEM ?:2’, callbackFunction);
If you just try the ? do you get anything? now ME specified?
We checked against version 9.2b so if you can look to plan for an upgrade that would be the version we would best be able to support this if there is a problem with it.
I believe we only pause if the question mark is at the end of the message.
Can you try using sendMessageWithResponse? It should allow you to pause and receive a response with a question mark in the middle.
I tried this:
rosstalk.sendMessageWithResponse(%const[‘hosts’][‘ACUITY.host’]%, %const[‘hosts’][‘ACUITY.port’]%, ‘MEM ?:2’, callbackFunction);
But that made Dashboard unhappy and it threw an exception.
And I can’t really push for an upgrade since this is just me playing with something on the side.
Originally posted by ****
Hi Mark,
Sorry for late reply.
The signature of sendMessageWithResponse is host, port, command, response terminator, callback
You are missing the response terminator, you should add ‘\r\n’ before the callback and the exception will go away
Thanks
Anand
No worries, appreciate the replies to begin with!
So the exception went away and instead I am getting read timed out instead. Replaced with commands I know work without the sendMessageWithResponse and still get the read timed out.
Did I need to add something to the (success, cmd, result, exception) too?
Originally posted by ****
Hi Mark,
Nope- that sounds like the switcher is not responding
I would consider trying Putty to connect to the switcher. Send the command over a ‘raw’ socket (in Putty) and see if/what it responds with
first, maybe try waiting on \n instead of \r\n in case it is just using a linefeed in its response
Thanks,
Anand
Hey Anand,
\n still gets read timed out. Putty gets the response like Les indicated it should.
Just so you know I do query the switcher regularly for XPT information, but like you indicated that statement ends in a ? and just uses the sendMessage.
Thanks for all the effort you are putting into this.
Originally posted by ****
Hi Mark,
Yes we are finally able to figure out whats the problem is!.
James suggested that when you sendmessage with response you have to manually add \r.
We have tested this with Les and seems to be working now!
Below is the code snippet for it.
function callback(success, sentData, resultString, exception)
{
ogscript.debug(resultString);
}
rosstalk.sendMessageWithResponse(‘172.16.11.11’, 7788, ‘MEM ?:2\r\n’, ‘\r\n’, callback);
Let us know how it goes.
Hi Anand,
Thank you all very much! Working perfectly now, sorry for the trouble, greatly appreciate all the effort.
I found another solution with Dashboard 9.2:
Using sendMessage with: mem ?:2:?
Adding the additonal question mark seemed to make the RossTalk work.
Sample Code:
rosstalk.sendMessage(acuity_ip, acuity_port), ‘mem ?:2:?’, function(success, cmd, result, exception){
//*** Display result in debug Window
ogscript.debug(result);
});
Hey Kurt!
That is very helpful to know, thanks for the update. remembering to put the return in properly gets me each time.