JE9PEL, Mineo Wakita wrote at 20:40:12 +0900, 16 Jul 2002: I had noticed that MA of WiSP3215 (GSC2.03) was less than the valid value. MA for AO-40 was about 126 slow as below. AO-40 UTC P3T WinTrak WiSP 19 Nov 2000, 01:22 23 23 153 (153+126-256= 23) 21 Nov 2000, 02:30 63 63 193 (193+126-256= 63) 28 Nov 2000, 08:39 250 250 124 (124+126=250) 02 Dec 2000, 01:12 120 120 250 (250+126-256=120) 02 Dec 2000, 07:13 250 250 124 (124+126=250) 02 Dec 2000, 19:34 5 5 135 (135+126-256=5) Is already available an updated WiSP version or update/FAQ that corrects the defect of AO-40 and the other satellites MA ? HB9OAB, Franco Borsa wrote at 14:11:14 +0200, 16 Jul 2002: Thanks for the added one of information. However the difference on my computer with real position 'MA' of AO40 is of approximately -10MA. Attention to update all the programs used for the test with the same keps. The WISP problem is that it calculates 0/256 in descendent position on the Equator and not to the perigee. Thanks for eventual info of a UPDATE of WISP that corrects the bug! 73's hb9oab@amsat.org AO40/SAT home site at: www.wlog2000.com/hb9oab WLOG2000Team: www.wlog2000.com JE9PEL, Mineo Wakita wrote at 18:15:28 +0900, 17 Jul 2002: I confirmed that MA of AO-40 with WiSP3215 (GSC 2.03) was approximately 9MA fast in 2002, although 126MA slow in 2000. And, MA of AO-10 was approximately 19MA slow. AO-40 UTC Calsat WinTrak WiSP 16 Jul 2002, 16:00 163 163 172 (-9) 16 Jul 2002, 17:00 176 176 185 (-9) 16 Jul 2002, 18:00 189 189 198 (-9) AO-10 UTC Calsat WinTrak WiSP 17 Jul 2002, 07:00 26 26 7 (+19) 17 Jul 2002, 08:00 48 48 29 (+19) 17 Jul 2002, 09:00 70 70 51 (+19) MA for the other satellite has the different error. So, MA of WiSP3215 (GSC 2.03) seems to have many errors. Now I think the orbit number of all the satellites increments at perigee. However, NASA for Shuttle missions uses the ascending node where increments the orbit number when the satellite crosses the equator (going northward).