Search the Community

Showing results for tags 'warning'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Found 3 results

  1. Good morning Today I have the honor to present you our project, on which we have worked the last months. We have been annoyed for years that when creating software in special machine building, sometimes the same/similar messages are created over and over again and then they are described similarly or the same in the machine documentation. The thought, if the mechanical components are mostly the same/similar, the error description can also be "copied" (at least initially). An Excel table with the error numbers seemed to us here a good beginning, however it would be practical, if with each message text also still the description to the message in a document, including pictures, tables etc., were deposited. This was then the point where we first thought about an online tool. This also solves problems with collaboration and makes it possible to work together. Also additional languages can be added if a machine is to be rolled out to a new market. PLC-Alarm is a young Austrian startup founded by PLC programmers to ease the handling with machine messages and their descriptions. Therefore we tried to solve the following problems besides the creation of an error list: Working together on message lists Hierarchical creation of message lists Inheritance of message texts and message descriptions to lower-level projects Adding additional message lists to make message texts more variable. Adding a description to any message text in any language via Google Docs. (Connection to Microsoft Word-online is in progress) Document template for uniform presentation Combining all message descriptions into one machine document file. Highlighting used messages to avoid having unused message text in the message list. And to shorten the machine document file. Upload a file containing the used message numbers to mark them automatically. Any export options for PLC, SCADA and HMI systems possible. (Currently optimized for TIA Portal only). Suggestions for additional features welcome As mentioned in the last point, currently only exporting for a TIA Portal text list is possible since the first customers are also programming on Siemens. But we are looking forward to extend this according to customer requirements. Do not hesitate contact us via e-mail. We invite you to test our free web applications and leave your feedback. The application is already successfully in use at the first customer and we are looking forward to more users. Homepage: https://plc-alarm.com WebApp: https://www.plc-alarm.app Thank you for reading to the end ;) Have a successful day Franz Pachinger PLC-Alarm.com Support@plc-alarm.app
  2. Hi, I have an OS32C-SN-DM Omron laser scanner on test and I am trying to set/read scanner parameters via Matlab, over TCP. The communication works as I am able to read the scanner range data etc. But I have a problem with changing zone set via Ethernet/IP (TCP) communication. I am using Omron OS32C Configuration tool 2.2.8 and the scanner OS32-SN-DM should support changing the zone set via EIP. In the Configuration tool I set Warning zone selection by EIP to Enable as shown in attached picture. The feature of changing the warning zone over EIP is explained in single paragraph: 4.21 Active Warning Zone Set Selection When the scanners "Monitoring zone" is configured for multiple detection zone sets and the "Warning zone selection by EIP" is enabled, the EtherNet/IP interface can be used to change the active warning zone set instead of using the zone inputs. When this feature is enabled an EtherNet/IP network device must select one of the 70 possible preprogrammed warning zone sets before starting normal operation. For more information on zone configuration and selection, see sections "Zone Set Selection and Configuration" and "Zone Set Input Selection" in the OS32C user manual. The switching time of the active warning zone set using the EtherNet/IP interface is one scan cycle or approximately 40 milliseconds. Output assembly objects 113, 114, 115 each can be used to define the active warning zone set as well as the vendor specific object 115 listed in Table 4.   I am using vendor specific object 115 (0x73,1,7) to change the Active Warning Zone Set, but the scanner is always in error code 70 (Incorrect number of active zone set select inputs (guarded machine stop). I tried with automatic mode, Start interlock mode etc, but the scanner always expects the digital inpuits to change the zone set.   Does anybody have any idea what could be a problem as the Omron local support does not know the answer. Thank you very much for any suggestion!   Jure  
  3. Hallo Community, i have the Problem that my complete project is made with grandient objects and my PV cant display that. When i was making a runtime application i got some warnings. "<MomentaryPushButton2> on display <Allgemein - PackML_State_Time> is using a Gradient Fill. When running the MER on a PanelView Plus 6 terminal, the system cannot process certain gradient fills. When running the MER on a computer, the system can process all gradient fills, this warning does not apply. Please refer to the online help for more detail on this warning." I got this message for every button on every side. The problem is that i dont use PV6 and because of that i thought its ok to ignore the warnings but on PV7 i have also no grandient and my objects are all blank now. Did i make something wrong? Thanks in advance!   Mit freundlichen Grüßen, Best regards Adrian Düringer