applecruncher1

MrPLC Member
  • Content count

    19
  • Joined

  • Last visited

Community Reputation

0 Neutral

About applecruncher1

  • Rank
    Sparky

Profile Information

  • Country Philippines
  1. Siemens S5-95U PLC and Battery Concern

    Hi, I apologize for the late reply as I have been busy lately.   We require the battery as the program in the RAM has machine data and modifications that does not exist in the EEPROM.  That said, it is quite difficult to catch the error with the I & B stack as the stops happen instantaneously such that by the time I open the I & B stacks the PLC is back to RUN status. Is there other ways to confirm whether this is a software or hardware fault?   Thanks,
  2. Siemens S5-95U PLC and Battery Concern

    Hi All, We have a hydraulic press that is being controlled by Siemens S5-95U PLC . Lately the S5-95U has been randomly stopping during operation thus causing the hydraulic press to stop running. However the S5-95U instantly returns to RUN status after stopping. This is the first time it has happened after a decade of service. Prior to the random stops issue, around January 2021 the S5-95U completely stopped and the program in the RAM was erased so we had to replace the PLC battery and restore the program with our backup. Strangely, the PLC battery we replaced still had 3.4VDC upon checking. What's even more baffling is that even after we replaced the PLC battery with a new one,  Battery LED is still yellow although the program is still retained in the RAM. In summary, we have two concerns: 1. S5-95U randomly stops and resumes during operation ever since we were forced to replace the PLC battery and restore the program. 2. PLC battery has been replaced but the Battery LED is still yellow but the program is still retained in the RAM.   I have a suspicion that the two concerns I mentioned above are somehow connected but I lack the technical expertise to diagnose. I'm hoping someone can help me figure out our issue. Worst case, I think our S5-95U needs to be replaced.   Thanks,  
  3. Hi All, We have a hydraulic press that is being controlled by Siemens S5-95U PLC . Lately the S5-95U has been randomly stopping during operation thus causing the hydraulic press to stop running. However the S5-95U instantly returns to RUN status after stopping. This is the first time it has happened after a decade of service. Prior to the random stops issue, around January 2021 the S5-95U completely stopped and the program in the RAM was erased so we had to replace the PLC battery and restore the program with our backup. Strangely, the PLC battery we replaced still had 3.4VDC upon checking. What's even more baffling is that even after we replaced the PLC battery with a new one,  Battery LED is still yellow although the program is still retained in the RAM. In summary, we have two concerns: 1. S5-95U randomly stops and resumes during operation ever since we were forced to replace the PLC battery and restore the program. 2. PLC battery has been replaced but the Battery LED is still yellow but the program is still retained in the RAM.   I have a suspicion that the two concerns I mentioned above are somehow connected but I lack the technical expertise to diagnose. I'm hoping someone can help me figure out our issue. Worst case, I think our S5-95U needs to be replaced.   Thanks,  
  4. Temperature Transmitter Configurations

    Hi JRoss and DanW, Firstly, thanks for the quick and comprehensive response. Actually, I do not have the configuration device for the Flextop so I cannot check what the default configuration is. I thought replacing the old temperature transmitter with a new one will immediately solve the problem but apparently the Flextop still has to be configured. What I did was adjusted the output value in the PLC so that it will match the readings of the dial indicator. I can confirm the Flextop partially works because it can react well when there is increase in temperature and will  but when temperature drops, it is very slow to change. Maybe it has to do with the damping value as DanW mentioned. DanW, you mentioned that the dial indicator is not an accurate way to validate the readings so can you suggest a more accurate way to test the validity of the readings of the Flextop? It is measuring incoming steam temperature by the way.   Thanks,
  5. Hi, Recently, we replaced our old digital temperature transmitter with a Baumer Flextop 2201 digital temp transmitter. The application of the digital temp transmitter is for a hydraulic press and the output is fed to the Siemens S95-U plc. The Flextop was able to react properly promptly when there is increase in temperature but whenever there are sudden drops in temperature it is slow to react. The analog transmitter (dial) was already at 25 C when the hydraulic press was shut down while the Flextop was still at 35 C. We used a three wire configuration for this. Does this have to do with our wire configuration? I know there are 2 wire ,3 wire, and 4 wire configurations for 4-20 ma sensors but I'm not sure what are their differences among them. Please see attached configurations below.     Thanks,
  6. Change Value of External Tags in WinCC 7.4

    Hi, Im trying to change the value of my external tag DB31, DW54. My plan is for the user to input the values in the I/O field and click a button to change the value of the external tag. My problem is I can only do it through left click event direct connection on the button but it can only change the value once. How do I do this dynamically in runtime?   Thanks,
  7. Communication of STAHL MT-40 and S5 PLC

    Hi, It seems that our HMI and S5 PLC has problems communicating. The error "H-DB is not available" keeps appearing on the MT-40. I think the cause is the missing handling blocks (Please see picture below). When I checked our PLC program, I cannot find them anywhere in the S5 PL at allC. Should it be that the S5 PLC download these blocks from the MT-40 HMI?
  8. STAHL HMI outpur error: DB NOT AVAILABLE

    Hmm, so it's running from Eprom? I have not reset my PLC yet.
  9. STAHL HMI outpur error: DB NOT AVAILABLE

    The message on HMI is present once the silver cable is connected to PG port of PLC. The error message is on display all the time even in operation.
  10. STAHL HMI outpur error: DB NOT AVAILABLE

    No, the silver cable connects the HMI to the PG Port of the PLC. This is how the HMI gets the output values of the sensor data. So whenever the machine is started up, the error message will flash on the HMI. There are warning signals that appear like "Press temperature < 90 C" so we know the HMI is somehow getting data from the PLC. However, besides that we can't do anything with the HMI. I think that the HMI cannot see the DB values.
  11. STAHL HMI outpur error: DB NOT AVAILABLE

    Attached here is the program. I'm not familiar much with the program though. Actually I'm studying it myself.   PRESS ST.S5D
  12. STAHL HMI outpur error: DB NOT AVAILABLE

    The HMI cable is the silver one that was connected to the PG Port so I can only check the PLC if I disconnect the cable. That's the problem, we cannot trace the origin. It just happened as we were operating.
  13. How to connect PG2000 to S5-95U using RS232/TTY + converter

    Hi dekor, Please check this http://forums.mrplc.com/index.php?/topic/31852-stahl-hmi-outpur-error-db-not-available/#comment-149554 Thanks,
  14. STAHL HMI outpur error: DB NOT AVAILABLE

    Hi, We have a MT-40-TTY/232 PROVICOM TYPE connected to our Siemens S5-95U. Recently we have been encountering an error message all the time: KOMMUNIKATION*** F E H L E R ***DB NICHT VORHANDEN     Apparently, in google translate it means DB NOT AVAILABLE. What does DB mean? Datablock? What could be the cause of this? Ever since this has happened, the HMI cannot output the real time sensor values and all of the keys we press on the HMI will not do anything at all. I am currently checking the output in the S5-95U using PG2000 and I've filtered the DB and they exist.  
  15. How to connect PG2000 to S5-95U using RS232/TTY + converter

    Hi dekor, Thanks for the advice! PG2000 is now able to read the data. Now my next problem is debugging the error.