Ascii Issues

It now functions properly...🍺 Thank you all for your help.


My boss just asked me if there is a way for the customer to add parts and limits through the HMI to the already 15 existing parts?
 
...My boss just asked me if there is a way for the customer to add parts and limits through the HMI to the already 15 existing parts?


The original has the parts' definitions hard-coded, so no, not with that code (did it work by the way or did you have to change a few things?).



With another approach then possibly, but it would be fairly involved, and limited to around 50 different parts with the current system, although that could be bumped to 128 (supply lower limit and range only) or even 256 (put lower limits and ranges in separate files) with indirect addressing and a different approach to the arithmetic while keeping the info in the PLC. If we export the information then the number is essentially unlimited, but then the system is also more brittle.


Another issue would be buttons for the HMI: is it possible for the HMI to add screens or buttons to itself programmatically?
 
...My boss just asked me if there is a way for the customer to add parts and limits through the HMI to the already 15 existing parts?


Actually there may be a fairly simple, if limited, way to do this: the current code uses 15 bits of B3:0 and B3:1 (i.e. bits 0 through 14 of each); that leaves the 16th bit, bit 15 unused*. It would be straightforward to add a few branches to process that bit, and the L12 WEIGHTDATA file already has room for a 16th set of weight parameters. Then create one more item on the HMI menu, call it "Custom," and provide a way for the operator to input weight parameters as well as a way for the HMI to write those parameters to the PLC from the HMI when that Custom part is in use. I assume the HMI is already writing to bits in B11:0 to select the part.


This does not provide a way to add multiple custom parts ad infinitum, but if custom runs are rare, then it might be a workable solution.




Also note that any approach that allows the operators to add multiple parts' specifications over time will be volatile i.e. a PLC reset, or long-term power failure or shutdown, or replacement might lose all of the operator/HMI-added parts i.e. those that were not hardcoded in the original program. So if they want to go to that level, it is better done in a database (or other non-volatile storage**) apart from, and accessed by, the HMI or PLC.



* It is not that the number of bits is limited to 16, however far more extensive modifications would be required to go beyond that with the current B11 file layout, while adding only the 16th option can be done with limited, surgical changes.


** This could be as simple as a paper hardcopy log book, if events that cause them to be lost are rare enough, and they are then added back manually from the book as they are used.
 
Last edited:

Similar Topics

I have a Keyence vision system (camera which will read text and output what it reads in ASCII) and a Productivity 2000 PAC. I am sending the ASCII...
Replies
27
Views
3,313
I have an L24ER-QB1B with a 1769-ASCII card in slot number 4. I'm looking to send data to this zebra printer after every completed sequence. I'm a...
Replies
2
Views
403
Hi to everybody. I need to read the first 12 characters of the message that a barcode reader sends to the ascii card (1734-rs232 ascii) and I...
Replies
8
Views
685
I am trying to import addresses and symbols from a PanelBuilder32 application into the RSLogix 5 Address/Symbol database - however each time I...
Replies
5
Views
503
Good day! I am working on a project at our campus to integrate fleet vehicle chargers with load management so we don't overwhelm our service. The...
Replies
37
Views
3,694
Back
Top Bottom