|
It explains around of that in detail because there are notes and disadvantages also in FB though it explained the convenience of FB last time.
|
Commentor / R.Takeuchi |
| |
Attractive FB (2) |
Want to think the correction in RUN when there is a bug in the code of FB is usual. Tentatively, it is necessary to write, to secure the rear of E for a built in memory in RUN of FB preliminarily, and to format it though the FB function of MELSEC correspondence around of that. "Writing Area in Running" has to secure without fail need not panic when in now RUN need to change scene, and need to format it.
Generally speaking externals of FB are only the shape of "Box" and the code executed with PLC is ladder/mnemonic. Therefore, it has become not FB but a ladder of automatically generated before when the program stored in PLC is loaded.
The function of storing together CPU of PC project data to in the operation of writing that have the shape of the function block by the version named V8.03 of GPPW was included. As a result, even if the engineer who did not have former project file went to the site with only PC, and Reading was loaded, it came to be able to read it in the form of FB.
However, no adjustment occurs if there is a pitfall that only the ladder and the mnemonic are changed when it is executed in online program changes and project data is not changed, if the saving data (project data) doesn't remain by any chance. After "online program changes" is executed, the data means "not normal reading".
And it is only for me that, equipment operated while online program changes it debugs, that came to save diligently after Project data comes to save and PC has hung up RUN?
Next, before made FB want to use by another project. It is possible to achieve it with GPPW tentatively though it is not my instinctive idea of operation method.
1. A new project or the project the misappropriation ahead is opened.
(A misappropriation former project should be the same as CPU type.)
2. "Copy" of "Project" menu is selected, and the project data of the copy origin is specified.
3. Here, the structure and the function block are able to import.
At the end, some items notify when FB is used are enumerated.
- The compilation operation is needed without fail. Writing is in RUN.
- It cannot be done to have to put FB in FB (nested construction).
- FB is not put in the SFC program.
- "Device with an automatic crack" area is taken. Default is as follows.
1) Word Device : D6144-D12287
2) Bit Device : M4096-M8191
3) Timer : T64-T2047
4) Counter : C512-C1023
This range can be changed by "Device setting with an automatic crack" of "Edit" menu with the label variable screen displayed.
As mentioned above, it is "Function that can be used." when seeing in total though it has explained the charm and notes of FB. How about because of advancing at the speed with a remarkable world of PLC if it tries so as not to miss it though using a new function, and changing the current idea
Tend to take little pains? As for the function that the development efficiency seems to go up reasonably, it is worth using it.
|
|
Inside MELSEC
Advanced OPC