CRC Error on Backup operation DWL - ACS355?
In Reference to my previous question https://forum-controlsystems.abb.com/20203624/How-to-backup-ACS355-parameters-into-my-laptop.
Hi, Kstoilov your answers had been of great help and I managed to communicate with my ACS355 successfully today. It goes Online, shows Drive Status and can perform all operations on drive like changing from Local to Remote and Start/Stop of Drive. Parameter Browser also gets updated with active drive parameters.
One problem I am facing now is on Backup operation. Though I can save Parameter Browser data as .DWP file but I want to make .VAR file with backup command. It goes up to 14%, one time up to 30% and then gives “ CRC Error “. Also at times, Drive gives PANEL LOSS fault. After resetting, fault clears. Backup/Restore is my primary objective of this whole activity and it fails with CRC error.
I am using DriveWindow Light 2.92 and communication is through OPCA-02 and then RS232 to USB adapter. Communication Settings in DWL are User Defined and are as follows;
Port = COM3
Baud Rate = 9600
Data = 8 Bit
Parity = None
Stop = 1
Timeout (ms) = 750
Modbus Address = 1 to 10
Drive couldn’t be identified in Auto-Mode settings and gave error “Modbus device returned an exception code 2 (ILLEGAL DATA ADDRESS: The data address received in the query is not an allowable address for the slave)”. So changed “Stop to 1 from Default 2” in User Defined settings and also in COM settings from Device Manager. Than identified automatically on DWL start-up and uploaded parameters.
Another confusion that I have is matching Communication settings in DWL with COM settings of RS232 to USB adapter in Device Manager. For connection they need to be same. But in DWL manual it says;
“Note! With ACS350, ACS/ACH550 and similar drives the communication speed mentioned here is the speed used at identification. After identification the communication speed is automatically set to the highest possible i.e. 115200 bit/s.”
Now if this applies to ACS355 as well, than DWL automatically setting speed to 115200 bit/sec won’t work because we have configured COM in Device Manager on 9600 bit/sec that was used in identification. In short, I think this Backup failure and Panel Loss is attributed to this communication failure.
Waiting for your expert opinion on this problem.
Insert the URL that your highlighted text will link to.
Copy the video's "embed" tag into Embedded Video below.