Dear Glenn,
Apologies for using the wrong name before.
Unfortunately MDAnalysis cannot handle the kind of trajectory you have here, where there are different numbers of atoms:
Frame 0: 7840 atoms (successfully read)
Frame 1: 7843 atoms (successfully reads first 7840 atoms, ignores last 3)
Frame 2: 7843 atoms (breaks here)
In MDAnalysis, trajectories must have the same number of atoms for each frame. The XYZReader is probably breaking upon reading Frame 2 because it is trying to read a new frame, but instead it is reading the last three atoms of Frame 1. That might also be why it’s showing 416 frames when you look at the length of the trajectory (although I can see the same behaviour as you, I can only index u.trajectory[0] and u.trajectory[1]).
If you add the C/C/H atoms to the first frame (maybe with zero coordinates), or drop the first frame, you'll be able to use MDAnalysis.
I hope that helps, please let me know if you have any more questions!
Cheers,
Lily