Ausman

Look at this post and the rest of the topic, for some possible help in what you want to do:

sgull, maybe you can do that on bigger Visions, but I only use 130s so that's the way I've done it for a while. cheers, Aus

OR....make one screen that is just for setting up the clock. It's easy to do. For example, setting the hours and minutes, a keyboard numeric entry with numbers restricted to 0 to 2359, and then the linked MI being used in a direct store to SI31. I've had this for years, and the thing that stands out for me doing this method is that if there is an incorrect entry in the field, like a time of 2186, the plc won't accept it. But if the time entry is correct, it does. Note the Plus/Minus was the convenient key to use in the example, nothing to do with actually altering the numbers in this case. Also, if the time zones are a long way apart, repeat runs of manual entry to stop the day rolling over incorrectly will let the days look after themselves. Or do the same storage method for the other SIs involved. You can use the same MI for different things, just changing what button you use, which changes what SI is written to. Again, if the entry is incorrect, the plc won't accept it. cheers, Aus

Fernando's explanation is the reason for my observation. For simple reading like you are doing, I have had great success in mounting sensors so that they are aligned axially to the motor shaft at the fan end. I machine a "slot" into the end of the shaft at the fan end so that you then have 2 segments of the shaft that the sensor can easily read by being mounted on the cooling fan shroud. This is all very easily set up and machining can be done without disassembling the motor if you are careful. No belts or other bits needed. The way it all then works is the way the sensor is designed to read such things, as the shaft face is parallel to the sensor face. If there is enough shaft length on the fan end that lets you do this with a small hub all the better, but most of the time I find the fan seats properly with very little shaft showing to effectively use a clamped on hub. Done correctly, you have 2 impulses per revolution. The obvious downside is the need to do stuff to the motor, or a replacement, so if you can do the tiny hub method it makes it a lot easier as you just change it to the replacement motor as needed. I did a little drawing but for some reason I can't upload it here at present. The slot is machined by running an end mill of suitable size across the shaft, centred, so that you get 2 equal sized shapes on the end of the shaft that are shaped like woodruff keys. Ohhh....and for some reason after doing the save process in a different way, NOW it does!! Depending on sensing needs and complexity of machining involved, you can vary the shape of the machining to create more or less segments as needed. cheers, Aus

Fernando, perhaps you need to add this into this topic: cheers, Aus 🙂

I'm pleased it looks like things are working out ok and fully agree with everything already said. But I also want to throw in something else. To me your sensor needs to have it's shaft revolutions to sensor triggering checked to confirm it is a fixed proportion over all speeds. This is easily done by looking at the sensor reading online whilst varying the shaft speed. eg 100 of output = X whilst 1000 of output = X x 10 and so on, over all the speed range possible. The reason is I wonder what metal your sensor target is made of (it looks to be aluminium) and whether the sensor is simply reading the steel screw that holds it in place on the shaft. With higher speeds it may not be triggering the sensor correctly, or long enough for it to be read correctly, if it is only sensing the screw. Not likely, but something to ensure is ok. Where the PLC controls the motor speed and also reads an output directly related to it, I always run this as a first check on this relationship by using a tiny bit of ladderwork for that machine that runs speed up and down in given steps and records results. I would also possibly slightly increase the sensor gap from the target. There's not much room there for any stray piece of waste etc floating around and getting caught. On the other hand, the way it is now.....it has to get into the tiny gap in the first place, which contradicts what I'm saying! Cheers, Aus

Hi all, today I've had to do a fair bit of shuffling around of MIs in a program and I have rediscovered one of my pet hates. I'd forgotten how annoying it is! If you have the operand list open on, say, a series of MIs that you want to move somewhere else, when you open Replace Operand the lower pane shifts to the Find tab. It is across all element types. You have the lot you want to move on screen, and then when you get to the area that controls the move, the things you want to move and need to easily see to ensure that everything is correct...have disappeared! For a few times of use it's tolerable, but doing a lot of moves it becomes a right PITA. Instead of visual references to make sure selections are correct, you have to write things down, or do a screenshot. It's silly! I'm still on 8.65 and wondering if this has been changed in later versions? Or is there a trick I don't know to keep the info there? cheers, Aus 😠

Before anyone can help you on this, the thing that needs to be fully understood is the number of shaft rotations to output length. In your program, what is E-stop? Emergency or End? Why the different formulas?...Trying different maths to see if it matches up to old? There are many things odd in the structure of your program that invite comment, but the distance relationship is a must know before all else. cheers, Aus

My little bit of input is to say that this is one of those times my pet method of using a single counter based on SB13, instead of timers, would be much easier to set up and also follow the logic online. The various things you want to do, you simply change the counter amount. No time to do a sample for you. Maybe later.

I haven't been able to replicate what happened. What I suspect I did is get 2 running instances confused. I usually run instance 1 doing a particular plc, and no. 2 running another. But I think that when starting, I opened the 2nd unit's file with a double click, and W7 always uses the first instance as the one for any open via file click. So I was perhaps re-naming things that were already open on screen. I do remember getting "program is already running" popups and puzzling over this until I sorted out the instances, and somewhere in this process the hiccouph occurred. It resolved on closing a visible instance and stopping a hung instance and then doing things correctly. On the Datakeeper front I again had a look around the web and found a little program which supposedly works the same way. I'm going to try it out and will advise. Every other "modern replacement" I've tried doesn't work the way I want/the way DKeeper did. But I'm sure there's something out there that does, I just haven't found it yet.

Flex, wondering if you have date issues/battery issues on your PC. Can't see how it might affect things, but perhaps....... Incidentally, (and perhaps not coincidentally) last night at a site I had an odd naming thing happen which I'm going to explore later today to see if I can repeat it. I renamed a vlp direct within the folder it was in, and on opening it was called the original name in the menu bar.

When doing ongoing work on anything important, I routinely run it as 2 names I pingpong b/n. XXXXa & XXXXb. Doing a save after every compile once I complete each step. Sometimes only a few minutes apart. And I also try to remember to occasionally restart Visi as well. But I know how easy it is to get in a groove on something and forget to do all of this sort of thing. I've often referred to the old program Datakeeper from PowerQuest being the best thing ever, but I have never found a good equivalent that works on modern OSs. cheers, Aus

After no.2 "virgin" many elements may not have been "null". Numbers may still exist and some operand references might still be hanging around etc. which you have found out yourself. I had to do a few init and resets in my case. I don't know for sure how to clear all data tables areas in one go. I do manual clearing on the few times needed. I would think that getting the plc to do a Clear Table on each one in use would be the trick, but as to how to effectively do an Init and Reset on all the memory used for all tables I don't know. I think it would be a bit tricky given the dynamic memory aspects. (Incidentally, the dynamic memory bit was my thinking of why you were having trouble in one of the other questions on the forum, with memory not being used exactly the same way and thus old bits perhaps upsetting things) @Joe Tauser , @kratmel , @Saragani or others. Is there a way to fully clear out the entire PLC for sure in one hit? Without battery removal? cheers, Aus

In chasing a particular image I needed, I stumbled on this guy. Truly amazing talent and a joy to spend a few minutes watching. I've always envied great artists.......my brain knows what it wants to put on the paper but it somehow gets lost in translation! https://www.facebook.com/MarcelloBarenghi cheers, Aus

Also, ensure that the OS and Visilogic version is the same as the existing ones in the new 120.

I'm with Kratmel's observations on SDs, but I'm curious to see whether b/n your steps 2 & 3 you did an online look at parameters, and also ran an Operands Not Reference query. Some years back I had a similar thing happen that did not run an SD that sent me a bit nuts, and the only thing that cured it was a number of Init and Resets....not just one.....on a blank program. I found some elements hanging around with numbers other than 0, even though this shouldn't happen. Also make sure your data tables are completely cleared during doing all of this, too. And finally, totally left field, did you try things with a brand new (checked ok) battery? cheers, Aus

I enlarged the snapin image and it's hard to tell, but make sure the 0V & V1 connections are in the end of the connector, not 1 location inwards. The alignment in the photo shows 5N1 and BP1 into 0V & V2 looking correct, but the same lines into 0V & V1 look the same visual alignment but this means that they are one terminal upwards. If you could redo pics of the an input and an outputs from the side which will show the exact cable insertions that might help checking. I'm assuming 5N1 is 0V. It also appears that you're running them from separate supplies. This can cause issues. On Gabriel's suggestion, there are many references on the forum to snap-in tricks and fixes. The main one being that they have little room for error in mounting, and need to be fully in and retained that way. Some people add screws where you can, I use gaffer tape. cheers, Aus

Ahh yes, sorry. I've used it within Vectors in the past and mis-remembered that it allowed a range to be done. I'm putting a trademark on mis-remembered. But I'll allow usage here on the forum. We can make it the person over 40s version of "mybad", which unfortunately covers a host of frustrating actions that have little responsibility attached. 🙂 cheers, Aus

I haven't tested this, but couldn't you use Toggle Bit in Vector for this? No other mucking around needed. cheers, Aus

bruch, please advise the 4-20 converter specifications.

The program in Kratmel's video link is Modbus Poll. From looking at it quickly, but not understanding the spoken language (which I think is Thai), it appears that some control parameters are done at 255 & 256 which might be a way of you doing it with the PC. I really think it's worthwhile in your case to fiddle with the sensor using a 485 system on your PC. Have you tried grounding the green in between steps 4 & 5 already mentioned? The manual says either leave floating or ground it, but maybe grounding is essential.

All a little off topic but who cares?! I don't really know, but I've also seen big name firms do similar things in running modbus ports in odd, non-standard ways regarding parity etc. I've mentioned this on the forum before. (side note: Have I mentioned how how one of them labels relays NC or NO according to what they do once the device is running OK/powered up. Very confusing and gave me issues on first use.) The devices I mentioned arrived with the ID at 0. Perhaps the issue here is simply translation based, with the thought that 0 is used in PLCs and elsewhere in modbus, so it must be ok to use it as an ID. But trying to get an answer from the manufacturer as to why it's done is very hard....the general response is essentially "So what?" I could have logged the comms b/n the special program and the sensor to trace the way of doing it without the program once I worked it all out after a few hours, but on success I didn't bother. Made notes for the future and put it to bed. The same method has been used on other things that have arrived the same way. And another FYI: One thing that the sensors DID have which made things easy was more registers in use than specified. In cruising around once I was connected, I found registers that had correctly converted values, which saved a little plc work. No mention of this at all. So sometimes it is worth having a little wander around registers close to those in the specs, to see what might come up. cheers, Aus

+1 to all that Kratmel has gone through with you. My general field is HVAC. I doubt that this is so in your instance, but I have encountered some sensors at the cheaper end of pricing that need a special program to write the value properly to EEPROM. One of them actually started the address at something that technically wasn't allowed, so none of my normal PC modbus programs could access it in the first place. Ensure that the sensor's website doesn't have a "setting program" available for download. In the past I found that such manufacturer's were no help at all, I have often had to figure out how to use the program myself. Hopefully things have improved a lot. And incidentally, the cheapies were got as trials, and once I got them working as I wanted, they have been perfectly reliable for over 7 years now, whereas some of the big name ones alongside them have failed. Hmmmm... cheers, Aus

On top of what Fernando says, doing it the way you're suggesting can create issues with the potential to have conflicting instructions occurring during one scan, which can play havoc with physical devices. If you are determined to continue along the path you've chosen, I would be placing a deliberate small time delay between each change of control, such that the "new" control does not do anything for a few scans at least, and likely longer would be better.

Gogggles translate and thanks adotromon: I had the same problem. The one that the plc brings is very short and I have to connect with terminals for the moment. and not being more I leave this data as support for those who have problems in the future. The cable is 3 pairs shielded, the connectors are metallic and next to the plc it has a ground cable that makes ground with the connector and the shield. the connections are as follows: plc side 1 . White blue 2. orange white 3. brown 4. orange 5. free 6. white brown 7. free 8. blue adapter side. 1.free 2. orange white 3. brown 4. orange 5. free 6. white brown 7. blue 8. blue white I hope these data will be useful to someone since there is not much information on the web.