I'm not actually in front of the equipment yet, but this is the information that I have been given by a client:
------------
Data from HART compatible Endress & Hauser Analyzer over Modbus TCP has successfully been read by Kingfisher CP-12 RTU's for many years, with apparently a HART board being added to the RTU to allow the data transfer. Client wanted different RTU in one spot - a Kingfisher CP-35. The same E&H sensor is being used in the same way for this new RTU, but after a short period of successful transmission on powerup, then the comms fails and takes a number of seconds to come back again, then the process repeats.
------------
Manufacturer of Kingfisher RTU's is Ovarro, and upon relaying the above information to them, they are trying to say that it's a sensor issue, despite using the sensor successfully CP12 RTU's for many years.
Sorry if description is vague. My plan would be maybe to use wireshark and look at the captures from CP-12 RTUs, and then look at the captures from CP-35, and see what is different.
Please let me know if by small chance anyone might have experience with something similar, or any ideas?
Thank you very much
Ovarro Kinfisher RTUs, stats for both, by selecting 'variant': https://ovarro.com/en/global/soluti...rtus-from-ovarro/2/kingfisher/kingfisherplus/
Page mentioning HART protocol for these RTUs: https://www.maximation.biz/wp-content/uploads/2017/08/KingfisherPLUS.pdf
CP-12: https://www.ebay.com.au/itm/272191048793
CP-35: https://isagraf.ru/images/industry_avt/soft/isagraf/kingfisher-plus-cp35_04.pdf
------------
Data from HART compatible Endress & Hauser Analyzer over Modbus TCP has successfully been read by Kingfisher CP-12 RTU's for many years, with apparently a HART board being added to the RTU to allow the data transfer. Client wanted different RTU in one spot - a Kingfisher CP-35. The same E&H sensor is being used in the same way for this new RTU, but after a short period of successful transmission on powerup, then the comms fails and takes a number of seconds to come back again, then the process repeats.
------------
Manufacturer of Kingfisher RTU's is Ovarro, and upon relaying the above information to them, they are trying to say that it's a sensor issue, despite using the sensor successfully CP12 RTU's for many years.
Sorry if description is vague. My plan would be maybe to use wireshark and look at the captures from CP-12 RTUs, and then look at the captures from CP-35, and see what is different.
Please let me know if by small chance anyone might have experience with something similar, or any ideas?
Thank you very much
Ovarro Kinfisher RTUs, stats for both, by selecting 'variant': https://ovarro.com/en/global/soluti...rtus-from-ovarro/2/kingfisher/kingfisherplus/
Page mentioning HART protocol for these RTUs: https://www.maximation.biz/wp-content/uploads/2017/08/KingfisherPLUS.pdf
CP-12: https://www.ebay.com.au/itm/272191048793
CP-35: https://isagraf.ru/images/industry_avt/soft/isagraf/kingfisher-plus-cp35_04.pdf