kolyur
Lifetime Supporting Member + Moderator
I am using an SLC 5/03 for recipe handling. The recipes are stored in one data file (16 recipes of 16 words apiece) and are accessed with indirect addressing. Using an attached PanelView, the operator can call up the different recipes and edit them.
This has worked great with one exception... the operator's modifications are easily overwritten if somebody (usually me) downloads a program update without uploading data table information first. I have read in other threads that it is not possible on the SLC platform to download only the program files without the data files.
So I was looking for a way to keep the recipe information safe and I had the idea of adding a small PLC to the network (DH485) which would not be running a program but I could read and write recipe info to it using the MSG command. I can get a ML1000 for under $100 but I found out that the integer file is only 105 words and you can't add more data files. So the next step up is a ML1200 ($300), which is not unreasonable, but it seems like overkill just for data storage.
Has anyone tried this or any other methods for retentive SLC data storage? I would be interested to hear other opinions.
Thanks,
John
This has worked great with one exception... the operator's modifications are easily overwritten if somebody (usually me) downloads a program update without uploading data table information first. I have read in other threads that it is not possible on the SLC platform to download only the program files without the data files.
So I was looking for a way to keep the recipe information safe and I had the idea of adding a small PLC to the network (DH485) which would not be running a program but I could read and write recipe info to it using the MSG command. I can get a ML1000 for under $100 but I found out that the integer file is only 105 words and you can't add more data files. So the next step up is a ML1200 ($300), which is not unreasonable, but it seems like overkill just for data storage.
Has anyone tried this or any other methods for retentive SLC data storage? I would be interested to hear other opinions.
Thanks,
John