For items that reference a slot number or a file number, that information is embedded in the text as well. The tag is set up with a multi-state format with 93 states to cover all of the error code texts as found in the RSLogix500 Online Help. This zipped cd3 file, built with Crimson 3.0 version 469.000, contains a tag (Status.SLC_ErrorLSW_Dec) which will display all of the error codes for a SLC. This app also includes SLC communications with alarming, and SLC error codes with complete text, and language switching (English and Spanish, but the Mexican flag icon was not properly saved with it, so if you click the American flag, it will disappear and switch to Spanish (machine translated!) just touch that area again to switch back to English. My goal with this conversion is to make it as easy as possible for veteran operators to adjust when we replace the Panelview 1000, so I made it look as much like the PB32 object as possible.ĮDIT: I should explain, to get the the page with the page list selector, hit the button at the bottom, 2nd from the left labeled "Screen Menu". Right now, it is set up for 50 pages, with a visible length of 14, but that is easy enough to change. It is built for a G310 and there are comments in the program files with some instructions for how to customize it for different lengths. I thought it would be a nice thing to have access to for those of us who have a lot of PB32 to G3 conversions in our future. I needed an equivalent to the Panelbuilder32 screen list selector for up to 26 pages with scrolling too, so I built one. If you find any bugs, please let me know.īuilt with Crimson 3.0 v707.000, tested in built-in emulator and used on Graphite G07s with both Crimson 3.0 and 3.1 runtimes. If you end up using it, toss a thanks my way if you can. You can see a mockup of a real world batch-entry view on the "Demo" page and edit the input fields to try to defeat the validation. The controls and bits on the right side of the test page allow you to tab through your pattern and the string and see what matches each char. Worth using this testbed to debug your pattern strings before using in a production environment. Pattern string syntax is described in the comments or by clicking the guide button. This can be auto-migrated to crimson 3.1. To use in your project, simply copy the pattern program folder to your project. I have also included toUpperCase and toLowerCase functions for strings. Usage is: pattern.isMatch(input string, input pattern) which will return 1 if match, 0 if not a match I also use it for serial input validation. It can be used for input validation and we needed it to enable validation of scanner gun input through the USB port. I developed this for work and thought I would share.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |