Skip to content

Troubleshooting

The dye table is empty at start-up

The default database C:\Users\Public\Documents\BFSpectra\BFSpectraDB.stream is missing. Reinstall BFSpectra, or use Open DB to open another database - and then Save DB it under that name and folder if you want it opened automatically.

The instrument box shows only None

No instrument files were found in C:\Users\Public\Documents\BFSpectra\Devices\. Reinstall, or copy the .ini files there, and restart BFSpectra.

A dye name is on a red background

Its excitation or emission spectrum is missing, or its wavelengths are out of order. Bars, Ex %, Select Colors and synthetic data for that dye will be wrong. Re-import its spectrum with Update DB - see Spectrum files.

Select Colors does nothing

An instrument must be chosen first, and at least one laser ticked.

The spillover window does not appear

It opens only when an instrument is chosen and two or more dyes are checked. If you closed it, check or uncheck a dye to bring it back.

No chemical structure is shown

  • More than one dye is checked - the panel shows a single dye only.
  • The dye has no SMILES. Add one with Edit - see Editing a dye. Polymer and tandem dyes usually have no published structure.

My edits to a dye disappeared after reinstalling

The installer replaces the default database. Keep edited databases under your own file name, or in a subset, which the installer does not overwrite. See What the installer puts where.

Check List reports "Wanted ..."

The names listed were not found in the current database or subset. Check the spelling in the ISAC dictionary, add the name as a synonym with Edit, or open the default database instead of a subset.

Read SVG adds nothing

The files were not plots BFSpectra recognises. It needs an SVG exported from a Highcharts-based spectra viewer, with the wavelength and intensity axis labels still in the file.

Resetting BFSpectra

Close BFSpectra and delete %APPDATA%\BFSpectra\BFSpectra.ini. The wavelength list, sort directions and remembered folders return to their defaults; databases are not affected.