CODESYS: Function Block Diagram (FBD) programming - First lesson
ฝัง
- เผยแพร่เมื่อ 3 เม.ย. 2016
- If you want to watch the videos in order, download the up-to-date version of the road map from the pinned comment of the corresponding video: • CODESYS: A road map fo...
-------------------------------------------------------------------------------------------------------------------------------------
In this video, you will learn the basics of programming PLCs with Function Block Diagramming (FBD) language. FBD is a graphical language, in which you deal with the blocks and the connection between the blocks.
Simple and direct. Perfect. Thank You Tohid.
Thanks a lot for your nice feedback.
Well done many thanks Mr Tohid
Thanks for the comment!
thank you very mach
Useful. Thanks. (Personally I'd like it WA-A-AY better without the music.)
Sorry for the music in the background. Certainly it was not a good idea to have it. I may redo similar videos without music in the future. But for now, I do not have the option of removing the music.
Pretty clear. I found the music distracting.
Duuuu duh duh deee
Hello sir,
how to create or download or add, 8051 microcontroller target file in CODESYS.
Hi Sayed Ali,
Sorry, but I do not have an answer for you. I am not sure if it is possible.
Good day Tohid, Do you know how to drag a connection from block to block?
Well, with FBD you do not have sucha freedom in placing the elements, and then making connection between the blocks (for this, you can use CFC instead of FBD). In FBD, you place the blocks in the rungs (networks) and you need to specify how the blocks are connected.
Now I have the problem with connection one block's output to another block's input if they are not in one line. For example my AND block is slightly below OR block, so they can't connect. If I drag whole AND block it will lose it's input branch.
Well, in FBD you can not simply do draging of the elements, specially between the networks. To have freedom in this sense, switch to CFC. Otherwise, you need to put the elements in the same network.
It is in the same network, may be there us some hot key combination to automatically connect them?
As far as I know, when you insert a block within FBD, you need to specify to which pin you would like to connect it. I mean, first you specify the connection, and then insert the block, and the connection gets created automatically. You can not put several blocks freely and then specify the way that they should be connected to each other.
I hope this helps you.
Hi, my toolbox is empty and I have no idea how to get anything to display on it
i dont have the whole bar with the insert box, etc.
It seems that your installation is not complete. Either install a fresh version or install the missing components.
@@TohidAlizadeh I've asked around, my program was running under ST and not FUP. Thanks for you help
Give link of software
you can get it from store.codesys.com
I dont understand why the Motor would run if stops is true. For me the logic should be a invers on the stop, so the motor only runs if stop is false. Like for example if you press a stop button, you would not like to have the motor start to running.
This is a safety feature. If the stop button loop had an open-circuit wiring fault, the input would stay true for a negated contact and allow the motor to keep running. Since a seal-in contact is used (in this case), there'd be no way of stopping it apart from (in more general cases) hard-wired e-stops, lanyards, limit switches or by isolating the motor supply. By ensuring that the stop button input on the PLC needs to see 24VDC for a ready-to-run or running condition, it causes the motor to stop if the wiring to the stop button went open circuit for whatever reason. It's certainly possible that the loop could short-circuit and provide a continuous 24VDC to a NO contact too, but this is less common than an open-circuit fault.
For any field devices, it helps to consider what the likely faults are and then wire them up and configure the PLC I/O so that the system fails as safe as possible. If it were just a software exercise, it wouldn't be so much of a problem, since only logical conditions are really what matters. In the case of physical control that can potentially hurt someone, some extra considerations need to be included for an overall design and implementation that protects people, the environment and equipment.
I used to think along the same lines as you. It wasn't until fault-finding in the field for a while and reconsidering the situation that I eventually realized why some things are better configured in a particular way. Still, your post was 4 years ago and perhaps you know the above quite well by now. It's a great question though and I thought I'd put a response in here in case anyone else comes across it with the same question in mind.