FDT 12 does not work, freelance 9.2 SP1 win XP sp312
FDT 12 does not work properly in a freelance 9.2 sp1, installed in a Windows XP sp3,
when we try to add one DTM slave it does nothing. and if we use one imported project with Dtm slaves already configured they appears as one error.
we review event viewer of windows and find this error messages:
BCM.sysTag0.5 ( I:\DIGIMAT\FDT12\COMPONENTS\BCM\SRC\BCMUTL.CPP[1685]): DetermineInstalledDevices: an exception occurred
FDT12
BCM.sysTag0.5 ( I:\DIGIMAT\FDT12\COMPONENTS\BCM\SRC\BCMUTL.CPP[4029]): m_pTestBaseContMan!=NULL
FDT12
BCM.sysTag0.5 ( I:\DIGIMAT\FDT12\COMPONENTS\BCM\SRC\BCMUTL.CPP[2691]): AnalyseInstallation
FDT12
Answers
More info required,
you are using HART or Profibus device DTM? Can you mention that device DTM details like DTM version/name, device type, Device version HW/FW?
Also pls check version compatibility or system requirements details in release notes for HART & Profibus DTM's under publications in solutions bank.
Hello,
Can you please give more information on this issue, which is the dtm you used to create the instance, does it pop up any error message? What are the components installed and the system version information.
Also mentioned that project is imported, can you send this information to dic@in.abb.com (Device Integration Center). We can look in to it and let you know about the solution.
Required:DTM setup, imported project and system information.
as you see in the image, the problem is with FDT 12, CBF can not see that FDT is installed, but you can see in the add or remove programs windows that FDT is already installed in this PC. I think the problem is not with DTM.
Is it your demo system or project install base ? Incase it is demo system try this...
1. Remove that node showing red color, I think it is from profibus slave,
Export that node before removal.
2. Save project and close freelance frame.
3. Goto add/rem program and repair FDT base and shared component.
4. Also repair your DTM's S800 or any device specific DTM.
4. now restart system and try to do fresh configuration for the removal node.
If all system requirements are meeting and it might be installation issue, after doing this It should work.
In case it is project system and you do not want to try this, Recommended to send details to dic contact details...
Hope it helps to you....
Add new comment