Jump to content

Joe Tauser

MVP 2017
  • Content Count

  • Joined

  • Last visited

  • Days Won


Joe Tauser last won the day on October 20

Joe Tauser had the most liked content!

Community Reputation

328 Excellent

About Joe Tauser

  • Rank
  • Birthday 02/06/1964

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Interests
    Antique Radios!

Recent Profile Visitors

21,837 profile views
  1. Post your program so we can see how you're handling Modbus. Joe T.
  2. This is actually not a trivial problem. It consists of three logical parts: 1. The primary TD timer (not hard) 2. The blinking lamp is achieved by two more timers - one for ON and one for OFF off the lamp. 3. Some math to examine the primary timer's preset vs accumulator %, decrease the OFF timer's preset, and increase the ON timer's preset. The sum of those two presets must equal the primary timer's preset. This is probably the easiest solution. If you want to take a swing at it and post your program we can probably help. Joe T.
  3. No easy out. The Data Table is the way to go. Joe T.
  4. The current date and time are bundled together in the SI registers so that a four digit number represents hours and minutes and/or month and day in a single number. You're going to have to do some math to strip them apart by dividing by 100 and then extracting the remainder out of SI 4. Post your program so we can have a look. Joe T.
  5. I would not continually force a value to the PID status register. The PID block should write that value all by itself to report what it's doing. Here's how I do PID- I also always make something on another screen to allow manual tuning- As far as manual tuning goes, I posted this a while back- Manual loop tuning 101: Start with Kp = 100 (10.0%) and Ki = 0. Then start lowering Kp until the process starts to just ring around the setpoint. If it overshoots wildly you need a bigger Kp. Measure the time between peaks. This is the natural c
  6. @t0r3r0s - please don't post the same problem in more than one place. Joe T.
  7. Is the screen totally blank? For starters, look in the Help under topic "bootstrap" on how to get the PLC into a mode where it will be more cooperative. A V280 is a standard PLC, as opposed to a V570 which is an enhanced unit. The suggestions here don't necessarily apply. The default baud rate for a V280 is 57600. Visilogic does not automatically try this baud rate, but relies on what the user sets it to. Joe T.
  8. No, there's not and you are definitely in the deep end of the pool. PCOM has become a legacy thing with the development of UniStream and I wouldn't expect any updated documentation to appear on the website. I looked over the PCOM document and the section on Data Tables is pretty short and ambiguous, as you have found. The fact that the newest PLC listed in it is a V280 is not encouraging. For your specific question, all Unitronics timers in a Vision are 0.01 timers with 32 bit values for the preset and accumulator. The HH:MM:SS.ss display is done in the software so us humans can under
  9. Do you have the wired Enable signal on the drive terminals connected (DI0)? Joe T.
  10. I thought this sounded familiar. Your Modbus words probably need to be swapped to have the correct value. Notice I said WORDS, not bytes. Keep in mind that Buffer data types are 8 bits (bytes), while Modbus returns registers in 16 bit words. This is VERY IMPORTANT - have you been able to actually read a value from your meter? What is that value? Do you know what the corresponding floating point value is? There is no right answer to this. I know you're trying very hard to get a firm definition, but the byte and word order on a floating point number varies from manufa
  11. I looked up IEEE 754 regarding Modbus and it seems that it's a standard floating point format, which is 32 bits. Have you tried reading it into a REAL data type? Joe T.
  12. I found when I went to move a program from Vision to UniStream that there were a significant number of differences between the way Vision does things and the way UniStream does things. Some function blocks available in Vision do not exist in UniStream, such as PWM. Data tables are different as well, for example. Tags and structure variables are a whole 'nother topic in the differences. You have to go back and look at your program and translate it, unless you choose "New (Pre-Defined Tags)" which will create arrays of tags with the same names as the Vision series. This
  13. My personal field setup is my ancient (+10 years old) Dell D830 running Win 7 with updates turned off. I use this particular unit because it still has a serial port and I have a lot of installed Unitronics base that still only has RS232 ports, and the direct connection with a real interrupt just works better. A modern laptop works well, too, but turning the updates off is still a key to long term usability with no surprises. I've used a program recommended by Ausman called Winaero that allows you to turn Win 10 updates off. The only problem with this is other Win 10 apps somehow cal
  14. I have a docking station for my Dell D830. When the laptop is docked the video characteristics of the system are different from when it is undocked. As it is locking up especially when you view the graphics editor I'd lean toward a Windows graphics driver problem. First - has this ever worked on the laptop by itself? Did a Windows update start the problem? What kind of laptop do you have? Do you have another laptop you can try this on? Joe T.
  • Create New...