kratmel

Please read tips from this topic

On one of the machines for metal laser cutting, I was asked to make a two-channel "speedometer" for coolant flow meters. All that was needed was an indication of two frequencies. Ironically this was my first Vision PLC installation in which I did not write a single line of ladder code .... I only created one HMI display

In my opinion, this is the most accurate method of all possible in the PLC. This is because a hardware pulse counter and a hardware timer are used to obtain the resulting frequency. All other methods using ladder code, timers and even interrupts have an error related to program execution time. That's why I use this method and recommend it to you.

This topic maybe helpful Or if it not help please contact to support@unitronics.com

Test result on table with V130-33-TA24. No input and output active. Backlight =100% Downloaded blank project and no info on display ------ PS +24V Ips=76.8mA Downloaded real project with 10 subrouting and floating point calculation, no info on display ------ PS +24V Ips=92.3mA Reduce backlight from 100% to 0 % = approx -13mA in both tested project. Then downloaded code add approx 0.36W of consumption.

This is a general trend towards energy saving. By turning off the extra light bulb, we are sure that somewhere it becomes easier for the electric generator and less emissions are released into the air Probably simplifying the code to the required minimum, we unexpectedly do something similar

Please send this quastion to support@unitronics.com. In UID manual present only filter time 1 to 32ms. Then maximum frequency must be below 1000Hz.

Thanks for the work done, I liked the formula and the minimum amount of code. I analyzed the subroutine and came to the conclusion that it will not work if the PLC is simply turned on constantly (the subroutine starts with SB2, which probably should not be there). Flex mentioned this in the first post.

You must replace battery to new one and test. If it is not battery issue - you have hardware problem. It sound like one of problem from this topic

Toucn on HMI for 4-5s Info mode appear, default Password 1111.

Please try to use Info mode for test TX and RX messages in hex on HMI.

So I will try to describe in words the algorithm for solving your problem, which in my opinion should work. Therefore, the first power-up of the PLC prompts the user to determine the start date of the weekly reports (it can be started in setup). After selecting the date and time, the user says OK. Further from this date, the PLC builds a Data Table of UTC-generated weekly readings (add 24*7*3600=604800s for the next week start) for the required max operating time. (After this max time log is stopped and user must define new period). After that, we compare >= the RTC to UTC with the next Data Table week start UTC countdown and set START Pulse for the log file create and start update week events if needed. At the same time START Pulse increment a row of the Data Table, rewrite to UTC variable the following consecutive next week countdown and PLC wait for it (Then START Pulse is disabled) . When you turn off and on the PLC, for example, in three weeks later PLC will have generated three empty files and wait for the beginning of the next working week and start append some info to the last created file. It may not be a perfect solution, but it is not afraid to turn off the PLC because it works on the condition that it is between fixed UTC readings compared with RTC. I will try to ladderize it on the weekend..

State machines were probably known before the invention of the PLC. Thanks to Joe, this work of programming art has become a good tool for solving many typical PLC programming problems. At the same time, I think that an example of LadderArt is a piece of code presented by Joe in this topic It doesn't matter who the author of this code is. Its simplicity, self-sufficiency and usefulness for forum users are important. Flex formulated a good task, it interested me and probably many users of the forum. Apparently, the solution to this problem can also become a work of art, regardless of who finds this solution.

Moved.... Some info from forum topics...

I also think so. The solution of the problem set in the topic does not lie in the plane of programming, but in the plane of error-free recognition the moment of week change in case of random disturbances.

Analyzing your proposed new terms, I will try to logically continue the idea and add a new term - Ladderart. Small tree (ladderrise) - should be cared for and watered. Mature tree (ladderage) - self-sufficient and fruitful. A product of art made of wood (ladderart) is something that will not change for a long time and will benefit everyone who looks at it. Probably a little too much philosophy ... But here on the forum I have already met many examples of compact, balanced and self-sufficient code in the Ladder language - Ladderart. Please correct me if I do not understand modern terminology enough.

An interesting idea of a new word, and as always in mind games, the word means that we visually represent the text of the PLC program from top to bottom. Did I understand correctly what it means - to program in the ladder language or to turn thoughts into a ladder? But I like it.

Accordingly, if you specify the week number in the year, the file will appear when the week number is changed. That is, the week number can be used to identify two or more consecutive weeks, even if the PLC does not turn on for a week, a month or more.

Please clarify the task. Should the event be run during the day (or at a specific time) on a specific day of the week? Does the event have to take place the next day if this programmed day (days) has passed but the PLC has been switched off? Should the event fire once if the PLC was turned off several times during the selected day? Perhaps a few more conditions need to be clarified. I think in the Visilogic Help example V350_Week_of_the_Year_Calculation.vlp it is a good idea to use the even and odd weeks of the year as a reason to change the bit you need at the beginning of the week. Although perhaps my assumption is wrong. There may be a problem with the New Year's transition.

Hi, please post ASDA A2 name plate foto or full model code. Only one model number type support CANopen (last model name character M). https://www.automatedpt.com/wp-content/uploads/2012/06/ASDA-A2-User-Manual.pdf p.1.4

Hi. I was trying to simulate your problem on my PLC. Unfortunately, I could not find a way to identify the projects recorded in the log list of the PLC. Therefore, in my opinion, the best way to identify is the exact time of loading the project into the PLC. Each version of the project you have has a Signature log table in the Unilogic Tools menu. Then in the Unistream you can find load time

Hi. I've reviewed the documentation for your sensor and the Unistream I / O module you have. I must emphasize that the temperature inputs can be used only in the mV mode in the range of -70mV----+70mV (or use separate passive temperature sensor). Your sensor has 10mV per 1 degree so you can only see +7 degrees maximum at this input regardless of the settings. My recommendations - connect the output of the 0-1V temperature sensor to the second analog input in 0-10V mode. It has a 14-bit resolution and you can easily calculate the limits of temperature change with the help of a linearization FB.

Hi, In Unilogic you can download an example from Unitronics and find the Communication folder. Please use the aperiodic Modbus master as an example. You can find a bit array in a tag, but you can also create a tag with the required array of voltage or current variables. As I saw from your photos, you read each variable at a separate address. Which at low transmission speeds significantly slows down the process. The Modbus communication standard provides the ability to read many variables whose addresses are sequentially starting from a specific specified starting address. Unfortunately, I do not have a device similar to your device to try to do. Maybe someone from the forum tried to do it in Unistream. I did things like that in Visilogic, but there was a slightly different approach to working with the Modbus network.

Hi, as I thought - the addresses of the registers you need to read are nearby. I don't know if your meter supports sequential reading of a number of registers by one command. Therefore, I advise you to try to use an array of registers instead of one in the Unistream settings - for example 3 in the voltage read command. If you manage to perform such a trick, you will need significantly fewer consecutive commands from all devices to read your parameters. Probably faster to transfer a lot of apples in the basket than to send them one by one.

Hi, i see that you can handle the task. If it possible - please post meter name plate or model number. There may be a way to read a lot of data in one command.