Ausman

The program has many things that I would do differently, particularly layout of elements. In rung 6 you've got 2 resets of MB28. So perhaps there is a similar overlooked hiccouph elsewhere that is upsetting what you want to achieve. However, to your specific issue (and I can't see that this observation will make a difference but it's worth a try), in rung 41 SD Utility you are referencing MI62 twice...looking at other parts of the program perhaps one of these should be MI6? Perhaps the double reference is confusing things? Regardless, what happens if you change your delimiters to << , >> (2C) ? I think this is partly what Gabriel is getting at. cheers, Aus

Yes Kratmel, this works, but I want a list of the theoretical times for any element or FB, and not need to construct my program to tell me this. If you've never encountered this in documentation it's understandable, but believe me it did exist in them thar good old days! What I want is very useful to have available, when deciding what of the various methods possible is the most efficient way of arriving at the same result. cheers, Aus

Most of my various older plc systems information/help have the info at the very top of the (paper!) page, as it was deemed important. Maybe 'cause things were a bit slower then and you needed to be clever at squeezing the best bang for the buck out of what was available. cheers, Aus

Hi all, whilst pondering Joe's elegant dead band rung elsewhere, I again thought of the usefulness of knowing separate element scan times. Has anyone got a list, or a link to a chart etc that shows what each element/FB takes in micro/nanoseconds etc to complete? I've never been able to find one, but surely it exists somewhere. And if it is blindingly obvious, I apologise right now for being a dumbbottom and missing it! cheers, Aus

Yeah, you could pre-tear a few strips of just the right size for the snap-ins and put them onto a pretty bit of silicone faced paper, selling them for a fortune on the huge markup possible! Anyway, we digress, but helpfully. How's it going, Todd? It did occur to me that you also need to be carefully checking the boiler earths, and it's inherent leakage anyway. You may possibly have something electrically serious going on at the boiler itself, which might be then coming down the earth lines to the plc for some reason, or simply interfering with the signals a lot. Don't forget that we are talking tiny amounts here, and the slightest induced variation from a variety of reasons can cause havoc with stability. But being a boiler one would think that it has a lot of innate earthing anyway. Give it a very good checkover. cheers, Aus

Also, in case you haven't already done this, have a good read of the Help files. Use index to find UniCan and then read Canbus UniCAN, looking at everything on the page be it the green links and also related topics, as well as UniCAN. cheers, Aus

Yes, but you need to do it to one decimal place. Have a look in the Help files and do a search for Analog I/O Ranges and you'll see a list of ranges etc. cheers, Aus

Hi Josh, you don't need linearization. Thermocouples read directly. You set up the parameters in the View/Hardware Config of the relevant input. You need to know what type of couple you are using for it to read correctly. When in the relevant analog input area, click on Type and you'll get a drop down list. You also choose C or F in Mode. cheers, Aus

Yes we have discussed this before, and the problem remains. I don't know what you funny Yanks call it, but to us upside down people duct tape isn't gaffer tape. I think you call gaffer tape race tape. It doesn't stretch, unlike duct tape which can be a sticky, half-pulled-itself-back PITA, a bit like trying to undo something wrapped in myriad layers of insulation tape after it's been in place a few years. Gaffer has a sort of woven backer and can be easily torn into strips or whatever is suitable, and sticks like toffee to a blanket. Duct tape has it's place, so does Gaffer. I always laughed in the Alien movies because here we are in space many years into the future, and heroine Sigourney is tying things to her super advanced weaponry with good old gaffer tape! cheers, Aus

Hi Matej, I think Joe has looked harder at the program than myself and might be more on the right track, but for my suggestion you are changing the wrong speed. The area you are in is the PC communication settings. You want to be in the UniCan settings, which is opened by double click as shown in the attached pic. You can then choose different speeds in the circle area. cheers, Aus

Hi Matej, I haven't looked in depth at your program, only quickly, and for a starting point I would be interested to know if slowing down your Unican rate helps at all. Shift it back to 10Kb and if that fixes the issue, then increase it in upward steps until you find the speed that is stable. Superfast is great, but sometimes buffers/line problems/fairiesandgoblins etc create issues that make it hard for the system to keep up with what's needed. Don't forget you need to change this speed on both units each trial. Perhaps a later closer program inspection might reveal something obvious, but try this for now please. cheers, Aus

Do what Flex is suggesting, but also...... To me this sounds like you need to have modem/router work done at the remote site. If you are saying it was all working fine, including Remote Operator, in the workshop before shipping, then it is a site issue. It is far preferable if the remote site has a static DNS rather than Dynamic. It can save you a lot of headaches. But if it can only be Dynamic, the very first thing needed is to get the modem/router telling the world what it's current address is. Most reasonable modem/routers have this facility built in. After that is happening the router then needs to have instructions given to direct the external requests correctly. For years I tried all sorts of free DNS providers that were decidedly haphazard in their effectiveness. In the end I stuck with paying a tiny amount of $s to dyndns.org which has always been rock solid performance. cheers, Aus

Ahh yes...I'm stuck in keeping it around 400 after it's been put up to 600 initially. That's why I said I was a bit confused about what was wanted. cheers, Aus

sgull is correct, but I would also add that in a lot of cases you have to build in a bit of hysterisis/deadband/whateveryoucallitcolloquially . The reason is that if you are working with inputs that can vary the reading slightly around an average, your output(s) will chatter which in some instances is very damaging to components. I was a bit confused about what you want to do as the temp setting seemed odd. My suggestion is that when you need to do something like this, a little diagram of what you want your temperature map to be is extremely helpful. You make the Y your temperature, with X the time, and along the X you can then note how you can achieve what is needed. cheers, Aus

Have you set up the Hardware Configuration correctly in the I/O specifications area you first get shown during specifying the plc type? Edit...And also set the internal jumpers correctly? cheers, Aus

Actually you need to answer MY question about off time. You do understand that 2.222222...... Hz is only a little quicker than 2 x 100mS pulses per second, don't you? You're not thinking in terms of KiloHz? So again, we get to what is the off time? On your full load specifications, if the on time is strictly a 100mS pulse, then the off time is approximately 350mS. Both of these intervals are easily read by a normal input. cheers, Aus

What are the readings if you connect the PT100s right at the snap-in, instead of via the normal location? If they are normal, then I would initially be carefully going over every single earth point in the installation, especially the earthing on the PT100 shields. But you saying they are all going wonky implies a main earth issue as the first thing to look at. Do a direct connection first and see. Also, I routinely remove/replace snap-ins on an annual basis, to keep the internal contacts ok. They always really seem to be not as tight as I would like, so I add a bit of gaffer tape on accessible seams to assist holding it together. cheers, Aus

100mS = 0.1 Seconds, so the really critical thing here is what is the off time. Are you saying the pulse is 100mS with 50 ON and 50 OFF? Or the pulse itself is 100mS ON. In that case what is the shortest time it will be OFF? If, for instance, the OFF time is 50mS then the plc can easily read this change of state situation on a normal Input. Scan time on a simple program is measured in mS well below 10, often 1 or 2. So you have a relatively long time for the change of state to be accurately read. But that is why the question about OFF time. If it is only a few mS, which I doubt, then you will need to use a high speed input, but even an OFF time of 10mS should likely be read OK. If your program is simple and the OFF time is >10 like I have written about, and your plc is not reading the input change correctly, then you have something wrong in your wiring or your other input related interfaces. Your question about writing 1 to MB shows a need to have a good look at the help files about the various operands used in Unitronics, and how they are implemented in the ladder. cheers, Aus

Joe has just replied whilst I was typing this. Yes it is for a 130, but the essence of how to do what you want is the same. Your picture also shows a few things of note, it looks like you're using cat 5 for the 485 connection, so how have got the terminations arranged? Is the plc end actually plugged into the com port and not the expansion port? I would be slowing your 485 speed to 9600 initially. Also, have you got the plc's internal 485 jumpers set correctly? cheers, Aus

There are a few things wrong here. My understanding is you want the plc to control the Hitachi. So the plc is going to be the Master. I suggest that you look at Visilogic/Help/Examples/Version 900/ Project examples/Communications/Modbus/V130 Modbus_Master to give you a better idea of how to go about things. cheers, Aus

A quick look appears to show MB114 linked to a "Zero Spindel" and a touch button that appears to be Bottom Right/Speendell Operation. Maybe pursue this a little? I can't read a lot of the screens, and assume it is a language issue. cheers, Aus

Before anything else, please confirm that the ATC8s have their jumpers set correctly for the different input types they are handling. Each input must be matched properly to what it is connected to. cheers, Aus

This topic is doubled. Everyone please only respond on this one. Copy of Kratmel's answer from duplicate topic: Maybe min and max position in system parameters is wrong. Max is in min parameter and min is in max. cheers, Aus

This topic is doubled. I moved the other one Gennady did as guest in the lounge into this area of the forum, without realising it had been posted here as well. The other one has the .vlp. and everyone please only work from that one. I wish people would not do this, it just confuses things. The other one is here: cheers, Aus

I have put the file directly here for everyone's convenience. More soon. cheers, Aus Laser Technion X Screw.vlp