Jump to content

Simon

MVP 2014
  • Posts

    598
  • Joined

  • Last visited

  • Days Won

    36

Posts posted by Simon

  1. 12 hours ago, kratmel said:

    Hi.

    You must know that working with Visilogic over port1 disables port1 from working over other protocols. You can check current port settings via Info mode.

    Even when using the USB port  port1 is disabled ( through the USB - COM adapter in the PLC).

    Best option - use second com port add on card for connection  or use Ethernet card for Visilogic communication.

    You can also connect PLC with PC Terminal software for check communication.

     

    P.S.  Sometimes RX and TX wire swap is problem - TX1 go to TX2 and RX1 go to RX2 - result - no connection.

     

    Hi Jalal,

    Thanks for getting in touch. I now understand what you are trying to do. The above comment from @kratmel is the essence of the issue. It sounds like you are using the programming cable that has the MJ10-22-CS25 adaptor on it. The alternative adaptor MJ10-22-CS76 achieves the RX to TX wire swap and also has the opposite DB9 connector.  I can organise a MJ10-22-CS76 for you to try.

    Kind Regards,

     

    • Like 2
  2. Hi Jalal,

    Jus to back things up a little, the second port is not fitted by default to the PLC. From the photo you sent I can see that the port 2 slot is empty:

    image.png

     

    The expansion port is completely separate to the add-on COM port. When you are trying to run serial comms and also debug the program using Visilogic, a second port is almost essential. Part number is V100-17-RS4 or V100-17-RS4X. I'll take a guess at who you are working for, but please direct message me to confirm and we will try to help you out.

    You won't get anywhere trying to connect a USB to serial adaptor into the USB programming port of the PLC.

    I hope this helps,

    Kind Regards,

    Simon

     

     

     

    • Like 1
  3. Hi Chris,

    I'll comment here to start with. I work for Colterlec who are the Australian distributor for Unitronics.  The advice above is great, as always.

    I agree, use Modbus for the Methane instrument.

    I have asked our customer service team to quote you for the Modular option and the Built-In option. We can also assist with the Classical option if needed. Since it sounds like you are working with an existing design, let me know what items that is using.

    I'll contact you via email also.

    Feel free to continue searching for answers here and asking application questions, However if you need commercial details or urgent answers please contact us directly.

    Kind Regards, 

     

     

    • Like 1
  4. I am working through an SDI-12 interfacing project, to read sensors using a Unistream PLC.

    I originally started down the track of using a SDI-12 to Modbus gateway. However for various reasons I am now using a RS485 to SDI-12 gateway and will be creating and parsing the messages as ASCII. I'd appreciate hearing of others' experience with decoding the data that is returned from the aD0! command and similar. I'm about to do my own testing, but any tips and points to note would be appreciated. Happy to share my own experience also.

    I am using 3 sensors. The most complex is an Atmos 14 Gen 2 environmental sensor. I have set the sensor to SDI address 2, an example data exchange is as follows:

    Send: 2M!
    Receive: 20014<0D><0A><00>
    Send: 2D0!
    Receive: 2+1.437+24.9+0.457+100.38<0D><0A><00>

    values are:
    * vapour pressure
    * temperature
    * Relative Humidity
    * Atmospheric pressure

    One of my hopes is that the message length is always the same, and the number of decimal places always stays the same for each value. I don't know SDI-12 well enough yet to be sure of that.

    FYI, I also purchased a USB to SDI-12 adaptor to assist with setup and testing, which was a wise decision. 

    I look forward to any words of wisdom I receive.

    Kind Regards,

    Simon

     

     

  5. You could have a local PC talking to the PLCs via the intranet, running the PC version of Remote Operator.

    They key point is then how you access that PC from the internet. If you use port forwarding and a public IP then the old problem still remains. However with a PC involved you have access to more secure methods such as TeamViewer or AnyDesk. This would mean connecting to that PC from the iOS/Android tablet, then operating the Remote Access app remotely using the iOS/Android device. This can be cumbersome if done on a phone, but not so bad on a tablet.

    I'll give another plug for UniCloud, as it now allows creation of a dashboard sized specifically for mobile devices.

    The UCR router supports 3rd party VPNs, you would just need to have a server set up with your chosen VPN installed.

    In terms of what I recommend, I'm just saying a VPN (or similar) is the most secure. Public IP and port forwarding is just about the least secure. I'd suggest considering multiple factors such as:

    * who will use the system and what is their expertise and comfort level with tech?
    * who will maintain the system, in-house experts or outsourced?
    * how frequently will it be used?
    * will it be monitor-only or monitor and control?

    Look at your available options and assess how well they fit the intended use. From experience I'd suggest that unless you are already an expert in VPN setups, pay for a professional service rather than try to teach yourself how to set up and manage a "free" system. That's just my opinion though 🙂

     

     

     

     

  6. Interestingly I also received a similar report from a customer.  I advised them to uninstall Visilogic, also delete the following folders and reboot the PC before re-installing:

    • Delete the folder “Unitronics VisiLogic_C” from C:\Program Files\Unitronics
    • Delete the folder “Unitronics” from C:\Program Files\Common Files

    When re-installing, run the installer as administrator and once it is installed run Visiloigc.exe as administrator.

    General details on uninstalling and reinstalling are here:

    https://forum.unitronics.com/topic/694-how-do-i-perform-a-full-re-install-of-visilogic/

    The problem was still not solved after this, they were using version 9.8.94.

    They then deleted all again and installed the latest (rev 9.8.96) and the registration completed successfully.

    I hope this helps. However if it doesn't I would also recommend the suggestion by @Flex727 above, to contact Unitronics support.

  7. Hi Rob,

    You can recover comms only by powering up the PLC into Stop mode. With power off hold down the (i) key while applying power. 

    If you do a normal power up, as soon as the program starts it will configure the COM port and lock you out. If you then put it into stop mode from running mode, the COM port remains configured for Modbus. only.

    To prevent this from happening there is an alternative code for initialising Modbus. In your net 112 where you store #600 to SI140, change the #600 to #599. This allows the U90 ladder comments to be recognised by the PLC, even though the port is configurred for Modbus. Code #600 configures the port exclusively for Modbus and non-modbus comms are ignored.

    This is information is in the Modbus topic in the U90 ladder help. But I first found out about it the hard way, by being locked out of a PLC after downloading the program 🙂

    • Like 1
  8. Hi Michael,

    Just to check a couple of things.

    Is the UID0808THS the only IO module on the system?  Is it directly connected to the CPU (no UAG-XK expansion cable?  The OS update to the IO module (and any associated debugging) is easier if this is the only IO module connected and there is no expansion cable.

    When you say you downloaded a blank project, did it at least have the IO configuration set to match the actual IO of the PLC?

    Simon

  9. Hi,

    I've given some though to this to solve one of my own application issues.  I think what you are wrestling with is that you don't want your automation network to be merged with the network that gives you internet access (eg office or home network - the "non-automation" network).

    I've reviewed the interchange between Aus and John in the post ref above.

    Whilst I haven't yet implemented a solution this way I would suggest using the router functionality of the UCR-ST-B5.  Don't put in a SIM card and just use the ethernet WAN port to connect to your cabled internet connection.  The WAN IP of the UCR will belong to the office LAN that has internet access.  Connect the PLC to the LAN port of the UCR.  The LAN IP of the UCR will be in the same subnet as the UniStream and the IO devices.  You will probably only need to set up the WAN and LAN IP address in the router.  I suspect the default port forwarding will allow the PLC to talk out to the internet and find the UniCloud server.  But you should check this.

    I hope this helps,

    Simon

  10. I agree with Joe's suggestions, and would highly recommend getting this to work using the standard examples before you then try to create your own application.

    The EX-RC1 was originally created as an IO slave for Vision PLCs, and the documentation most likely still reflects this.  It has since been applied as an IO slave for UniStream as well.

    Simon

  11. FWIW I've approach the versions and compatibility question from a few different angles over the years.  At one stage I had a large number of swapper versions installed.  I've also seen plenty of messes that happened when losing track of which swapper version is currently the registered version.  I now tend to uninstall and reinstall versions if I swap, partly because it's not as often as it once was.

    As far as problems with upgrading files is concerned, keep at least 2 backups.  That way if one gets munched by a glitch, you can take a copy of the second (or third...) backup.  In my experience it's rare for programs to be destroyed with a Visilogic version upgrade.

    From a support point of view, I usually update windows, so that i am familiar with any issues that creates.  Run as Administrator is definitely one thing to always remember, and also the User Account Control setting.

    Simon

  12. Hi Miguel,

    You are describing an encoder follower.

    Firstly, in response to your second question, I think there is a speed and response time problem. Just doing the maths on your encoder signal, with a 400ppr encoder at 1800rpm, you will get at least 12,000 pulses per second.  Depending on how you have set up the high-speed input you could be seeing 2x or 4x that many pulses (24 or 48kHz).  if you want to trigger an event (PTO move) every 4 pulses, then you are trying to trigger an event at least 3000 times a second.  Even with interrupts, the fastest is 1.25ms (800Hz).  The PLC can't respond fast enough.

    Do a quick check on your encoder, turn it one revolution and see how many pulses you get.  Often the PPR specification of an encoder is for each single channel.  So a 400ppr encoder gives 800 or 1600 pulses when using the (A,B) Shaft Encoder 2x or 4x settings , or just 400 pulses if you use just a simple High-Speed counter.  

    I suggest dividing the encoder pulses by some factor so that you are executing your PTO move less frequently, maybe 10 -100 times per second.  Obviously each PTO move will then need to be more pulses.

    That's looking in terms of your second question, from that point of view. 

    However, I don't think you will get what you want by attempting to re-trigger multiple PTO moves.  This suggests each move needs to be completed before the next one starts, and that will not give you continuous motion.

    I'd suggest that you start the move when the encoder begins to turn and then continuously update the target position based on the pulses received from the encoder.  That is, add pulses to the target position, using your scale factor from input encoder pusles to output stepper pulses, and do this 10-100 times a second.  In this way the move never ends until the input encoder stops rotating.  i think this will work, but I don't have a system to test with right now.

    Hope this helps,

    Simon

  13. Hi @VFU1076

    I haven't done it but have discussed it with a customer.  The following youtube video explains the process well.  Just note that the video shows the connection using ethernet to the V570, and at that step you would set up the serial parameters instead.

     

    Hope this helps,

    Simon

  14. Hi Cveko,

    I guess the golden question is, does it still work after you put the power supply back correctly?  Do you have any "known good" examples you can test with?  Was the CAN working before this mishap?

    Also, I presume from the title of the post, you are referring to the -V and +V on the CAN interface on the V1210, not the main power supply.  I have spend a bit of time messing with Unitronics CAN.  I don't recall destroying any, and I probably crossed wires at least once somewhere along the way.

    Hope this helps,

  15. Hi,

    It all depends on the reasons why you need to use a 4-wire sensor.  Often a 4-wire sensor is used so that it can have a signal common that is galvanically isolated from the power supply common.  Is that a requirement for you?  Note also that the URA0800O does not have galvanic isolation between the input commons and the 0V supply common.

    If you don't need isolation, you can use the above module, as follows:

    * link all the sensor +24V supply terminals to the main +24V supply

    * Link all the sensors 0V supply terminals to the main supply 0V

    * Unless the sensor user manual specifically says not to, link all the sensor signal grounds to 0V common.  If possible do this at the sensor rather than at the PLC, to avoid earth loops.

    * connect the sensor signal outputs to the input channels of the URA-0800O

    Note also that the URA0400O has 4 inputs and 4 commons, which gives you a convenient terminating point for the signal ground wire. 

    If you know that you need isolation, or if the sensors are on very long cable runs and/or a noisy electrical environment, then i would suggest using signal isolators in the same cabinet as the URA0800O units.

     

    Hope this helps.

    • Like 1
×
×
  • Create New...