Ausman

Yes, I get that, but perhaps the protocol or something else has an error that relates to baud rate in use, and the way to check is to run different ones to see if it changes something.

I'm addicted to drinking brake fluid, but I can stop whenever I want. What is Forrest Gump's password? 1Forrest1. (Still here? ok...here's more...) I have a side job making plastic Draculas. There are only 2 of us doing it, so I have to make every second count. What do you call a pony with a cough? A little horse. (Ok, you can go arrgghhhhh now! But there will be more...... 😉) cheers, Aus

I've been squizzing at the specs for that module, and a question is what baud rate are you using? Does changing the rate change the timings you're experiencing? Start low and speed up for the tests. And questions which might sound insulting, given it sounds like you know what you are doing..... Are the correct resistors in the correct place, and/or the unit's termination set correctly? Is the cable a quality one? cheers, Aus

I've got a few 130s and none have had a failure. But perhaps there is another element in play here. Nearly all the time my cards are not doing any actual "work" apart from maintaining, or trying to maintain, the connection. The only use is a daily login to check a few things, and other slightly longer times when there will be a program update etc. Vastly different to an installation that might be running the cards non-stop with large constant chatter between systems. So the question is whether the amount of card usage might heat things up too much? That is something I don't know and can't answer. Logically a device constantly doing "work" must generate more heat than if doing little, but perhaps not. And a side note on "duct" tape. I've mentioned this before but a repeat. "Duct" tape in Aus refers to a wider tape that is similar material to insulation tape. Invariably this stuff slightly retracts over time and leaves a horrible sticky residue on removal, especially when subjected to any heat elevation. If you are cutting squares of it to put over holes, it will likely not stay in place that well. The better thing to use is what we call "Gaffer" tape which is also known as Race tape and perhaps other names around the globe. It is cloth based and is much better for permanency in situations like this. The other alternatives for covering openings, which I've had to do sometimes after removing a card and not having a replacement "breakout" piece, are: 1). use a small cable tie to hold an external cover in place, with the tie run through dedicated holes or existing slots nearby. 2). tiny silicone dabs which are large enough to hold the cover piece, but small enough to enable ease of removal if needed. Over the years I've actually found that this is the best of the lot, but "needs must" applies at the time! cheers, Aus

I'm a Non-Unilogic user, but I agree with Joe that it sounds like a retry length issue, which can be a problem if not correctly set up to allow for the time errors take to run out of attempts on the current request before trying another. Are you sure that retries and numbers of them are being allowed for, or better yet for testing purposes, there are none? Perhaps there is a setting squirreled away somewhere that you have forgotten? Or don't know about? We all learn something new each day! 😉 Question for my learning...is this 485 or TCP? I don't know the table source due to not having Unilogic. If TCP, could the plc be dropping the ethernet connection for some reason, and it's not actually a modbus issue at all? If 485, bump the timeout UP a bit and see what happens. And also, is this involving the device that does addressing in hex? Just curious..... cheers, Aus

I think that before doing anything else, you need to use Info mode to find what O/S is in the PLC. This will then tell you what version of Visilogic you should be using at present for best compatibility. https://forum.unitronics.com/topic/5839-new-visilogic-version-to-what-os-list/ Once you have got all the info you want from the plc you could then update to latest. Please also read this to ensure that all is well with your actual installation of Visi: https://forum.unitronics.com/topic/7917-visilogic-doesnt-work-properly-after-installation-what-install-as-administrator-really-means/ cheers, Aus

I can't see why this would be too hard. Each of the 3 attempts is handled on it's own for display purposes, with it's own unique display based on the variables' maths. Then a fixed time after the attempt for the next one to happen for each participant. Then the over/under time averaging of their 3 attempts can be simply compared to the previous one to decide who is the current leader. If the previous one is better it remains as the leader, if the new attempt is shorter times, it replaces/updates the old details in the MIs which retain the data. At the end of the fun it gets the email entry, which is really the only thing I see needing a data table, perhaps routinely saved to the SD as a progressively named file. Of course this sounds easy, but I do think the reality won't be too hard to achieve, with very little head banging on brick wall/cursing/etc. I'm assuming that you'd simply put Remote Access or Operator onto a big screen nearby, to save any need for complex display conversions. cheers, Aus

Hmmmm...why not get the 1210 (or other unit) to perfectly time the gun shot, instead of teaching humans their failings? Seems a little roundabout to me.

In my use of modbus devices, I've never encountered this. All of them never mention hex numbers in their manuals for register work. If you do have a lot to work with for some reason, do an excel sheet that does the conversion for you. It's not hard.....HEX2DEC etc cheers, Aus

And now one for today's world..... Not so light hearted, but well worth a show.

Later Edit: I thought this was in Visilogic's area. Tired...sorry. But in some ways the fundamental idea might work for Uni. I don't use PID, but perhaps simply running the output through an intermediary MI that is stored, I would think that you could get a very close thing to what is wanted. Perhaps even holding the previous MI output value for a little while on restart until things stabilise a bit at around the stored output. I know this is my "simplified non-user" impression, but it might be worth a try. On the other hand, I might be talking absolute nonsense! cheers, Aus

In all of this have you ever consulted the various Help files, which show in detail how to do everything you've asked?

Looking at Merle's other posts I think you're right. Not enough initial info, and perhaps should have been started in the Unilogic software area.

Help...... Then...

For the moment with what you are trying achieve, I would not be using Version Swapper at all. If possible, try what Saragani has given you on a completely new installation of Visilogic 9.8.96 on a PC that has not had any Visilogic installation at all, or one where all Visilogic references (including version swapper etc) have been completely uninstalled using something like Revo Uninstaller or similar. cheers, Aus