Doubtful, considering you replaced it. I would, instead, look for protocol details where there could be a discrepancy. CRC errors are data-related. Thus, they could be due to poor synchronization, noise, or improperly rendered data strings. If there is a timing element (that is, it depends upon the same time at both ends), you may need NTP served up to the two devices. You might need to set their clocks to the same date, time, and time zone. But it is possible you need to short RTS and CTS or some other hard wiring. Noise can be caused with power fluctuations or if building power has a floating ground. It can also happen when the hot and return are reversed on one of the outlets where you have the devices plugged in. But this question is going on five years old and you have probably solved the problem. Please close this question.

Doubtful, considering you replaced it. I would, instead, look for protocol details where there could be a discrepancy. CRC errors are data-related. Thus, they could be due to poor synchronization, noise, or improperly rendered data strings. If there is a timing element (that is, it depends upon the same time at both ends), you may need NTP served up to the two devices. You might need to set their clocks to the same date, time, and time zone. But it is possible you need to short RTS and CTS or some other hard wiring. Noise can be caused with power fluctuations or if building power has a floating ground. It can also happen when the hot and return are reversed on one of the outlets where you have the devices plugged in. But this question is going on five years old and you have probably solved the problem. Please close this question.