Problems after using Pet123 settings

[cs3007]

Hi, I have a 7020 and have used the Pet123 in conjunction we Dreamboxedit. I have Ftp'd across and most of the listings work ok, as the motor moves and I can see the selected channel. But on 28.2e and 1w (they are the ones I have found so far) when I select a channel off them Sats I get "service not found", I have looked under the motor setup and can only see one transpnder listed which is 10788/22000 for 28.2e and likewise for 1w.

Any ideas?

Cheers

[cs3007]

Forgot to add, that when selecting channels on 28.2 and 1w, I do not get the "motor is turning" message, just the error message. Whereas on the other Sats I get the motor turning message ok.

[BGonaSTICK]

Hi djc. Nice to see you here

I'm not certain, but from your description, it sounds like your satellites.xml file is out of sync with your satellite definitions from PET123 file.

You may well find that for Thor2/3, one says 1W and one says 0.8W. Similarly, Eurobird1 is at 28.5E as opposed to 28.2E, and this can cause a similar problem. It's probably easier to alter the definitions in your PET123 file and re-FTP them.

I may be wrong, but that's my guess.

Have a read of this, as it might give you some background.

http://www.satellitehelp.co.uk/forum...hp?topic=195.0

Of course, this may be nothing to do with your problem! Think it might be though

STICK

[cs3007]

Hi Stick, I remember you from a year or 2 ago when you were active on the other Satellite forum, you helped me a lot then Nice to see you again too.

But I have solved this problem, by deleting the existing satellites from satellite config page, then when it was empty, selected the many sats by rotor option and it then re-populated with a new set of satellites (could tell as the name format was slightly different), I then ftp'd the pet settings and everything now works great.

Cheers

[BGonaSTICK]

I thought your nick rang a bell :spite: Welcome m8.

Glad you're sorted. Problems caused by the introduction of some external channel/TP/satellite data are usually to do with a mismatch with how the receiver already sees the world. What you've effectively done is the opposite to what I said - i.e. you've deleted and rebuilt the 'other' end of the problem.

Nice to know that works too for future reference. I'll file that one away in the old grey matter

STICK