Jak525 Posted October 11, 2020 Share Posted October 11, 2020 The castle switch logic for Automatic Acquisition (AACQ) is a bit off right now. Currently, the logic is "Castle right with TDC assigned to RDR ATTK = AACQ". The logic however should be "Castle toward RDR ATTK with TDC assigned to RDR ATTK = AACQ". So obviously if you have the RDR ATTK on the right DDI, as is typical, behavior is the same. The problem lies in when you put the RDR ATTK on the left DDI. You assign TDC to the RDR ATTK on the left and castle right to command AACQ. This commands AACQ but then moves the TDC to the RDDI as well. All other applications of the "bump toward format" castle switch behavior works, like with the FLIR to cycle tracking modes and even the A/G RDR ATTK format to start FTT/GMTT. Current behavior: AACQ commanded by Castle right with TDC assigned to RDR ATTK, regardless of if it's on L or RDDI Intended behavior: AACQ commanded by Castle toward the format the RDR ATTK is on, with TDC assigned to the RDR ATTK. E.g. Castle right for RDR ATTK on RDDI; castle left for RDR ATTK on LDDI. Track attached demonstrating this, and also the FLIR and A/G RDR ATTK format behavior that is already correct.AACQ castle switch bug.miz.trk Link to comment Share on other sites More sharing options...
rob10 Posted October 11, 2020 Share Posted October 11, 2020 You already reported this and it was marked “not a bug” https://forums.eagle.ru/showthread.php?t=240376&highlight=Aacq Link to comment Share on other sites More sharing options...
Santi871 Posted October 11, 2020 Share Posted October 11, 2020 It is a bug. Link to comment Share on other sites More sharing options...
Santi871 Posted October 12, 2020 Share Posted October 12, 2020 Reported Link to comment Share on other sites More sharing options...
Recommended Posts