FORUM CTRLX AUTOMATION
ctrlX World Partner Apps for ctrlX AUTOMATION
Dear Community User! We have started the migration process.
This community is now in READ ONLY mode.
Read more: Important
information on the platform change.
04-08-2024 12:42 PM
Hello Team,
I am making a configuration on CtrlX Configurator, please find the configuration image attached. I can see that the Mains filter size is automatically choosen, with the current configuration with XCD2323 DC bus coupled with 2 XMD0606 i get 16A mains filter, but i feel it has to be 30A mains filter.
Question 1: can we change the mains filter size in the configurator in the XCD2323 configuration or we need to add it separately by selecting the XCD2323 without filter option?
Question 2: Is my calcualtion correct or is there something I am missing?
COuld any one please help me with this?
Thank you in advance
Solved! Go to Solution.
04-08-2024 01:05 PM - edited 04-08-2024 01:06 PM
Moved to corresponding sub forum ctrlX SERVICES.
04-09-2024 03:16 PM
Hello Tasty_Tech,
for selecting a mains filter, the mains input continuous current in A is relevant.
XCD2-W2323:
Mains input continuous current at ULN_nenn and PDC_cont (three-phase, with mains choke) in A (ILN) = 15,9
Mains input continuous current at ULN_nenn and PDC_cont (three-phase, without mains choke) in A (ILN) = 8,1
NFD03.1-480-016:
Rated current mains filter in A = 16
Looking at the current, the mains filter fits to the converter. If a deeper consideration is required please contact our colleagues in product management.
04-10-2024 03:32 PM
This XCD* W2323 has a 54 Amp rectifier bridge inside. Perfectly for use as a Modulair Setup Powersupply .
That means that the Current values are higher then 16 Amp... So I think a Filter with higher amps fits better..
04-11-2024 07:58 AM
Hello @Pinball_NL and @Tasty_Tech,
the technical values in the data base of the configurator and the project planning manual don't match in this case.
According project planning manual you are right: the 30A mains filter should be selected.
I will open a Bug ticket and we are going to fix as soon as possible.
Thanks for the info.