Jump to content


Privileged Member
  • Posts

  • Joined

  • Last visited

  • Days Won


Isakovic last won the day on November 6 2020

Isakovic had the most liked content!

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

2,119 profile views

Isakovic's Achievements


UniGuru (4/4)



  1. I'll tell you configuration that works well with stepper, from my experience and similar application. V430-J-TR34 with configured outputs as "High Speed Output (Step Control)", with ramping done via linearization block. Input to LIN block is distance from encoder, ouput frequency. In your case input could be acceleration/deceleration time if there is no distance measurement. EDIT: I see now that you are using V130, I personally never worked with that model, but maybe this can give you an idea.
  2. Yes, that's how I would do it. Wait for graph to reach some round number, take screenshot, then read "duration" time from "Online" box and calculate ratio.
  3. Sorry for derailing topic. I tried playing with it. When monitoring 1 unit is 1 minute and 2-3 seconds. When running autotune 1 unit is about 30ms. It doesn't seem consistent, it is the same if you change sample time. Maybe it depends on communication with controller. If you need time values to analyze your system I suggest calculating it manually by dividing your total online time with displayed units under the graph. Maybe someone who knows better can chime in, but I don't see any more settings for time axis.
  4. You did not speak favorably about sacred cult of PID, I have to react >.< Jokes aside, I used modified method from VisiLogic example program "PID motorized valve" to control 3-point and analogue actuators on systems running 24/7 and valve actuators last a long time. I did use relatively simple method before PID and it worked well, just little less stable.
  5. That is right. N3 is solved. It is used in compressor control to sort working hours. On that project I learned you'll need to use loops when doing optimization problems, I avoided them before. Whole program is a heap of loops. Code like this written in ladder gets hard to follow even for simple stuff, bunch of indirect addressing. This program was written some time ago, if I needed to do it now I would try with UniLogic and C scripts, never used UL C functions to run actual machine, only for testing.
  6. Number 3 Vague reference - this controller controls other machines
  7. If you need bit for one scan every second you should use transition contact in Gabriel's example, Felx's example will also work with normal contact. I don't know why this function was omitted from system bits in UniLogic, it is present in VisiLogic and I believe it is often used. Now I have a question here which method is best practice. In documentation for VisiLogic it is suggested to reduce the number of transition contacts, so I personally use one timer like Flex posted but with normal contact wherever it is needed in program. Is this still an issue in UniLogic or we can simply use frequency bit with transition contact?
  8. In similar project I had some time ago I used HSO in Step Control mode (not PWM), and frequencies for acceleration and deceleration are calculated in linearization block and copied to register for frequency, effectively the same thing you did. I remember having those issues that output would start with high frequency and motor couldn't speed up but can't say for sure what the solution was. When stopping are you ramping the frequency down or just set it to 0? Maybe put a delay after setting run bit if this is allowed. I'm not sure what you mean by another source.
  9. People are shocked when they find out what a terrible electrician I am.
  10. Maybe try using an auxiliary data table as a buffer for reading/writing instead of modbusing directly tables PLC uses for logic. That way you can verify if data is valid, if not repeat synchonization. This may slow down your process if mistakes are frequent.
  11. I guess it should work, I never tested it with my own PC. In the ladder before MB2 you can place condition DW0>3000000 so it won't update unrealistic time. I think you also need to account daylight savings time and your time zone (this comes down to adding Nx3600 to DW0).
  12. If I understand manual correctly this Master Clock can work as an NTP server. There is a function in VisiLogic called RFC-1305 for time synchronization with NTP server, there is also an example. It works fine, but if something goes wrong and server returns 0 it will reset PLC clock to midnight 1.1.2001. Just make sure to have some logic preventing this. Or if wiring allows it use digital input as Ausman says, that will take less programming time and be pretty accurate for this case.
  13. Oh I see it now! If the PLC and Hama are powered from the same supply both CH1 and GND on the PLC module will effectively be on the ground potential. Now I suspect AI08O also has GND and negative power terminal connected, so switching terminal places would not work. But will it work if separate power supply is used only to power Hama (not referenced to the ground), and other supply is used for current loop and PLC?
  14. I'll jump into this discussion because I am little confused here. More so after reading other quoted forum posts. Why wouldn't HI 98143-20 work? From the technical description I would wire it like this: Like any other two-wire 4-20mA transmitter. Is something not right here?
  • Create New...