Jump to content

Ausman

MVP 2017
  • Content Count

    1,434
  • Joined

  • Last visited

  • Days Won

    77

Ausman last won the day on March 30

Ausman had the most liked content!

Community Reputation

147 Excellent

About Ausman

  • Rank
    UniGuru

Profile Information

  • Gender
    Not Telling
  • Interests
    Love/Hate waking up with a solution to a problem. Thanks brain....for not sleeping properly!

Recent Profile Visitors

6,400 profile views
  1. You might want to talk to tmoulder, who had the same thoughts ages ago: I haven't seen him/her around for a while, don't know if they're still active etc. But my thoughts are that they would be the Ubuntu guru on this. cheers, Aus
  2. Flex is correct in that Support is likely best, but in case you haven't got onto them yet, what happens if you install Visilogic on another PC etc that has never had it? Did you do the install as Right click/Run as Admin? After installation also confirmed the installed .exe is set to Run as Admin as well? What is using up the PLC memory? What happens if you use info mode on one of the Sambas to completely reset it? ie no program at all. cheers, Aus
  3. Joe & Flex have given great advice here. I would like to add some comments, and reference particular help files. The most sophisticated plc I use is the 130 series. I have never had a need for touch screens, I only have knowledge of manual keypads. Using subs linked to screens for manual keypads is fraught with hazard, due to the fact that screens take a number of scans to load. It is also very easy to get an unexpected action because a button push might over-run into the next screen. There is much in the Help files about this sort of issue, but it is scattered around a bit. I strongly suggest that anyone new to Vision spends some time looking carefully at: How Keypad Entry Variables Work Program Sequencing: Modules, Subroutines, Labels & Jumps. In particular the image box near the bottom that is headed "Runs HMI Program" and the notes within. Take really good note of how the use of certain system bits lets you control things much better. On the comment "disable " that button which opens that display, that's the best way! There is one proviso though, the ONLY time I might have such a thing in a program that is accessible to the user, is if the machine may need careful manual control in an Emergency Stop situation. It is all well and good for a machine to have an emergency stop, but it's NO good if someone is trapped by the "Stop" situation that could be easily cured by very careful manual control of part of the machine that would otherwise be very difficult to do. Humans will always find a way of getting around the most stringent safety systems, often with bad (for the human) results. cheers, Aus
  4. That's great SoCold, Everyone's done such a thing in missing a "typo" during programming. That important document you spend hours on proof reading till it's perfect? A minute after you send it you notice another error! cheers, Aus
  5. I feel the need to add something to Denis's comment "if you need address 1, 5 and 7 on the device, it is better to read 1 and set a length of 7 than to try to read using 3 separate reads." On many devices I use, this is not possible. If the device itself doesn't have any knowledge or use of any register involved in the vector, it will often return an error. Many, many times I have to do separate reads on a single device to get all the info I need because of this quirk. It is a complete PITA, as the makers often spread the "most relevant to what the sensor does" registers many numbers apart, with gaps in b/n. Air sensors with temp at 013, Hum at 121, CO² at 217 ....... instead of all 3 in registers 2, 3 & 4; with the rest of the useless to the user garbage that they use internally but for some reason have them as register usage, placed everywhere else but often with number gaps. You get the idea. I'd really like to give the people who make the devices a big smack on the bottom and then send them to the dunce corner for the day. With NO coffee or chocolate allowed at all for the rest of the month. The vector method is certainly much faster, but you can only do it after initial testing using the PC to see if it is "actually" possible. cheers, Aus
  6. +100, Joe. All of it, especially "Modbus via RS485 is nowhere near fast enough or reliable enough". 🐌 cheers, Aus
  7. Hi SoCo, I don't use Unilogic at all, just a Vision man.......ooops.....person (with external gonads!) But....on the actual reads from the sensors, are you doing your reads concurrently? What happens if you split the reads equidistant in timing? What is the actual "regular interval" time on the reads anyway? Along the same lines, what happens if you flip-flop between 10 & 13 at a given time interval so that they are both not doing it all the time.. ie only enable rung 10 this second, only enable rung 13 the other one, perhaps with a small time buffer between each alternate. Behaviour exhibited after doing this would perhaps help in analysis. cheers, Aus
  8. @AlexUT @Cara Bereck Levy this size limit has come up before. What should happen is for the Formatter to NOT let any actions happen if the card is larger than whatever you deem the best size eg 16Gb. Or change it a bit. As Joe says, "I don't know why it let you try anything else. " It shouldn't. It's very frustrating that the program will tell you the Total Size of the card but it doesn't work if the card is too big. The Total Size should trigger a message saying something like "get a < 16Gb card, your card is too big". This can't be too hard to do, and should have been done ages ago. Off the shelf card sizes are getting bigger all the time, with smaller ones that used to be big now not even being available. (Gee......isn't it amazing that you can have 1Gb on this little thing!!!) At some stage you've got to get the system able to handle them automatically. cheers, Aus
  9. I can tell. 😊 cheers, Aus
  10. Come on Alex. Please tell us all! 😉 cheers, Aus
  11. Don't forget that modbus via 485 is not inherently fast. If you are wanting things to happen in "real time" then you are going to be struggling using 485. Even if you limit timings to the bare minimum, you are still not going to get "real time" operaton, there will always be delays. As Isak says, 100ms is not likely to be anywhere near a long enough time. It further compounds issues if your system does a retry on a failed attempt. Total times on all attempts to one ID have to be allowed for, and then a tiny bit more to allow buffers to fully clear. "The distance between the components is small". Does this mean you have all the VFDs in the same enclosure? Bad move if you do. Any plc needs to be shielded as much as possible against likely interference from them. Aside from your timings problem, it is one of the first things to look at on a system that has intermittent odd issues and runs VFDs. cheers, Aus
  12. Permanently run remote access or remote operator on the PC and tuck it away in a little used corner of the desktop? Or....have a look at UniDDE, or perhaps UniOPC https://unitronicsplc.com/Download/SoftwareUtilities/UniDDESetup_1_3_6.exe DDE will likely give you the basics of what you want, but you might need a little script running to cycle things periodically to fully achieve your needs. So you'd have a little excel window running and updating with just the info you want visible. cheers, Aus
  13. And another PS on the SI30-38. You can use the SIs directly, but I do some operations on them, to change them to numbers that are much easier to use when viewing things in Excel. Simpler to do it in the record itself, than mucking about with Excel. See the screenshots and it might explain it better. The MIs are derived from the various SIs. The trigger is when the seconds in the RTC roll over to 1, and in this case it enables the writing of 2 logs. cheers, Aus and the table that results is:
×
×
  • Create New...