Ausman

I still do it manually myself, but I thought the installer system had been changed so that this was being done automatically since a few versions ago? cheers, Aus

"soresting" I didn't quite interpret, sorry. Have one of each doing 485 comms, with the vision reporting collated data to the Unistream and being "instructed" what to send out by the Unistream. It all depends a little on what speeds are needed for monitoring all 57 units. Using both a vision and unistream should effectively halve this time against doing it with just one plc, if you are planning to only switch through them sequentially...1-57 at a fixed rate etc. Aus

It doesn't take too long to do a full partition(s) copy just in case!! You chicken...you! 😉 But I know exactly where you're coming from. It is mightily annoying having to spend (lots of) time fixing an issue that shouldn't have happened on your perfectly running, stable system. cheers, Aus

And it does seem strange that an ID of 49 cannot be changed! That is certainly an odd number to have as a "permanent" default! Have you played with it using a modbus/serial tool on the PC to see if you can do it through "unconventional" registers? I work with a few sensors that supposedly need a special program to change their defaults, but once you find the code it is easy. Sometimes there is also a locking register as well. You change that, then you can change the ID register. cheers, Aus

Hi Orso, did you have a read of this topic and my suggestion further down to perhaps incorporate V130s into the mix? You collate/send data from/to them with the Unistream as necessary. One issue that you may not be aware of is that there appears to be a problem with the 232 port operations on the 02RSC module. Using 130 (s?) might be a cheaper, and perhaps better way around the issue, and could cover the double address issue quite easily. cheers, Aus

Ohh well...there goes that theory! cheers, Aus

Joe has just replied whilst typing this. I am also just wondering whether you being on W10 is actually the culprit here. M$oft dicks about with all sorts of things so often (and without really telling you) that perhaps the blame is being incorrectly laid, and you have been subject to an update that is the real reason? @Joe Tauser, what W version were you on when you had your issues? ...from memory you are another W10 hater. And whilst I'm on the anti 10 bent again, I repeat my suggestion to all of using Winaero Tweaker to stop some W10 annoyances. cheers, Aus

I found the topic I wrote on: I don't know whether it still happens on later versions. And the question arises for bm....were you hooked into anything else on your pc ports at the time? I think it is all clutching at straws a bit, but who knows...might be helpful to pinpoint the cause. cheers, Aus

In looking for something else I stumbled on this question, and although it is old is still current and can be answered by this post and topic: cheers, Aus

I think Flex was saying to post your actual compressor control program, if you're willing, so that we can check it out ourselves. Aus

I'd perhaps be trying to get the O/S and boot back to what they were. But before that, download a simple program that will react to physical inputs and give physical outputs without any screen interaction, and see if the plc is working those responses correctly. If so, then that points to there being something fundamentally wrong with the screen. cheers, Aus

Great response, all there. The O/S update all went though OK to the very end? Perhaps pull the battery for an hour and reinsert? Shouldn't make any difference, though. Something weird going on, vot haf u done, munchkin?!! Time for thinking caps and pondering....will advise. The different boot and O/S numbers bother me....comments and research needed. cheers, Aus

Also, if you have to update the O/S and this brings up the wizard, read everything on the wizard screens very carefully before progressing to the next one.

Flex has just replied with his bit, but also ensure that when you worked on the jumpers internally that you haven't upset some other connection in the guts of the unit. And in online mode, check SB8.

These messages reek of the issue I discovered ages ago and wrote about on the forum, I've forgotten where, where Visi seemed to open the comm port for no reason at all on opening the program. Wondering if that might be the case, and the program is getting confused as to where it is meant to be doing things. Regardless...... @Cara Bereck Levy....have you read the thoughts on not having the beta prominent? cheers, Aus

You have sort of stumbled on the method that I (and others) repeatedly mention on the forum with anything involving serial comms. Monitor all comms using just your PC and the device, with a serial stream recorder of any description between the two, to initially find exactly what is going on when you do something successfully. Once you have that information you then transfer it to the plc program. It is a complete PITA trying to troubleshoot serial comms issues only using the plc. cheers, Aus

@Cara Bereck Levy Cara, given that Fotonic is having issues and that the UMI VFDs seem to be "typical" with the myriad settings available, perhaps it would be a good idea if you changed the "Quick Start" in the manual to essential fundamentals, that does good explanations of how to do a basic hookup and get the thing running in no time at all. cheers, Aus

Glad it's fixed, but that still reeks of something interfering with the linearization operation. Have you done a find on all your Linz operands to ensure there isn't one doubled up on use somewhere? In any area of the row of an operand, right click to access the find/watch menus. cheers, Aus

Have you got them in a subroutine that isn't being called? Have you done a full Initialise and Reset after downloading your PTO program? cheers, Aus

On the screen issue, in theory it can't happen with Visi not letting you do it, but sometimes it does and needs an extra pixel clearance on what Visi lets you do as minimum etc. I know this is a bit convoluted explain, but its the best I can do! cheers, Aus

Nothing wrong with 9.8.65!! I'm initially wondering if you aren't calling your reference properly, or you have it doubled up somewhere else by accident. As Cam has just said, post your code if possible. I've also seen strange things happen if there is an overlap of area on the screen. Ensure this isn't happening. cheers, Aus

Wondering if the switch position shown is a bit like some of the other plc install instructions, in that the black and white are not really well explained, so you don't really know which way is correct. Joe posted about this conundrum here: Perhaps worth a look. cheers, Aus

Agree with both of you on this re beta shouldn't be priority, but also just wondering if the file actually exists somewhere else? Have you done a system wide search for the file, or even just an extension search and see if it is anywhere else? I have had occasional instances in general windows use where a file has not been saved where I told the system to do it. This seemed to happen if there was more than one instance of explorer going on, and I also thought I was going nuts. It wasn't until I discovered the file sitting in something like My Documents etc, which I normally never use, that I started to investigate. It would appear that sometimes when windows wanted the extra explorer to run, somehow the file system got a bit out of whack. Another of those "this shouldn't happen, but it does and there is no pattern to it" type of issue. cheers, Aus

Great, Cara. And Leon....did you also try Reset Numeric as suggested? cheers, Aus

Remember me saying that VFD manuals need to be completely read! The switch settings look clear enough in this, but perhaps they are physically hard to find. Haven't handled one in the flesh. cheers, Aus