Ausman

And just to clarify, my logging writes to the data table an entire 24 hours worth, and then writes as the udt to the SD. So the data table holds the data until it is reset by the system finishing the udt write. But, in my case it doesn't check for a successful write by checking the SD itself, for me it's not that important. But such a check would not be that hard to do. cheers, Aus

You might want to consider what is in the topic linked below. It's not exactly what you need, but might point you in a better direction. For your purposes a .udt log might be better. From your process description I feel sure that your temp logging could be done on a 60 second basis, but if needed to be shorter, a data table would still likely handle it. It would be easy to check if the previous (few) .udts have been written ok to the sd, and then a FIFO "restart" of the data table(s) logging could proceed. cheers, Aus https://forum.unitronics.com/topic/3460-write-table-to-sd-with-date-stamp/?do=findComment&comment=12633

Please explain the reason for using SB0. I don't use it at all, but my understanding is that it is always OFF. To my eye on a quick look, even if it changes to permanently off in the first scan, some of other logic running from it won't work anyway. Perhaps it's meant to be SB1? cheers, Aus

And now a wonder of nature and the flukes it can do. Noticed this twig this morning, it had floated in high wind from a tree 20m away, and landed perfectly upright and aligned so that it would wedge into the one tiny hole that would accept it, and hold it in position despite the wind! Meanwhile I'm fumbling using tweezers, getting jumpers perfectly aligned in awkward spaces! 🙂 cheers, Aus

"Damage" is such a broad description! If it was mechanical damage then it is quite possible that such a connection, perhaps inadvertently, took place and became obvious after repairs. But I'm betting on human error during the replacement. Connections on snaps can be a bit confusing and lots of attention and double-checking is needed.

Depending on urgency, I'd be replacing with new, and then investigating the dud unit on your test bench using Kratmel's advice. It will never hurt them to have a repaired spare on hand. BUT, and it's a big BUT (bigger than one belonging to a "famous influencer" 🙂), I'd be very carefully checking all the sensors operations with manual readings on a suitable meter, before reconnecting to the new snap. They've done something seriously wrong to have upset the snap. Check ALL connections are correct, and no other supply fuses are blown that might have been missed. cheers, Aus

I stand corrected. Missed that it was an HMI. Re the toggle coil, I had never thought it would be put on the rail, but agree it looks that way. This is akin to those manuals where the people who made the product explain how to use it, but because they know it innately the manual has lots of missing info because the writers know all about it in the first place. So I'm happy to be punched a bit on all of this! 🥊 Bad case of the way too much to dos and not enough time this morning. I shouldn't have looked at the forum at all. 🙃 cheers, Aus

Edit.....this line incorrect!.....Elevator test is being called, but only on one scan after TD210 times out. Rung 4. Flex, my suggestion was a different way to control the output other than what was initially being done, but I was expecting Nico to control the toggle somewhere else using logic they would think out. The whole point was don't have 2 MBs that will possibly conflict with each other controlling an output. How to do it and how to display it was a point of learning for Nico. Nico, what's the reasoning behind your formula in rung 1 with all the IP addresses being added? It makes no sense to me at all, unless you're using it as a check to see if someone's been fiddling. Be aware that your result MI may not be large enough to handle the numbers and might need to be an ML. Also, be aware that on the forum we often see people coming from a totally different method of programming who think that ladderwork runs the way they are used to, which is mostly a totally incorrect assumption. There are many aspects that need to be learnt, and the help files are a good source of basic info. I'd actually be starting from scratch, play with the plc doing trial and error on basic concepts, building knowledge about the unit along the way. That way you'll end up with a much better code layout, with everything needed running according to the basics of how best the plc handles things. cheers, Aus

If you are online to the unit, left click the output coil in the window, and you'll have a little popup appear. Right click on "Set" and the ability to force the output on or off etc appears. See if forcing it on actually does so. If it does, then something else in your logic is upsetting the process. If you can't figure it out, then post the program. I am also assuming that the program you have written HAS been downloaded to the PLC, using Connection/Download. Some of your descriptions imply that you are only changing things at the PC end, without the PLC being told of these changes. cheers, Aus

On top of what Kratmel says, I would be changing the entire method. Use a toggle coil that directly switches a single reference to O84. Then use a Binary Text for the screen indication, based on MB7 (if you choose to keep that MB). There might be other factors that make this impractical, but to me you are complicating things and also run the risk of instruction clashes due to using 2 separate MBs as controls. Think your existing logic through, bearing in mind that the ladder always works on the last instruction that acts on an operand. MB7 O84 -(X)------( )---- cheers, Aus

On top of Gabriel suggesting a colour change, which is incidentally done through Project/Properties/Colors, perhaps my suggestion here in a related topic might make things easier. cheers, Aus https://forum.unitronics.com/topic/4619-call-me-a-relic-go-ahead-call-me-a-relic/?do=findComment&comment=17158

Senior, Alex is likely heading this way with his question....but did you notice the "Previous Versions"? Also the "looking for other versions?" at the bottom. Visilogic constantly evolves, and improvements sometimes mean fundamental changes are necessary. Most times you stick with the version originally used. Have a look at this topic: https://forum.unitronics.com/topic/7245-dont-update-just-because-you-can/ And here's a screenshot of the older versions readily available. cheers, Aus

Hi all, in again visiting this site for a specific need, I realised that it has many things that might be useful for forum users. My link is for the hex colour picker, but look at all the headers and you'll see how informative it is. cheers, Aus https://www.w3schools.com/colors/colors_hexadecimal.asp

The relevant question that has not yet been asked is "What model PLC is it?" Remote doesn't work for some smaller models. This is not made clear at all until you find out after lots of frustration and heartache trying to connect. cheers, Aus And a later edit, I note that the app help file does now show the list of models. When I was first trying the app just after it was released, there was no mention of this limitation at all. Have a look at this topic... https://forum.unitronics.com/topic/4218-remote-operator-on-pc-works-but-android-version-does-not/?do=findComment&comment=15486

Shahar please note the comment in the forum welcome area. "The forum is not the official Unitronics support channel - it is manned by volunteer users and sometimes gets visited by Unitronics employees". Your comment We are not here to write your program for you. We get paid to do such things for clients. As Joe says in his #4, you need to learn about Visilogic using the Help files and examples, and try writing things for yourself. Many things are best learnt by trying basics on the actual PLC before going further. We give advice on problems you might have along the way, but you have to do a lot of learning yourself.

Victor, this appears to be a classic mistake where you want instant results of correct reads from your system on boot. In most instances you need to build into your programming a delay after boot before the PLC starts acting on anything. The delay time must be matched to the maximum time it takes for all your external sensors to stabilise, and also to a lesser extent the various digital and analogue inputs of the PLC itself depending on your HW configuration. Also, if you have value averaging set up in the PLC, then this needs to be allowed for as well. cheers, Aus

So we're entering another New Year in a little while. With the full range of the vagaries of humans being displayed on the planet during 2022, it's a timely perspective to watch the universe simply rolling along. cheers, Aus saturnmoon.mp4

And a PS to all of it. For the price of the gnome you could easily get an old laptop with a native serial port. Many users on the forum have such things, purely used for the multiple older systems we service that only use serial. It's a constant issue faced with newer PCs/laptops etc. Makers ignore the fact that serial ports are still needed by many people in the real world, but because it's an "older, out of date" comms method they don't include them. Grrr. cheers, Aus

My input on this is that the reference to the modem you are seeing is there all the time, but users don't often notice it. I've always figured it's the way the connection is done internally in Visilogic. If connections are slow, you can see it very briefly on disconnect and then it disappears. I would suggest that you go into Connection/Modem services and choose a com port there that is not used in your PC at all. Ensure it is not the one designated in Visilogic for your normal serial work, and is a free one by making sure hidden connections are also shown when using Device Manager. For me this hasn't made a difference, but at least it ensures there is no potential conflict going on and it is still simply Visi doing it's thing. My thoughts on the connection issue is that the Gnome is too sophisticated to do the job wanted. In particular, the web page you've linked to says it needs configuration via the web interface. Way too clever for what is needed!! You want a simple usb to serial converter based on the Prolific chip. If you query google using "Prolific USB to serial converter" you'll find lots of options. cheers, Aus

Tommy, that link is still working for me. You have to be logged in to get it. cheers, Aus

I've just downloaded the file and my paid A/V spent a fair while examining it all, but came up with nothing wrong anywhere. I would say it's a limitation of using the free version of Avast. cheers, Aus

On top of all this good info from Flex, you can do a test connection without upsetting anything going on. Hook your new cable into the programming port, which is the one that doesn't have a metal surround. With your cable connection done correctly to the PC, you should be able to interrogate the PLC using Visilogic, using Connection/Communication & OS, with the Type in the first tab as Serial and the correct PC port and then clicking Get OPLC Information at the bottom. If that works ok, you can then see if the program is accessible or not, by exiting that window, opening Connection/Upload, and following through any on asks presented, and again clicking Get OPLC Information. It will again show the same information, but on clicking Exit, this time Visilogic will try and get the program out of the plc. If you encounter Password protected all is not lost, but if you get no upload enabled your hunt definitely needs to start. Also check if there is an SD card in the PLC, the program might be on there....if you're lucky and the original creator has thought it prudent! But by the sound of the machine, it is probably proprietary. Good luck. cheers, Aus

Mario, that link you gave is not for Unilogic, it's for Visilogic. So the question might relate to where you got the Unilogic file from? Looking at your screenshot, it appears that you got it from here, which should be ok: https://unitronicsplc.com/Download/SoftwareVersions/UniLogic/UniLogicSetup_1_32_Build_61.exe Have you done a complete system scan before running the file, in case there's something lurking on your system? cheers, Aus

curtharrington1, I don't know what happens in Unilogic as I don't use it, but you have to be very careful doing this in Visilogic as such an action completely stomps on any matching operands that are used in the destination file. It would be useful to know if this caution is correct for Unilogic. cheers, Aus

Technically, it's not....it's just free from the PLC's maker. Unlike many other PLC makers, who can charge a fortune for the means to program their units. Further to Joe's comment, you might be lucky. Check if the unit has an SD card in place, there might be a copy of the program on there that you can access. Otherwise, yes, you're screwed. cheers, Aus