Originally posted by Traveller
View Post
"No, it's miscoded on one transponder. Went wonky on April 18 and has been using both hex codes since. 8980C4 last used on May 6 but it has used 896030 about a dozen times prior to then, so clearly miscoded on one box."
I have checked this again and seems that the use of 8980C4 in May was fake with the data coming from scheduling. It has used 898030 continuously since 17/4 so I have made the change in the database, sorry for the delay.
Comment