Jump to content

Simon

MVP 2014
  • Posts

    595
  • Joined

  • Last visited

  • Days Won

    34

Simon last won the day on December 16 2022

Simon had the most liked content!

2 Followers

About Simon

Contact Methods

  • Website URL
    http://www.colterlec.com.au

Profile Information

  • Gender
    Male
  • Interests
    Unitronics Distributor

Recent Profile Visitors

37,318 profile views

Simon's Achievements

UniGuru

UniGuru (4/4)

54

Reputation

  1. 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
  2. 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 🙂
  3. The most secure way to prevent this is with a VPN. Unitronics have UniCloud, but there are 3rd party options as well.
  4. 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.
  5. 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 🙂
  6. Hi Michael, It sounded like a firmware issue, good to hear it has been resolved. SImon
  7. 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
  8. 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
  9. Also just checking, did you select the correct coefficient in the hardware configuration: Also, what temperature range are you measuring?
  10. The "Burn Upload Project" option should also burn the project to flash so it isn't lost if the battery goes flat. Try doing a test with the battery removed.
  11. 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
  12. To add a related point, if it is safe to access the PLC with the power on, and the battery cover is accessible (no snap in module installed) then you can replace the battery without powering down the PLC. While the PLC has 24VDC power, the battery is not required for retaining data. Simon
  13. 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
  14. 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
×
×
  • Create New...