Ausman

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

The crucial word here for me is "clutch". Check that it is engaging properly with no slippage. Especially as it appears that it was disturbed a week ago. As for proper testing, you'd need to somehow imitate the mechanical movement needed into the encoder. I have often had small motors doing a variety of things on a test bench! cheers, Aus

Sarkis, have you read the Help files on PID that are native to U90? PID is listed under the Controller header and opening it lets you do all details. cheers, Aus

I had this issue recently in using another program, and after many hours hunting and hair tearing I finally found the solution. It was that the program would only run the mouse correctly if the puter was a single core system. The program had some sort of innate error (using old definitions that had somehow been missed during development??) such that it would NOT work the mouse correctly on anything running multi cores. Given that the creators are pretty sharp, I don't think this will be the case, but it would be worth trying the following to see if the behaviour changes: Run msconfig and go to the boot tab. Select Advanced options and tick the Number of processors box and set it at 1. Do all the OK/Apply backouts and restart. Try it out, checking that the system is indeed only running as a single core. Don't forget to set it back once you are finished! When you again go to msconfig you'll find things look a little different so choose correctly according to what sort of system you have...and what it was set at previously...which should have been the total no. of cores possible anyway. cheers, Aus

Are the modules from another machine or brand new? Did you place them in exactly the same physical sequence as before? Is the controller set to run these modules? Does "transformer that feeds them is drown" mean that the system got wet/flooded? Or is "drown" a translation mixup and meant to be "down"? You can post in your own language Ramon, many people here on the forum can/will translate. cheers, Aus

My comment on this "empty space" and "big icons/buttons/selection_methods" is that it seems to have become the "standard" for anything of late, as stuff has been tailored to be useable on smartphones. Anyone who uses a real computer has had this issue thrust on them for no really good reason, having to put up with all sorts of oversized junk thrown at them. The W10 start system is a classic example of this.....Stuff that occupies heaps of the screen if you let it. The "one size fits all" thinking that is completely flawed. Even though I don't use Unilogic, I am on board a fair bit with this comment as the screenshots clearly show that it has succumbed to the same type of thinking, when in fact it shouldn't at all. cheers, Aus

And further to what Cam has said, if you need to repeat a "function block", you have to do the same register work again for your next requirement. This can be a little confusing as you might think that this will upset things by having more than one reference to the involved registers in one scan. But the scan runs through and treats each "FB" separately, as long as you follow the rules. cheers, Aus

Kiki, I'm not exactly sure what you're asking here! Is it along the lines of "will something blow up if I get things wrong?" Or is it just doing bench testing. Something else? cheers, Aus

In answer to your question Flex, I'd ask support....maybe they know a trick. I don't. Sometimes having a native °F is useful if a little more precision is wanted without lots of mucking around. Due to the inherently larger numbers in °F. It is always possible to do a whole lot of calculations on °C if your actual hardware makes such calcs accurate. But if it only goes to 0.1 accuracy on °C, then the °F conversion is always a little flawed. For my critical processes I always have gear that can give me readings to 2 decimal places in °C. You Yanks just have to get with it! However, to put things in perspective, here in Aus we've been on metrics since 1974 yet we still have Whitworth/SAE/BSP/younameit bolts, double marked tape measures, a whole host of imperial stuff etc! So I think you'll be like Dan (and myself) for quite some time yet. cheers, Aus

For my customers it is simply just "the controller" as they don't interact with it much. The panel is mostly always just for me. So....no relevant comment from Aus!