Connect / networked location of Datasets

Still in the process of setting up Aecosim Connect I've run into a problem when trying to setup our networked company workspace.

So far I was able to configure my PC that it reads configuration files from the network.

The problem I have now is that I am unable to define the correct location of the datasets.

  • TF_DATASETS points to the local drive.
    By doing a little research I found out that this variable is defined in the program folder that way:

    TF_DATASETS : $(_TF_WORKSPACEROOT)Datasets/
  • _TF_WORKSPACEROOT also points to a local folder
    The local definition of this variable is:

    _TF_WORKSPACEROOT : ${_USTN_CONFIGURATION}
  • _USTN_CONFIGURATION points to our network drive.

So in theory _TF_WORKSPACEROOT should point to our network drive, which is doesn't

On assuming that something isn't working, I have defined _TF_WORKSPACEROOT in the WorkSpaceSetup.cfg file in that way.

%lock _TF_WORKSPACEROOT = M:/Microstation/Workspace_Connect/Configuration/

The funny thing now is, that this doesn't change anything - the variable still points to a local drive.

Any ideas?

Parents
  • Hi Andreas,

    This is the same issue as your new SR, correct?



  • Yes, that's correct (SrvReqNo:[7000811510]).

    We can take it there an post a final conclusion when we have found out about the problem.

  • Re-reading and stepping back from the detail in my previous post, I still recommend changing the default datasets location using TF_DATASETS. Try adding:

    TF_DATASETS = <path to my networked dataset>

    in ...\Organization\Standards.cfg, e.g.:

    TF_DATASETS = M:/Microstation/Workspace_Connect/Configuration/

    That defines the location of the networked datasets.

    The TF_DATASETNAME statement in the WorkSet.cfg (equivalent of V8i PCF) will define the name of the dataset to be used by the WorkSet. e.g.:

    TF_DATASETNAME = Dataset_NM

    The example BuildingTemplate_NM.cfg contains this statement.


    The correct syntax for the locked example statement above should be:

    _TF_WORKSPACEROOT = M:/Microstation/Workspace_Connect/Configuration/
    %lock _TF_WORKSPACEROOT

    You have to set the variable then lock it. However a lock is normally only really needed if you wish to prevent users from changing standard settings in the UI.

    Locked variables are best avoided as they can have unexpected results downstream.

    Marc

  • We are discussing in 2 different threads, but that's ok for me.

    I finally managed to set _TF_WORKSPACEROOT by this change to standards.cfg in the Organization folder.

    _TF_WORKSPACEROOT = ${_USTN_CUSTOM_CONFIGURATION}

    As I have written in the other thread, I am having problems with the _USTN_CONFIGURATION variable, which doesn't take the value of the _USTN_CUSTOM_CONFIGURATION variable. Which again is caused by the dynamic nature of ConfigurationSetup.cfg.

  • Here's another example of the same problem, variable _USTN_USERINTROOT.

    Definition in msconfig.cfg

    _USTN_USERINTROOT       : $(_USTN_WORKSPACEROOT)interfaces/

    No value visible in Configuration Explorer, undefined when running Aecosim.

    _USTN_WORKSPACEROOT is M:\Microstation\Workspace_Connect\WorkSpaces\NODE\

    Why isn't _USTN_USERINTROOT defined then?

  • Did some more checks now after fixing a bug in ConfigurationSetup.cfg, I had a typo which pointed to an invalid folder name.

    At least the basic setup with a local ConfigurationSetup.cfg pointing to a networked WorksSpaceSetup.cfg now works.

    However this has not changed anything regarding _TF_WORKSPACEROOT. As you remember, this variable is defined in BuildingDesigner.cfg

    _TF_WORKSPACEROOT        : ${_USTN_CONFIGURATION}

    I have to include this line in the networked standards.cfg to get it correct

    _TF_WORKSPACEROOT = ${_USTN_CONFIGURATION}

    The same thing applies to _USTN_USERINTROOT , which doesn't work without this line in standards.cfg. This variable is defined in msconfig.cfg.

    _USTN_USERINTROOT = $(_USTN_WORKSPACEROOT)interfaces/

Reply
  • Did some more checks now after fixing a bug in ConfigurationSetup.cfg, I had a typo which pointed to an invalid folder name.

    At least the basic setup with a local ConfigurationSetup.cfg pointing to a networked WorksSpaceSetup.cfg now works.

    However this has not changed anything regarding _TF_WORKSPACEROOT. As you remember, this variable is defined in BuildingDesigner.cfg

    _TF_WORKSPACEROOT        : ${_USTN_CONFIGURATION}

    I have to include this line in the networked standards.cfg to get it correct

    _TF_WORKSPACEROOT = ${_USTN_CONFIGURATION}

    The same thing applies to _USTN_USERINTROOT , which doesn't work without this line in standards.cfg. This variable is defined in msconfig.cfg.

    _USTN_USERINTROOT = $(_USTN_WORKSPACEROOT)interfaces/

Children
No Data