4/12/2016 12:55 PM | |
Posts: 112 Rating:
|
Hi Oreca, another basic question, for my SFC, the level transmitter is crucial. The value it gives is an input byte. Could you or anyone else tell me where I could define an input byte instead of an input word. I looked at my hardware configuration but I cannot see the option. ------------------------------------------------------------------------------------------ |
Last edited by: AGrS at: 4/12/2016 12:56:03 PMLast edited by: Min_Moderator at: 4/12/2016 1:52:36 PMNew subject after splitting |
|
4/12/2016 2:12 PM | |
Joined: 3/14/2008 Last visit: 8/16/2024 Posts: 2086 Rating:
|
Hello!
What module are you using? Are you sure it is the correct module you configured? For your second question: There is something wrong with your hardware address if your are generating module drivers. If you are not generating module drivers, you have to set the correct "Mode" setting manually. For example: If your hardware input is a 4-20mA signal, the mode is set to 16#80000203. Please see the help file about channel blocks which modes you must choose when using a PT100 or 4-20mA signals or others. If the mode is set correctly the "Bad" signal goes away. But if you are generating the module drivers, the function creates interconnections to your Pcs7AnIn channel block. If this is not the case, there is no existing module driver for it, indicating it is not released or is a third party component. What is the type and MLFB number of the module you are using? |
Last edited by: Oreca at: 4/12/2016 2:20:22 PMIf I could help you, you can use the RATE button. Thank you. |
|
4/12/2016 3:30 PM | |
Joined: 3/14/2008 Last visit: 8/16/2024 Posts: 2086 Rating:
|
Hi, I cannot detect the module in the v8.1 library in the hardware catalog. It's successor is 1KF02. In the released modules, the discontinuation date of the 1KF01 is set at 01/10. This is the problem! Try to insert the 6ES7331-1KF02-0AB0 and try a compile CFC. The module drivers will be generated by the system. To confirm I attached a screenshot. The IO with address 512 is a 1KF01 module and the IO with address IW528 is a 1KF02 module. For the 1KF02 the module drivers are generated, but not for 1KF01. Attachmentmodulewrong.pdf (220 Downloads) |
Last edited by: Oreca at: 4/12/2016 3:33:36 PMLast edited by: Oreca at: 4/12/2016 3:36:39 PMIf I could help you, you can use the RATE button. Thank you. |
|
This contribution was helpful to
1 thankful Users |
4/12/2016 9:04 PM | |
Joined: 3/14/2008 Last visit: 8/16/2024 Posts: 2086 Rating:
|
Glad I could help you! What do you mean with your last sentence? Are you talking about exchanging the 1KF01 to 1KF02 or addressing of the IO like IW1088 and/or IW1090. Maybe I can give you more info... |
If I could help you, you can use the RATE button. Thank you. |
|
This contribution was helpful to
1 thankful Users |
4/14/2016 11:10 AM | |
Joined: 3/14/2008 Last visit: 8/16/2024 Posts: 2086 Rating:
|
Well, The 1KF01 is an old module, which was not released for your PCS7 version. Normally new modules of the same type are compatible with the old ones (backwards compatible). I can't say if this is the case for everything. The same goes the other way around. In our installation, we have ET200M modules, but some are replaced by newer types. It can work. |
If I could help you, you can use the RATE button. Thank you. |
|
This contribution was helpful to
1 thankful Users |
Follow us on