Do you have your Zoop in Nitrox mode?
I just found this on Reddit:
I have the same problem. I centered the problem down to a firmware issue in my 2 year old zoop computer. First I'm using the zoop in imperial not metric mode. When I'm in air mode, between dives on the boat, I could check surface interval as many times as I wanted regardless of the depth I was using it at. I'd download the dives into DM5 and the profiles would be correct. When I'm in nitrox mode, and do anything to any of the buttons, like checking surface interval, when I downloaded into DM5, I'd get really deep dive profiles. To solve the problem, I bought a cheap watch that was good to 100' or so and use it as a stopwatch timer. When I set the zoop to nitrox all I do is look at the screen and leave the buttons alone until after 24 hours have passed. If you do the math, you went to 55 ft but when you down loaded into DM5, the zoop thought you were at 55 meters and converted it to 180ish feet (55 meters = 180.44 ft). In nitrox mode, my zoop would dive correctly and be fairly accurate, and the memory profiles would be correct but when downloading into DM5 the zoop thought it was in meters-feet and then convert to feet-meters or something. I haven't sent the zoop to suunto because I don't want to loose the dive memory. I also use Diving Log 6.0 software to download dive profiles. Its crazy, I'll download into DM5 and have deep profiles, then download into Diving Log 6.0 and the profiles are correct every time.
The first time I saw this problem was last June, just after I did my Nitrox class. I had my computers in nitrox mode for the entire week, even though I was on air the first two days, and just changed my O
2% to match. My numbers don't seem to match up to a meter to feet conversion exactly between the two computers, but it's pretty close. One thing that's weird about the Zoop is that once you do a a nitrox dive, you can't get back into air mode until your no fly time clears, and despite doing about a dozen dives on air over the summer, I kept forgetting to change it back to air (I had it set to EAN21), so I don't know if that would fix the problem.