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. 

Storing Send-in frames in a defined bin location

 

Bin number for Send in frames.

This is a simple way to record a location for the frames that are received and are waiting for lenses to arrive.

In Settings / Job Entry / Frame Actions, tick “Ask for Bin on Send In Frames”.

In Order Entry, when the order is placed a question for the frame bin number is asked. This is usually done by having a set of small tags / barcodes with bin numbers on. One of these is taken from the free list of unused tags and entered. This number is then recorded on the order and can be printed on the layout.

The frame is then taken to the area and placed in the appropriate bin with the tag. The frame bin can also be seen in View Order.

When the lenses arrive, the receive program is used to record the lenses which will also show the frame bin.

The frame is matched to the lenses. The tag can then be returned to the free list or placed in the tray. If there is a glazing reject then the tag can be used to return the frame to the bin. In this case when the order is completed then the tag can be returned to the free list.

Including EORI on delivery notes

There are program updates to include an EORI number in the delivery note.  

More details are here: 

EORI Updates

Automatic Sending Orders to Supplier

 Sending Orders to the suppler automatically.

Firstly, the 'Include in Auto' in the supplier configuration is ticked. If tracking status is to be obtained then the 'Tracking' is ticked also.

Santiago is used to start a task to send the orders automatically. This is normally done by creating a batch file to do this.

Eg

l:\progs\annapurna.exe USER=xxxx PASSWORD=yyyy AUTO

User xxxx needs to be created in Annapurna with Password yyyy. Importantly in the user configuration for xxxx in the “Automatic” section, then 'Send Orders' needs to be ticked. This setting tells Annapurna when the user logs in to start the order sending.

Normal operation is to send orders and then look for status updates. It is possible to change this by starting Annapurna (or amending the batch file) to have

SENDONLY to send orders only

TRACKONLY to read the tracking only.

Some sites will have SENDONLY running every 30 minutes but TRACKONLY set for twice a day. This is done by creating separate Santiago entries.