Jump to content

sgull

Members
  • Content Count

    183
  • Joined

  • Last visited

  • Days Won

    10

sgull last won the day on December 24 2018

sgull had the most liked content!

Community Reputation

13 Good

1 Follower

About sgull

  • Rank
    UniGuru
  • Birthday 01/24/1968

Profile Information

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks NoamM When is the expected release date for Version 30
  2. Where did you get 1.29.145? the latest version appears to be 1.29.111
  3. Hi Bernd I think this behavior is correct. For example if you want to run from midnight for 1 minute you set the start for 00:00 and end at 00:01. It runs for 1 minute and stops at the start of 00:01. If it ran to the end of 00:01 it would have run for 2 minutes The problem is that the schedule does not allow you to enter seconds. If you want to run for 24 hours set the start to 00:00 and the end to 00:00 Denis
  4. Hi I think if you select project in the top left corner of VISILOGIC. Then select properties. Under the Colors tab, I think it might be "marking view color" that you change to the same background color. Regards Denis
  5. Hi Charisteas Right click on the curve you want to display and set the position of the decimal point in "decimal format".
  6. Hi Charisteas Right click on the trend you have problems with on the left of the screen Select properties. Make sure that the Run/Stop bit (in this case MB24) has a power up value of 1. The trend will only start recording when this bit is powered up. I have forgotten this on many occasions and it can be difficult to troubleshoot. Regards Denis
  7. Hi DaveH The configuration should have downloaded with the program you have. Also remember that when you download the program to a new PLC you will need to manually enter any setpoints or timer values unless they are assigned power up values. All registers will be set to 0 unless the have power up values. After download power down and restart the PLC.
  8. Thanks Ofir I didnt see that. That solves the problem. Regards Denis
  9. Thanks Kratmel and Aus. The post referenced above is similiar in so far as the buttons pressed on the HMI can be seen on VNC. The buttons pressed on VNC can also be seen locally on HMI The post offers no solutions, Aus - The password that is entered is masked with stars, but as the buttons are pressed on VNC or local on HMI, anyone can easily see the "button pressed" indication on the opposite device. To get someones password just tell them you have a problem and as they log in remotely watch which buttons are being pressed. Maybe it is just the VNC viewer I am using that does this (Real VNC), but I will try later with another. Regards Denis
  10. When connected remotely through VNC, if someone is standing at the HMI they can easily see passwords as they are being entered. The button presses appear as the keys are pressed remotely. Many times when I connect remotely is to troubleshoot and there is normally an operator looking on locally. Is there any setting available to disable the key presses when connected remotely? Regards Denis
  11. Hi Vinicius If you want the timers to continue to run when you leave the display, you must put them in a subroutine that is being called all of the time. On rung 10 you are using a positive transition contact of MB 35 to start timer 2. This may explain why you are stopping at 4 seconds Regards Denis
  12. Hi Kevin Have you the latest software on the PLC? On your screensaver if you have an image, assign a touched bit in order to go to a specific page, this should work with the latest version and most VNC Another way is to put a button the full size of the screen with a touch property to take you out of the screensaver. In the button settings set the background to transparent so that it cant be seen. These two methods mean that you don't need to use the screen touched bit Another alternative is if you click on the system tag at the bottom of UNILOGIC, you will see a bit assigned to VNC connected. You can use this bit to go out of screensave and prevent the screensaver from starting when it is on. Regards Denis
  13. Hi Kevin I would suggest that you call the read and write sub-routines in your program continuously. Conditional calling of sub-routines sometimes gives unexpected results. Try increasing the time on TD0, everything is trying to happen too fast. On you RHR 3 block you are reading 2 values and sending them to MI3. This will store one value in MI3 and the second in MI4. However you are using MI4 in the same block to show the status. Be careful of this, if you are reading several values you must allow enough room to store them. Visilogic will not automatically reserve the space for you. I you are going to read more than one value try to do it on one read. for example if you need address 1, 5 and 7 on the device, it is better to read 1 and set a length of 7 than to try to read using 3 separate reads. It works out much faster and you can just ignore what you don't need. When reading and writing in MODBUS try to set up a sequence. Set a bit perform a read or write using a positive transition contact of the bit and use this to set the bit for the next action. Continue this to complete all the read/writes and at the end reset every thing and start again. Start read - Set MB1 Positive transition MB1 - Read first piece of data and set MB 2 Positive transition MB2 - Read second piece of data and set MB 3 Positive transition MB3 - Write first piece of data and set MB 4 ETC. when all data is pooled reset all MB and start again. You are writing the value to MI6 in the modbus data block, did you intend to display this on the write screen? Regards Denis
  14. Hi LE BERRE MI36 is set to 0. I think this is the number of registers you want to read. What is shown is that you want to start at register 0 and read 0 registers and store them in MI24 Change MI36 "read value length" to a fixed number and see what happens. Also be sure that the plug that you use to connect the devices uses pin 1 and 6, most cables of this type only use pins 2,3 and 4. Check your communication settings, in the program you are using slave ID=7 and in the attached picture the address 0x0077 Parity and all port settings must match on both ends. Regards Denis
  15. for 12 bit it should be 819-4095 How accurate is your pressure transmitter and meter? This does not seem to be a huge difference. You can always do a small calibration routine in the program to create an offset
×
×
  • Create New...