A CE fault code (fault code 20 on the touchscreen) indicates a modbus comms fault. This means that communication has been lost between the VFD and the control source (touchscreen controller or AirLynk). Note that this differs from a CALL alarm in that CE means that communication was established and lost, whereas CALL means communication has never been established since the drive has powered on.
You should never see this fault on our standard V1000 programs. If you do, it is highly likely that the VFD is programmed incorrectly. Contact MacroAir Technical Support for further troubleshooting.
Note that if the fan is using an analog remote, a CE fault indicates that it is programmed incorrectly for analog. Please contact MacroAir Technical Support for further information.
Even though a CE should never appear, there is likely an issue with communications that requires troubleshooting. The possible causes of a CE fault are numerous. You will need to use your best judgment when troubleshooting to determine what happened. Below are some examples of common reasons for a CE fault.
1. The controller may have been unplugged or otherwise turned off and back on, but the VFD remained on. Clear the fault on the touchscreen or AirLynk. If the fault reappears, it is likely due to causes other than the controller turning off and further troubleshooting will be required.
2. Insufficient or damaged CAT5. CAT5 must be CAT5E shielded stranded at a minimum. A 568B pinout configuration is required.
3. Incorrect CAT5 lengths. CAT5 length is limited to 200' to a standard touchscreen remote and a total of 4000' on networks from the control source (network controller) to the last fan in line. The CAT5 length from the screen to the first fan or between fans does not matter as long as the total length does not exceed 4000', with the exception of a Controller 4, which must be within 200' of the first fan.
4. Incorrect CAT5 wiring. CAT5 wiring must be daisy chained between control panels. There must be a single beginning and end to a network. Splicing of CAT5 is not recommended other than to tie in an AirEffect sensor.
5. Noise/Electrical interference. The communication signal can degrade if the CAT5 is ran too close to the fan's incoming power or other high voltage (120VAC and up) wiring. Ensure that the CAT5 wiring is ran at least 6" away from any power wires. The further away, the better. Never run CAT5 and power wiring in the same conduit. CAT5 cannot be coiled and any excess must be cut or ran in a method that eliminates any coils.
6. The controller is not plugged in or powered on. Ensure that the controller has power and is properly plugged into the CAT5. If using the standard touchscreen controller, ensure the dial on the back of the controller is pointed to 0. There should be 5VDC on the blue pair and 10-24VDC on the brown pair depending on fan model. Confirm that you are getting the same voltage readings both on the VFD output terminals and the terminal block on the back of the touchscreen.
7. The controller is not compatible with the fan. Contact MacroAir Technical Support to confirm that the touchscreen/AirLynk software version is compatible.
8. The VFD is not properly grounded. Check all wiring between the VFD and the breaker to ensure that the system is grounded properly.
9. There is a bad VFD on the network affecting other VFDs. Isolate fans on a network and test them individually to ensure that the VFDs can communicate properly with the diagnostic touchscreen. Add fans back to the network one at a time to identify where the communication breakdown is occurring.
10. Communication parameters on the drive may have changed. Contact MacroAir Technical Support to confirm the VFD programming.
Comments
0 comments
Please sign in to leave a comment.