Jump to content


Popular Content

Showing content with the highest reputation since 02/15/2018 in all areas

  1. 4 points
    Download the attached Rar file, and extract the files to UniLogic installation directory. This means that the "UniLogic Diagnostics.exe" (and all the other files) must be placed in the same directory where "Unitronics.Shell.UI.exe" is located (usually at: "C:\Program Files (x86)\Unitronics\UniLogic\") After you've extracted the files, run "UniLogic Diagnostics.exe" and click on Diagnose. Most chances that it will show "SQL Instance" as one that has problems. In case it find problems, the "Fix" button will become enabled. Click on Fix, and the program will attempt to fix the problem, and then it will re-diagnose the problems to confirm that they are fixed. Please tell me what problems it found . Also tell me if it managed to fix the problem that you're experiencing with UniLogic (that it is stuck in loading components). Thanks. UniLogic Diagnostics.rar
  2. 3 points
    I'm convinced this is delusional. CDs were originally pretty bad because sound engineers failed to properly tailor the sound for the new media and instead used the equilization curves for vinyl with insufficient modification. That's no longer the case. Nowadays, the abysmal compression of MP3s may be worse than vinyl, but no one who really cares about sound quality should be listening to either compressed MP3 or vinyl. Vinyl necessarily has extreme equalization in order to achieve any bass response, necessarily lacks sufficient channel separation, and degrades every time the record is played. </rant> THIS I agree with wholeheartedly.
  3. 3 points
    This major release introduces MQTT, another piece of the Industry 4.0 puzzle. MQTT is a machine-to-machine connectivity protocol that runs over TCP/IP. MQTT joins the UniStream range of communication channels and protocols that supply the connectivity required by Industry 4.0 including SQL, built-in webserver that enables the controller to be accessed via any browser, and more. This release also supports new UniStream 5” models US5-Bx-R38 + US5-Bx-T42, offering new, built-in I/O configurations. Other important features in this release: HID Device support for devices such as scanners PostgreSQL support, in addition to SQL Server and MySQL UniApps localization for Korean & Italian, plus a new Korean virtual keyboard Read the version changes for more features at: https://unitronicsplc.com/software-unilogic-for-programmable-controllers/
  4. 2 points
    Try going to project in the toolbar. Then options. Then try unchecking ping on discovery
  5. 2 points
    I patented that term a few months ago. Please cough up if you are going to use it! ? cheers, Aus
  6. 2 points
    This may sound insignificant, but I want to be able to be able to add color to the comments to make it easier to see when scanning down through longer programs. You can color the side bar of the rungs but not the comments. Thanks Visilogic Team! Paul
  7. 2 points
    Hi, 1). Vision reads bar. 2). Vision executes bar entry routine. 3). Vision proceeds to bar. 4). Vision reads different codes. 5). Vision interprets codes, runs decision-making subroutine. 6). Vision waits for a while accepting results of decision-making sub. 7). Vision leaves bar sub.....somewhat unsteadily. 8). Vision attempts to run main program normally, but errors appear out of nowhere. Sorry JT. Couldn't help myself. You'll get a serious answer soon from someone who really knows how. cheers, Aus
  8. 2 points
    Your code is actually fairly straightforward and easy to read. One thing I would change is how your command numbers get set. This is a classic example of how Unitronics doesn't always compile the way we think it will. In this code- The logic I see is "If SB 147 and MB 460 pressed then Toggle MB 450 then based on MB 450 write either 0 or 1 to MI 60 and set MB 470". So I'm guessing you want to toggle MB 450 first and then write a number. But that's not how it compiles. Look at the STL Quick View for this network (right click on the network number)- "!" is the beginning of a logical statement the PLC solves. So let's break it down: 1. ! - Look at the state of MB 450 and copy it to LB 0 (local scratch bit 0) 2. ! - Look at SB 147 and the Rising edge of MB 460. If true, toggle MB 450. So far so good. 3. ! - Look at SB 147 and the Rising edge of MB 460 (again) AND the state of LB 0. If true, write 1 to MI 60. But wait! Didn't we want to toggle MB 450 and then consider it's state for the Store blocks? As you can see, this won't happen. General rule of thumb for Unitronics programming. If you operate on a bit (MB or timer), don't use it as a condition in the same network. To get predictable results, you need to break the network apart: I realize this seems redundant and illogical. But that's how it is. Enter this logic and look at the resultant STL views to see for yourself. Joe T.
  9. 2 points
  10. 2 points
    Talked to Dan at US tech support - he suggested SD File Utilities -> File Status function block The "A" output bit MB 39 does what I need. I just call this function before I write the data line to see if I have to call a another Write Line for the header first. Joe T.
  11. 1 point
    This is what your linearization block should look like for the example I described above: This will linearize the 4-20mA input to 0.0 to 100.0.
  12. 1 point
  13. 1 point
    A quick reply before shuteye! What you are wanting to do is "ramping". You will likely find that your drive can do this for you....most variable speed drives can......so that all you need to do from the plc is tell it the most basic instructions like stop/ go /direction. This method does make it easy. However, if you want to do it all through the plc, an example would be to use a MI (linked to the drive output) that starts at 4000 (for example) and you subtract 1 from it every few scans to reduce it down to the 0 output that has the drive turned off. You then ramp it up the same way for the other direction. Depending on your scan rate you might achieve what you want doing this every scan, but you may also need to do the subtraction every 2nd, 3rd or however many counts the scan time/ramp time maths works out to arrive at your ideal ramping speed. To adjust the speeds to other ones, you would have the same sort of thing in place....the current MI output is the start point, and another is the target which gets ramped to and then once reached becomes available for the next speed change input. Don't forget emergency stops in all of this!! cheers, Aus
  14. 1 point
    Hey Hoover, I put together many solid Uni/Festo applications. I can email you my demo for V350 supporting FHPP in profile positioning and direct mode (not record select). What is cool about Festo Handling Positioning Protocol is it works exactly the same over tcp or canbus. When reading from the cmmo first 4 bytes are status bits and the last 4bytes are a double word representing position/speed/current draw % depending on which mode your in. When you write these 8 bytes they are control bits and ref command. I’m on my iPad so I’ll try and post the vlp from laptop tomorrow.
  15. 1 point
    @cirocastro, check above under "Pages"/"Webinars" to see some great tutorials. Also, browse the Help file - you will learn a lot. @Cara Bereck Levy and others have put a lot of effort into the Help file and it is a great resource. There are also a lot of example programs that came with your VisiLogic installation. Review those to see how to do specific tasks. But most importantly, get a cheap PLC and start experimenting. There is no better way to learn than hands on trial and error.
  16. 1 point
    Was the install done as Admin? Can you try to run RO on another computer running W7 to see if the problem is W10 specific? cheers, Aus
  17. 1 point
    Greg Hi I send you my files for PLC & EX-RC1 , First make adress in your extenzion devices and separatly programming each. After that look the programm and make yours aplication programm and adjust for yours screen in V 560. Joe explained to you how to make address, but programming time for RC1 is the safest at 38,400 via RS232 Evrything next is very simple. Good luck RC TEST V1040.vlp RC#2.vlp RC#3.vlp RC#4.vlp
  18. 1 point
    Have a squiz at this. Hopefully it makes sense. And "direct action"? "drive" action. cheers, Aus
  19. 1 point
    Perhaps you have port numbers confused? Without seeing your program I can't tell. Your exercise (!) is to put the original comms element(s) relating to just one comm setting back into your program and see which lot upsets things. This should point you to your answer. Please let us know! cheers, Aus
  20. 1 point
    I almost had a chat with a guest while chat room was still available.
  21. 1 point
    I'm glad that the question was answered, even if it was not the answer you might have preferred--sorry that it took some time to be answered. It was a holiday weekend (Purim) over here in UniLand . Always feel free to tag me directly with @Cara Bereck Levy. (but please don't send me support messages directly, or post them on my profile, I often miss these)
  22. 1 point
    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.
  23. 1 point
    U90 Ladder shows the +/- 10V notation, so I would say that is definitive. For the record, the IO-AI2-AO4 expansion module also has +/- 10V outputs (Jazz does not support expansion modules).
  24. 1 point
    Hi MattP_Mac, 1.Make ping from your PC to PLC IP. Does PLC answers? 2.Open DOS prompt at your PC and enter "telnet 20256". DOS display will blink, clean and stay black. Is this what you see? 3.Enter PLC info mode and check Socket 1 status. Is it connected? Share test results. B.R.
  25. 1 point
    This type of error is caused by a fault within the logic. An unlikely sequence of events or a faulty FB within the program could potentially cause this issue. To review the code within VisiLogic you can use the Ldr code to search for the subroutine that causes the issue. This feature can be found under the Edit menu, then selecting Find Subroutine by Ladder Error Code. This error may also be generated by a fault in the O/S. I would recommend either updating or reinstalling the operating system within the controller.