VFD Videos

VFD Videos

The following videos are applicable for SMV Variable Frequency Drives utilizing the 571 programming file.  They do not apply to the new i500 series products or older AC-Tech/Lenze products

Programming VFDs




VFD Faults




VFD Ground Fault Troubleshooting

Video Transcript
0:02
hello everyone and welcome back to
0:03
another service video
0:04
today we're going to talk about tracking
0:06
down a ground fault on a vfd in one of
0:08
our control packages

Safety

0:09
be sure to follow all safe work
0:11
practices especially the use of ppe
0:13
all circuits should be de-energized
0:15
prior to any wiring or service
0:17
remember many of our controls will have
0:19
more than one circuit that will need to
0:20
be turned off
0:21
after de-energizing the circuit verify
0:24
that the circuit is dead
0:25
then lock out and tag the breaker

Identifying Ground Faults

0:30
so first let's talk about what the fault
0:31
is a ground fault simply means that
0:34
there's a short to ground
0:35
somewhere between the vfd itself and the
0:38
motor that it's supplying
0:40
so if you notice here i have this vfd
0:42
and it's flashing sp
0:44
sp is start pending is what sp stands
0:47
for and that's a four minute delay
0:49
so what this vfd is gonna do it's gonna
0:51
try to start goes into fault
0:53
it starts flashing sp four minutes later
0:56
it's gonna try to start again
0:58
on its own it's going to try to send
1:00
power to that fan if it faults again
1:02
it's going to go do this four minute
1:04
delay if it does that four times in a
1:06
row
1:06
it eventually goes to fault lockout and
1:08
the display will say
1:10
lc so if you ever get to somewhere and
1:12
you have a vfd where it's displaying lc
1:14
that's fault lockout
1:16
the only way to reset a lockout is to
1:18
cycle power to the drive
1:19
so while it's showing sp on the drive
1:22
you can push the stop button
1:24
and it'll show you the fault fof1 is a
1:26
ground fault
1:27
so if you look in the lens manual it's
1:29
going to say ground fault

Locating Ground Faults

1:30
so now let's talk about how to find that
1:32
fault where it is in the circuit
1:34
start by getting the vfd to a stopped
1:36
condition or powered down
1:38
then turn off the disconnect to the fan
1:40
that the vfd is controlling
1:42
now restart or power up the vfd if the
1:45
vfd starts
1:46
to count up normally that means that
1:48
your short exists
1:50
between the disconnect and the motor on
1:51
the fan
1:53
if however you get the fault again the
1:55
short is before the disconnect
1:58
if this is the case then stop the vfd as
2:00
before disconnect the load wires from
2:02
the vfd
2:03
or at the quick disconnect in the
2:05
control package and restart the vfd
2:07
if the vfd starts up normally then you
2:09
know your short is between the vfd
2:11
and the fan disconnect if the ground
2:13
fault still exists
2:15
the fault is in the vfd and the vfd
2:17
should be replaced

Closing

2:19
following these simple steps will help
2:21
you find the ground fault in your fan
2:22
circuit
2:23
and save you time and frustration if you
2:25
have any questions about this video or
2:27
any of our products feel free to contact
2:29
our tech support team
2:30
thanks for watching
 


VFD Modbus Fault Troubleshooting

Video Transcript

Intro

0:02
welcome everybody to another service
0:03
video
0:04
today i'm going to talk about the modbus
0:05
network that we use here in our control
0:07
packages
0:08
we're going to talk about what it is how
0:10
it works and some common faults that we
0:12
see here in the tech support team

Safety

0:15
be sure to follow all safe work
0:16
practices especially the use of ppe
0:18
all circuits should be de-energized
0:20
prior to any wiring or service
0:22
remember many of our controls will have
0:24
more than one circuit that will need to
0:26
be turned off after de-energizing the
0:28
circuit
0:29
verify that the circuit is dead then
0:31
lock out and tag the breaker

ModBus Network

0:35
first let me explain what a modbus
0:36
network is a modbus network is an
0:39
internal device network where you have
0:41
several devices all connected together
0:43
daisy chained together with cat5 cable
0:45
all this blue cable here
0:47
so for example we have three vfds so
0:50
because they're all daisy chained
0:52
together
0:52
on one network with one single cable
0:54
each device has to have its own unique
0:56
address
0:57
so for example we have two exhaust fans
1:00
and a supply fan vfd
1:02
the two exhaust fan address will be 11
1:04
and 12.
1:05
supply fan addresses start at 21 and
1:08
then all the other devices on the
1:09
network
1:10
hmis core panels filter monitors
1:14
each device is going to have to have a
1:16
unique address to all work on this
1:18
network so every modbus fault

Communication Problems

1:21
is a communication problem so one of
1:24
three things is going to happen
1:25
either the circuit board is looking for
1:28
a device it's programmed to look for a
1:30
device that doesn't exist in the network
1:32
maybe your device is powered down you
1:34
haven't plugged it in something like
1:36
that
1:38
you have a device that's in a fault
1:39
condition that'll cause a modbus fault
1:43
or this circuit board controls these
1:46
devices it tells these devices what to
1:48
do
1:50
if this board is telling this device to
1:52
do something that it cannot do
1:54
because of an internal limit that'll
1:57
cause a modbus fault
1:58
just remember that any modbus fault is
2:01
going to take
2:02
about 10 to 20 seconds to show up and
2:04
it's going to take just as long to go
2:06
away
2:07
so when you're troubleshooting you're
2:08
tracking down a modbus fault
2:11
you kind of have to work at a slower
2:12
pace because the modbus fault you make a
2:15
change in the network say you change
2:16
this cable you suspect this cable is bad
2:18
you plug in a new cable
2:20
the fault doesn't go away right away oh
2:23
now you're frustrated because well that
2:24
didn't fix it
2:26
just give it a little bit of time give
2:27
it 10 20 30 seconds
2:29
for the fault to clear itself because
2:31
this board is going out and pinging each
2:33
device periodically and that's when it
2:35
clears and that's when it shows up
2:37
so again work at a little bit slower
2:38
pace because the faults take a long time
2:40
to show up and a long time to go away

Most Common Faults

2:42
so now i'm going to talk about some of
2:44
the most common faults that we see
2:46
here at tech support especially on new
2:48
startups new jobs as soon as you apply
2:50
power and vfds are powered up you get
2:52
some faults these are the most common
2:54
ones
2:55
the most common is just a general modbus
2:57
fault hmi is going to say modbus fault
2:59
and give you a device number you know
3:01
vfd number one
3:02
vfd number two something like that and
3:04
then you have to track it down you have
3:05
to figure out where the fault's coming
3:06
from
3:08
the most common problem a lot of times
3:11
is the vfds aren't powered up
3:13
you've powered up the board you've
3:15
applied power to the circuit board but
3:16
the vfds are not
3:18
powered up that'll cause a modbus fault
3:20
because again it's a communication
3:21
problem
3:22
the board is looking for a device it
3:24
can't see because it doesn't have any
3:25
power
3:26
so make sure all your vfds are powered
3:28
up
3:29
the other most common problem is after
3:31
tested balance you have a test and
3:33
balance agent come in
3:34
he'll set the fan speed we set fan speed
3:37
on the
3:38
display on the front of the hood through
3:39
this circuit board
3:41
there are limits inside the vfd and we
3:44
do that because we're using direct drive
3:46
fans the fan wheels have a
3:49
specific maximum rpm that they can't
3:51
exceed
3:52
that rpm is calculated and we put a
3:55
limit in the vfd for max speed
3:58
well the board doesn't know what that
4:00
limit is you can set the board
4:02
above that limit so when you do that
4:05
and you push the fans button you tell it
4:07
to run at high speed you'll get a modbus
4:08
fault
4:09
and it just says modbus fault exhaust
4:11
fan vfd number one
4:13
something like that the problem is is
4:15
that the board
4:17
is asking the vfd to run at a higher
4:19
speed
4:20
than the vfd is allowed to run that'll
4:23
cause a modbus fault and that trips
4:24
people up all the time we see it most of
4:26
the time after
4:27
the air balancer is finished the last

Fan VFD

4:30
common problem that we see
4:31
at startup on a new job is when you have
4:34
a vfd that's mounted in a fan
4:36
so this is our supply fan vfd for
4:38
example this could be mounted
4:40
in the dedicated makeup air unit on the
4:42
roof
4:43
in the fan if that's the case
4:46
you have to run a cat5 cable from this
4:49
vfd
4:50
up to the roof to the one that's mounted
4:52
in the fan that gets missed a lot
4:54
and so the guys will turn everything on
4:56
and have a modbus fault supply vfd
4:59
and that's usually the most common
5:01
problem the other common problem we see
5:03
is when you make up a cat5 cable in the
5:05
field when you're actually making it up
5:07
putting the ends on crimping it down
5:09
if you get two wires reversed something
5:11
like that that'll cause a modbus fault
5:13
so get yourself a cheap tester it's
5:15
available at all the big box hardware
5:16
stores
5:17
it's a good little investment to be able
5:19
to test that cable after you've done it
5:21
avoid a lot of problems
5:22
the last problem i want to talk about is
5:24
a possible address
5:25
problem where you have a vfd that's
5:27
addressed wrong
5:29
the time that we see this and we get
5:30
most phone calls in is
5:33
when a vfd has gone bad electrician
5:36
whoever
5:37
service guy has ordered a new vfd
5:39
installed it
5:40
now he has a modbus fault as soon as he
5:42
powers it up gets a modbus fault
5:44
why am i getting this fault a lot of
5:46
times when you order these vfds
5:48
if we don't have really good details got
5:51
duplicate vfds the factory doesn't know
5:53
how to program they don't know what
5:54
address to program it for
5:56
so a lot of times they'll come out
5:57
programmed for it
5:59
at address 11 or exhaust fan number one
6:02
maybe you replaced exhaust fan number
6:04
two so now you have two vfds with the
6:06
same address 11
6:07
that's going to cause a modbus fault so
6:10
again
6:10
if you suspect that it's an address
6:12
problem contact the tech support team
6:15
for help on changing the address it's
6:17
kind of a little bit of drawn out
6:18
process getting into the vfd
6:20
so i recommend that you contact our team
6:21
for help with that
6:23
the next modbus fault that i'm going to
6:25
talk about is when the device is
6:26
actually in a fault condition
6:29
some of the most common ones we see
6:30
especially at startup brand new jobs
6:32
most common is the fault number eight so
6:35
you get the
6:36
everything powered up push fans button
6:38
fans start coming up
6:39
and boom you have an hmi just showing a
6:42
modbus
6:43
fault fault number eight exhaust vfd one
6:46
something like that what a fault number
6:48
eight is it's an overload fault
6:49
it just simply means that the motor just
6:51
pulled too many amps it's like an old
6:53
you know mechanical overload so you have

Motor Fault

6:55
to troubleshoot the motor
6:56
why it's pulling too many amps it could
6:58
be that the rotation is backwards
7:01
that's the most common problem is
7:02
backwards rotation remember you have to
7:04
check the rotation on the fans visually
7:06
you can't just test that it's moving air
7:08
in the right direction they'll move air
7:10
in the right direction even when they're
7:11
running backwards but they pull really
7:12
high amps
7:14
the next problem could be that you have
7:15
the wrong fan on the wrong vfd
7:18
so say you have two fans you have a one
7:19
horsepower motor and a two horsepower
7:21
motor
7:22
you put the two horsepower motor on the
7:23
one horsepower vfd that'll cause them
7:26
oddball's fault
7:27
because you can't run a larger motor
7:28
than the vfd is rated for

Ground Fault

7:30
the next most common problem that we see
7:33
not as common as
7:34
fault number eight but it's fault number
7:35
three number three is a ground fault
7:38
to track down a ground fault there's a
7:40
few steps that will help you kind of
7:41
narrow down where the ground fault was
7:43
going to be
7:44
ground fault is simply just a short to
7:46
ground a direct short to ground
7:48
between the vfd and the motor it's
7:51
controlling

Troubleshooting Ground Fault

7:52
so we suggest you watch our video on
7:55
troubleshooting ground faults it's going
7:56
to give you a lot more detail on how to
7:58
troubleshoot narrow down where that
7:59
fault is
8:00
so you're not having to look through the
8:01
entire circuit the last two most common

Troubleshooting Temperature Fault

8:04
faults that we see
8:05
maybe not so much as startup but you
8:07
know after long term is a fault number
8:09
four
8:10
and a fault number seven fault number
8:12
four
8:13
is a temperature fault that simply means
8:15
that the drive itself is getting too hot
8:18
and it will shut down and give you a
8:20
show you display a fault number four on
8:22
the hmi
8:24
things to look for is some of these
8:26
drives the bigger drives and three
8:28
horsepower or larger i believe
8:30
they get an internal cooling fan so make
8:32
sure that fan is running
8:34
the other thing to check is make sure
8:36
this cooling fan the cabinet fan is
8:37
running
8:38
that the filter on top is clear you
8:41
don't have any paper sitting up here
8:43
no dust anything like that and lastly
8:46
that all the
8:47
cabinet vents are clear so that you're
8:49
getting good airflow through this
8:50
cabinet to keep those drives
8:52
cool and then the last fault we'll talk
8:54
about is the fault number seven
8:57
number seven is uh low dc bus voltage we
9:00
get that call
9:00
a lot and it mainly comes after
9:04
say there's a thunderstorm that rolls
9:06
through the area and the restaurant
9:08
experiences a power failure in the
9:09
middle of dinner service for example
9:12
when the system comes back up a lot of
9:15
times they'll show us fault number seven
9:17
and it's a low dc bus voltage it's an
9:20
internal fault to the drive
9:22
all it simply means is that the line
9:24
voltage to the drive
9:26
dropped below a certain point which is
9:29
exactly what it did when the power went
9:31
out so to clear the fault
9:33
all you have to do is cycle power to the
9:35
drive at the breaker panel
9:37
so you turn the breaker off wait for
9:39
this display to go blank
9:41
as soon as it goes blank you can turn
9:43
the breaker panel back on
9:45
this drive will reset and you should be
9:46
good to go that should solve this fault
9:48
number seven so there are other devices

Outro

9:51
and situations that can cause a modbus
9:53
fault but just remember a modbus fault
9:55
is always a communication fault
9:57
so the troubleshooting is going to be
9:58
basically the same if you have any
10:00
questions on this or any of our products
10:02
feel free to contact our tech support
10:03
team thanks for watching