Machine Automation Forum
A forum addressing machine automation solutions for the complete machine lifecycle. Including offers like Machine Advisor, Modicon PLC/PacDrive, Lexium or Preventa. Discuss and share knowledge on offers relating to cloud-based service platforms, machine localization and monitoring, industrial operations control, motion products as well as safety function!
Link copied. Please paste this link to share this article on your social media post.
Posted: 2022-11-18 01:24 AM
I've problem with installations with TM172 (fw 596.12) as a master for modbus rtu heat meters network. Sites've worked correctly from few to several dosen minutes and after that controller indicate .miss on all slave devices with 2 status code, missCnt is increasing. Slave network is terminated correctly and have aplied bias resistors.
To restore communication I've to perform reboot on TM, aftertheat communication returns but again only for certain period and all trouble return.
There is a way to restart RS485-2 port or hold and release all readouts from code without need to reboot controller?
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2022-11-18 02:45 AM
Hello,
there is not a way to restart the serial (controller can be rebooted using sysWD_Background(0)).
Have you tried to monitor the line with an oscilloscope?
If you disconnect/reconnect slaves or master Modbus connector, does something happen?
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2022-11-18 05:10 AM
Thank you, there are all remote sites but I wiil try to find someone enought brave locally to touch automation box and switch on /off cables. Oscilloscope is out of option at this moment, and from this my previous question about possibility to restart only serial interface without whole controller (from obious reason). If it is not possible I will have to find other workaround solution
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2022-11-18 05:20 AM
If you use the target blocks sysMbMERTU_FC** you could generat an commication which could be startet and stopped via application. But this way is normally not so fast and not so comfortabel.
I could be a workaround but not a solving of the real probelm.
The heat meters the only modbus devices you read?
How many heat meter did you read?
Which hardware did you use exactly.
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2022-11-18 09:40 AM
Temporaily I've supressed this by use of the one of free DO in TM to make a short for about four cycles with 100ms timing task RS485-2 '+' signal to Gnd on port RS485-2 socket. I'm affraid that there could be a problem related to some kind of slave tranceivers because it appears on Modbus RTU for Kamstrup heat meters 601 and I've similar problem witcg Schneider FM40 Uniflair chiller
Link copied. Please paste this link to share this article on your social media post.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.