adccommunitymod (AutomationDirect) asked a question.
Created Date: February 27,2020
Created By: James Ferguson
**** This post has been imported from our legacy forum. Information in this post may be outdated and links contained in the post may no longer work.****
first of all, im brand new to this programming thing. i am setting up a cmore ea9 panel easy operator controls for the cavemen i work with. basically...the screen im working on is a is a list of reasons why the rod is being rejected. can push any button or all of them. ive assigned them all tags and have moved said tags to the p1000. what i need is a way to compile the data to an sd card. also need help configuring the ladder logic on the p1000 to recognize the buttons being pressed. i know its alot to ask...but im so lost right now. any help is greatly apppreciated
Created Date: February 27,2020
Created by: James Ferguson
first of all, im brand new to this programming thing. i am setting up a cmore ea9 panel easy operator controls for the cavemen i work with. basically...the screen im working on is a is a list of reasons why the rod is being rejected. can push any button or all of them. ive assigned them all tags and have moved said tags to the p1000. what i need is a way to compile the data to an sd card. also need help configuring the ladder logic on the p1000 to recognize the buttons being pressed. i know its alot to ask...but im so lost right now. any help is greatly apppreciated
Created Date: February 28,2020
Created by: ADC_CommTeam02
Can you attach your EA9 and P1000 project files? Need to see what you have up to this point to provide suggestions to get you going.
Created Date: February 28,2020
Created by: James Ferguson
i am currently moving full speed ahead. buttons are all working properly and data is being collected with every push of the submit button. not sure how i figured all this out but its working. thanks for getting back to me. have a great friday
Created Date: March 06,2020
Created by: James Ferguson
ok. i dont like the way this is going. the ladder logic in the plc is sloppy at best. effective but if i want to log the different rod failures i have to log way too many tags. how can i set it up to where if the boolean is on it will log that tag and not every off tag as well? still learning here but i am definitely needing some help
Created Date: March 09,2020
Created by: MikeN
Are you using the data logger built into the Productivity to log tags to an SD card?
As far as I know, the capabilities of Productivity logging are quite low. If you want to only log some tags at certain times and other tags at other times you have to do it in a sort of hacky method.
I personally love Productivity for most things, but any time I do data logging I use a BRX in the system and do all logging on that.
Created Date: March 09,2020
Created by: techme
Why not make your button tags momentary and use event manager to increment a tag set up in the plc? In the attached example I used internal tags, but it could be tags to a plc device. Not sure what you are trying to do in the plc logic or how your are data logging.
Created Date: March 10,2020
Created by: kewakl
Describe your desired "caveman " interaction with HMI.
Created Date: March 23,2020
Created by: James Ferguson
Implemented the pack bits function. Allowed me to basically assign a numerical value to each of the tags individually and only log the last one that was activated. Used a submit button to gather the data and reset the buttons on the hmi. Then i set up a series of timers and switches in the ladder logic to log data when i needed it to. Went from four tasks to 7 real fast. Also used the pack bits to assign users a number so i can tell who is operating the machine at the time. Cut my number of tags down exponentially. You are correct about the data logging being lax. Which is only hurting the boss mans feelings because he wants the files to look a certain way and theres nothing i can do about it. I'll just keep swimming and climbing over walls as i get to them. At least we are gathering some data and thats the whole point of this project.
Created Date: March 23,2020
Created by: James Ferguson
I would like to hear more about the BRX. If i can come closer to making the boss man happy then i can probably keep my job here. lol
Created Date: March 24,2020
Created by: MikeN
I would like to hear more about the BRX. If i can come closer to making the boss man happy then i can probably keep my job here. lol
{ "alt ": "Click image for larger version Name:\tFileLog.png Views:\t0 Size:\t34.2 KB ID:\t129606 ", "data-align ": "none ", "data-attachmentid ": "129606 ", "data-size ": "full "}
With the BRX you get a "FileLog " instruction. With it, you can choose any memory address you want to log. As many, or as little as you want. You can also have multiple FileLog instructions in a program. These instructions can be left on and set to log on their own at the top of the minute, hour, day, etc. Or on a trigger. You can also choose to save that data to an SD card, or built in RAM to the BRX. RAM will get lost if the power goes out and you have no battery backup though, but is a good place to store highly written to data that you want to export only once or twice a day.
So for you, a bunch of FileLog instructions could be set up and each is triggered from a different button on the HMI and would store a different memory address ' data (or a string of text). Or some other setup that you feel works better for your situation. The biggest part is you can have a bunch of FileLog instructions and choose how much or how little data you want to log in each one. You can also have multiple instructions write to the same log file and they will append data to the next line, or they can all write to a differently named file to keep things separate.
There is also an email instruction that lets you sends that data out of the PLC to an email somewhere. Again this can be set up and left on, and send an email with the log on the top fo the hour, day, month, etc., or triggered from a tag/event to send the email. You can email a log file either stored in the SD card or the RAM.