[Imported] 4203-DR

[sbeadle]

>>Message imported from previous forum - Category:Realflo Electronic Flow Measurement<<
User: mchartrand, originally posted: 2018-10-17 17:53:07 Id:56
This is a re-posting from the obsoleted (October 2018) "Schneider Electric Telemetry & SCADA" forum.

-------------------------------

_**scadaservicetech:
I was able to connect to a 4203-DR with the 4000 configurator and it displayed that it found one transmitter. I then click "view readings" and got a screen with an error message with a red mark say "parameters are wrong". I just can't access the configuration or anything else. However it connects using the firmware loader and i was able to update the firmware but still having the same problem. The display is now blank and only comes on shortly when applying power. I tried a cold boot but the problem persist. Anyone here can give me help with this?**_

___________________________________

du5tin:
Hey! Sounds like a bit of a pickle.
From factory a 4203-DR transmitter is setup to be the transmitter AND the flow computer. It has the brains of a SCADAPack inside of it. This means if you are doing calibrations or sensor setup you should be using Realflo software to work with the unit. This is why firmware loader works.
The 4000-series configurator software is for the sensor only versions of the transmitter (4102). That version doesn't have all the extra brains like the 4203. It is a modbus transmitter.
Anyway, hopefully that explains things a bit. Good luck

____________________________________

_**scadaservicetech:
Thanks alot that really help me. I am still a little surprise I can't atleast do some basic configuration with the 4000 configurator as the manual says it is combatible. But as you said Real Flo is the way to go for this transmitter.**_

____________________________________

du5tin:
Well I think you can force a 4203 to act like a 4102, but I'm not sure how to do that.

It is my opinion that calibrating through Realflo is better anyway. The procedure is a little more controlled. Also Realflo records the caclibration events in the EFM event log which is better for auditability (so long as you are pulling events out somehow).