Ausman

I'm sure Flex is on the right track, but if not, then I would also be trying something really off field. And also keep it in mind forever as well. W10 has dropped many abilities in the Compatibility settings, and I had similar nightmares on a heap of older ( and not so old ) programs in getting them to display things correctly. Really dumb stuff like some, but not all, control buttons in my CAD program appearing upside down, sideways or not there at all! The solution is that the missing controls still work, you just have to do registry entries to make it so...another case of "the genius gang at Msoft has done it again!!" In my case, the relevant thing that no longer appears in W10 was "Disable visual themes". The registry entry is this, but note that I have simply pasted my reg entry for my program here, only slightly modified it, so it will need to be tweaked for your instance of Remote Access......or whatever other program you might need it for in the future: [HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers] "C:\\Program Files\\*****Master folder name if there is one*****\\******Second folder name if there is one etc etc*****\\name of exe.exe"="~^ DISABLETHEMES DISABLEDWM RUNASADMIN WIN98 " The C path needs to be correct. If you have already done a compatibility setting then you will likely find an entry here already. You just need to add in the DisableThemes bit. Note in my example the other controls that I have in place as well.....run as admin, as W98 etc. If you get this right, and it is indeed the problem, magically everything will come back to normal. It is simply amazing to see it happen from such a small registry entry, when you have been lead to believe that all your expensive programs have been reduced to pieces of garbage....and you need to update....often to something that doesn't do your particular job anywhere near as well. cheers, Aus

Hi Kratmel, Denis's idea is good, but I am also a little confused on what is being wanted. If the need is simply to measure the length of time the power has been off, and not actually do anything else, you could easily implement this using UTC. Store the current RTC to UTC reading every second. Have a power up bit that activates a subroutine that compares the current UTC to your stored one, does maths that then displays results on a screen that tells you both the delay time and also flash an alert if it is over 15 minutes. Or have a routine that always compares current UTC to the stored one, and if it goes over, or gets close etc does the same alert system. But without things being dependent on a power-up. cheers, Aus

We could always make this a little competition, with people throwing in their theories. 🧐 Those who actually know could wait a week and then tell us. No cheating, Joe T! So here's my first 2 ....."Unifying different control lines into one coherent stream?" "I can't wait for the clock to get to the white zone so I can have a break." cheers, Aus

So....Isak....you've run out of things to do? 😀 cheers, Aus

That's fine, Wa.... Simulators are nice, but all the ones I have encountered can never fully imitate the real world conditions I work in, so a real plc is always best. And I often have to leave fine tuning until a site is complete, due to the myriad things involved in getting a program right. Unitronics in your case is like a TV program, if you don't like it, turn it off. However, don't necessarily can a product you don't like on first impressions, until you've learnt a lot about it and how to use everything properly. This is called a learning curve. If you buy a top of the line Mercedes/Porsche etc after only riding a bike, do you expect to know how to use all it's features without learning a whole heap of stuff from the manual? No. And you are showing your obvious ignorance through claiming that Unistream and Visilogic are the same in your I4.0 post. They are vastly different animals. The forum welcomes informed discussion and offers a very large knowledge base to those who want to use it. To those who don't.....have a nice day and goodbye. cheers, Aus

Changed for new, or tried one of the others known good? Ensure that all the plugs, cables and sockets connecting the expansion modules are fully in place and in good condition. Do continuity checks on all the connections from source to destination. cheers, Aus

Any multiple register read I put into a vector of MIs, and then pick out the ones I want to work with by using the store function to put them into other MIs, or put them in a data table. What I also do during this transition is have a +/- addition going on, that lets me fine tune readings to my external master, be it pressure, temp etc. I try to never adjust a sending device direct. cheers, Aus

+1 to Kratmels suggestions. Also, I know someone who had a weird issue and the cell was connected incorrectly, back to front I recall. Was miles away in the bush, and he picked up the error looking at photos sent to him. Don't know the full ins and outs, though, just that it was a wrong connection. cheers, Olfa

Uhmmm. Not being picky, but doesn't getting 200mm out of 1000 counts mean that 1 count = 0.2mm , and subsequent maths should be based on that. You look like you've got the target correct, Visco, just a little bit more coffee needed on the other relationship. 😉 Other MLs immediately storing the encoder's current count can be used and manipulated, thus not upsetting the main encoder count at all. cheers, Aus

I understand the situation, and I could be wrong but it's likely that earlier versions of RO will work ok on later O/Ss. edit: But there might be issues with the program not knowing about the latest plc versions and how to display them. There would possibly be nothing wrong with you using an early version, thus getting around the issue. And if you don't have a copy, you could ask here for what version you want. cheers, Aus

So Joe, are you saying I'm old 'cause I've got lots of those? 😀 As soon as I read your suggestion I was cursing that that thought hadn't popped into my brain. Maybe the old grey matter was simply thinking along the lines of a hub anyway, forgetting "modern" progress. cheers, Aus

And my brain has obviously pondered this all day, because tonight up popped this other idea. (thanks so very much for keeping my brain active!) Further to your "Just as an update", I think you should try running everything through a router, which might give you better control and monitoring to ensure that the Samba is indeed correctly on the network. Or simply wait for someone who actually knows the full details to post their secrets! But it might be a long wait. cheers, Aus

Kratmel, SB314 is the same for 130s. Whenever I have no comms it is one of the first things I check, but in this case I dismissed it given the problem's description. But it would be worthwhile for CRPLC to actually check it via info mode...just to make sure it is OFF and, as you say, it hasn't been accidentally set to ON. cheers, AUs

Do you have another puter you can try things on that has a native 232 port? And I've assumed all along that the plc doesn't have an ethernet card. If it does, use that instead. cheers, Aus

You say that you have 2 cards. So perhaps your correct layout should be with the PC purely acting as a pass through, with shark monitoring the line. I was thinking that you might need another card, but when re-reading your post saw that you already have one on board. And another thought, perhaps all you need might be obvious if you monitor comms using serial. In theory the contents of packets would be vaguely similar and you might be able to combine this with other methods you are already using that you know works. cheers, Aus

It appears that you are using a usb to serial adapter. The port settings that info mode is showing should work ok, so the only other thing that might be sus is........ Is the adapter showing correctly in device manager when you plug it into the usb port? Ensure that the com settings everywhere......device manager, Visilogic match perfectly to what is needed, sometimes this cures isses. And ensure that you haven't accidentally changed the comm type in Visi itself...you should be using Serial on whatever port it shows up at. Hmmmm. perhaps that is the issue. Wondering if something has upset the port numbering so Visi is now trying on the wrong port. Ensure that the port number showing in Device Manager is the one in your Visi comms settings. If that doesn't work, I'd uninstall the usb adapter completely.....take out the drivers too, and then reinstall it in the correct order it says to with the drivers it came with. cheers, Aus

Hmmmm. Ensure your A/V isn't blocking anything. Try using a crossover cable on your first method to eliminate the switch. I can't see that will help, but perhaps worth a try. Further thinking needed. Seemed like a good idea, but I knew it might be hard to do! It does sound like some crucial bit of info is being stopped somewhere along the route. cheers, Aus

One way that I could see you getting an idea of what you need would be for you to actually write a small program that uses one of your Sambas as a Master to use the Read from Data Table FB. Once you have that in place (and obviously with a bit of extra cabling) run the FB whilst using a monitor on the line to see what is actually being said b/n the Master and the interrogated Slave. Something like SmartSniff etc might do the job. Whether it will translate easily is the unknown, but it will at least give you a fairly definite starting point. cheers, Aus

No. I tried pinky-click all over the place and I get your result. Sorry about the wrong comment selection. I can open a scroll command box, I can open the font format etc, but I can't make the comment space any bigger either, and I spent 10 minutes hunting around playing "find the hidden control". It looks like a bug to me, as the thing on the RHS looks like the top of a scroll bar that I assume is meant to be showing completely when you choose to see a comment. Perhaps the creators think that hovering is the best way to see the full comment...that works, but is a bit impractical. cheers, Aus

One of my main issues is W10 repeatedly changing my "do not update my drivers" setting to "let us stuff up your system by changing your drivers because you have now unticked the box that stops this happening...even though we actually unticked it for you without telling you". It is so bad that on one system they even change a whole lot of gpedit settings to enable this to happen. So I have to be careful every major update to ensure all of these settings get changed back to what I have set before enough time goes by that they can do it again and make the system unbootable. I can't use WinAero on this system to stop updates happening......"security!" It's a bit like your car service guys filling your petrol vehicle's tank with diesel during a routine service. After it comes back from them you have to drain the tank, flush the lines, refill with petrol and then crank it all up and check things! Just to make your car runs correctly again. And all at your time and expense, even though they charged you for the work they did. cheers, Aus

For a less sophisticated version of what Joe is talking about, forget the word "timers" completely. I think him saying "combination of a timer incrementing a pointer" is essentially referring to what I call a counter being incremented by 1 every time cycle. I often mention that in many instances counter based systems are the much forgotten/ignored method that is a much better solution than a combination of timers, due to their simplicity of making outputs do whatever you want at a certain time......but for "time" read "a section of the count". For the less sophisticated method, use compares that set your outputs on when they fall in range on the numbers coming up as the counter is running. Once everything is on, stop the counter at that point but don't reset it. To shut down, start the counter again and the outputs are shut down progressively as the compares do their stuff. Once everything is finished, you stop the counter and reset it either at the stop or the next start signal. Accuracy needed dictates what you use as your timer that increments the counter. cheers, Aus

Hi Joe, As I'm not really into Unilogic, I only have 1.18.60 on my system for occasional playing around. It appears to handle comments fine. See attachments. It will automatically roll into another line and open a scroll bar if necessary. I was simply playing galloping horses on the keyboard. Same thing but with the ladder area widened. Wondering if it might be another hiccouph in the new release? Incidentally, and probably another topic, I was intrigued that I couldn't open my simple test program if I clanged the Unitronics.Notifier.exe after program open but before opening the ulpr. What exactly does this part of Unilogic do? Hmmm?!! cheers, Aus

You're forgiven! But it really depends on how you view the screen...if you're the screen looking out it is on the right! 🤪 cheers, Aus

Try Stemberra's suggestion before doing my full reset....which is a little akin to reinstalling Windows! But not too hard and time consuming. Just making sure that you fully understood this. You have no com init in your program at all? It still sounds to me like you have something in your program that is altering the com port settings. cheers, Aus

Have you tried other cables? (the first thing to try.....you wouldn't believe the coincidences and subsequent frustrations that happen with a cable failure!!) Did your program change anything relating to the com port? What is the com port showing in info mode? Can you access it at all in boot mode? Have you tried doing a full reset of the plc using info mode and then loaded your original progam back in after doing everything else needed? cheers, Aus