Jump to content

PeterFukt

Members
  • Content count

    39
  • Joined

  • Last visited

  • Days Won

    1

PeterFukt last won the day on August 19 2016

PeterFukt had the most liked content!

Community Reputation

3 Neutral

About PeterFukt

  • Rank
    Advanced Member

Recent Profile Visitors

486 profile views
  1. It's the same phenomenon with a SM35-J-TA22 straight out of the box when I enter Info mode. Firmware: 4.4 (28) Oct 16 2017 Boot: 2.2 (24) Oct 29 2014 Bin library 0-2.10 (04) After updating the PLC the issue was resolved. Firmware: 4.4 (31) Oct 19 2017 Boot: 2.2 (48) Sep 25 2016 Bin library 0-2.10 (04)
  2. Hello, with the latest batch of Samba SM35-J-T20 PLC's I've programmed, I have noticed that the buttons in the virtual keyboard stay pressed when you touch them once. I must touch them again to make the button appear unpressed. Is this a change in the firmware? It seems to work anyway. Just curious what is causing this. Buttons stay pressed with this PLC Firmware: 4.4 (28) Oct 16 2017 Bin library 0-2.10 (04) Buttons works normally with this PLC Firmware: 4.4 (09) Apr 5 2017 Bin library: 0-2.10 (03) Cheers, Peter
  3. According to tech support, there was a bug in Visilogic 9.8.31 with the Com FB that they fixed in 9.8.64. I got the explanation that it was not possible to choose RS485 in the older version but that it now is fixed. It seems as if the bug was present in 9.8.64. I tried the same thing with 9.8.65, and now it is again possible to choose RS485. Also programs made in version 64 that showed a grayed out RS232 com init setting, do show RS485 again in version 65. /Peter
  4. It is good to know that the same happened to you. So it must be a change or error in the newer version that Unitronics haven't told us.
  5. Hello Ausman, something has definitely changed. When I start a new project in Visilogic 9.8.31 I can choose between RS232 and RS485. In 9.8.64, it is RS232 only. When I saved the test program in 9.8.31 (RS485 in com init) and opened it in 9.8.64, com init said RS232 and it was grayed out. I'm stuck with 9.8.64 because all my recent programs are made in that version and can't be opened in an earlier version. It seems though as if the PLC recognise the com card as RS485 when I run the program in a PLC with an installed Modbus card. Can someone from the development team answer if there has been a change in the program that affect the com init block for Samba PLCs? Best regards Peter
  6. I see, break it up in like one separate Com init + modbus configuration per net? The Samba need a communication card for RS485 or for TCP/IP. But I want to prepare the program so it supports both. I just found it wierd that I can't choose RS485. If I choose Vision in HW configuration, I can choose between RS232 or RS485.
  7. Also, the code looks like this. I'm just wondering if it is okay to place the contacts like that. When I did an Online test, if I activate MB81 in the HMI, all com init FB's turns red. If I activate one below, all com init except the first one get red. Is that normal or is the ladder code not optimal?
  8. Hello, I have made programs for SAMBA PLC SM35-J-T20 and TA22 with Modbus configuration. In Com init help, it tell me to select RS232 or RS485. But the field is grayed out on RS232 and I can't select RS485. If I remember right, I could select RS485 when I did the program for the first time, but when I chech the Com Init settings, they all say RS232 and not RS485. Doesn't it matter if it say RS232? I had to change it to RS485 in Info mode to get communication to work, but if I loose power, it returns to RS232.
  9. Thanks for the help. I think I got it to work finally.
  10. Hello VisiLogic creators! I see that this function is still not implemented in the program. I have made a program that use several linearization blocks and for each one, I must use two compares and two store direct to prevent the output from getting false values when the input goes outside the X1-X2 range. It would be great if you could implement an option so that the Y value only stay within the Y1-Y2 range, even if the X input is larger or smaller than the X1-X2 range. Any plans of doing so in a future update? Best regards Peter
  11. Thanks Joe and Hotwires, I think I might figure it out. Some code would have been very helpful. To much to do but no time for extra thinking at the moment.
  12. Is there an example of this somewhere? I want the unit to run normally even if Modbus is not used at all. //Peter
  13. Hello, I'm trying to figure out how to make a watchdog function in a Samba SM35-TA22- The customer will use TCP/IP to mostly read values from the PLC. If the communication goes down, the unit should stop. But I have no idea how to make this. I was looking at SB147 which is Socket 0 connected but it is constantly changing when I disrupt the connection, I guess it is due to auto connect. Is it the best option to use SB147 with perhaps a timer so if it is on for 10 seconds, that means the communication is up and the unit can run, but if sb147 change, the timer reset and the unit is stopped. I just want some feedback if I'm all wrong here. Thanks! //Peter
  14. I like this thread also. I had to use a 3-point valve because I was an analogue output short. I think I got it to work pretty good. I programmed it so the valve closes for 20 sec extra (total runtime is 30 sec for the valve) every time PID output reaches zero and the virtual position is below 20. It worked almost smoother than a modulating valve. Thank for your advice.
  15. Hi, I made a solution like this to count runtime hours for a fan. In the HMI I can both read, edit and reset the ML4 value.
×