Hello @narsimh_kamath,
This is a tricky one, and we would need more details regarding the implementation to be able to propose a solution for this.
The first thing which come into my mind is if everything works for 6 AFEs but not for 8, this might suggest a timing issue. What is the Simulink step size vs. the time it takes to execute all the conversions for the 8 devices and to communicate the values via TPL? What can happen here is that the measurements and transfer time might be longer than the step time and some values lost. How is the data acquisition procedure implemented? Did the team used the global conversion and then in the same step window read the values of all the 8 AFEs? Or they have continued to use a round-robin approach as in the enabling example we provide in our toolbox?
Also, depending on the approach, the Transaction Descriptor buffer might overload. Was the TD buffer sized increased or resized to be able to store all the requested data from the AFEs?
It is curious that only the first 4 AFEs readings are correct per each device, when it is increased to 8 AFEs. I think this depends on the actual implementation for the reading sequence. Is there every device handled separately (start conversion, waiting for the conversions to be finalized and then reading the results) per each device. Of course the external configuration tools project and the initializaion sequence must be double checked here, but maybe the data acquisition approach should be optimized.
Secondly, I am thinking rather or not it is an issue with the FreeMASTER. We have noticed that in the FreeMASTER we add a way higher amount of variables to be monitored, some of the data is not displayed. To elimintate this, you can create a new watched sublock and add there only the 8 analog values from the 8th BCC and test only with that.
Please describe the reading technique used, so that we can have a better understanding of the implementation to try understanding where is the issue coming from.
Regards,
Marius
