Toolkit 1.11.9 Error!

Hi all,

This little gem happened today while attempting to edit the labels on a DLT.

It occured while changing the default font from Arial to Verdana inside the custom font selector and the clicking OK.







Although the DLT still functions correctly, the problem now occurs every time I try to edit that particular device, either from the network or database, the load unit info bar graph gets to 98% then the same error sequence occurs.

I have removed the offending device from the network and then replaced it, re-addressed it all with no avail, toolkit dies as soon as the retrieved data from that device hits 98%.

I can't figure why toolkit trying to locate a drive? is it looking for font file? or something, one thing is sure, I cant re-programme that DLT so i'm stuck,

Your help would be appreciated,

thanks,

Paul,

p.s. I have emailed the exception error to clipsal for future reference.

 

Hi Paul,

If this issue is what I think it is then the following should help.

1) Close Toolkit and C-Gate if they are running
2) Go to the directory "C:\Clipsal\C-Gate2\tag" and locate the file which looks like this PROJECT-DLTD-index.txt, where PROJECT is the name of your project. Open it in the Notepad.

The contents of the file will look similar to this:

2000,Font=MjAwMCwxLFRhaG9tYSwxMCxERUZBVUxULEIsMSwwLDAsR3JwIDAw,Pic2000.bmp
2001,Font=MjAwMSwxLFRhaG9tYSw4LERFRkFVTFQsQiwxLDAsMCxHcnAgMDE=,Pic2001.bmp
2002,Font=MjAwMiwxLFRhaG9tYSw4LCwsMCwwLDEsR3JwIDAy,Pic2002.bmp
2003,Font=MjAwMywxLEFyaWFsIEJsYWNrLDEwLERFRkFVTFQsQiwwLC0yLDAsR3JwIDI=,Pic2003.bmp
2004,Font=MjAwNCwxLEFyaWFsIEJsYWNrLDEwLERFRkFVTFQsLDAsLTEsMCxBUyAwMA==,Pic2004.bmp
2005,Font=MjAwNSwxLEFyaWFsIEJsYWNrLDEwLERFRkFVTFQsQiwwLC0yLDAsRzMgdjI=,Pic2005.bmp

3) Now please find in this list the line which doesn't have file name part on the end, or has it's file name part malformed (file name missing, or extension missing) and type in the name of the bitmap file which is supposed to be there, so the line looks just like other lines. You will probably have to view all BMP files to identify the one which most likely should be mentioned in that line. If you can't identify the file, then just delete that malformed line from the TXT file. Save changes.

4) Start Toolkit and try to open the DLT GUI.

Regards,
George

 

George, many thanks, your advice worked a treat, had to delete the entire line though as it was full of hieroglyphs.

Obviously a couple of issues for Clipsal to sort out here, mainly the untrapped Exception, toolkit shouldn't shut down because of an error in a local data file....rant... rant.

Once again, thanks,

Regards, paul.

 

I'm glad to hear this helped and thanks for reporting this issue, Paul. It will be fixed in the next major release of Toolkit.

George