Customer Options in the customer record have been moved.

 The optical processing options in the customer record have been moved to a new screen tab. This is to allow even more options to b e added in the future.

RFID

 There is a new module which will act as a bridge between RFID from Nordic and Annapurna.

This means that a RFID tag can be placed in a tray and when the tray is presented near the scanner then a message is sent which is picked up the new module. In turn, this is created into a tracking message as though the tray had been scanned by a barcode scanner.  Different RFID bridges can be set to indicate different Annapurna status points.

VCADevice over a VPN

 It is now possible to run Annapurna and send OMA files over a VPN to a copy of VCADevice in an external location for edging.

Tracers supported

 From time to time, e are asked what tracing formats are supported. This summarises:

Format.

There are 3 formats that we support.

OMA/VCA - preferred

Nidek

Hoya

If it is a Nidek or a Hoya tracer then it is necessary to check if  the tracer is set to the bespoke format.

OM/VCA format is preferred as that is the format that is used to transfer trace data to other systems so the Nidek and Hoya formats are converted. It is better to get the data in this format to avoid any risk of potential data loss in the conversion.

Communication.

Serial

Ethernet

USB Driver

Serial

This can be either a serial cable or more likely a serial to USB convertor at the PC end. Both of these 

Ethernet.

This is a connection over the LAN. There are two methods, where the tracer is the 'server/host' or the PC is. Which depends on the tracer manufacturer.

USB.

This requires a USB driver to be installed. Currently there is only a Hoya driver provided.

The default is OMA/VCA over Serial communication.

SF6 Option details

 There is an additional CSV file that can be used to set options requirements for the SF6 catalogue. On the SLZLang / SF6 tab there is a new link SF6 Option Details.  This is in version 2.70.

If this is clicked then a CSV file is opened with various columns for the information that SF6 require. Earlier versions made an educated guess on the values based on the treatment type and description.

PC going to sleep and MySQL 'gone away'

 There have been a number of incidents recently where problems have been reported with the database such as MySQL gone away.  Investigation has linked these to when the PC goes to sleep and this causing a disconnection to the server which in turn causes the database to disconnect the PC.

This seems prevalent among laptop users taking their devices off to meeting rooms for video calls and resuming Annapurna session straight afterwards.  If this is relevant then please review the PC sleep settings and/or restart Annapurna after returning.

Using Lens and Treatment combination to specify a different lens.

This documentation describes how it is possible to allow a combination of lens and treatment to be converted to a lens that has the treatment included. An example is an order for a lens with a sunglass tint that is converted to a pre-tinted lens code.

The data is maintained in a CSV file. The CSV file is accessible from Data / Lens Data.  In the bottom right there is a “More…”.  Click on this and then click on “Pre-tint Conversion CSV”. The CSV file will then opened.

The combination is based on lens and the treatments. If a treatment such as coating, tint or UV is not be considered then it is left blank in the CSV file.

The conversion csv file is deployed when the lens data is deployed.