Empty frames in ethercat debug data

[guihomework]

In rosbag recording ethercat debug data, we noticed some rare (0.003% of the messages) incoming messages are completely empty.

Good data

1463751182233841219,409523,1463751182235725486,,3433,2547,3428,2183,2952,2880,3105,2131,3627,2833,3286,2255,2944,2432,3097,2117,2096,1119,1787,1800,2145,1983,14,3040,1275,2484,0,0,0,0,0,0,7,18,5,9,0,5,1,699050,0,3,20,-12,-2,8,-1,0,0,1,0,2,3,1,4,12,1,1,1,7,0,1,31,1023,1023,1023,1023,1023,322

Empty data

1463751182234379755,409524,1463751182236515571,,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0

The filters would not see that change, but some joints are not filtered right now.
Even if all joints were filtered, does it make sense to send an empty frame (invalid data) ? Is it not better to not publish invalid data ?
You might argue this is debug data, but actually this topic is used by the calibration tool, and we used it for researching on raw vs real angle calibration.