We installed x3 “new” G4 AD8 on an existing mistic board, and using x3 existing G4 AD8s for a set of 6 thermocouples.
Then I use the “MoveIOUnitToNumTable” command.
Now I am having a strange issue where one of the existing TEs and one of the new TEs have an IVAL of 0, with an expected XVAL. The other four TEs have expected matching IVALs/XVALs. The numeric table is pulling the IVAL of 0 and not the expected XVAL which means the rest of the strategy is not working.
Is this an issue with the MoveIO command? Should I be using something different for legacy mistic? Or doing an enable/check communications to the units first? (-not sure why this would change anything since only some are failing).
Or is this a wiring / hardware issue?
I seem to recall that you need to address the Mistic points or the iVal won’t update with the Xval.
Can you try just moving the TEs to a variable named trash or such, ie any var you really don’t care about.
That might be what’s needed. (Note: You can still do your move io via table, but in a looping chart (with a good delay—something in the order of seconds), also move each TE to that trash var.)
Okay so I moved them to their own individual float numeric variables straight from the Analog Input. However, they are still showing the same thing- IVAL 0, XVAL as the expected readings.
(It was in a looping chart already, but the delay was 800msec, so increased it to 3sec. Did not seem to fix the issue either).
