Simon
-
Posts
598 -
Joined
-
Last visited
-
Days Won
34
Content Type
Profiles
Forums
Gallery
Events
Blogs
Downloads
Articles
Media Demo
Posts posted by Simon
-
-
Firstly, I agree with your comments.
The version swapper goes part of the way to answering this, though it mainly reduces the time taken to find the right version, rather than eliminate the need to search.
If you put the swapper versions on your PC you can go through them and find the version of OS that belongs with each version of Visilogic. The firmware files are in and around the following location (example her for V1040/V1210 OS files):
C:\Program Files\Unitronics\Unitronics VisiLogic_C V931\Data\Os Vision\V1040\OS
It has been an idle fancy of mine to create a collated list, but I usually end up just going back to my swapper versions and looking it up (i have collected a few over the years).
I do what I can to counsel users on keeping backups and keeping good records of what is on site, including version information. This doesn't cover all the bases, but in many cases we find users who keep absolutely no records at all.
Going back to your specific problem, around the time of version 9.4.0 there was an update made to the on-screen keypad images for the V1040/V1210. Advice at the time was to download a blank project during the upgrade sequence, to ensure that the PLC received a copy of the new images. I can't remember the exact sequence. I think if you also do a "build all" of your project before downloading in 9.4.0 it also helps.
I think this was mentioned in the "What's New" section of the Visilogic 9.4.0 helpfile.
This post has been full of vague comments, but I hope at least some of it has been helpful.
-
Hi,
Since you haven't yet purchased the PLC, I would suggest looking at the V130. They are a newer generation unit and should compare well on price with the V120. For example the V130-33-TR20 is equivalent to the V120-22-R1. If you want the higher resolution of 12 or 14-bit on the analogue signal, you can go to the V130-33-TRA22.
Even a pinhole should lose pressure at 5psi, its just the timeframe that will vary depending on hole size. A higher resolution will let you detect smaller leaks in a shorter time. Take a look at price difference between the TR20 and the TRA22 and buy the higher resolution unit if you can.
If you want to hedge, I would suggest possibly purchasing the transducer first and using an analogue meter to measure the pressure drop for different sized holes.
As for defining the test, write out the logic in steps, like:
* check bottle in position
* extend plunger to bottle mouth
* open air valve,
* when bottle at test pressure close air valve
* measure starting pressure
* start timer
* when timer expires measure ending pressure
* calculate pressure loss
* determine pass/fail.
*... and so on....
By defining the sequence well at the start, you have the best chance of setting up the program structure to suit the application. If you start out with the wrong program structure, it can be difficult to "bend" it into the final shape you want. However, even with all the best planning, and especially if you are starting out, you may find that once you get the machine working, it is best to rewrite the program from scratch, to include all the lessons learnt by doing it the first time.
-
looks like an error on the webpage, IMHO.
-
From that example you have highlighted one of the common errors that gets made with Vectors. Make sure you know where your vectors are and don't accidentally allocate them to something else.
Visilogic doesn't automaticlly mark vectors as "in use" so I usually type a description for each operand in the vector. You can highlight a range and the system will name all of them together. This will then mark them as "in use".
-
A vector is a group of consecutive registers (usually MI values in Unitronics). In J1939 the data area is usually 8 bytes long, so the vector is going to be 4 consecutive MI values (eg MI10, MI11, MI12 and MI13. The vector is addressed by using the first element (MI10) and the length (4).
By changing the data in this vector, you change the information that is being sent when you trigger the PGN send operation.
Since the SPNs can be any length, you may have some work to do when converting the 8 bytes of PGN to and from the individual SPN values it contains.
-
I recall this being the case going right back to when the on-board USB port was first introduced. I think I said similar things to you at the time - a more elegant failure mode would be nice. I get caught out from time to time, but generally I remember to stop online monitoring before unplugging the PLC.
-
When I first saw this I said "huh?"
But I recently ran a training course and one of the participants showed me this on his screen. In his case the laptop had a full HD screen (1920x1080, or something similar). I am pretty sure the PC was Windows 7, but not sure whether it was 32 or 64 bit.
It was still possible to edit the links and jumps, but it was an odd effect.
-
Now you mention it, I have also encountered that effect.
If the variable-length field is at the end, the situation is very simple, the system only needs to look for the ETX character in order to complete the scan.
If the variable-length field is in the middle of the string, if affects the relative position of everything that follows. So the system needs to track much more information and the string decoding becomes more complex.
That's my understanding...
-
I did something similar and at the time elected to use the M91 to trade off cost with Scan time. In more recent times, the cost difference between M91 and V130 is not as much as it used to be.
The new Jazz-2 seems to scan about as fast as the V130. However the programming is much simpler in the V130.
-
I can't say for sure, but I would not expect the string manipulation logic to significantly increase scan time. That is based on the example strings you have shown above. String manipulation is usually just simple searches and block data moves. This usually happens pretty quickly.
As Joe suggests, if the string has no floating point decimals, and generally can be captured by a relatively small number of different length templates, then using the method I suggest should save you lots of time on writing and debugging the program. String manipulation is more universal, but also requires more effort to write and test.
-
It depends how many variations you are looking for. If you have for example a range of 1 digit to 5 digits you can create 5 fixed-length strings, and the PLC will match the incomig message with the appropriate string. You should be able to catch the +/- sign as part of the number.
R+n<CR><LF>
.
.
.
R-nnnnn<CR><LF>
-
This should be simple - resolution is 320x240pixels. Did you use pixels or mm/inches when you refer to "dimensions"? You need to use pixels.
Once you have confirmed that the image is 320x240 pixels, re-insert into Visilogic if you have made any changes. Right click on the image in the PLC, Go to "Properties" and made sure the Left=0, Top=0, Width=320, Height=240
-
It's a bit messy but it can be done. It's much, much easier in the Vision family.
Firstly, if your bits are in Boolean registers (MB, I, O, etc) you need to convert them to MI values. Use SI170, 171, 172; SB170, 171 (search "bit convert" in the help). 3 MI values will be required.
Since the U90 Ladder only works with 16-bit values, you need to shift one word at a time and repeat it 3 times for your 40-bit value. You also need to manually carry the overflow bit from one operation to the next. That is, if you shift the first word left, you need to capture what the left-hand bit was before the shift. Then shift the second word to the left, and bring the captured value of the left hand bit from the first word and place it in the right hand bit of the second word.
I can see two ways to do this:
1. use Si87, SI88 and SB87, SB88 (see help file). These do the shifting. Then use "AND" functions with masks to test and set/reset bits
2. Use multiply/divide by 2 to shift left/right. I suspect you can only use 15 bits of each word to avoid problems with the sign bit. Use the remainder value (SI4) to carry the overflow bit to the next word, and add it on.
Once the shift is done perform the opposite conversion of MI back to MB to get your individual bits.
I hope this helps.
-
To ensure a quick response I would recommend emailing the text of your post above to support@unitronics.com
Also attach the Visilogic project file to the email if possible.
-
Following on from the previous post,
Once you get the block of 16-bits into an MI on the PLC, use the "Numeric to Bits" function from the "Vector" menu to unpack the value to 16 individual bits.
-
Reset alarm even without you see it?
Hi Emil,
I have received this request before, for reset of alarm by a method other than the HMI/keypad. The point is that there is no-one there to see the alarm in the first place, as many of these systems are remotely controlled. For example the alarm may be sent out via SMS.
If the alarm could be cleared by setting a bit, it could be done via SMS, direct digital input or SCADA system. it would be up to the system designer to ensure the appropriate procedures were in place to record and track the alarm events.
Based on some of the from Alex:
The meaning of such design is to bring REAL operator attention, and sometime keep a record who did reset/acknowledge of alarm.
This is a requirement of standards for specific industries.
It seems you have a specific industry in mind. However the restrictions imposed by this do limit the usefulness of the built-in alarms for other industries.
-
Hi Michael,
Thanks for that. It all works as you have described.
I thought I had previously tried the +/- key, but obviously not.
As for the up/down arrows, I now see that in the document that describes the differences between V120 and V130.
My suggestion would be to get this added to the help file. It has good descriptions for all the other model families, but not the V130.
I am looking at the section:
Home > HMI Displays > Display Variable Types > ASCII String
-
This seems like a simple question, but I can't find the answer.
I am looking at a customer program where the customer has attempted to use the ASCII keypad entry to enter an email address.
When I go to test the program, I see two problems:
1. The (i) button does not appear to switch between upper and lower case as it does on the V120 (and help file description).
2. The list of symbols doesn't include the "full stop"/"period"/"dot" character, for defining the domain name as in the dot in .com. Looks like this is the same on the V120.
Am I missing something obvious? Is it possible to enter a full email address on a V130 using the ASCII keypad entry variable?
My PLC is a V130-33-TA24, OS version 3.7 (B02),
(as an amusing aside, I have a label printer, and it prints a large number of symbols via several lookup tables. I searched the tables and could not find the "+" sign in all the many symbols that it can print. I eventually found the "+" sign, directly on a key all by itself, no lookup table needed...)
-
I suspect you will need to set up 3 different listening ports, 1 for each PLC.
The use of Connect and Disconnect functions implies you are using TCP.
I understand the general principles, but don't have a deep understanding of the .net code.
Even if I am wrong, setting up the 3 ports may be a valuable debugging step. I hope this helps.
-
Can you draw up a physical wiring diagram of the old relay connection as well as the new PLC connection?
The diagram may help you, or you can post it.
When it seems too simple to be wrong, sometimes the only way is to go right back to basics.
-
---| |--- ---|\|--- ---( )---
That is the logic you describe. As for pin numbers on the specific relay, you would need to draw the electrical circuit to confirm that matches your description.
-
That's a thing of beauty!
Does it use the "draw line" and do 1 pixel at a time?
-
I haven't done this before (two simultaneous slaves) but I don't see why it wouldn't work. The following should be eliminated as possible problems.
When you say "connect" do you mean the TCP Socket Connect or the Modbus polling/acknowledgement?
I would say the Network ID fields on both configurations need to be 255.
Also double-check that your two SCAN_EX blocks are attached to different configurations.
You could try enabling them each on their own, as well as together and see what happens.
Also post your code, as that will help us find the most likely issues.
-
First place to start is to confirm the type of protocol that can be used with the drive. Is it Modbus?
Then get the detailed user manuals for the drive communciations protocols.
EX-RC1 Connection problem *factory program visilogic error*
in Vision & Samba PLC + HMI Controllers & VisiLogic Software
Posted
Firstly, the best resource for Ex-RC1 programming is the following webinar:
http://www.unitronics.com/support/webinars/canbus-unican
Double-check your CAN Cable connections. Check the Power supply to the CAN cable, it should only be connected to the power supply at one end.
You say the cable is 4x1.5 - is that a dual twisted pair cable? Just a 4-conductor all-over shielded cable is not good enough. The longer the cable, the more issue that is. Ideally you should be using "Thick" Devicenet cable.