Jump to content

PeterFukt

Members
  • Content Count

    39
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by PeterFukt

  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. 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
  10. 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.
  11. Is there an example of this somewhere? I want the unit to run normally even if Modbus is not used at all. //Peter
  12. 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
  13. 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.
  14. 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.
  15. I updated to the new version and opened a project made in the previous version. I noticed that the program was using more memory than before, when running the "projected memory map" action. Now it say " Exceeds the limit: Used 101 % of 100 %". Is that due to wider net or what could the reason be? It's giving me a headache needing to remove variables from the HMI before being able to add new ones. Cheers, Peter
  16. Hello, a customer is having problems with the remote operator software. They can run it on their laptops but when they try to run it on their SCADA PC (desktop) they get a "Run-time error 5: Invalid procedure call or argument" and the program crashes. Any ideas why that happens?
  17. Hi, I made many changes in a program today and created a project file for the customer to download it with Unidownloader. But after I saved it, I noticed that the project file saved itself with the same filename as the original program, including the .vlp format. So now I have a project file but no Visilogic program file. Is there anyway I can get the program back using the .vdf file or is the program code including half a day of work lost?
  18. The customer won't change their network so we must unfortunately make the PLC work for them. I make a few com inits and some buttons with a toggle function in the HMI to choose preset settings. One question remain: is Unit ID needed? When I tried the program, I could communicate with RS485 using the Modbus TCP/IP ID number. The Unit ID has always been the default 1. I tried to set Unit ID to 64, and use that in my Modbus master program but that did not work. When I used the Modbus ID number, it worked well. So I'm wondering since the 485 help file tells me I must set the Unit ID. Is it not needed on the Samba?
  19. Spot on, it is a German company that use the 9600,8,e,1 setting so it is "not acceptable" that we have other default settings that cannot be changed so that the change is saved at power loss. If the settings could be stored as MI's everything would be fine. I read somewhere that if the master has a lower baud rate setting than the slave, it still works, that the slave will communicate with this lower baud rate. Is that so? In that case, I could make a couple of com inits that have 8,n,1 and 8,e,1. 8 to choose from. 8 and 1 seem to be most common bit setting.
  20. The customer use 9600,8,E,1 in their network. After setting the PLC to those settings using Info mode, serial menu, the communication only works partly. Everything else in their network works. Also very strange, when they connect the Modbus, they can no longer push a button on the HMI to start the unit. It is being locked. It calls MB2 to start the unit. The customer also say that they can't trigger this function with modbus. When I tested it, I got it to read and write coils on address 2. With Modbus TCP I can use MIs to change TCP IP card settings. That is not possible with the com init. Our PLC program is supposed to be universal meaning we don't customize the program with specific com settings. It's also a PLC memory issue, I can't add much more to my HMI. What settings are essential for a master to communicate with a PLC slave? I need the least amount of possible com init combinations to select from a HMI page. If slave has 57600 and master 9600 or the other way around, does it still work? Is it more important that data bits, stop bits or parity is the same? Sorry for all the questions, but all of a sudden, I'm getting lots of messages from annoyed customers that do not use 57600,8,1,n.
  21. Another question on the RS-485 matter. A customer is getting very upset that they do not get communication to work properly. In the com init block, my program set 57600,8,n,1. If the customer use these settings, everything works. But their system use 9600,8,e,1 and when they change the PLC settings in info mode to their settings, the communication only works partly, all commands are not working for them. Any idea why this is? Also, must I make a com init block for each possible combination and a HMI page where the customer can choose one combination of RS-485 settings or how else is the problem with different com settings at the customers taken care of since info mode changes gets overwritten at power up? Maybe make the change in info mode and after that activate a button that prevents the com init block from running again?
  22. I see. But if the Modbus master communicate with other baud rates, it can still communicate with the PLC right? What does the Unit ID that you can set in information mode do? The RS-485 documentation say that a Unit ID must be set to communicate with the PLC but when I try it with a Modbus master program, it seems to only use the Modbus ID. Can Unit ID be disregarded and kept on 1(Canbus) when using RS-485?
  23. Hello, I just got informed about an issue with the program I have made for a Samba SM35 regarding Modbus settings. I use a Com Init block directly after a power-up bit that initializes factory com settings. If I enter Information Mode and change the serial settings for RS485 there, everything is fine until a power loss. The settings are overwritten at power-up. Is there a way to prevent the settings from getting restored to Com init settings after a power-loss or unit shut down?
×
×
  • Create New...