POPUP TEXT

MEANING

RECOMMENDATION

The Matrix XXX is synchronized [within YYY ms]

CLC/MX2 is now synchronized with PC (should only popup if there was previously an UNSYNCHRONIZED popup)

None

The Matrix XXX is no longer synchronized [not within YYY ms]

CLC/MX2 has become unsynchronized with PC (as determined by threshold we set)  This is usually due to PC clock changing erratically due to other Windows operations (installs, network activity, anti-virus, etc.)

Make sure any services DSI recommends to turn off are not running (i.e. Windows Update, competing time synchronization services, etc.)

The Matrix XXX is not synchronized [still initializing]

CLC/MX2 has not yet synchronized to the PC after an CLC/MX2 restart either because the PC’s NTP server is not yet responding to synchronization requests (takes approx. 5 minutes after PC/service restart), the NTP service is not running on the PC, or a firewall/anti-virus program is interfering with the NTP communication.

If you have just restarted your PC, it can take around 5 minutes for the NTP service to start synchronizing CLC/MX2s. Also make sure any services DSI recommends to turn off are not running (i.e. Windows Update, competing time synchronization services, etc.)

See the IT Guide for more information.

The Matrix XXX is no longer synchronized [bad IP: www.xxx.yyy.zzz]

CLC/MX2 is no longer synchronizing to the acquisition PC.  This is normally due to someone else manually changing the NTP address on the CLC/MX2 web page while an acquisition is taking place.

Do not make changes to CLC/MX2 web-page while acquiring.  Stop and restart acquisition.

The Matrix XXX could not parse the NTP synchronization status[asdfasdfasf;alsfdj]

CLC/MX2 has sent us an NTP status that is unreadable.  This does occasionally occur, but should be benign unless it doesn’t resolve itself after a few occurrences.

This should resolve itself.

If this occurs frequently, contact DSI Technical Support.

Matrix communication failed

Cannot (re)connect to CLC/MX2.  This usually resolves within 30 seconds unless the CLC/MX2 has been ‘stolen’ by another system or for some other reason the CLC/MX2 is no longer available on the network (power, network failure, etc.)

Make sure CLC/MX2 is on, connected to network, no error LEDs are red, and no other PC is now using the CLC/MX2.  Stop and restart acquisition.

POPUP TEXT

MEANING

RECOMMENDATION

Received an error[<ERROR>] on implant[XXXXX] : YYYYY

<ERROR> = ERR_BAD_CALIBRATIONS

The implant calibration values are not correct for the signal.

Recheck the entered values and correct as needed.

<ERROR> = ERR_CALIBRATION_CRC

The implant’s programmed calibrations are not correct or the software received a garbled transmission..

Try turning OFF the implant and back ON again to re-send calibration data. 

If the error persists, contact DSI Technical Support.

<ERROR> = ERR_NO_SIGNAL

Since acquisition was started on this implant we have never received any valid data from it.

Make sure the correct receiver is assigned to the implant in question, it is within range of the receiver, and the implant is magnet-swiped on.

<ERROR> = ERR_BATTERY_EOL

Battery in implant is below specification.

Implant has reached its end of life and should be returned to DSI for exchange.  It is not recommended to reuse this implant again.

<ERROR> = ERR_ON_TIME_ALARM

Implant ‘on time’ (tracked within implant) is beyond alarm threshold (default is warranted battery life period).

Verify the ‘On Time’ parameter for the implant and send back to DSI if the value has reached the warranted battery life.  If not, the transmitter may be reused.

<ERROR> = ERR_TIME_ERR

The estimated error between the accumulated data time span and the time detected through the hardware is too large. Restart sampling to correct.

Restart the source.

<ERROR> = ERR_BUFFER

<ERROR> = ERR_CIRC_WRITE_TIMEOUT

<ERROR> = ERR_PANIC

An unexpected condition was encountered during processing of implant data.  Processing of data will not continue correctly.

Stop acquisition and Ponemah.

Contact DSI Technical Support.

<ERROR> = OutOfMemory

The program has run out of system memory.

Stop acquisition and Ponemah.

Contact DSI Technical Support.

OTHER MESSAGES

There are no RXs connected to MX2 'XXX'.  The MX2 is unable to connect to any sources

No receivers are currently connected to the MX2.

Make sure all receivers being used in study are connected to MX2 while acquiring.

Last/only RX has been disconnected.  Implant XXX has been disconnected as a source

All receivers assigned to this implant have been disconnected.

Make sure all receivers being used in study are connected to MX2 while acquiring.

POPUP TEXT

MEANING

RECOMMENDATION

IMPLANT MESSAGES 

Implant internal error

In most cases an implant reset occurred, and the CLC has sent a command that would only be sent to an ‘active’ implant.

Make sure CLC firmware is upgraded.  Possibly add more TRXs.

Implant removed from system

Hunt timeout, implant will revert to shipping mode

Turn implant back on.

Unknown implant message code XXX: YYY

An implant message was received that the current version of software is unaware of.

Depends on the message: this could be a benign message or a fatal message. 

Contact DSI Technical Support.

TRX MESSAGES

TRX SN XXX error at J? of CLC: YYYY

Usually due to plugging/unplugging TRX while acquiring.

Almost always can be ignored as it will have minimal effect.

TRX SN XXX disconnected at J? of CLC: YYYY

A TRX was disconnected while acquisition is taking place.

Reconnect TRX.

TRX SN XXX from wrong region connected at J? of CLC: YYYY

A TRX was connected whose operating region does not match the other TRXs currently connected to the CLC.

Make sure the region of the TRX specified matches your operating region.

Contact DSI Technical Support if you believe you were erroneously sent a TRX that does not match your region.

Unknown TRX message code XXX for SN YYY at J? of CLC: ZZZ

A TRX message was received that the current version of software is unaware of.

Depends on the message: this could be a benign message or a fatal message. 

Contact DSI Technical Support.

CLC MESSAGES

CLC (XXX) DSP incoming data queue full

CLC having problems with data packet from implant (usually due to RF or TRX coverage issues) and will result in a 2 second data loss.

Add more TRXs to CLC, increase the RSSI threshold of every TRX connected, or switch operating frequency (in case of interferer on that frequency)

Unknown CLC message code XXX from CLC(SN YYY) : ZZZZ

Unhandled Clc message (xxx) - <message-text-from-CLC>

This error is posted when we receive an error message from a CLC that the running version of DSILINK is unaware of.  This should only occur when CLC firmware that is newer than the DSILINK software is being used.

Depends on the message: this could be a benign message or a fatal message. 

Contact DSI Technical Support.

PhysioTel Digital error response (<#>) from CLC: XXX 

<#> = 1 (Invalid CLC command code)

A command was sent to the CLC that was not recognized.  In all likelihood, the CLC firmware needs to be upgraded.

Make sure the correct CLC firmware is loaded.

Contact DSI Technical Support.

<#> = 2 (Invalid CLC parameter)

A command was sent to the CLC that contained a parameter that was not valid.

Make sure the correct CLC firmware is loaded.

Contact DSI Technical Support.

<#> = 4 (Unknown Implant ID)

Software sent an implant command to the CLC for an implant that it has no knowledge of (not in TDMA, etc.)

Make sure the CLC/Implants loaded in your configuration are currently available.

<#> = 5 (Implant in active mode, command unavailable)

A command that can only be run on implants in standby mode is being sent to an implant that is currently in active/acquiring mode.

Implant should be returned to standby, and restart acquisition.

<#> = 6 (Invalid implant configuration)

A configuration command was sent to an implant with settings that are not valid for this implant type.

Contact DSI Technical Support.

<#> = 7 (Implant factory configuration unavailable)

An attempt to get implant configuration information was unsuccessful.

Probably RF issues.

<#> = 8 (Implant calibration data unavailable)

An attempt to get implant calibration information was unsuccessful.

Probably RF issues.

<#> = 9 (Implant not ready to start acquisition)

An attempt was made to set an implant to active/acquiring mode before successfully setting the sensor data processing configuration (see #6)

Probably RF issues caused #6, leading to this.

<#> = 10 (Implant does not respond to commands)

An attempt was made to send a command to an implant but the CLC received no response.

Make sure implant is on and in-range.

<#> = 11 (Implant out of range)

An attempt was made to start acquiring on an implant that the CLC believes is ‘out-of-range’.

Check that no other CLC has stolen the implant, that the implant is ‘in-range’, and there is no RF interference stopping normal communication.

OTHER MESSAGES 

Implant ‘XXX’ has been disconnected because its CLC has been reset

The CLC was reset while acquiring.

The CLC was reset while acquiring.  If this was not done by user, check the connection to the switch(power).

Contact DSI Technical Support.

Last/only TRX has been disconnected.  Implant XXX has been disconnected as a source

No TRXs are currently connected to a CLC that is currently acquiring.

Make sure all TRXs being used in study are connected to CLC while acquiring.