That is right, Greg. I am currently working on mTangoREST.server-rc4-0.1. In a few days it will be released.
Rebooting could actually fix the problem.
Regards,
That is right, Greg. I am currently working on mTangoREST.server-rc4-0.1. In a few days it will be released.
Rebooting could actually fix the problem.
Regards,
[quote]
Igor
That is right, Greg. I am currently working on mTangoREST.server-rc4-0.1. In a few days it will be released.[/quote]
That’s great. In parallel with your work , we’ve developped a TangoJS IMAGE component. It’s almost complete.
@SOLEIL, we don’t use TangoAccessControl. I would like to improve TangoRestServer and make it possible to use it without TangoAccesControl but still use PlainTextAuthConfiguration or LDAP Authentication to connect to the TangoRestServer.
Cool!
I have updated the code base for mTangoREST.server. So you can build and test it from source.
Just want to stress that image response is not a 2D matrix. It is a JSON object with a data array and width and height attributes.
{
"data":[213,228,207,115,227,137,54,...],
"width": 251,
"height": 251
}
Is this OK?
This is perfect. This JSON object is what I expected to receive.
Ok.
So I guess that before rebooting, the facade state was different, and this state was not handled correctly by the REST API.
Thanks
Jerome
Igor, thanks for the delivery of RC4.

Looks fantastic!
Hope you will present it on the next Tango meeting ![]()