Danfoss FC302 - "Fieldbus Fault W34" Appearing after Install of new FC302.

Hi All,
Installed a brand new Danfoss FC302 which was a replacement for a failed FC300 drive. Copied all parameters from the FC300 to the LCP (Danfoss Drive HMI) and uploaded all parameters to the new FC302 drive. When this was complete and the new replacement FC302 was parameterized, "Fieldbus Fault W34" appeared.

  1. Checked wiring of ProfiBus to drive.
  2. Checked parameter "9-18 Node Address" - The Node address didn't update after parameters were copied and uploaded from the previous drive. Updated the Node Address, but the fault was still present, the slave was also in error on the plant SCADA systems ProfiBus network.
  3. Checked parameter "9-53 Profibus Warning Word" what I assume is a parameter for some sort of Hexadecimal language for detecting fieldbus faults on the drive - This parameter was set at 'A001 hex' on the FC302 but set at '0000 hex' on the FC300. The LCP was stuck in "Read-Only Mode".
  4. Checked all relevant dipswitches local to the Profibus hardware on the drive.

Found some other parameters on the "9 - PROFIdrive" settings that didn't match up.

Noticed that the Profibus communications card (MCA 101 - Option A 130B1100) had a more recent software version on the FC302 "V5.20" compared to FC300's "V5.11".
I Powered down the drive and swapped out the FC300's Profibus card for the new FC302's card and the fault disappeared, with the "9-53 returning to 0000hex".

Has anybody come across this issue before and if so what is the reason behind it ?
 
Hi All,
Installed a brand new Danfoss FC302 which was a replacement for a failed FC300 drive. Copied all parameters from the FC300 to the LCP (Danfoss Drive HMI) and uploaded all parameters to the new FC302 drive. When this was complete and the new replacement FC302 was parameterized, "Fieldbus Fault W34" appeared.

  1. Checked wiring of ProfiBus to drive.
  2. Checked parameter "9-18 Node Address" - The Node address didn't update after parameters were copied and uploaded from the previous drive. Updated the Node Address, but the fault was still present, the slave was also in error on the plant SCADA systems ProfiBus network.
  3. Checked parameter "9-53 Profibus Warning Word" what I assume is a parameter for some sort of Hexadecimal language for detecting fieldbus faults on the drive - This parameter was set at 'A001 hex' on the FC302 but set at '0000 hex' on the FC300. The LCP was stuck in "Read-Only Mode".
  4. Checked all relevant dipswitches local to the Profibus hardware on the drive.

Found some other parameters on the "9 - PROFIdrive" settings that didn't match up.

Noticed that the Profibus communications card (MCA 101 - Option A 130B1100) had a more recent software version on the FC302 "V5.20" compared to FC300's "V5.11".
I Powered down the drive and swapped out the FC300's Profibus card for the new FC302's card and the fault disappeared, with the "9-53 returning to 0000hex".

Has anybody come across this issue before and if so what is the reason behind it ?
Hi

Thanks for the inputs/tips

Here what i found on that similar issue:
https://www.incontrolhvac.com/blog/2016/8/10/danfoss-warning-34-communication-failure

Hope it can highlight you on the reason !

Always glad to support !

James
 
Warning 34 won't hurt anything.
It usually comes up during startup, if the VFD has an communications option card (bacnet) and no communications connected.
After a couple of minutes without communications, you will get "Fieldbus Fault W34", a comm failure on the card.
It has no effect on the operation of the VFD, but if you want it to go away you can do one of 3 things:
1. Connect your bacnet comm (with some bacnet traffic).
2. Power off the vfd and remove the card, restart the drive. It will tell you that there has been an "option change", clear that alarm and you should be fine. This works if you are never going to use the card.
3. Change function 8-02 "control source" from Option A to "none". That way the vfd won't look for control comm from the card and the warning won't come up.
The intent of warning 34 is that if you lost communications on the card you could trigger certain events-- stop/full speed/preset speed-- things you might want to do if comm went down and you lost control of the VFD. Call us for more info you want to run a sequence like this.
 
Top