Flex727
-
Posts
3,325 -
Joined
-
Last visited
-
Days Won
241
Content Type
Profiles
Forums
Gallery
Events
Blogs
Downloads
Articles
Media Demo
Posts posted by Flex727
-
-
I don't use this feature so I may not be of much help, however, did you check the basics? Has the SD card been formatted with the Unitronics SD card utility? Is SB 217 turned on with the SD card inserted? Is the html file in the correct folder?
Also, what capacity is the SD card?
-
Why did you update the PC software?
2 hours ago, bobnorway said:plc control is serious business! Damaging the customers production line costs money!
Totally agree with this. That's why I ALWAYS maintain the same version programming software as used in the installed system unless there is some overwhelming necessity for updating, in which case I will be prepared for all the machinations required to update the PLC.
-
By the way, standard programming loops (and GOTOs) are very poor practice in PLCs using Ladder Logic. A mistake could trigger the Watchdog Timer and halt your program. It's much better to use a State Machine instead.
-
Is there some reason something simple like this won't work for you?
Substitute the Exit Loop bit for whatever conveniently exits your loop.
-
I split this off to the appropriate forum.
-
@Joe Tauser, were you ever able to solve this issue?
-
According to the Technical Spec sheet, that is an error code that means the input is greatly above the input range (i.e. it's measuring greatly above 20mA on the input). Check your wiring and make sure the connections are correct and there isn't a short.
You don't mention the minus side of the power supply. It should be connected to the common terminal of the analog input.
-
Desktop (about 7 years old): Windows 7 64-bit, Intel CPU i5-3330 @ 3.00GHz, 8 GB RAM, and a 512 GB SSD for the main drive. Graphics is on-board since my video card died, which I haven't replaced since the system is pretty old and will be replaced soon.
Laptop (<1 year old): Windows 10 64-bit, Intel CPU i5-8250U @ 1.6GHz, 8 GB RAM, and a 1TB SSD. On-board graphics.
The slow graphics in VisiLogic is virtually identical between the two systems (7+ seconds to deselect elements by clicking on a blank area). This astonishes me.
-
This could be either hardware or software. On the off chance it's software, try the following:
- Make sure you have a copy of the VisiLogic project running on the PLC on your PC or laptop.
- Load a BLANK project into the PLC.
- Perform Initialize & Reset on the PLC.
- Re-load your original project.
If this doesn't fix the problem and you are able to see the boot text clearly, search this forum for additional help regarding firmware, etc.
-
I split this comment off to a more appropriate topic and forum.
-
I checked the RAM issue on my laptop. Same amount of RAM, but not maxed out there. The only reason it's maxed out on my desktop is that it rarely gets rebooted and there's a dozen different instances of Chrome, each with multiple tabs, Outlook, Excel, Acrobat, etc, all running. The laptop was freshly booted and was only running VisiLogic. The deselect on the same project file also took over 7 seconds and neither CPU, RAM usage, nor disk activity rose substantially.
I'm at a loss.
-
This is my desktop running Windows 7. The CPU is an Intel i5-3330 @ 3.00GHz, 8 GB RAM, and a 512 GB SSD for the main drive. There is only 1 processor core.
I checked on my laptop, which is brand new and running Windows 10. It has an Intel i5-8250U @ 1.6GHz, 8 GB RAM, and a 1TB SSD. There is only one processor core on this machine as well. It does exactly the same thing - takes over 7 seconds to deselect elements on the HMI.
The RAM seems to be nearly maxed out when I check. Maybe that's the issue.
-
Is it just that I have a relatively slow computer, or is handling complex HMI screens with 9.8.80 just extraordinarily excruciating? If you fill up a V1210 screen with many elements, then selecting and deselecting elements can take a very long time (I timed it - a full 7 seconds each time). Also, if you have a few elements selected and try to select a different few elements, it won't let you - it will deselect all of them (after waiting 7 seconds). Same thing with trying to move many elements simultaneously - elements get deselected (or lose focus) each time they are moved.
Building a complex HMI screen can take many frustrating hours waiting for elements to select and deselect. I'm at my wits end with this. It was not this bad with previous versions.
-
I don't remember off the top of my head all the differences between the JZ10 and JZ20, but I'm fairly sure you can simply change the PLC model to the JZ20 in the hardware configuration of the program and it will work fine.
-
Think about what an actual integral is. You take the curve and slice it up in small pieces and the area under the curve is the sum of the areas of the rectangles created as the widths approach zero. You can fairly accurately approximate this by determining the minimum time slice needed where you have little variation in the analog input (typically 100ms to 1 sec). I'll use 1 sec for this example. If you take your flow rate value (liters/hr) and divide by 3600, then you have the volume that flowed in 1 second. Sum that number every second to give a continuous volume.
One thing to be cautious of is that your initial flow rate number be large enough so that you don't lose resolution by dividing by 3600. To prevent that, do your linearization to about 3 decimal places (i.e. if your flow sensor were 0-100 liters/hr, then linearize to 0-100,000 instead of 0-100 - this provides an implied 3 decimals of precision that you can use if need be or drop off your final value by dividing the final number by 1000).
-
1
-
-
Try re-activating the PID Configuration FB.
-
For Holding Registers, add 40,001 to the MI address in VisiLogic. In other words, if you're trying to read MI 123, the Holding Register read address in Ignition should be 40124.
-
Moved to the correct forum.
-
1
-
-
I know from experience that the Ignition software will work with a V1210 using MODBUS TCP. I don't see anything in your posts where you show the register addresses you're trying to read.
-
On 8/30/2019 at 6:01 PM, Ausman said:
Are you in a train full of women with weird hats
Whenever possible.
-
Nice! I love the V700!
-
@Ausman, is this what the world maps look like in Australia?
-
There are good examples that came with your VisiLogic installation that will show you how to communicate. It's pretty simple.
-
There are any number of ways to do this, but they all involve some sort of communications. If the PLCs have Ethernet cards, or you are willing to purchase and install them, then the easiest way would probably be MODBUS IP. I think both of these PLCs have CANbus ports, so you could run CANbus wiring between them and communicate that way. You could also use serial communications.
Update 1.25 to 1.28
in UniLogic Software
Posted
This is not true. Right now I have 13 versions of VisiLogic and 8 versions of UniLogic installed on my PC. I switch between them with ease.
With VisiLogic, you have to use Version Swapper, which takes about 5-7 seconds. With UniLogic, it's only a matter of clicking the correct shortcut for the version I want to run.