Ausman

Hi Mal, Trends and other File types do have limits, and these are listed in Help under SD Cards. Scroll down a bit to Folders and File Types. Trends are listed as a total of 320 .utr spread across subfolders. Generally the rule seems to be for the number in a folder to be 64. Please note other topics in the forum where corruption has occured and limits seem to be able to be exceeded. For what it's worth, I've been trying a quality Toshiba SD in a system that routinely corrupted things, and for a year or so now it has been fine, so I an inclined to believe that "although all cards are created equal, some are better than others!" But it does appear that the PLC only really likes working with 64 in a folder. However, some of my experiences are more than that in sub-folders, but they don't show properly if more than 64. cheers, Aus

Kratmel and Flex questions very pertinent and if none fix, some other points to ponder. So you can't access it at all, even with Visilogic simply using Get OPLC Information in Connection? I'm thus assuming that you have the reinit as part of your coding, initiated by screen, which then resurrects everything? No VFDs or poorly shielded interference going on? Is it only on a LAN, or does it involve use of WAN? And static address there, or dynamic? If the dropout is occuring around certain times I'd check the router settings. I once had a forgotten instruction in a router such that when it did an auto-reboot, it upset comms to only the PLC. Took lots of inspecting settings pages to pick it up, which resulted in much personal grumbling afterwards. 🙂 cheers, Aus

As you can communicate via 232, in theory you can use U90 to try and get the program out of the unit for you to then examine. If successful, I am guessing that one of the inputs is used to monitor whether power of a certain type is on, and this is raising what I think will be a screen that is part of the user program in the unit. As Alex says, not quite enough detail. U90 has lots of help to assist your learning. cheers, Aus

Total bummer that the word is actually Regeneration.

Without the password you are in trouble. However, was the Visilogic programming done using a company computer that still exists? If so, the actual project might still be in the computer, and you will then have a copy. Check the name of the project in the PLC by using Info mode to try and match it up to any remaining projects in the computer. Use the Help file in Visilogic to find out how to access Info mode. But Info mode might also have a non-standard password, it all depends on what the original programmer did. Also check whether there is a project copy on the mini SD card if one is fitted in the PLC.

I've just asked support to get in on this topic as I think it is important. As well, re the above, is this info below the above screenshots relevant? .........To me , it is....... As I don't use Modbus IP at all, my knowledge is limited. But am following this topic with interest. cheers, Aus

Fernando, any chance in your systems of wiring up UniCan? You could possibly get simpler and better performance by using UniCan for simple fast comms b/n all your 570s and 700s, and then localised serial which your slaves may be able to do. cheers, Aus

I also suggest that you take a look at deriving your time by using a 1.25 or 2.5mS Interrupt Routine. Bearing in mind all of Joe's comments, using the Interrupt might give you better accuracy. In some ways it is likely easier to implement, too. Look up Interrupt in the Help index, and then go to Interrupt Routines. You could easily implement both measures concurrently to let the PLC show it's own comparisons over a week or so. I suspect that you will find the Interrupt will be better accuracy, but it would be interesting to know the result. cheers, Aus

Please also note that if you are simply showing a countdown for people to observe, Kratmel's answer is perfect. But if the 130 is actually controlling the fan's run time, the ideal method of doing this is for the timer to be linked to the fan control output with a little ladderwork. Having 2 separate timers running for essentially the same thing will work, but is not ideal in case the fan output is turned off for some reason. In that case the timer will still be implying the fan is running. cheers, Aus

Hi Jamie, please read the "Getting Started" topic in the Help files, with particular attention to "Ladder Net' which is a sub heading at the bottom of "Ladder Editor". This will better explain what is going on with your existing ladder construction, and the entire Topic is worthy of a full read for your learning curve. As are all the Help files. cheers, Aus

Without knowing more, to me this is the answer to your issue. You have 2 things controlling 1 thing. Don't forget that in ladder, the last active reference to an output is the one that will be used. cheers, Aus

The Slave Address table that Joe posted is part of the Help page I asked you about. Rather than do screenshots I thought it would be wise for you to know the page location for an indepth read. Help generally has all the info one needs, but sometimes does need deep digging. cheers, Aus

Have you fully read the entire Help file listed as MODBUS in U90 Help index? cheers, Aus

And to top off the info from Flex and Fernando, it looks like you want to use ON status for your controls so you end up with all 8 MBs ON., instead of one ON shifting along through the MBs like I thought. To easily restart such a sequence, use 16MBs and vector fill. Do 2 fills in your "turning off" action. 1 fill is 1 to the adjacent 8 MBs, the other fill sets your controlling MBs to 0, and then leave fill alone until the next "all stop" which repeats both fills ready for the next start. By moving 16 bits, you will progress the 8 ON bits along your MB vector, progressively turning them all ON. cheers, Aus

I don't use this, but your description is exactly what help says. I believe your need is to move the 1 progressively from MB40-47, which then changes motors being run as only one of these MBs will be on. Correct? If you change your Vector Shift amount to 8, it should work as you want. But I can't check this at present. cheers, Aus

I have never had to do this, but can't see any real issues that can't be done via maths and manipulation of numbers as everyone has already said. The other question is how do you want it to actually show? Will it be as simple as 6.8 - 03- or something more complex? As mentioned by others, you will have to take a few steps to achieve the result, which will end up as either a string or number being displayed on the screen, possibly with other smaller notations accompanying the main "number" to make it look the way you want. Joe's question re range you want is very relevant. As well, have you actually considered what your transducer can actually do in working with the PLC? If it is running 0 as absolute vac, and 10v as "atmospheric", your range of of 4096 via the plc is actually only going to be able to show something like .25mbar at an input reading of 1. Which actually isn't that low a vacuum. cheers, Aus

Welcome Ben, highly relevant to your question is the need to know what model Vision you have?

1). The comment re the battery being low seems to be a mistake from deriving the battery level from a working screen, which would show an external battery level during operation. It is not the plc's battery, as you've checked. 2). Your last photo directly above this post shows that the laptop IS communicating with the PLC. The Model etc is shown at the bottom. I would carefully check all cables for errors, as well as noting next point....... 3). Are you using a usb to serial adapter? It must use a genuine Prolific chip. Other adapters may work, but not completely and correctly. 4). Did you do the Visilogic installation as Administrator? Read this: https://forum.unitronics.com/topic/7917-visilogic-doesnt-work-properly-after-installation-what-install-as-administrator-really-means/ 5). Start your baud rate at 57600 as Dan described, and pay attention the his other comments: Power up, check communications - COM 1 57,600. Use Info Mode (At the PLC) to check COM settings. Does your program modify COM Settings for a device? Have you changed them? Please note again that this is forum is manned by volunteers. It is not the Makers of the PLC responding to your requests. However, from the appearance of all your results it would appear that the PLC is working as best as it can, but has somehow had it's operating system corrupted. This could be due to large power spikes during your work, or even nearby heavy loads or VFDs. The issue is likely easily resolved by the forum, but because we are not on site, it is difficult as we can only go on the information we get. For now I suggest you follow what Visilogic and the PLC are telling you to do. Also check what O/S the plc needs by looking at the program you uploaded and selecting Project Information. This will show you what Visilogic version it was created with. Note this carefully as this is the version you should be working with on your laptop, and using for all the PLC work. Later versions of Visilogic than the one used to first create a program can create issues. This is not a fault, it is the nature of continual improvements.

As a Vision only user, that looks like an Endian problem, which would require some simple rearranging of data, in a consistent pattern for everything received. In Vision this is done with Swap Bytes, don't know what it is called in Unilogic, but have to assume it exists. cheers, Aus

Hi Brugola, my post is telling the makers of the PLC that there IS missing information. I am confirming your post. That is why I have highlighted in blue, "Slow blink" and "Rapid blink"....there is no "On". Cara is the head of the information section, and faces many difficulties in keeping literature up to date. cheers, Aus

Hi Brugola, this does appear to be a case of missing info. Others may already know the answer. @Cara Bereck Levy could you perhaps please follow up on this. Status LED A triple color LED. Indications are as follows: Color LED State Status Green On Operating normally Slow blink Boot Rapid blink OS initialization Green/Red Slow blink Configuration mismatch Red Slow blink No IO exchange Rapid blink Communication error Orange Rapid blink OS Upgrade This info copy paste is lifted from the UIS-WCB2-SPEC-1-16 pdf. cheers, Aus

Gariel has just replied as I write this, with a point I was typing! Also, the usb adapter must use a Prolific chip. From what you have said, I gather that you use the same adapter to connect to the PLC on your "line". Check that the link is working with this unit ok, and if it is, use info mode to find comms settings. Can you get anything out of the plc when you simply do a Get OPLC Information from the Connection/Communication & OS. If all else fails, I'd be doing a full reinstall of OS etc, that matches what your unit on the line. Don't upgrade for no good reason, it might create big headaches. cheers, Aus

I've seen my A/V play funny buggers with addresses at times, with the virtual adapters it uses. Try with it fully disabled, just to check that isn't the cause. And you haven't forgotten any leftover static specs in the adapter settings that might be upsetting things?

As well as Kratmel's suggestion, the "91" error is the classic one that comes up without install and run as Admin. See here: https://forum.unitronics.com/topic/7917-visilogic-doesnt-work-properly-after-installation-what-install-as-administrator-really-means/

Good call, Cam, the fuse was indeed blown. I've never had one blow so had pretty much forgotten they are there, and being an M91 I hardly work with them now. I had them on a number of projects that have all been demolished in the last few years. The unit is running on a 12V battery system that is not permanently connected. Wondering if a mistake reversed connection would do the fuse, but there appears to be innate reverse diode protection? If this is so, seems strange it didn't take out the lower amp F1. again with protection. A few mods are going in along with repairs. cheers, Aus