Jump to content

Paul Rylatt

Members
  • Posts

    40
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Paul Rylatt

  1. Two questions about the vector:struct function: 1. For the "Length" value, is there any way to make it variable, i.e. using a MI to change its size? 2. What does "Import" do, since it is not covered in the Help system? Thanks.
  2. Is there a way to read all of a certain type of input, i.e. digital or analog, and directly store into MB or MI locations without having to provide a ladder for each item being read? For example, the V350-35-TR6 has digital inputs I0-I7. These need to be placed into MB0-MB7 for internal processing. I would like not to use 7 ladders to do this if it is possible. If it isn't, oh well. My application will have remote I/O of a variable quantity for each project and I would like to not have to modify the software each and every time, especially since the input quantities could get upwards of 100 or more.. Thanks.
  3. For running the V130 as a MODBUS RTU slave over RS-485, my preferred method is shielded-twisted-pair cables with termination resistors at each end and the shield grounded at only 1 end, usually the Master end. These cables must be rated for the maximum voltage present in the installation. You will need sufficient conductors in the cable to provide all the required signals that can be found listed on the V130 technical documents. I would not recommend using this cable for anything else. If you are running the V130 as a MODBUS TCP/IP slave over Ethernet, use a CAT 5e or CAT 6 cable. This should be either straight through or crossover, depending upon the hub/switch you are using. Most modern hubs and switches can detect either and self-configure for this. Again, only use this cable for your communications.
  4. New problem I have not seen before: 1. When I first start up a V130 the Ethernet initializes properly from the values stored in a data table. 2. Ethernet communications works correctly. 3. When I do an "Initialize/Reset" from Visilogic or "Init" from the V130, my Ethernet settings are all reset to "000.000.000.000" in the PLC, but are still correct in my data table. 4. If I completely cycle the power to the V130, all Ethernet settings are restored to the correct value and Ethernet functions correctly. I don't remember this happening before. Anybody have any ideas? I have been using V9.5.0 since it came out with a V130-T4-TR6.
  5. I am using a V130-T4-TR6 and need to verify some information on the HSO output that seems contradictory between the tech spec and the V9.5.0 help file. Per the tech spec, the HSO freq. range is 5Hz to 200kHz. According to the help file, a value of 0 can be used but is not mentioned in the tech spec. It seems that the 0 value is used for a constant "ON" signal. Is this value available in the V130 and if so, please verify its function.
  6. I am attempting to use the RFC-1305 block in a program on a V130. Currently, the block cycles every 5 seconds. This seems somewhat excessive. I would like to make it adjustable so that the user has control over the cycle time and can eliminate unnecessary clock server calls. Another problem is that if NIST servers are used, pings faster than every 10 seconds are considered denial-of-service attacks and geographically remote PLCs without an intervening local PC clock would not be able to use UTC.
  7. I am currently using the 3.4(18) version of the V130 operating system. What is the current version and how is it different from the version I am currently using? I want to know what the effects could be on programs written with Visilogic 9.3.1.
  8. I am having a problem reading the MF variables via Modbus on a V130. I have not been able to download any values. When bitwise downloading all registers from 7700 to 7800, no bits are set. The MF values display correctly on my HMI screens. Any ideas on why Modbus is not picking up these values.
  9. Is Unitronics looking into what would be required to implement IPv6? It seems this is coming pretty fast and is inevitable.
  10. A customer wants to know if the ethernet connection is half or full duplex. I have set the V130 to use MODBUS TCP/IP over Ethernet. This is the only socket I make available to the customer.
  11. I have not been able to find this in the documentation. The Ethernet card for the V130; is it full and/or half duplex and what network speeds can it run at? I currently have a test unit at my desk hooked to a gigabit switch and running at 100Mbps. I am figuring that is the speed limit since my companies network is 1000Mbps.
  12. Is there any way of putting the updated boot files for 9.0.1 on the controllers other than via the RS-232 port from a PC? The application that the V130 is used for does not allow for access to the back of the PLC for temporarily attaching RS-232 cables. The V130 units out in the field will not be able to have the 9.0.1 boot files customer-installed. The software used on these units is subject to occasional updates. Otherwise, I will have to maintain 2 versions of my software, 1 for 8.6.3 and 1 for 9.x.x and after.
  13. Is the Remote Access Version 9.0.1 compatible with programs written under Visilogic 8.6.3?
  14. I cannot load a 9.0.1 clone file onto a machine running an 8.6.3 clone file or a pre-9.0.1 PLC boot file. It will not load. Also, if I attempt to load an 8.6.3 clone file onto a machine running a 9.0.1 clone file, the PLC goes into stop mode and display a manufacturer's system screen. Why the compatibility issues? I cannot adopt 9.0.1 until these compatibility issues are resolved. The PLC I was using for software development has been mothballed until this is resolved. Luckily, I have an older PLC that I could load the 8.6.3 clone file and has the old PLC boot file.:(
  15. It would be nice to erase files from the SD card from the front display. Make it a third option along with loading and saving files from/to the SD card.
×
×
  • Create New...