activelook / activelook-api-documentation Goto Github PK

i'm writing a web app and using the web bluetooth api. i'm able to connect to the device however i'm unable to write any text to the screen using the example from the api doc:

0xFF3700140098008000020F68656C6C6F203000AA
display text hello 0 at (152;128) (center of the screen) with direction 0, the font 2 and the color 15.

do i need to issue some config or layout commands before writing the text?

edit: sorry, i had a typo in the write characteristic uuid. send text commands works now.

• an option to 'not overwrite 0 bytes' when drawing an image would be great; that would allow composing images
• the imgStream (and possibly imgDisplay for 1bpp images) could follow the color settings
• specify a rotation of an image; it seems that this could be done with integer math without division: https://www.geometrictools.com/Documentation/IntegerBasedRotation.pdf

Use case: I'm trying to create a kind of navigation compass and it seems currently the only way is to stream the 1bpp image to the device. Composing it from several different images directly in the device could work much better.

How can one use a GIF animation file to display animation on the device? I'm using the iOS example app and SDK but there don't seem to be any animation examples? It would be very helpful if you could please a high level overview of how to achieve this? Or ideally, a full iOS implementation.

I have worked on the integration of ENGO smart glasses with ESP32 and I noted a few things related to the documentation:

1. Here I have a bit of a confusion. I am using these 16 bit UUIDs:

static BLEUUID GenericAccess_DeviceNameUUID((uint16_t)0x2a00);
static BLEUUID GenericAccess_AppearanceUUID((uint16_t)0x2a01);
static BLEUUID GenericAccess_PeripheralUUID((uint16_t)0x2A04);

instead of these 128 bit UUIDs as stated in the documentation:

00002A00-0000-1000-8000-00805F9B34FB
00002A01-0000-1000-8000-00805F9B34FB
00002A04-0000-1000-8000-00805F9B34FB

The 128 bit versions do not work, only the 16 bit do work. In general the BLE library for ESP32 that I am using can handle both 16 and 128 bit UUIDs and it works. So I am a bit confused.

2. The "0783b03e-8535-b5a0-7140-a304d2495cb7" UUID (ActiveLook® Commands Interface) in the documenation has a "0x" in front of it. I think this is not consistent with a policy where the 16 bit UUIDs do have "0x" and the 128 bit do not have.

Can a Jetson Nano single board computer send information to sports glasses (e.g. Engo 2) using the Activelook APIs?
thanks

I want to use the built-in fonts in graphical tools to make UI mockups and designs. Is there a TTF/OTF version of the built-in fonts that you can provide?