Ausman

What are these exactly? They are the likely cause of issues if not correct/good enough. cheers, Aus

Hmmmm.....in Visi, ALL my favourites are saved in the evb file. Hence my solution to the "security" issue here, which is also in the "not quite pinned" list: http://forum.unitronics.com/topic/5439-hiding-remote-locations-on-your-pc-from-crooks/?tab=comments#comment-21086 It would be nice if only the relevant details were saved on each project. After all, if you've got it open, you probably want to use it! I don't use the key of my car to just hop in and sit there making vroom vroom noises. Well......sometimes I do. 🏎️ cheers, Aus

Or change your thinking and use a count of your own making. Cascading timers can work, but can also be an endless source of problems. The beauty of counts is that you can manipulate things much easier on complex progressions. "Hmmmm....run that process.....from here to there". Timers do make part of this sort of thing easier, but if your timer initiation/ending goes astray you can easily get headaches. To get around the issue of using counts, you can do "invisible to the user" maths to make the count adjustments automatically allow for any changes in the total progression. cheers, Aus

Don't forget the tip on holding the snap-in in place a lot better by using some carefully cut and applied "gaffer" tape.

As it is working, I am with Kratmel. I've had power supplies make very odd noises, but I then don't trust the unit and replace it. However.... Ensure that the installers didn't let any swarf etc into the unit. I've had many plcs stuffed by "experts" relocating equipment and drilling/cutting holes willy nilly without any covers over all the control gear at all, with subsequent failure. "Aus, it doesn't work anymore!" "That's because you are a pack of dills". I used to work with a PLC brand that came with paper protection all over the vents, explaining about removal after ALL works were finished. Great idea. Time to remove a cover to see what is really going on, me thinks. 😨 cheers, Aus

It is confusing berndp, isn't it? Across different PLC species you get varied responses to this sort of instruction. @Cara Bereck Levy Maybe better wording in the descriptions would help? cheers, Aus.

Douglas Adams was so clever he probably knew this. Any book(s) of his you have to read at least 3 or more times to get all the linked things.

John, in case you haven't found them yet, the info on these is squirreled away in the tech library under Accessories/Routers. There were some minor spec errors on first release which may have been fixed by now, but I haven't looked. cheers, Aus https://unitronicsplc.com/support-technical-library/

Pierre, in doing this you may like to try multiple instances of Visilogic which makes it so much easier. cheers, Aus http://forum.unitronics.com/topic/4015-multiple-connection-live-checking-tip/

balazs, in your screenshot your item #2 (linked to TB1) is not 1000, it is 1500. Does changing it to 1000 make a difference? Also, have you actually got some values in the plc for it to work with? cheers, Aus

Cara, knowing it is a token loop explains a lot. The entire topic of UniCan and best practices has lots of info in Help, but for the learner it's a bit hard to tie it all together. I use Structs to assemble/disassemble the vectors for UniCan sends and have them in series, which is not covered as being possible. Same for the UniCan Sends. The help files imply that you can only do 16 integers in a single send, and that's true...but you can do lots of sends in one rung. I wrote about this here: http://forum.unitronics.com/topic/4084-unican-sends-512-mis-per-scanhow/?hl=unican The other thing that is not well explained and actually needs more work on it in Visilogic is the source/destination naming issue in Structs. Unless you keep careful track of this via something like Excel, it gets very confusing. I touched on this here: http://forum.unitronics.com/topic/6527-with-vectors-why-didnt-i-think-of-this-ages-ago/ For me I also seem to have buffer issues that the system doesn't seem to allow for. "Everything is done" says the system.....but unless you allow a few more scans for the buffers to fully clear you'll run into overload problems. I am going to try again on some layouts...as discussed above. To me the issue is that it needs some example layouts in the help files that show the entire principle for all types of different operations. The sample projects show the basics, but don't show how much you can enlarge on what is being shown. I know this is a learning curve, but I don't like stumbling along in the dark finding things out by trial and error. I well remember spending days banging away on this when I first started doing it, having to do lots of testbench trials. And you have to work with at least 2 plcs to do it properly, which adds to the annoyance as you have the 2 lots of download each time you try something. cheers, Aus

If Flex's link is not enough to get you going, have a look at Topic 4 in this pinned list, where Joe explains it well. cheers, Aus http://forum.unitronics.com/topic/6229-ongoing-13-topics-almost-worth-pinning/?_fromLogin=1

A quick look at this and for starters I'd fix all your Input Status Determine inputs......they are all the same......Input 0. As for your comms woes, are you using an MJ20-RS? If not, you should be. It is possible that your 485 sends are being interpreted on the 232 input of an MJ20-PRG, but it cannot send on 485. I suggest you have a good read of the various Help files.....Com Port Mode: RS232/RS485 etc You should initially be just trying out what you want to do on just one I/O, testing this thoroughly until it all works correctly and you understand it completely, then progressively add in other additions you want, testing along the way. cheers, Aus

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

@Simon attention grabber for above, in case you aren't looking too hard.

In hunting up a favourite laser cutter this morning I noticed that they also like to interact with Catholics. cheers, Aus ⚠️

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

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

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

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

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

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

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

Yep, it's almost as if it's written by M$oft programmers! They are the absolute specialists at double triple negatives. cheers, Aus

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