Jump to content

Ausman

MVP 2017
  • Content Count

    1,565
  • Joined

  • Last visited

  • Days Won

    83

Everything posted by Ausman

  1. On top of Flex's suggestion, did you install Visilogic using right click/run as Administrator? Also have the visilogic.exe in Program Files (x86) Unitronics UnitronicsVisilogic_C Main set to run as admin in compatibility settings? If you have done this and still have the issue, how are you connecting to the 350? If using a USB to serial adapter, some of the cheap no-name types don't work properly. cheers, Aus
  2. @Simon attention grabber for above, in case you aren't looking too hard.
  3. In hunting up a favourite laser cutter this morning I noticed that they also like to interact with Catholics. cheers, Aus ⚠️
  4. Yay for you and Joe! The cable is very important to do properly, and ENSURE you couple up the earth correctly. This morning I had a brainwave that perhaps you needed to ensure the 1210 was on the latest firmware, but it looks like that isn't needed now. cheers, Aus
  5. Part of your issue is "Micro" vs "Milli". Blink really really quickly....damn you missed it. The other thing is that (and I quote) if this causes a delay greater than 600 milliseconds, the PLC watchdog may be activated. As Cam and Alex have said, use timers or a count. Also, your layout of (S) then another (S) needs separating. cheers, Aus
  6. Joe...you've got the SEE-virus. 😷 Sorry, couldn't let that one go un-posted. It is a dumb method but very common and VERY annoying. After all....they are TICKS which generally mean YES. cheers, Aus
  7. And a PS to the above, I have a 130 that needs doing so I'll try using Ethernet (via external connections) when I'm next on site, not due for a few months yet, though. cheers, Aus
  8. Good that it fixed it. It seems that Run as Admin isn't always done automatically. There has been much talk about this on the forum. Originally it was a known crucial part of the installation procedure, but after lots of trouble with people not knowing this and having issues, it was made automatic. But this then created problems with some installations not being able to be done due to user authority levels. It still seems to crop up now and then, maybe the "default into Admin" has been dropped on latest versions. @Saragani would likely know this as I've nagged him on this over the years! cheers, Aus
  9. Flex & Gabriel, I've always done it just as a matter of course. Have never considered it to be just an indicator...always thought it crucial. Can't experiment whether it actually DOES anything at present. Colodetti, 1). I thought perhaps the resolution might be the reason, but suggested anyway. 2). OK on NPN/PNP but still think you should very carefully check everything and try. 3). What happens if you drop the rest of the I/Os off, and just have the D16A3? Not hard to do as just a trial program. Doesn't have to have anything in it, just the correct hardware configuration for it on it's own. Slide the other modules along a bit so you can disconnect the cable, then try with power to them connected AND disconnected. cheers, Aus
  10. I've had units totally fall over doing it by ethernet, and have had to do lots of travel to fix as the only method was serial. That said, I mainly use 130s, which shouldn't affect this but perhaps does. I remember whingeing about this on the forum once, but couldn't find it with a quick look. Wanted a big red warning to come up saying don't do it!! Haven't been game to try since. All updates now done when on site. cheers, Aus
  11. Yep, it's almost as if it's written by M$oft programmers! They are the absolute specialists at double triple negatives. cheers, Aus
  12. Are you SURE you have the wiring correct for NPN or PNP and ALSO have the NPN/PNP selection done correctly in the Project's Hardware Configuration? The PNP/NPN selection is in the left column of the Digital Inputs Tab in Hardware Configuration and is easily missed. Once done, you must compile this, save as new, reload it into the controller and do an Init and Reset. I also notice in the photos that it looks like you are only using one input on the AI8. You could perhaps get rid of this module completely by using the AI on the D16A3. cheers, Aus
  13. Thanks Joe, I didn't know it was token. I think I've always been literally going on this illustration: My brain always puzzled on this along the lines of "how do all the networked recipients do this at the same time without conflicts?" Makes much more sense now. And yes, I'm a dumbo for not picking it in the first place. cheers, Aus
  14. My reply could be read as "speed is of the essence'', but it's not true. What I want to do is run UniCan as it appears in it's description, and have it totally reliable. I can only get this to work by having calls being made at a given periodic speed. There is a fine time interval that the joined systems will tolerate. Cabling is spec and only quite short runs less than 2m. My eagerness to do it like you say is to have it done "properly". It has always seemed a bit odd that having a request sent periodically via the ladder always has the potential for a conflict with another request somewhere else on the loop. Especially doing it with a "defined" time interval. It is unlikely, but entirely possible, that calls from different plcs could coincide exactly, and do so for some time if based on something like SB 13 or 15. I think at the moment that I'd love the Creators to chime in and explain exactly how it all works, how the loop reacts to different plc calls etc. Help gives information, but I think it could go into a lot more depth, covering things like Structs etc. The "mechanics"of how it all works ok, including any time allowances for the amount of data zinging around, would be nice to know. It is only logical, Captain, that more data means more time needed! @Saragani @AlexUT @Cara Bereck Levy ? cheers, Aus
  15. Thanks Joe, I have tried this in the past and couldn't get it to be reliable. However, I am also using quite a few structs in series that might be upsetting transfer speeds, as some of the numbers involved vary significantly. The other thing is that I may have made a boo boo somewhere in previous attempts, so I'll try it all again some time and see how it goes, as I would prefer your method. Do you put in some extra scans after the blocks change state, or just react to them immediately? All my hiccouphs still say buffer over-run to me. cheers, Aus
  16. Everything said already is perfectly valid. Flex suggested O/S, but I'd also be starting from absolute scratch on the affected plc. It appears it is recognising the card is there, but saying it can't work it. Delete everything via info mode, then reload boot, O/S etc, then try to load a completely empty program. I'm thinking a crook part, but try the unit's brain surgery first. cheers, Aus
  17. Perhaps this is the issue. Maybe you need to be able to manually select (under a "maintenance password") particular controllers in the loop. Take it out of the loop for the shutdown, then put it back in after powerup? Having never done this, I don't know whether this is possible the way UniCan works. I'll ponder on this and let you know, unless someone else who may have done it OK chimes in....please. The SB13 in the example is just that, an example, I often do it with counters incrementing each scan that let various calls be fine tuned much more precisely. Mostly my scan times are consistent. If not, I use the 2.5/1.25ms interrupt. cheers, Aus
  18. Annatooli, have you tried putting a "cyclical" call (eg below) on the UniCan actions? Or raise/lower the bitrate? I have found it is easy to overload the buffers and you need to reduce the demand on the comms loop. You can often set up a flipflop sort of thing on the various calls around the loop, allowing a few scans before proceeding to the next one. The trouble with this method is if one receive/send falls over you have to program in a timeout "over-ride" progression. In theory all of this isn't needed, but I have found it's the only way I can get it to work sometimes...depends on load. I've mentioned elsewhere on the forum how I have decreased interval times to the bare minimum that appeared to be working ok, only to find it falling over later, most likely due to a buffer issue. A tiny increase in timings and the problem was fixed. cheers, Aus
  19. One of many related references coming up using search:
  20. Ausman

    Net 3.5 tip

    Warning, not advising this at all....... Doing the above method lets me then save under the current version. The hidden issue is that perhaps something that is utilised in the project then doesn't show up if it is only in the later version. However.... Flex, you could always use your many installs of Version Swapper to look at what changes. Do some saves of the same file under different editions and then peek using the likes of Notepad+. Something obvious and tiny might show up. Or it might be a totally different way of assembling the file which will completely klang the idea! I can't do this as I shifted away from Swapper and only run one version these days. cheers, Aus
  21. I'm sure there's a bit of sarcasm there. Much better than mine! But they still need a cleanout and terminal reinsert now and then. cheers, Aus
  22. Ausman

    Net 3.5 tip

    I know we are digressing, but for me, most of the time a project made on a newer Visilogic version will try to open but display an error. Most of the time, but not always, you then have to close Visi in Task Manager. Open the project again and it will bring up "Visi not shut down properly, reload blah blah" and if you select ok it will open the newer version, which you can then work with. I do this frequently on the forum's user projects as I am still sticking with just 8.65 and many of the submitted projects are done in later versions. cheers, Aus
  23. Annatooli, I'd be interested to see if a complete dustout and wiggle/remove/reinsert every connection including ram on your puter would fix this. Also do a serious check on your drives, check and also defrag them if not solid state. If it's a laptop, you'd also be surprised how much gunk can get into cooling systems. They need a good periodic clean, excess heat issues can cause havoc. cheers, Aus.
  24. gijoe. Thanks for the comment and your eagerness to berate someone who tells you to use your own initiative and FIND OUT ABOUT SOMETHING SIMPLE FOR YOURSELF. Do you own a car? Did you read the manual to learn how to operate some things in it? Or did you ask a forum how to put fuel in the tank? Hmmmmmm.
×
×
  • Create New...