• Not Answered

VB Error 13 - Type mismatch, when opening popups

Hello guys,


I have a recent problem since reinstalling Windows 7 and DeltaV because of some unexplained self-restarts.
When I click on a button to open an AI/Valve/Motor faceplate, I get a Error Number: 13 (D) - Type Mismatch.
After I click OK, I can work normally with the faceplate, until next time I open a new one.

I found an old thread for using frszOpenTagForm, but when I looked in the scripts of a button for faceplate opening or in the actual faceplate, I don't find any usage of such functions.
I even get the error, while opening custom popup pictures which I've made and am opening them with frsOpenPic "pictureNameHere".

Does anyone have any ideas where should I look for the problem?

Thank you!

3 Replies

  • Based on the fact that the error is also shown when opening by frsOpenPic, the error occurs most probably in the Faceplate script.
    You could open the faceplate in configure mode and compile the script.
    If you do not get a compile error, you could debug the script line-by-line to see when the error pops up.
    Also (do make a backup copy of your existing faceplate!) you could add some Message lines to see till how far the script runs without problems.
  • In reply to Maarten van der Waal:

    I tackled a bit with the scripts, not knowing a lot of visual basic, and I created a new button for my custom faceplate with frsOpenPic and everything is OK.
    I've tried to load a faceplate of a valve with "frszDynamoLoadIA "DVSYS.KV1", Me" but I still get the error, even though when commissioning the system before a few years I haven't made any changes in the script.
    I am used to Simatic WinCC and it's diagnostics console. Is the Trace Messages the same and can I print text in it? I tried using frsTrace as written in the help files, but it gives me compiler error Error Number 91 and I don't know what to object to set...
    DeltaV help files are useless or possibly can be used by people who have had DeltaV training...
  • In reply to nikola_hadjinikolov:

    The problem has been found!
    In the regional settings, the formats were Bulgarian. It has to be English (US)...