I'm working on extracting Modbus addresses from an S600+ Flow Computer's 'mbslave.txt' file provided by the client. Unfortunately, I lack the S600config software to open the corresponding '.cfg' file. Given my experience with flow computers and their software, I'm struggling to interpret the Modbus addresses in the 'mbslave.txt' file. I've attached both the 'mbslave.txt' and '.cfg' files for reference. Any guidance on extracting the necessary Modbus addresses would be greatly appreciated.
Thanks
https://drive.google.com/drive/folders/1sr35BYU8lXU0Epohy55le1TnFxrnb6JA?usp=drive_link
In reply to ian firth:
Thank you for your suggestion. I have obtained the slave map report, which includes Coil Data Map and Register Data Map sections. I have the following questions:
Please refer to the attached images. I appreciate any clarification you can provide.
In reply to Moazzam Ali:
1. eventing mode just means if a value is changed via modbus we add it to the event log
2. Field is just the name of the field associated with alarm for example. ADC01 above Low Hi, under range are the ones enabled in the config and why not all are mapped
3.Yes, If field security set to 9 in the actual configuration it is read only. Generally slave maps are all read only
4. These are your basetime reports, You can have up to three different basetimes configured. ie 8am, midnight, 6 pm for when a day starts for example if you have an hourly report this would be basetime 1 period 1 and in your case STR01 PREV FWA VAR1 would be the flow weighted average of the previous hour, by default var1 is pressure, var 2 temperature and basetime 1 prd 2 would most likely be previous day of the same variable, prd 3 will be weekly or monthly again of teh same variable