Ausman

I don't know about doing it directly, but you could possibly send an email that his PC is set to uniquely recognise and thus alert him. cheers, Aus

Pls tell me that's not the finished rack? If it is, please send me the unused DI & RO 16...I can always use some spares! 😀 cheers, Aus

This is a classic example of how a transitional being called affects things akin to my statement above: " something unexpected going on during one of those "setup" scans can affect things ". The plc deciding what is being asked and finally setting things at the end of the scan, such that only one scan totally disrupts an expected operation, is an easy trap to fall into. And we have all done it at some stage! "Why didn't that work? Hmmmmmmm....the logic looks right so it must be a sequence issue missed by the dumbkerfarfen who wrote it!" (Hey...my new word that google's never heard of!) Without knowing the rest of your program, I would be putting ALL your motor controls in the one sub, which is constantly called. Another thing that you may possibly need to take into account is that you are running the motor via modbus, which has inherent delays that must be allowed for within all your controls. Things like emergency stops, deadband/hysteresis, etc. cheers, Aus

All noted & reasons etc 😢 😀 .......I was always looking at it with the view that this was the only modbus thing going on in the program. At this stage have you actually done a right click on element and done a "Find"? Just to make sure that you're not referencing things somewhere else. And are you sure that the sub is being called at that time. Visi displays power flow in a way that has a sub looking like it has power when in fact it doesn't, and this has been discussed here ad nauseum. One way that is used to check subs are truly active is to put a counter at the very top. Also you might have some other button reference that is stopping the sub during push. Keep in mind that Button interaction on different screens can sometimes be a big PITA, as there are often a few scans involved to fully set things correctly and something unexpected going on during one of those "setup" scans can affect things. A careful read of the way screens work is crucial, as the use of a rising edge during such times often leads to problems. cheers, Aus

Have you read my post 3 above this one? (Which Flex nicely replied to!) Also, I would try doing a full Initialise and Reset, and then running your program again. This often clears up strange gremlins that seem to arise due to "old internal references" somehow being retained. Connection/Communication & OS/2nd tab/bottom right. cheers, Aus

Why do you have MB33 at all? MB12 can go straight in front of MB30 in your ladder. cheers, Aus

Did you also install as administrator by using right click/run as admin? If not, uninstall using something like Revo Uninstaller and install again as admin, and once installed set the .exe to run as admin. cheers, Aus

From your description I am only assuming that your "new" CPU and touch are the same as the original.....it isn't exactly clear that this is definitely the case. If they are identical, have you ensured that all firmware matches the version of the program being used? Or go back to the original program and it's firmware? cheers, Aus

And also, why have you got the unit set as network ID 255? And why the 0s in the Client area? cheers, Aus

Did you install U90 using right click/run as Admin? And have you got the U90Ladder.exe (that is the main program once installed) set to Run as Admin using compatibility settings? If you did not do either of these, I would uninstall using RevoUninstaller portable and put things back in like I say. cheers, Aus

+1 to both Cam & Flex's suggestions, especially Flex's FYI. IP setting is not obvious at first in Help...you might be thinking as Flex says. Use the Search tab in Help to find TCP\IP: Socket Init and other mentions. These will steer you in the right direction to having the socket set in your program. cheers, Aus

I'd love to take all the credit for this suggestion, but it has been mentioned by lots of people over time. 🤓 cheers, Aus

Have you looked at Help/Contents which is next to Tools in the U90 menus? In the index, Analog, Thermocouple and Modbus are clearly displayed along with more references and explanations once you open the topic. cheers, Aus

I know it's a bit late now, but a thing to remember for the future is the use of Revo Uninstaller. It often solves incomplete uninstall problems. I always use the portable type, free/$ versions available here: https://www.revouninstaller.com/revo-uninstaller-free-download/ cheers, Aus

OK Dan, I have to ask! How many times did you bang your head on the wall during finding this answer? Good stuff. cheers, Aus

Flex, you forgot to add the label OCD to your name! 🤓 😀 Seriously now, perhaps mention 8). What type of download? 10). SB 168 powerup as 1 cheers, Aus

Have you tried using Modem Services, built-in to U90? If you look up "Modem, PC" in the index in Help, Modem Services is amongst the host of relevant titles and might cure the issue. cheers, Aus

It does? Perhaps you missed this one.... cheers, Aus

That's great Marcel. Glad it all worked in the end. cheers, Aus

I'm with Joe on it being the adapter. I use a combination of: desk systems MUST have a native com port (still possible if you look hard enough and often simply needs a header fitted as many mboards are still capable and have the pins in place); older laptops with native ports; or PCMCIA cards and usb adapters from reputable makers like Shentek etc. These have always worked fine in recent laptops, including one on W10. If you cruise around the forum you'll find all sorts of issues with inferior USB adapters. All our terrible experiences in the past wasting countless hours are available free of charge for your benefit....which boils down to "Get a Proper One"!! cheers, Aus

And another comment. Be aware that you cannot cut/paste between the instances, owing to the fundamentals of how it all works. The best you can do in this regard is Export from one and Import to another, but this needs to be done with great care owing to Import overwriting any contained elements that already exist in your destination program. cheers, Aus

OK. In theory, unless some new model has appeared that I don't know about, you don't have a usb port. So the next questions to all be tried/answered are: 1). Are you using the MJ10-22-CS25 adapter and cable that came with the unit? Checked the continuity of the cable? 2). Are you connecting this adapter using a native com port on your puter or using a usb to 232 adapter? If a USB to 232 adapter, what make and model? There are various issues with types from "little known" makers. 3). Did you install Visilogic as Administrator by right click on the installer and run as admin, and also set the visilogic.exe as "run as admin" as well? 4). If you can access Info mode on the plc, and you should be able to, go to System/Mode and choose 5 or 6 and start again with your communications with Visilogic. 5). For your comms to work ok, I have often found that I need to manually set the 232 speed in Device Manager to match what is being tried in Visilogic. This is meant to run at 115200, so start with that. But I have occasionally found that for some (unknown) reason I need to set this speed slower, so if things don't work, lower the speed progressively in steps and see how it goes. 6). You should be able to do all you need with Visilogic. cheers, Aus

What model of plc? Is it actually a 130-33 as shown in the screenshots? And please don't do double posts about the same problem. All posts on the forum are moderated, so there will be a delay before yours appears.

Sorry Master Yoda Joe. I thought I did. Indirectly. 😊 I do love that link. cheers, Aus

To me the video is showing that you are counting into an MI which is running out of capacity. If your "real world" scenario never gets numbers this high, it doesn't matter. Otherwise change to an ML etc. cheers, Aus