Jump to content

Ausman

MVP 2017
  • Content Count

    1,201
  • Joined

  • Last visited

  • Days Won

    68

Ausman last won the day on July 2

Ausman had the most liked content!

Community Reputation

130 Excellent

About Ausman

  • Rank
    UniGuru

Profile Information

  • Gender
    Not Telling
  • Interests
    Love/Hate waking up with a solution to a problem. Thanks brain....for not sleeping properly!

Recent Profile Visitors

5,848 profile views
  1. And also, why have you got the unit set as network ID 255? And why the 0s in the Client area? cheers, Aus
  2. 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
  3. +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
  4. I'd love to take all the credit for this suggestion, but it has been mentioned by lots of people over time. 🤓 cheers, Aus
  5. 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
  6. 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
  7. 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
  8. 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
  9. 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
  10. It does? Perhaps you missed this one.... cheers, Aus
  11. 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
  12. 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
  13. 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
  14. 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.
×
×
  • Create New...