Damian
-
Posts
534 -
Joined
-
Last visited
-
Days Won
13
Content Type
Profiles
Forums
Gallery
Events
Blogs
Downloads
Articles
Media Demo
Posts posted by Damian
-
-
Hi Damian
I'm running on Windows 7 64bit and had a few crashes with VisiLogic 9.3. Haven't had any trouble with VisiLogic 9.3.1 though, and no slow downs on any version. What anti virus are you using?
Thanks for the feedback.
My system is a Dell Precision M6500 with core i7 & 8GB ram, Windows 7 Ultimate 64bit
Also have a SSD, not sure if it is relevant but if it was I wouldn't expect different behavior within the VM.
I am running Kaspersky Internet Security 11.0.1.400. It was the first place I looked when the problem occured. Turning it off had no effect.
The slowness is sporadic, but once it shows up it never just clears up.
It is most noticeable when doing communications related activities, and doing File Save/Open types of things.
It also happens often when selecting different subroutines or HMI screens, or inside the HW configuration.
If I am just building ladder, I rarely see it when I am actually drawing the logic. Only occasionally when I highlight a new network it will go to sleep for a spell.
-
Hi Damian,
I've been running Visilogic under an XP virtual machine for a year now, under Linux and Win7 hosts:
http://forum.unitron...age__mode__show
I've not had the problem you describe. Are you using vmware or virtualbox?
TM
Hi Tim,
Windows 7 actually has a built in virtual machine, so I am not using VMware or Virtual Box. The attractive part about the built in version is that you get a "free" XP liscense/install whereas VMware and the others require you to install a purchased copy of XP. I have read, and enjoyed your blog on using VMWare, and actually will be giving it a try eventually as it appears to be much easier to back up than the built in Microsoft version.
I am really getting frustrated with the odd behavior of Visilogic under Windows 7 64bit. I am suprised that nobody else has been making noise about it. It would be nice to compare systems with someone who is to help possibly indentify the root cause. Since it works in the VM, I can't justify the expense in time trying to work out the Win7 issue.
Thanks,
Damian
-
"Thats true -- but as long as i have no idea of how to work with indirect addressing -- i must make it like this."
The amount of time you would spend doing it long hand will easily exceed learning how to use indirect addressing.
With the 64 HMI variable limit, I don't see that you have any choice either.
Instead of having 30 screens, you only need 1.
You will have one set of variables as "buffers" for your data.
These are the ones you will view on your one screen.
You will have another variable as the index.
Therefore, instead of Screen # 15, you will instead have index 15 as a selection.
Allow them to scroll the index on the screen. Everytime the index changes, it loads the values from the MI table into the buffer.
Everytime they change a a value in the buffer, it then copies those values into the MI table.
You have 256 MIs to work with. That should be enough.
You are better off not using "timers", just base everything off the clock.
Read the HELP on the Store Indirect MI function.
Read the HELP on the Indirect Clock Functions.
Unfortunately the U90 does ont appear to allow you to do Indirect bit addressing. Maybe someone else here can correct me if I am wrong. Either way, I don't think you need to.
The instruction set for U90 is very limited. If this is just a one-up job I would highly recommend bumping up to a vision series controller. The amount of time it will save you in coding will be large. Then you have access to data tables and much more advanced features to save you time.
"My question was if it is possible to change a MB direct -- cause if i choose MB i can only display this Bit but not write into this MB."
Yes, The same way you did the MIs.
That is my plan, i want to compare the RTC with the MI's where i saved the entered times. --- but i do not know how to solve this problem in real programming.
if the result is true, i will switch on my mixer for a defined time"
You will just have to experiment with the Comparators to get a feel for how they operate.
You have a Start time and a Duration. You will have to have one comparator go true for the on time and go false for the off time.
You will have to calculate the off time as OFF TIME = START TIME + DURATION
"So i must make a Variable as MI (Limit: 1) than mask out the last Bit and compare it with #1 and than save this result in a MB.
Than i combine this MB with my MB-Mixer-ON with a &-Funktion.
I can only use Integers in a compare-Funktion and only Bits in a &-Funktion"
Not really following you here. I don't see why this would be necessary.
Good Luck,
-
Alright, now i am experiencing all the same issues with the U90 software as well.
They must both be using some driver/library/function that is conflicting with something else on Win7.
-
Agree with Joe and Emil.
If you have to do it 138 times.................. write it once, debug it once.
You can use indirect addressing to carefully organized operand ranges, or data tables.
With 138 operations, the data tables might be a little slow, but would be easier to deal with.
If you have a lot of timers, you might want to build your own based of the internal clocks rather than the built in timers.
-
I have resorted to running Visilogic in an XP virtual machine because it is simply unusable under Windows 7 64 bit.
For anyone else who may also want to run Visilogic within the XP virtual machine built into Win7, after installing you may notice that your Visilogic screens may appear garbled. This is because XP mode defaults to 16 bit color mode.
If you go to the windows properties and attempt to change the screen settings to 32 bit, you will notice that only 16bit shows as available.
You must first go up to tools and select "Disable Integration Features".
Then go back to configuration and you will now find that 32bit color is now an option.
Unfortunately you will not be able to re-enable integration features and retain the 32 bit color mode, but it is not necessary for running Visilogic as long as you are communicating over Ethernet or and USB to Serial converter.
-
Another matter of interest.
Running Visilogic in an XP virtual machine on the same computer and it performs normally. It is faster in the virtual machine than the machine itself.
-
Visilogic under windows 7 has now slowed to such an immense crawl that it is uterly unusable.
I can click on "save" and literally wait over two minutes before the window will pop up to ask me for a file name.
I can click on "download" and it will literally be 5+ minutes before it actually starts downloading.
Uninstalling and Installing 9.3.1 had no effect, or it may actually be worse.
I can't be the only one experiencing this can I? The PC I am using is a beast, so there is not reason for ill performance. There is some kind of conflict going on here.
-
Welcome to the forum!
To start with, it would help greatly to state the part number and model of the unit you are using.
There are features that vary from one to the next.
Rather than do this with 30 screens, you may want to seriously consider utilizing indirect addressing and only building a couple screens.
It would be a lot less work, and also a lot less code overall.
You should also consider, instead of using indivdual timers, to either just base it off of the clock and comparators, or base it off of one timer and comparators.
This also would cut down on the code.
Yes, you can enter integers on the screen.
You need to create variable links under HMI>Variables, to associate a variable number with a memory area.
You can then "right click" on the screen view and hit attach variable.
When you create your variables, you define what that variable is under Variable type. (You can make it a BIT, or Integer, or Date,Time, etc)
-
I have had the same error in the past, and in my instance it was EMI related due to some grounding issues.
Try going through the published Unitronics document regarding EMI and the measures to take to minimize its effect.
You can download it at the very bottom of this link
http://www.unitronics.com/Content.aspx?page=Technical_Library
It can also generate that error with a bad connection on the snap in IO and well as a bad connection to expansion IO.
The unfortunate thing is there are many different things that can cause that same exact error. It is best to just start with the most likely and address them one at a time until you rule them out.
-
A little hard to understand your problem.
Just a guess, are you using transitions to call your screens and functions?
It will be easier if you post your code.
-
The Unitronics will recognize a larger SD, but remember that the largest size file that is supported under windows is 4 Gig, so after that you need to create a new file.
Hi TM, thanks for the correction on the SD card and the Unitronics.
On a side note......
Isn't the 4Gig thing more to do with FAT32 than windows? I have plenty of files in windows over 4GB in size under NTFS. My outlooking.pst file being the largest.
-
I am trying to create a project and I am running into a few roadblocks. I need to record a pressure every 2mS and record it to the SD card. I have a 16GB card so I should be able to record a ton of data, all I need to record is a 4-digit MI value. My problem is writing the data to the SD card. What is the best way to do this?
Currently I am trying to do it in pulses. Step 1) for the first 5sec I record my value every 2mS with an indirect store. Step 2) for the next 25sec I want to write this vector of values to the SD card. Step 3) Rinse and repeat.
What would be the best way to record tthe vector to the SD card?
Someone may correct me if I am wrong, but I think 4GB is the largest SD memory that the Unitronics will recognize. So even with a 16gig card your still bumping into that 4gig limit.
2mS is pretty fast. What is your scan time? What OPLC are you using? You probably want something with the fastest CPU like the V570.
Does your 2mS need to be precise, or can you cope with just sampling it every scan?
One trick you can do to keep things linear is to use the interval timer to time stamp the interval between each sample. This way when you chart things out in for example excel you can plot against your time interval axis.
Also leep in mind, at 2mS the instrumention and the electronics reading that instrumentation is probably not fast enough to be giving you realistic data at that rate. Depending on what hardware you are using to read the values in (I am assuming analog) the unitronics modules all have varying degrees of update rates from one product to the next. Before you go too fat down the programming path you may wish to verify that your hardware is capable of the response times you require.
-
My appologies. It is the slave that is causing the issue. If I power the V120 with 12VDC and power the slave with 24VDC everything works fine.
-
I am using a V120-22-T2C.
It is communicating on Comm2 by way of RS485 to a single slave.
The distance is very short (less than a foot) and terminating resistors are enabled on both ends.
It has been working fine (flawlessly) on 24vdc. I had to switch to 12Vdc power, and now the comms will not work.
Even if I put it back on the same power supply, an go off the 12VDC taps instead of the 24VDC taps, it will not communicate. It only works properly on 24VDC.
Why will the RS485 not function properly on 12VDC?
-
I update the OS over the Ethernet port all the time. It is much faster. This should not have been causing you problems.
How old is the unit you are updating?
-
Nacho, Thank you.
At the moment I am trying to scarf up some hardware to test with. My M90 only has one serial port.
-
In Visilogic, go to
Help>>Check For Updates>>Operating System.
Hit OK and allow Visilogic to update its OS files.
Hopefully if your OS files were corrupted this will take care of it.
Now go to
Connection>>Communication&OS>>{click the fourth tab from the left that looks like a fiery eyeball}
Assuming you are conneted and communicating, Hit check, and then hit download.
Let it do its thing
-
Here's a program with the SMS table configured. I don't have the hardware here right now to test it.
MB 1 triggers the send. MB 2 "should" come on when it receives the reply. You'll want the read the Help on Com Port->Jazz series to use special function 310 to get the port parameters the way you want them. You'll also want to read all the SMS Help topics. I learned many moons ago that SMS allows us to control the com port - just leave the "Use GSM Modem" unchecked.
This program automatically converts the incoming stream to a number. This may or may not work for what you're trying to do.
Good luck. Let me know if I need to bring some hardware home to bang on it some more.
Joe T.
Hi Joe,
Thanks for the direction. I'll play around with it and let you know how I am making out.
Damian
-
Damian,
Post a sample of the string this thing spits out.
Joe T.
Hi Joe,
Attached is the V120 program I would like to mimic. The overall goal is to use the smallest size controller.
-
Argh!!!!!!!!!!!!!!
Until now I have always assumed that this utility actually worked with all PLCs.
Just tried it on two V570 programs and
Ouch!! Your not really going to make me go through each and every network of two fairly large programs to find the differences are you?
Is anyone working on this, or has it been scuttled?
As far as the ladder, why is it so much harder to compare enhanced models than it is standard models? Seem practically the same other than the X operands.
-
In this particular case, I would be talking to a SunX sensor via RS232 using a proprietary ASCII protocol. I would need to be able to parse the incoming characters, sort out the data, and convert to numeric.
I have a working program for it on a V120, but the unit is physically too large. I may have to use a microcontroller or BASIC stamp.
It is not clear to me how I could accomplish the same thing in U90.
-
Do any of the Jazz controllers support ASCII communication?
-
Dairy maid! Not the Dairy Queen!?
Visilogic in XP virtual machine on Win 7 machine
in Vision & Samba PLC + HMI Controllers & VisiLogic Software
Posted
Hi TM,
The only reason Mircosoft packaged the XP VM in Win 7 was to attenuate peoples fears of backwards compatibilites. So far the only glitches I have not been able to overcome are getting Rockwells activation server to work properly in the VM (I am told it want's to see a client/server setup with the host, but that defeats part of the point of having the VM in the first place), and issues with Rockwells drive server and recognizing the thrid octet of the IP address properly. I look forward to giving VMWare a try, largely because the backup routine for the XP machine in Win7 is not what I would call convenient.
Thanks for all the info. Sorry to hear you had to lose the Linux.
D