Ausman

Joe's cartridge might have just a few more copper wires than necessary! Flex, what's wrong with that? They even have safety handles for easy disconnect, much better than the real thing! And a reminder of the topic here: https://forum.unitronics.com/topic/5862-what-not-to-do-when-you-run-out-of-fuses/ I think we've all unfortunately been there at some part of our lives. I well remember years ago a crucial contactor failure at a mine site in the middle of a desert in Aus. No spares, nothing else suitable, coil failure due to high ambients. The only possible cure was some carefully wedged matchsticks mechanically jamming things on, with subsequent very careful, continual observation of clamp meters until spares arrived by light plane quite a few hours later. 🌩️ cheers, Aus

For your "password" I think that Compare/Within Range would do all you want.

The pdf you supplied shows that the parity can be changed in the sensor. Bottom of page 8. It would be possible to do UniLogic programming to change the parity, you would simply need to add some code to do a write to the sensor instead of a read. Once the change is done, you would then change Unilogic to whatever parity you decided to use for both sensors and perhaps the code could sit in readiness for next use, or be deleted. To me, your easiest way of doing this is to connect to the sensor by using a RS 485 port on your PC. The parity register can then be easily accessed with a variety of modbus tools freely available online and changed to what you want. No Unilogic programming needed at all. cheers, Aus

Further to sgull's comment.. https://forum.unitronics.com/topic/8850-important-sub-routine-advice/ You should also see whether the bit is actually being set and then reset so quickly that you can't observe it happening. For the sort of thing you're wanting to do, your existing instructions have the bits being Set and Reset all day, every scan, which means you can probably not use Set and Reset. (And I ask are both meant to be sets? One is a reset...is this a typo?) If you actually need MB154 to be a Set that is then Reset elsewhere in the program once something is achieved during that day, you need to have the initial time logic end up as a transitional contact doing the set. Sometimes this is best done through interacting directly with SI30-38, rather than the "convenient" method. cheers, Aus

To me it all depends on speed of response required. If not "immediate", as they're running separately you could possibly use 485 to send simple relevant commands if the drivers can handle such input. This would keep it very simple, but 485 ability is the issue. cheers, Aus

There won't be with no wiring connected. They are relays with a shared common. You either make the common - or +, but I always prefer to switch the +. So + goes to the CM# and on relay activation you get + at the relevant output. FYI, this is really electronics 101. Prior to doing further work, I suggest that you need to do some initial learning of some basics. cheers, Aus

As well.... To me this is the essence of your entire issue. Somewhere in all of this process the way the information is being stored is affecting the data's structure.

I get that completely. The different hardware trick I told you about a while back would likely help a lot here, but I understand it's a big undertaking to implement in your situation. Perhaps in eventually changing things over you could get rid of presets completely and simply rely on the plc loading everything from the SD store on boot, which means it would be fully up to date. Easy to say, hard to achieve on a big scale, likely worth it when you've got the time. cheers, Aus

Ok, I'm being dumb here and have probably lost some of the complete amount of info in the topic...... If reloading presets is an issue, but having them in the first place is essential to ultimate correct operation, why not initially run from all presets for just a few scans on the first boot with outputs locked off, then automatically stop things and reload stored parameters from file. It might even be possible to have this all happen automatically, finally ending up with correct stuff. But I think this will likely get back to you having odd numbers appearing. I wonder if there's an easy way to singly check all parameters against what they're meant to be in the stored ones, and doing any corrections that are needed. It wouldn't take long for the plc to do this on its own, if it's possible. Thinking cap time....... cheers, Aus

@Saragani The TU24 issue appears to have been overlooked, so wondering if it could please be rectified. We've also had other models mentioned on the forum that aren't listed, so a little more time fully checking the lists wouldn't go astray.

Ok on all of that except the initial generation of the UDC that Download Manager then handles. ??? That was why I made my comment. Thought: Prior to the next step initiate the SD save on all; Then send out to all a blank project with just the necessary addresses for each specific plc in each blank project; As part of that project have the plc do an init and reset on first run of the blank project; Then do the correct download and load things from the SD, perhaps this might cure the issues? cheers, Aus

With regards to the SB75 puzzle, I also thought it an odd thing on my first read about it in your post. I mean...it implies that the system is doing scans and the bit turns on for one scan once the download is finished. Huh? It's running scans during the download? I'm wondering whether it might be a mixup of comms direction, part of the back to front naming re down/upload to the plc. It might be referring to upload? @Saragani could you please explain this completely, how it works etc? And also look into the entire issue presented in this topic? Re the random numbers, it still implies the way the numbers are innately stored in the plc moving around a little. Please confirm that every plc is using the same OS, same version of Visilogic, same everything before you start the process. I have now installed DM to look at it better and I note that it has the ability to download everything to the plc, embedded into the file. Are you using this, or just doing the application? I also wonder if different versions of Download Manager only match perfectly with specific versions of Visilogic? Finally...during getting the program I also noted something that is perhaps important. As I have said, I have never used it before. My highlighted bit implies only a single PLC for Unidownloader, so maybe this is the issue. But how do you make the UDC in the first place for multiple same units? I think what is needed is a comprehensive method description by someone who completely knows all of this. cheers, Aus cheers, Aus

I don't use Download manager so don't know it's quirks. However, I am wondering how many operands you are wanting to store and retrieve each time? And why not use SB2 to trigger your reload? I think you're interpreting SB75's action incorrectly. My interpretation is it turns on for a single scan and THEN you can run your application, so your ladder test won't work. But SB2 should do what you want, along with an inbuilt startup delay to allow all operands to come in. That's why the question on numbers..... cheers, Aus

Fernando, at present I can't answer your DT RAM question. But a thought you might want to check.... Leftover operands might be upsetting the process. Have you very carefully gone through your entire project and deleted unused operands? Use View/Operands not referenced in Project. I always use the unused operands list very carefully, cross checking everything, as I have sometimes had it referencing things I know are in use. But mostly this relates to vectors. However, it is very good at picking up those small changes you tried years ago that you didn't ultimately use, but an MB or MI here and there done at the time that you've forgotten to delete still exists. If they are still around, they may affect things the way you're thinking re clusters etc. Even just one element hanging around might upset a host of other "real" ones. cheers, Aus

To me it depends on what is harder to implement overall. If the numbers always remain the same you could have a database in the plc that matches numbers to the visual description you want, and then displays that instead. But if the numbers change all the time, then you need to do as described. cheers, Aus

No-one has mentioned this yet, (and your program does need adjusting) but ensure that ALL the power supply requirements for the snap-in are correct and it is seated correctly. The snap-in manual is easy to misread as it separately notes various power connections . Please also look at point 11 in the pinned topic here: https://forum.unitronics.com/topic/6229-ongoing-22-topics-almost-worth-pinning/ cheers, Aus

Thanks Fernando, it's been so long since I first discovered this that I'd forgotten that part. Isn't it amazing what one finds when you look up Help! I don't know the answer re V700s. cheers, Aus

@Cara Bereck Levy I must be missing a perfectly valid reason why SB168 doesn't default as set at power-up. We often have users not knowing about this, and it seems a bit odd to me that it has to be activated when it is actually an essential part of the process. cheers, Aus

Don't forget that you need to allow a read offset of -1 for the plc to read things. If the target's register is 001 you need the plc to be referring to it as 000. Also, on many modbus items if you try to read even a small "block" of registers and the target doesn't use a register within that block, things will fall over as well. cheers, Aus

I'm trying to sell a pair of glove puppets. Hoping someone here can take them off my hands. 🖐️ 🙃 I know, I know, they're getting worse......

pascal, I've tried that method and I've never been able to get the function to work as you say between the two environments. But my attempts have always been with Visilogic. I'm also wondering what virtual environment you are running? Mine are older versions of windows so perhaps that is the issue. I haven't tried an "identical" version. It would be nice to know a definite method that works. cheers, Aus

One thing that might assist, but you may not know and is not obvious, is the ability to view Hex is easy. In the operand window under Format, if you left click DEC it changes to HEX. cheers, Aus

No-on so far has directly mentioned this, but as Kratmel says, check the jumpers. Being at default they are wrong. Default is the small asterisk. From your wording you appear to think that changing things in Visilogic sets the input correctly, but physical jumper position must be matched as well.