Good news is, Ekos is now communicating with the UPBv2. I will upload logs after more testing.

Hello Jasem,

Attached is the log file for the UPBv2. I have also included a list of observations. Thank you.

1. [WARNING] Received wrong number of power sensor data. Retrying...

2. Cannot obtain absolute position of focuser stepper motor. Stepper motor makes a loud "crunching" sound.

3. 'Dew' tab > Dew B is not measuring current.

4. 'Dew' tab > Dew C is not measuring current.

5. 'Power' tab > "Power on boot" option not retaining data after configuration save.

6. 'Main Control' tab > Adjustable output voltage setting is not being retained after a configuration save.



Kindly,
cl330b

FYI The “power on boot” configuration also does not save on the version 1 Pegasus hub eihter...

I'd also like to add that the following:

7. The adjustable voltage output isn't outputting any voltage no matter how the parameter is set (Could be moved to the "Power" tab.

8. USB ON/OFF control of individual ports. (2 of the ports on the UPBv2 hub are "Off".

9. Will the changes to the driver be incorporated to the raspi repo as well?



kindly
cl330b

Ok, just pushed an update. Please check.

What do you mean by #8 exactly?

Hi Jasem,

I've pulled and I'm currently testing. Thanks for all you do for the community.

Statement #8:

I was referring to the fact that each of the 6 USB ports are individually controllable using the U#:b command (e.g. U1:1 = ON or U1:0 = OFF). The same for all 6 USB ports. Two out of the 6 ports are 'OFF' on my UPBv2. This individual USB port control is in addition to the global control over the USB hub using the
PU:b command.

Kindly,
cl330b

One more quick question. Why do code and formatting tags break when I edit a post?

Ok thanks, please share the logs after testing and let's take it from there.

Hi Jasem,

Please see attached log file and below.

"Firmware" Tab

1. "Uptime" not working
2. Version displays "NA".

"Environment" Tab

1. Seems to be working

"Focuser" Tab

1. Temperature not working. Reading "0". (Same temp sensor as displayed on "Environment".
2. [ERROR] Focuser failed to move to new requested position.

*Focuser has a lot of issues. I have reached out to Pegasus Astro regarding the focuser issues.

"USB" Tab

1. Individual control for each of the six USB ports in addition to the global control of the USB hub.

"Dew" Tab

1. Auto Dew - untested at this time.
2. "Dew C" not working. Parameter does not control the output.
3. Dew Current measurements not working for all three outputs (Dew A, Dew B, & Dew C).

"Power" Tab

1. Power Control is working.
2. Adjustable output isn't working. No voltage out from the adjustable output.

"Options" Tab

1. All is working.

"Connection" Tab

1. All is working.

"Main Control" Tab

1. All appears to be working.

Kindly,
Christopher

Thanks for the quality reporting, this made tracking the issues a lot easier. I just pushed one more update that I believe would resolve most of the issues reported above, including the focuser issues. Please git pull and report back.

Thank you Jasem,

Yes, most of the issues are resolved.

"Power" Tab
1. Adjustable output isn't working. No voltage out from the adjustable output.

*I have also reached out to Pegasus Astro regarding this issue.

"Focuser" Tab

1. Temperature not working. Reading "0". (Same temp sensor as displayed on "Environment".
2. I can not increase the focuser speed greater than 50% without the stepper motor making a "clicking" sound. A focuser speed greater than ~60% causes the "clicking" sound with no movement.
3. When I choose to the move the focuser 5000 steps in the outward direction using the "Absolute Position", the focuser moves properly. When I attempt to return the focuser to absolute position zero by 5000 steps, the focuser stops a few millimeters short of zero and no error is reported.

*Will this issue affect the temperature dependent focus changes?

"Dew" Tab

1. Auto Dew - untested at this time.

Unfortunately I cannot get the focuser to move [Moonlite] with the new git pull. I am still new to Indi, so I can't provide logs, but I'd like someone else to verify if I am doing something wrong, or if the driver issues are still in effect.