0:02
join me as I take the challenge of
0:03
creating a Simple Start stop circuit in
0:05
ladder logic using deep seek AI let's
0:09
it in Industrial Automation the ability
0:12
to design and simulate control circuits
0:14
is essential for ensuring a
0:16
functionality of safety a variety of
0:18
systems one of the fundamental circuits
0:21
used in a control system is the start
0:22
stop circuit today we will explore
0:24
creating a start stop circuit using deep
0:27
seek AI for later logic programming we
0:29
will enter and test this generated code
0:31
using completely free do more designer
0:33
software PLC simulator let's get
0:36
started detailed information contained
0:39
in this video can be found at ACC
0:45
automation.com examples making a
0:47
One-Stop shop for all your automation
0:58
automation.com that develops open-source
1:01
large language models
1:03
llms deep seek AI models are designed to
1:06
be more costeffective than other AI
1:08
models while still being capable of
1:10
generating human-like responses it may
1:12
provide tools or solutions that enhance
1:15
efficiency and programming or
1:16
controlling Machinery such as those
1:18
through lad logic programs used in plc's
1:21
or program logic controller
1:25
programming what is a start stop
1:28
circuit a stop start Circ circuit is the
1:30
fundamental Control process that allows
1:32
users to start and stop a motor or other
1:33
devices at will this circuit typically
1:36
involves push buttons one for starting
1:38
normally open and one for stopping
1:41
closed understanding how a start stop
1:43
circuit operates is vital for anyone
1:45
working in automation as it serves as a
1:47
foundation for more complex
1:51
systems asking if AI can program a
1:56
PLC after logging into deep seek on your
1:58
browser select the Deep think R1 option
2:01
this will allow you to understand how
2:03
the AI is answering your question we
2:05
will ask can you program a bricks doore
2:14
logic okay so the user is asking if I
2:16
can program a BRX do more PLC using
2:17
latter logic let me start by recalling
2:19
what I know about BRX series plcs I
2:21
remember that BX is a product line from
2:22
automation direct and the do more series
2:24
is their newer generation of plc's
2:25
designed for more advanced control
2:26
applications first I need to confirm
2:28
whether the BRX D more PLC supports
2:30
logic programming from what I've learned
2:31
most plcs especially those aimed at
2:33
Industrial Automation do support latter
2:34
logic because it's a widely used
2:35
standard but I should double check if
2:37
there are any exceptions or specific
2:38
details about the BRX series I think
2:39
automation direct provides software
2:41
called do more designer for programming
2:42
their plcs let me verify that yes do
2:44
more designer is the official IDE for
2:45
BRX do more plcs now does this software
2:47
support latter Logic the name designer
2:49
might imply a multilanguage environment
2:50
latter logic is one of the I 61131 to
2:53
three standard languages which also
2:54
include structured text function block
2:56
diagrams Etc since BX is a modern PLC
2:58
it's likely compliant with the these
3:00
standards but maybe the user is
3:01
specifically asking about latter logic
3:02
because they are more comfortable with
3:03
it I should confirm that latter logic is
3:05
not only supported but is a primary
3:06
method for programming these plcs
3:08
looking back at automation directs
3:09
documentation the BRX series does indeed
3:11
support latter logic along with other
3:12
languages the do more designer software
3:14
uses latter logic as one of its main
3:15
programming paradigms which is good news
3:17
for the user now considering the user
3:18
might be someone new to BRX plc's they
3:20
might need a basic example I should
3:21
provide a simple latter logic example
3:23
like turning on an output when an input
3:24
is activated but wait I need to make
3:26
sure about the addressing scheme for BRX
3:27
plcs for example discret inputs might be
3:29
addressed x0 X1 Etc and outputs as y0 y1
3:33
however BRX plcs might use a different
3:34
addressing convention let me check that
3:36
upon reviewing BRX PLC use a tag based
3:38
system which allows users to Define
3:39
symbolic names for inputs outputs and
3:41
other variables however they also
3:43
support direct addressing for example
3:44
inputs could be referenced as x0 X1 and
3:46
output says y0 y1 so a simple Ladder
3:48
rung would have a normally open contact
3:50
x0 in series with a coil y0 that would
3:52
make y0 turn on when x0 is activated but
3:54
the user might also benefit from knowing
3:55
how the software environment works for
3:57
instance creating a new project and do
3:58
more designer selecting the BRX model
4:00
configuring the hardware and then
4:01
writing the lad logic including steps
4:03
like compiling and downloading the
4:04
program to the PLC would be helpful
4:06
another point to consider is any
4:07
Specific Instructions or features unique
4:08
to the BRX series for example do more
4:10
plc's have advanced instructions for
4:12
motion control networking and data
4:13
handling but for a basic example
4:14
sticking with simple contacts and coils
4:16
is better I should also mention that do
4:17
more designer provides simulation
4:18
capabilities allowing users to test
4:20
their ladder logic without physical
4:21
Hardware this is useful for
4:22
troubleshooting and learning wait the
4:24
user might also want to know about
4:25
documentation or resources including a
4:26
note about automation directs website
4:28
user manuals and example projects could
4:29
be helpful but since the question is
4:31
about whether it's possible in a simple
4:32
example maybe that's beyond the scope
4:33
unless the user asks for it in summary
4:35
the answer should confirm that BRX do
4:37
more plcs can be programmed in latter
4:38
logic using dour designer provide a
4:40
basic example and mention the software's
4:41
features relevant to latter logic
4:42
programming also ensure that the example
4:44
uses the correct addressing and syntax
4:46
specific to BRX plc's yes you can
4:48
program a BRX do more PLC using ladder
4:50
logic which is fully supported by
4:51
automation directs do more designer
4:53
software here's a concise breakdown key
4:55
details software use do more designer
4:57
free download from automation direct to
4:59
write simulate and deploy ladder logic
5:01
ladder Logic support BRX plc's natively
5:03
support ladder logic LD as part of the
5:05
IEC 61131 to3 standard ideal for
5:08
Industrial Automation tasks like relays
5:10
timers counters and complex control
5:12
logic simple example turn on an output
5:14
with an input lad rung x0 input EGA
5:17
sensor or button y0 output EGA motor or
5:20
light when x0 is activated y0 energizes
5:23
steps to program create a project open
5:25
do more designer select your VX model
5:28
configure IO map physical inputs /
5:29
outputs to addresses EG x0 y0 write
5:32
logic drag and drop ladder elements
5:34
contacts coils timers simulate test
5:36
logic in the built-in emulator download
5:38
transfer the program to the PLC via USB
5:40
or ethernet Advanced features tag based
5:42
addressing use symbolic names EG start
5:45
button instead of XZ integrated
5:46
instructions timers T counters CTU P
5:49
loops and motion control networking
5:51
easily integrate with HMI Scot or other
5:54
plcs via ethernet/ip or modbus
5:56
documentation refer to automation
5:58
directs BRX manuals for detailed guid
5:59
sides and examples latter logic is a
6:01
core strength of the BRX platform making
6:03
it accessible for both beginners and
6:06
users like Gemini I was originally
6:08
impressed with deep seek AI it even
6:10
gives me a link to the automation direct
6:12
website where I can find information
6:14
about the bricks do more PLC deep seeks
6:17
thought process is interesting it allows
6:19
us to see how it tries to solve the
6:20
question which helps us understand and
6:24
algorithm I will now ask deep seek to
6:26
create a start stop circuit for the
6:28
bricks plc X1 is the start X2 is the
6:31
Stop and y1 is the motor
6:40
output okay the user wants a start stop
6:42
circuit for a BRX PLC using ladder logic
6:44
they specified X1 as start X2 is stop
6:46
and y1 as the motor output let me recall
6:48
how a standard start stop latch Works
6:49
typically it's a self-holding circuit
6:51
where the start button normally open is
6:52
pressed energizing the coil which then
6:54
uses a parallel contact to keep itself
6:55
on even after the start button is
6:56
released the stop button is usually
6:58
normally closed so that pressing it
6:59
breaks the circuit wait the user
7:00
mentioned X2 is a stop in plcs physical
7:03
stop buttons are often wired as normally
7:04
closed and C4 safety so in the latter
7:06
logic if the physical input is in C the
7:07
PLC will see X2 is normally High when
7:09
the stop is pressed X2 opens and the PLC
7:11
input goes low therefore in the ladder
7:13
we should use a normally open and O
7:14
contact for X2 but since the physical
7:16
input is in C the logic might need to be
7:17
inverted hm maybe I should clarify that
7:19
but the user didn't specify the type of
7:21
input contacts let me assume that X1 is
7:22
an in push button start and X2 is NC
7:24
push button stop so in the latter X2
7:26
would be a normally closed instruction
7:28
because the physical stop is in C wait
7:29
no if the physical input is in C when
7:31
the stop is not pressed the input is
7:32
active X2 is on when you press the stop
7:35
the input becomes off so in the ladder
7:36
to have the stop button act as a brake
7:38
we should use a normally closed contact
7:39
for X2 that way when the stop isn't
7:41
pressed the contact is closed allowing
7:42
current to flow when pressed the contact
7:44
opens stopping the motor so the Ladder
7:45
rung would be start X1 in O in parallel
7:47
with y1 latching in series with stop X2
7:49
and C wait no wait the standard start
7:51
stop is start and O in parallel with the
7:53
motor contact y one all in series with
7:55
stop and see wait no let me think again
7:57
the standard circuit is stop and see
7:58
contact in series with start and no
8:00
contact in parallel with the motor
8:01
contact and no contact so when you press
8:03
start the motor turns on and the
8:04
parallel contact latches it the stop is
8:06
in series so if stop is pressed it
8:07
breaks the circuit but in terms of
8:09
Latter Logic the stop button if
8:10
physically and C would be represented as
8:12
a normally closed instruction X2 so the
8:14
rung would be X2 and C X1 and0 y1 and O
8:17
in parallel with X1 then y1 coil wait
8:19
maybe I need to draw it out let me
8:20
structure it step by step the correct
8:21
ladder structure for a start stop
8:22
latches the stop button X2 is a normally
8:24
closed and C contact the start button X1
8:27
is a normally open and O contact the
8:28
motor contact y1 is in parallel with X1
8:30
to latch the circuit so the rung would
8:33
be wait no let me correct that the
8:36
correct structure is the stop is in
8:37
series with a combination of start in
8:38
parallel with the motor contact so the
8:40
stop X2 and C is the first element then
8:42
in parallel the start X1 and0 and the y1
8:44
and O contact then the y1 coil so the
8:46
latter rung would look like in latter
8:48
logic notation that would
8:50
be wait maybe I'm mixing up the drawing
8:52
let me try to represent it correctly the
8:53
stop X2 and C is in series with the
8:55
start X1 and0 and the latching contact
8:57
y1 and0 in parallel so the rung is X2
8:59
and C contact then a branch where One
9:01
path is X1 and O and the other is y1 and
9:03
O in parallel then the y1 coil so in
9:08
it's wait no the y1 contact should be in
9:10
parallel with X1 so the correct way is
9:13
wait that's not right let's break it
9:14
down the current flows through X2 and C
9:16
then either through X1 and o or y1 and O
9:18
in parallel so the structure is X2 and C
9:20
is in series with a parallel combination
9:22
of X1 and O and y1 and0 then the y1 coil
9:24
so in latter logic but that's not
9:27
correct wait maybe the correct way is
9:28
the X2 and C contct is first then a
9:30
branch starts where One path is X1 and O
9:32
and the other path is y1 and O both
9:33
paths are in parallel after that the y1
9:35
coil so the rung would
9:38
be yes that's right so the stop X2 and C
9:41
is in series with the parallel
9:42
combination of start X1 and O and y1 and
9:44
O then the y1 coil so when X2 is closed
9:46
stop not pressed pressing X1 start
9:48
energizes y1 which then keeps itself
9:50
energized through its own contact
9:51
pressing X2 stop opens the X2 contact
9:53
breaking the circuit but in terms of
9:54
Latter logic elements the X2 is
9:56
represented as a normally closed
9:57
instruction forward slash X1 is nor open
10:00
and y1 contact is normally open in
10:01
parallel with X1 so the final Ladder
10:03
rung should look like wait no the y1
10:05
contact is in parallel with X1 so after
10:07
X2 the path splits into two one through
10:09
X1 the other through y1 then they merge
10:10
and go to the coil so the correct
10:12
representation is this seems correct
10:13
when X2 is closed stop not pressed
10:15
either X1 or y1 can keep y1 energized
10:16
pressing X1 start energizes y1 and y1
10:18
stays on by its own contact pressing X2
10:19
stop opens the X2 contact the energizing
10:20
y1 I should also mention that in the BRX
10:21
PLC the inputs and outputs are map is x0
10:23
X1 etc for inputs and Y Z y1 for outputs
10:25
so using X1 is start and O X2 is stop
10:26
and c and y1 as the motor output is
10:28
correct additionally it's important to
10:29
know that the the stop button X2 is
10:30
wired asn't see for safy reasons if the
10:31
wire breaks the PLC will see it as a
10:32
stop condition which is safer than in
10:33
contact where a broken wire wouldn't
10:34
trigger a stop so putting it all
10:35
together the ladder room for the start
10:36
stop circuit should be as described let
10:37
me make sure there are no errors let me
10:37
simulate mentally when X2 is not pressed
10:39
and C so contact is closed and X1 is
10:40
pressed and no contact closes y One
10:41
turns on y one's contact closes latching
10:42
the circuit even when X1 is released y
10:44
one stays on through its own contact
10:45
when X2 is pressed contact opens the
10:46
circuit breaks y1 turns off and it's
10:47
contact opens when X2 is released
10:48
contact closes again y1 remains off
10:49
until X1 is pressed again yes that's
10:50
correct so the lad logic is accurate
10:52
here's the start stop lat circuit for
10:53
the BRX PLC using ladder logic this
10:55
classic sealin circuit keeps the motor y
10:57
one running after the start button X1 is
11:00
released and stops the motor when the
11:01
stop button X2 is pressed lad logic
11:04
diagram explanation stop button X2
11:06
physically wired as a normally closed
11:08
and C button for safety open when
11:09
pressed represented as X2 with a
11:11
normally closed contact forward slash in
11:13
the ladder logic start button X1
11:15
physically wired as a normally open and
11:17
o button closed when pressed represented
11:19
as X1 with a normally open contact motor
11:21
output y1 the output coil y1 is
11:23
energized when the circuit is closed a
11:25
self-sealing latching contact y1 in
11:27
parallel with X1 keeps y1 ized after X1
11:30
is released Behavior start when X1 is
11:32
pressed current flows through X2 closed
11:34
and X1 closed energizing y1 latch once
11:37
y1 is energized its parallel contact
11:39
closes maintaining the circuit even
11:40
after X1 is released stop when X2 is
11:43
pressed its contact opens breaking the
11:45
circuit and de energizing y1 key notes
11:47
safety the stop button X2 is Inc in
11:50
Hardware to ensure the motor stops if
11:51
the circuit loses power or wire braks
11:53
addressing use symbolic tags EG start
11:55
stop motor and do more designer for
11:56
readability debouncing add timers a
11:58
physical buttons cause noise not
12:00
typically needed for basic setups
12:02
testing and do more designer open the
12:03
software and configure your BX PLC model
12:06
assign X1 start X2 stop and y1 motor in
12:09
the io mapping program the Ladder rung
12:10
above simulate using the built-in
12:12
emulator to verify the latch / unlatch
12:14
Behavior download to the PLC and test
12:16
with physical buttons for more details
12:18
refer to the BRX user manual this
12:19
circuit is foundational for motor
12:20
controls Conveyor Systems and other
12:22
Industrial Automation
12:24
tasks if we try this in the bricks do
12:27
more designer PLC simulator we you can
12:29
turn the output on but we you cannot
12:33
off if you are enjoying this video
12:35
please hit the like button below keeping
12:37
up with the latest automation
12:39
Innovations can be difficult so hit the
12:40
Subscribe button remember to click the
12:42
Bell beside your subscription to
12:44
actually receive those
12:46
notifications let's see if deep SE can
12:48
modify the program for the correct
12:50
ladder Logic for the start stop
12:52
circuit the ladder circuit diagram is
12:57
incorrect okay the user set the lad
12:59
circuit diagram I provided is incorrect
13:00
let me double check what I wrote in my
13:01
previous response the ladder logic was
13:02
drawn with X2 stop as a normally closed
13:04
contact X1 start as normally open and y1
13:06
in parallel with X1 that should create a
13:07
seal in circuit wait but maybe the way I
13:09
drew the rung is structurally wrong in
13:10
latter logic terms let me visualize it
13:11
again the user is using a BX PLC so the
13:13
contacts and coils need to follow the
13:14
correct syntax the stop button x two is
13:16
typically a normally closed and C
13:17
physical button so in the latter logic
13:18
it should be represented as a normally
13:19
open and0 contact because when the
13:20
button is not pressed the circuit is
13:21
closed Wait no that's a common confusion
13:23
let me clarify physical NC stop button
13:24
wired to the PLC input when the button
13:26
is not pressed the input is active on
13:27
and when pressed the input is off so so
13:29
in the latter logic to have the stop
13:30
button act as a break we should use a
13:31
normally closed andc contact symbol
13:32
forward slash which will open when the
13:33
input X2 is activated button pressed so
13:35
when X2 is pressed the contact opens
13:36
breaking the circuit that part seems
13:38
right but maybe the way the parallel
13:39
branch is drawn is incorrect In latter
13:40
Logic the sealing contact y1 should be
13:41
in parallel with X1 so the start button
13:43
X1 and O and y1 and O are in parallel
13:44
both in series with the stop button X2
13:46
and C wait no the standard start stop
13:47
circuit has the Stop and C contact in
13:48
series with the start and no contact and
13:50
the ceiling contact let me sketch it
13:51
mentally the main rung should be stop X2
13:53
and C contact in series with a
13:54
combination of start X1 and O in
13:55
parallel with y1 and O contact then
13:57
driving the y1 coil so the structure is
13:58
X2 and C X1 and O y1 and O y1 coil but
14:01
in latter Logic the parallel branch is
14:02
created by a branch around the X1
14:03
contact so the correct diagram would
14:05
have X2 and C in series with X1 and O
14:06
then a branch around X1 that has y1 and
14:08
O then the y1 coil let me confirm with a
14:11
ladder you're absolutely right my
14:13
initial ladder diagram had an error in
14:14
the y1 contact type incorrectly shown as
14:16
normally closed instead of normally open
14:18
let me provide the corrected circuit
14:20
with a clear explanation corrected start
14:23
logic step-by-step explanation stop
14:25
button X2 Hardware physically wired as a
14:27
normally closed NC button opens when
14:29
pressed lad logic represented as a
14:31
normally closed contact forward slash
14:34
this ensures the motor stops if the
14:35
button is pressed or if there's a wiring
14:36
fault start button X1 Hardware
14:39
physically wired as a normally open and
14:40
o button closes when pressed ladder
14:42
logic represented as a normally open
14:44
contact sealing contact y1 function a
14:47
normally open and no contact of y1 in
14:49
parallel with X1 when y1 energizes this
14:51
contact closes creating a self
14:53
sustaining circuit latching motor output
14:55
y1 energizes when the circuit is closed
14:56
and de energizes when the circuit breaks
14:58
Behavior starting the motor press X1 the
15:01
circuit closes through X2 closed and X1
15:03
closed y1 energizes y1 inoc contact
15:05
closes latches the circuit even after X1
15:07
is released stopping the motor press X2
15:09
X2 zenc contact opens the circuit breaks
15:11
y1 de energizes y1 Zeno contact reopens
15:14
unlatches the circuit key fixes from
15:16
previous diagram y1 contact type change
15:18
from forward slash n C2 and no to enable
15:21
proper latching parallel Branch logic
15:23
ensures why one's contact is in parallel
15:24
with X1 not in series testing and do
15:27
more designer assign addresses X 1
15:29
equals start and no physical button X2
15:31
equals stop and C physical button y1
15:33
equals motor output simulate use the
15:35
emulator to verify press X1 y1 stays on
15:37
after releasing X1 press X2 y1 turns off
15:40
why this works safety X2 breaks the
15:42
circuit when pressed fail safe design
15:44
latching y1 Zen contact seals the
15:46
circuit eliminating the need to hold X1
15:48
thank you for catching that error let me
15:50
know if you need further
15:53
clarification deep seek still has the
15:55
Simple Start stop lad logic incorrect in
15:57
a circuit diagram for the Logic the stop
16:00
X2 or normally closed should be outside
16:02
the ceiling contact from the start X1
16:06
input here's a modification required in
16:09
the ladder logic programming software
16:11
although we were not able to get deep
16:12
seek to create the ladder logic it was
16:14
interesting to see how the logorithm
16:19
problem five languages can be used to
16:21
program plc's using the IEC 611 31-1
16:25
standard AI large language models llm
16:29
using textual languages seem better
16:32
suited over graphical control structured
16:35
text and instruction lists are the two
16:37
textual PLC programming
16:41
languages we recently used AI to program
16:43
the ls electric xgb PLC inst structure
16:46
text click here to see how we did it
16:49
click here to see the entire series on
16:51
the bricks do more PLC and simulator