Jump to content


Members More Space
  • Content count

  • Joined

  • Last visited

  • Days Won


Isakovic last won the day on March 12

Isakovic had the most liked content!

Community Reputation

11 Good

1 Follower

About Isakovic

  • Rank
    Advanced Member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

1,019 profile views
  1. I can't think of a way of making a dynamic piechart. Maybe you could make 8 bargraphs for the same result of visually comparing relative values because they allow dynamic min/max (0 - minimim, sum of all variables - maximum).
  2. That Awkward Moment...

    I almost had a chat with a guest while chat room was still available.
  3. It looks correct (you even have a response for every command you sent to slave), but value to force is 0. Force coil command is reading status of MB6 (0 or 1) and writing it to slave when command is called. If this command is always writing 1 use SB1 (always on) for "Value to Force". You can write just 6 in destination address.
  4. You should definitely try breaking it into several nets, it looks like it should work from STL though. I wish you could set parameters for serial communication on Vision in MIs. I think you need RS485 card for Sambas, it's standard for Visions.
  5. They look like circuit boards from inside old consoles cartridges.
  6. What's the scan time on that one?
  7. I couldn't find any reset coil elements for timers in ladder. Are you resetting it by not calling a subroutine? Someone correct me if I'm wrong, but I think that nets in subroutines won't get updated if subroutine is not called (so bits that were 1 when program last time passed through subroutine will remain 1). I find this not intuitive so I usually run through all routines from main and use bits as conditions. Maybe your program will work if you used reset coil for timer.
  8. I tried reading UTC from PLC and got the same one day lag with that formula, but PLC has correct date data. Must be leap year missing a day every 400 years or something like that, there must be a code for conversion somewhere. Why don't you put date into data table as integer or string? (I regretted it every time when I put it as a string)
  9. I had a quick look, maybe I could give a few suggestions. - Use Scan_Ex block and separate all those functions into separate blocks (one net for config, one for scan etc.) - You are calling connect block after every Modbus operation, maybe try calling it via transition contact only when Socket that you use is not connected. Tell us back how it goes.
  10. - Make a new Variable with that MI in it. - Select part of the screen where you want this MI to be displayed, then right click -> Attach Variable - Input will activate whenever you navigate to that screen. If you want to have input only when you press a certain key (usually enter), you'll need to make a logic that will set SB39 each time you open a new screen, and reload a screen when enter (or whichever key) is pressed. I think there's a topic about this in forum somewhere, maybe even in examples in U90.
  11. Looks like this is always the case with energy meters. You use "Struct" block under Vector -> Struct for merging those two registers into a float. There is an explanation for struct block in help file. After that use math function blocks for floats to extract the values if you need them converted to int.
  12. Hello Rog, What do you mean by taking out IP address? After net 6 is executed what status do you get for Socket 1, 19 or 23? As Flex said it should work the same regardless of controller used, V570 or V700.
  13. Status 23 means it is connected. You run connect block when Socket 1 is connected in your logic, it should be MI2 not equal 23. Also, nets 4 and 5 are the same.
  14. Reuse Socket

    Hello Aus, I also set SB168 at power up, I tried messing with system bits but that didn't work. What I found to work is next sequence: - Init Socket 3 to TCP master (port as before 20259) - Delay 2 seconds - TCP connect on Socket 3 to timekeeper Server on port 123 - Delay 2 seconds - Init Socket 3 to UDP, port 123 - Delay 2 seconds - Whole update sequence - After 1 minute Init block to restore Socket 3 to original settings I don't know why it works, but it works. Hope this helps someone.
  15. Reuse Socket

    This is what I found: It will work normally as long as no TCP connections take place on Socket 3, like accessing from VisiLogic or Remote Operator. As soon as PC connects at least once it will not work until PLC restarts. It doesn't matter if PC-PLC connection disconnects normally or it is violently broken. I don't know how to clear whatever PLC set in its memory. I tried closing the socket and then initializing it to other TCP and even this Modbus workaround Javier did but it doesn't work.