Jerry I have solved my Universal Firmware Configuration issue with help from Tyler and Wes. My problem now is I no longer have POTH Telescope to control the mount. It is missing from the ASCOM

Paul: Are you up an running now? I am loosing the bubble on these threads.... Wes. -- Wes, Southport NC EXos2-GT PMC-8, iExos 100 ES ED 127, 10" LX200GPS+wedge, Astro-Tech 8" Newt, ETX-90, 60mm

Wayne Thanks for the feedback. I think that is what is leading most astray. Wes -- Wes, Southport NC EXos2-GT PMC-8, iExos 100 ES ED 127, 10" LX200GPS+wedge, Astro-Tech 8" Newt, ETX-90, 60mm

Wes you are correct I was hitting the get configuration button not set configuration. I believe this is what Jerry showed in the video.

Wes, I don't know how to say it more clearly. step 2 in your order fails when you just have flashed your new firmware. Get configuration fails whether I click on EXOS 2 or not :( --

Wayne: I wanted to ask you a detail on the procedure you were using that failed everytime until you did the P9 fix. Here is what I thik you were doing: 1. Boot everything, selet Comm port and then

Hi Mike: Thanks for the observations. What happens is sometimes I overthink things, which in the case of the power supply thing you were worried about is probably also an overthink. I believe every

Paul: Correct. Per your video, you selected the mount to ne exos2 then clicked GET CONFIGURATION. SElecting the mount type did not change the configuration, it just set a new configuration state in

Luiz If the old driver connects so too will the new driver -- no changes there. Did you setup the new driver for the correct comm port and for serial comms? Yes wait for INDI to be fixed properly.

PauL As i recall the first thing about the INDI was that we broke the mount id part as the get version command response is changed. The second thing that is broken is a slew to a static az el.

Asiair Pro seems to be working still after the firmware upgrade. At least, the buttons used to manually slew RA and Dec still make the mount move. Since there's cloud at the moment, I can't test

Wes, thank you for this fix. It worked perfectly. I appreciate your help. Wayne

I have a iExus 100, and after upgrade, the INDI driver don´t connect with the mount using Kstars on mac (I am wanting for the new driver) and the NEW Ascom driver also don´t connect, only the old

This was not after changing anything. It was after updating the firmware, and running UFCT for the very first time. So, the mount type isn't detected from the get go. It is only set after saving the

Wes, Everything worked after the configuration was saved one time. That's seems bit counter intuitive to me, but once you know that, it's workable. Maybe it could be explained in the instructions. I

Hi Wes, I was following Jerry Hubbels video instructions in episode 141. At around 38 minutes is where he starts to configure the firmware. The first thing he does is reboots the PMC-8. When he does

Mike Right You must have also selected the correct pmc8 box prior to setting. This is the correct procedure. Glad you are up and running. Yes the always on comms from both ends was one of those

Alan and mick If you are using the asi air I am not sure you should upgrade yet. Doesn’t it use the indi driver? If so wait at least until that is done. The present firmware run the mount well as

Paul And everybody When you look at paul’s movie you see him choosing exos2 and pressing get configuration, the result being the same error message. This is correct! What one must do after

Paul Sorry about the issue you are experiencing. I put out a note on chxanging P9 manually to get around this. Look on the firmware update thread. The northern/Southern Hemisphere is not exactly