Jump to content

Alexander

Members
  • Posts

    390
  • Joined

  • Last visited

  • Days Won

    18

Posts posted by Alexander

  1. This should be possible using simple contacts and coils in our system. If you have not worked with our products before I would recommend watching a few of our basic webinars that will help you get started programming the PLC's. Starting out I would highly recommend the following webinars which should be helpful:

     

    ·         Lights and Buttons Programming – Basic

     

    ·         Timers, HMI Jumps & More Programming – Basic

     

    http://www.unitronics.com/support/webinars

     

    These webinars should be helpful in getting started using the software by going through example programs and VisiLogic operation. Also helpful are a variety of example programs built into the VisiLogic software. They can be found within the Help/ Examples folder in VisiLogic.

  2. The Previous Screen jump would only just to the last HMI that was active, which in your example would be HMI 101. If you want, the ESC button could always jump to HMI 5.

     

    The issue becomes how do you know which screen you want to be the original? If the user is on HMI 102 then selects different screens the PLC will have to know that when the operator presses ESC they wish to go back to only a particular screen.

     

    One solution for this is to have a "Set Home" button on each page. When enabled it will then trigger logic in the ladder so that when the ESC button is pressed, and a certain set home bit is active, it will jump to the desired screen.

  3. Flex, you are correct that was my mistake. Although I had read it was the Samba, my mind went to UniLogic since we were in this subforum.

     

    Gherman, it would be a similar process to accept and send ASCII strings with the Samba over RS232. Please find the correct tutorial for the FB protocol blocks which will be used for the Samba and our ViisLogic software.

     

    http://www.unitronics.com/support/webinars/fb-protocol

    • Upvote 1
  4. Modbus is a defined protocol that does not use a changing message format. It sounds as if the loadcell you are connecting with uses a custom protocol as you defined. This can absolutely be read into our controller using the Message Composer features within UniLogic.

     

    If you are unfamiliar with this feature or custom protocols we have a helpful webinar that should help explain how to set it up within our software. This will allow the application to both accept ASCII code and send replies if necessary. Using the link below or navigating to our YouTube channel there is a tutorial regarding the Message Composer.

     

    Message Composer Tutorial: https://www.youtube.com/watch?v=G8bWtpYDt7E

  5. All you should need to perform is the TCP/IP connect function within the ladder. Once the controller connects to the PC running DataXport, it will automatically collect all of the data that was set up for that site.

     

    I did notice that in your application the Comm Test button was referenced as a direct contact in the logic. This will cause it to be triggered each scan that your finger holds it down, it may be 10's or 100's of times which can cause issues with the TCP/IP connect block. I would suggest changing the contact to a positive transition so that it can only occur once each time it is pressed. Otherwise the ladder is set up properly where it can only perform a connect operation if the socket isn't already connected.

  6. Currently the only way to modify the slaves IP address to use the advanced Modbus function blocks, and is not available within the basic Modbus configuration. These settings are not enabled by default but can be added by navigating to the Project menu, selecting Options, then enabling the check box for the Modbus advanced ladder functions. There is also an example project available. Please send an email to support@unitronics.com and we would be happy to send it to you.

     

    This requires the ladder to manually connect using the TCP/IP connect block, and then build a struct of information for the Modbus commands. This would allow the IP address of the slave device to be dynamically changed.

  7. The last couple of nets were causing an issue with the sequence. By eliminating these nets, and causing the 2nd set out of outputs (O2 and O4) to be powered once the first set was done I found to be an easier solution. Once O3 finishes (negative transition of O3) then that will start the next TE timer for O5.

     

    As a safety I added MB15 in front of each output net. This will prevent them from running when MB15 is off. Also the last next will reset all 4 timers when MB15 is off so they will not continue to run.

     

    On Off Control

     

  8. When I navigate to the Product Overview page and select the V700 I am brought to the page linked below, which is different than the original one you had linked. Please let me know if the link is still problematic. If possible please send a screenshot of the element you select into support@unitronics.com so that we can correct the link.

     

    http://www.unitronics.com/plc-hmi/plc-vision-enhanced/v700-

  9. It is not recommended to place any touch element in the top right of the screen due to the UniApps menu. When placed in the same area it could interfere with the operation of the controller since the UniApps menu will appear after a few seconds of holding down the top right corner of the screen.

  10. The limit for each folder is only 64 files. Attempting to store additional information past this limit will cause errors such as the file corruption. Although the folder may accept additional files if you attempt to write it will cause issues when trying to read, write, or delete folders which can cause the corruption as shown in your previous post.

     

    I would recommend using an incrementer that limits how many times the DT to SD function can be triggered. Once it logs it’s 64th file prevent any additional files from being created unless the SD card is cleared. The incrementer can then be reset and comparison statement will allow the function to operate again.

     

    If possible I would also recommend adding in the SD card is Present and SD cards is write enabled, SB 217 and 218 respectively, before the DT to SD write block. This will ensure that it will only execute the function if an SD card is detected and able to write information.

     

    By manually tracking how many files are written to the SD card this should prevent any possible data corruption in the future.

  11. There is a way to hide the element using the Tag: Visibility attribute in the properties window. This will perform the same task as "hide" in VisiLogic.

     

    There is not a marking color, though the disable color can be modified instead of the standard grey. Another way to draw attention would be to place a simple colored rectangle behind the element that could be hidden by default, but then enabled which would put a border around the element or change the background color if the background of the element is transparent.

×
×
  • Create New...