1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 <2023> 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 <2023> 2024 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: problem reading data from PLC |
From: | Sebastian Marsching via Tech-talk <tech-talk at aps.anl.gov> |
To: | Abhishek Dutta <abhishek.d at vecc.gov.in> |
Cc: | tech-talk at aps.anl.gov |
Date: | Mon, 7 Aug 2023 12:52:41 +0200 |
Hi, in my experience, this kind of has one of three causes: 1. As already mentioned, the address might be invalid. It might make sense to add the address to a watch table in TIA Portal in order to verify that is correct and provides the right value. 2. The parameter passed to s7nodaveConfigureIsoTcpPort might be incorrect. Please ensure that the rack number and slot number match the CPU (again, this information can be found in TIA Portal). 3. The PLC has to be configured to allow access GET/PUT access and protection and optimized block access must be disabled. You can find details (including screenshots of the relevant configuration options in TIA Portal) in the Snap7 documentation, which is the library used by s7nodave: https://snap7.sourceforge.net/snap7_client.html#1200_1500 Best regards, Sebastian
|
Attachment:
smime.p7s
Description: S/MIME cryptographic signature