I'm experiencing many connection dropouts during my workout between Edge 1030 and Neo 2T.
Here an example where you can see how many time the signal goes to ZERO values:

This is the official Garmin answer to the email that I sent to the support:
Hi, I've just bougth the Tacx NEO 2T one week ago. It seems a great product (and I hope it :D) but I have a 2 big problem. …
(Problem persists after FW 0.0.32). I was quite busy the last couple of days, but I updated the neo2t to FW 0.0.32. as soon I read about the FW here.
I am still experiencing the drop outs. From my steady…
I have the same issue on a new Tacx Neo 2T in the year 2024 with the newest firmware!
ANT+ on an Edge 530.
My other powermeters (pedal and crank based) have no dropouts at all.
That seems to add some evidence to my findings. Thanks for testing.
I did a trainer ride without the remote paired last night & had very few dropouts. Those that did occur were of a much shorter duration than with the remote paired.
I also recorded the workout on my old Edge 1030 as a comparison & had no dropouts at all on that unit. The only difference in setups is that my new unit has the trainer sensor paired for FE-C control So although I believe the remote pairing is causing a majority of the dropouts it seems the FE-C pairing is also having a detrimental effect
Are you talking about edge remote?
Because I'm experiencing dropouts again when I use Laptop to control the trainer using Desktop Tacx App.
ANT+ signal from HR band to laptop is always ok, but BLE/ANT+ signal from trainer to laptop continue to have dropouts.
In the same time and session the signal from both devices to Edge 1030 is perfect, with NO dropouts.
But I have the Edge Remote connected, not because I need it, but simply because I do not unmount it from bike.
That's right I'm talking about the Edge Remote. I haven't used the Tacx app to control the trainer & would probably use the Bluetooth if I did rather than ANT+ as I don't have a ANT+ dongle
Regarding the remote connection to your Edge1030. Are you pressing a button on the remote to connect it to your Edge when switch the Edge on? Otherwise although the Remote is paired it won't actually be connected.
That's a good result, the more evidence that points towards an issue with a remote pairing the better.
I've completed my testing & submitted the data to Garmin. Rather than post a load of screen shots here I'll update this post later with a link to the document I sent them