Jump to content

Meeg

Members
  • Posts

    29
  • Joined

  • Last visited

Recent Profile Visitors

1,350 profile views

Meeg's Achievements

Member

Member (2/4)

0

Reputation

  1. Thanks for your help, Saragani. And also thanks for the tip on the ladder element for Export\Import retained tags to SD. This will be a good backup of retained tags in case the battery goes low.
  2. Yes, you understand me correct. I have missed a function where i read the actual value for all (or selected) retained tags into the initial value. Then compile the code with this new values. In Siemens there is a possibility to write both initial and actual values to Excel-sheets and then compare and copy actual values with the initial values. But I have not found any similar function in Unistream. In my program I have a lot of parameters that I "tune" during commisioning, and now they are only stored with battery. This I do not feel as safe as having them as compiled code. And I am to lazy to copy by hand... 🙂 Also it would have solved my version-problem which i started this discussion with since I could have updated the initial values in the old project before upgrading.
  3. Actually, a function i have missed in Unilogic is the possibillity to update the default value in tags from the running program. Typically this would be useful for all parameters that is adjusted from the HMI-panel during commisioning, eg. controller parameters, I/O scaling etc. This will reduce the risk of problems later, typically if the battery backup fails.
  4. Yes, I can send it to you. But the file is 13MB so I guess it is easiest to do it by email. My address is anders.meeg@energi.no. Send me yours and I will forward the program.
  5. I have upgraded and downloaded the project, but then all the retained tags are set with their default value. Is it a possibility to update the default values of the retained tags with the actual values in the PLC before I upgrade? Previously (before upgrade) I have always used the function "Upload PLC retained memory to PC". This saves the values of the retain memory as a file. Then, in the new project I first have to download the PLC program, then I download the retained tags from this file to get my parameters correctly copied from the old project. This has worked fine previously, but after I upgraded the software version I am no longer able to do copy the retained tags from the old to the new PLS in this way. Do You have any other solutions to this?
  6. Hello I have a project written in version 1.25.560 that I have renamed an upgraded to 1.35.227. The program upgraded OK but when I try to download the retained tags from my old project i get the message below. My program include lots of parameters that is carefully tuned and I want to avoid to do this tuning again. Any suggestions on how I may solve this? Workarounds?
  7. Thanks. The tip regarding battery alarm was useful. I will implement that in my systems from now on. But my real problem is that my panel keeps rebooting after displaying the "Unistream" logo. This is in my development setup, and it started to do this during a period when I was not working with it. So my question is realy if there is anything I can do to recover it? Or do I have to assume it is defect and by a new one? I did find this in the forum. Rescue Procedure to recover UniStream Panels. But that procedure did not work Also i did find this: Unistream recovery to factory settings procedure I have not tried this as i do not have the MAC of the panel. Is it worth a try? If so, where should I ask to get the MAC adress ? I have the serial no.: QCR65B30082
  8. I have a system with a USP-070-B08 panel and USC-P-B10 CPU and some I/O. The system has been running fine for 5-6 years. Then it suddenly startet to infenitely reboot the panel. When the system is powered up it displays "UNISTREAM", gives a beep, flashes the ethernet LEDs and then stops before the same starts over again. Any idea on how I might fix this? I may also mention that the CPU battery has not been changed since new (5-6 years). Can this be the cause? If so, how do I get the system running again? Also, a general question; what is the consequencenses if the battery is not changed? I doubt that any of my customers will do this unless i instruct them so, which I have not done yet..
  9. So if I understand you correct: - Data Tables are not stored in the SD card before the "store to file" command is executed. - "load from file" can be used at initialisation (after Power failure) in order to recover the stored values?
  10. I have a question regarding Data Tables and the "retained" option. I have some rather large tables, to big to have them all as retained. But I still want to keep the values in case of Power failure. In your help function it is noted that Data Tables reside the SD card.. Still there is an option if they should be "retained". But is it not retained anyway if it is stored in the SD? Will they always be recovered from the SD card at power up? Or does it have to be done using the "store to file" and "load from file" functions? In my application is acceptable to store the tables periodically (once every hour or day) even if i loose the newest (unstored) data on the recovery. Also in your help function a ladder function "Initialize Data Table" is mentioned.: "In most cases, Data Tables values should be initialized after power-up (but i can not find this initialize" function). Please help me to understand the best way of doing this... ? Regards Meeg
  11. Hello, And thanks to both of you for good answers. You are obviously a lot more experienced with Modbus than I am. Unfortunately the sensors can only communicate at 9600baud. Trying aperiodic is probably a good idea. But maybe using a timer rather than the session Counter? Refer 2) below, the session counter will count even if the variable is not updated with a new value. You are reffering to UART, CPU, or ladder execution times to slow things down. To me this sounds strange as it must also be able to handle much higher baudrates and amounts of data? So what I still do not understand is: 1. If I activate communication on ONLY ONE sensor, communication works fine at 100ms. But when activating communication on TWO sensors, I need to slow the update rate to more than 500ms (it works at 600ms) to get it working. I would have expected 200-250ms. 2. Also a bit strange that at 400ms rate the "success" counter on ID2 continues to Count, and the "fail" counter does not count. But still it does not update the values read from the sensor. Did Unistream receive a value from the sensor (hence the "success") but not transfer it to the variable?
  12. Hello I am using modbus RTU Reading two sensors. Modbus ID = 1 & 2 respectively. From each sensor i read two values, one 16bit and one 32bit float. Baudrate = 9600. When I activate communication using "Active periodic" bit any one of the sensors (only) I can set my update interval at 100ms without having failures. The "funny" things occur when when i activate both: If I set my update interval at 400ms: It updates values from both sensor for a few Seconds (at 400ms rate), then it stops completely updating the reading/values from ID2. But the "success" Counter continues to count. And the values from ID1 continues to at 400ms rate. If I set my update interval at 500ms: It updates values from both sensor for a few Seconds (at 500ms rate), After a few second the ID2 values are updated at 50% rate (1s). ID1 continues to update 500ms. If I set my update interval at 1000ms: It updates values from both sensor at 1000ms without any problem. Any tips on why this happens and how to solve it? In my Application I need as fast update rates and would have thougt that beeing able to read one sensor at 100ms, I should be able to read 2 sensors at 200-250ms. Thanks for a super Product! Meeg
  13. Thanks for helping ORS! I only had the the old example projects downloaded (from V1.15). With the help from the Advanced commands in V1.19 I was able to see that the commands was OK. It turned out to be a hardware problem. The sensor (ECD DS80 conductivity sensor) was not 100% rs485 compatible so I had to turn of the resistors on the CPU and use a 1k resistor instead. By the way, do you know why it is 2 resistors on the CPU? And what size and how are the resistors connected? The CPU manual does not give any details and normally only one 150ohm is used for cable termination. Is the two resistors for "pull up" and "pull Down" so that the line termination must be added externally? Regards Anders
  14. Hello. I have the same question. Is there any detailed description somewhere yet? My problem is Reading 2 values from a sensor. Using a Modbus simulator it Works fine from my PC, but not from the PLC. The communication from my PC is shown in enclosed file. When I use the "Modbus Read Builder" it seems that the "request buffer" is the same as TX in the enclosed document. But I am not sure if (or how) to use the "Read parser" to get the answer? Thanks for an excelent software! Regards Anders Meeg Modbus to DS80.docx
  15. Thanks for Your answer. I tried to send but the file was to big (1.5Mb). It contained approx 20 screens. But import/export worked fine when it was splitted in modules of 5-6 screens each. After my experiance With export/import I have a "wish -list" for additional functionality : export/import of data tables export/import of data samplers export/import of alarms That export/import of trends should keep their trend-labels Thank you for a great Product anyway! Another question: According to documentation, the UIA-0800N has 13 bit resolution (8192). I assume this resolution is for 0-10V/0-20mA Is the actual resolution still 8192 for a 2-10V/4-20 mA signal or is it reduced to 6554? I have actually asked this before but is not sure if my question was understood. What I should like to know is the effektive resolution of the AD Conversion. Regards Anders
×
×
  • Create New...