Jump to content

Cam

Members
  • Posts

    218
  • Joined

  • Last visited

  • Days Won

    14

Posts posted by Cam

  1. No the PLC doesn't need to be in a specific mode in order to upload, Run mode or Stop mode either is fine.

    If you know which version of Visilogic the program was originally written in you can try using it, however a newer Visilogic will upload a project written in an older version.

    As for the run-time errors, I  haven't ever had that issue.   I'd suggest taking screen shots and sending and email to support@unitroincs.com.

  2. Take a look at the UniDownloader software tool.    It lets you create compressed download files to send a customer so they can update PLC's with out seeing the ladder code or needing Visilogic.   You can even include an O/S update if needed.

    Download page

    https://www.unitronicsplc.com/software-visilogic-for-programmable-controllers/

     

    Download link

     

    https://downloads.unitronicsplc.com/Sites/plc/Visilogic/Download Software Utilities/UnitronicsUniDownloader_5_0_B29.exe

  3. I’ve seen PLC brick during O/S updates but never during a program down load.   A EX-RC1 is basically a stripped down V120.

    I’d try the following 

     

    1) what baud rate is your communication set to?   If you communicating with an EX-RC1 it should be 57600

     

    2) If you can’t get communication established with the EX-RC1 via a serial link , yet you are able to communicate with the V280.  You should be able to use the V280 as a bridge to talk to the EX-RC1 over the CanBus connection.    You would need to look at your communication setting and change from a direct connection to a Within Network.    Then select the ID of the node (in your case 2) to communicate with. Try getting the OPLC information.  It should come back with the EX-RC1.   You should now be able to down load as normal.

     

     


     

     

  4. 16 minutes ago, garydreppert said:

    According to all the documentation I have it does. I am able to get the vision 700 to connect to the actuator controller I'm just having trouble figuring out how to send receive messages between the 2.

    You might be able to get it to connect to the IP address, however you not going to be establish an IO connection to pass data with  explicit or implicit messaging as the Vision series doesn't support Ethernet/IP protocol.     It supports Ethernet TCP/IP (which is something entirely different), or Modbus TCP as Ethernet communication protocols.

    Unitronics built Ethernet/IP communication into the UniStream series of controllers, I'd recommend contacting your local distributor and seeing about getting one of them to do this as it supports the required protocol.

     

  5. The manual you provided states that it's for Ethernet/IP communication between a AB unit and the IAI actuator.    The V700 doesn't support Ethernet/IP communication protocol.   I'd recommend looking at a UniStream(US7 series if you want the same size display) as it supports the required protocol and with the supplied manual you should be able to created the required structs to establish the Ethernet/IP communication.

  6. IngitionComm is a FunctionIn Tag which is linked to IgnitionCommunition from the 02_Input Map.

     

    The reason you can’t see the IgnitionComm changing state when in online mode during testing is a quirk in the UniLogic programming software.   FunctionIn, FunctionOut and Local tags are not monitored by default when you’re in online mode,  you need to turn on monitoring function for this UDFB/Subroutines that they are in, so you can see them when online.

     

    To do so please do the following:

     

    -In 01_Main Function right click on the 06_Ignition Call Func located in net 5

    -Select Monitor “06_Ignition”

    -Select the 06_Ignition subroutine from Module 1 by left clicking

                    -In Net 5 right click on the 06_AOI_TraceTrace_Client_NOAC2 Call Func

                    -Select Monitor “06_AOI_TraceTrace_Client_NOAC2”

    I did check the logic and when the process value is 2012 and IgnitionComm(passed from Ignition Communction) is active TraceDataRecorded does Set, it's not visibly set as it resets almost instantly due to net three in 06_AOI_TrackTrace_Client_NOAC2.

     

    One draw back is turning on monitoring apparently prevents you from editing Tag values in the subroutine your monitoring.  I did ask support about it and they are verifying if that's the intended functionality or not.

  7. Hi Victor,

     

    You have a power up value set for MI 3 of 30   when ever the PLC goes through a power up cycle MI 30 will be set to 30 regardless of the value that was in that MI when power was removed.

     

    The check box to the right of the DEC drop down is controlling this.  If you don't want a power up value remove the check mark in the box.

×
×
  • Create New...