×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

Ultimate Powerbox v2 - connectivity issues?

  • Posts: 527
  • Thank you received: 139
I've been having some strange issues with focus lately using the UPBv2 and a Moonlite focuser. See here. If you examine the logs, there are all kinds of power issues. I'm wondering two things. First, if this is the same power issues you all are seeing. And second, if this power issue plays into the focus system at all, or just affects the power ports. I'm considering going back to my Moonlite focus controller soon if this doesn't seem to get sorted out.
3 years 11 months ago #53756

Please Log in or Create an account to join the conversation.

  • Posts: 220
  • Thank you received: 27
No the power issues are related on how the powerbox handles the command for PowerOff/On all ports. If you send off it disables all 4 ports (The 5V and 12V always on can't be manipulated) and also turns off all dew heaters. If you send all ports on, the 4 ports are enabled but also the dew -heaters are enabled at "full strenght" but it does not show in the settings. (so the slider value is 0, you can see amp usage for the dew heaters but that is easily overlooked, and the scope can heat up a bit)

So I am changing it by 2 separate buttons; one for power and one for dew heaters and set all ports individually. Still need to introduce a global "off" switch.

Paul
3 years 11 months ago #53763

Please Log in or Create an account to join the conversation.

  • Posts: 57
  • Thank you received: 4
Thanks for the input. Which version of the driver are people using? Should I be using the nightly build?
3 years 11 months ago #53773

Please Log in or Create an account to join the conversation.

  • Posts: 57
  • Thank you received: 4
So I switched to the Ubuntu bleeding edge/ nightly build, and updated everything. I still can't see the control to adjust voltage for the variable voltage port. Am I missing something?
3 years 11 months ago #54325

Please Log in or Create an account to join the conversation.

  • Posts: 220
  • Thank you received: 27
It should be in the Power Tab under Adjustable voltage.
Can't check the box now but the c++ source says

IUFillNumber(&AdjustableOutputN[0], "ADJUSTABLE_VOLTAGE_VALUE", "Voltage (V)", "%.f", 3, 12, 1, 12);
IUFillNumberVector(&AdjustableOutputNP, AdjustableOutputN, 1, getDeviceName(), "ADJUSTABLE_VOLTAGE", "Adj. Output",
POWER_TAB, IP_RW, 60, IPS_IDLE);


and further

if (version == UPB_V2)
defineNumber(&AdjustableOutputNP);


so only in UPB_V2 (VB1 does no have the function?)

And that is there already for some time

P
3 years 11 months ago #54347

Please Log in or Create an account to join the conversation.

  • Posts: 1067
  • Thank you received: 140
Yes, the adjustable output works fine on mine...
3 years 11 months ago #54351

Please Log in or Create an account to join the conversation.

  • Posts: 57
  • Thank you received: 4
OK, I updated the UPBv2 firmware and it all works now. :woohoo:
3 years 11 months ago #54383

Please Log in or Create an account to join the conversation.

  • Posts: 57
  • Thank you received: 4
Now I'm getting consistent crashes every time I try to connect the Indi driver to the UPBv2.

Any ideas what the problem is?
[2020-06-16T14:04:02.082 EDT INFO ][           org.kde.kstars.ekos] - "Pegasus UPB" Version: "1.3" Interface: 32904 is connected.
[2020-06-16T14:04:02.082 EDT DEBG ][           org.kde.kstars.ekos] - 1  devices connected out of  3
[2020-06-16T14:04:02.983 EDT DEBG ][           org.kde.kstars.indi] - INDI Server:  "2020-06-16T18:04:02: Driver indi_pegasus_upb: terminate called after throwing an instance of 'std::invalid_argument'"
[2020-06-16T14:04:02.983 EDT DEBG ][           org.kde.kstars.indi] - INDI Server:  "2020-06-16T18:04:02: Driver indi_pegasus_upb:   what():  stol"
[2020-06-16T14:04:02.984 EDT DEBG ][           org.kde.kstars.indi] - INDI Server:  ""
[2020-06-16T14:04:02.984 EDT DEBG ][           org.kde.kstars.indi] - INDI Server:  "Child process 13009 died"
[2020-06-16T14:04:02.984 EDT DEBG ][           org.kde.kstars.indi] - Removing device "Pegasus UPB"
[2020-06-16T14:04:02.984 EDT DEBG ][           org.kde.kstars.indi] - INDI Server:  "2020-06-16T18:04:02: Driver indi_pegasus_upb: stderr EOF"
[2020-06-16T14:04:02.984 EDT DEBG ][           org.kde.kstars.indi] - INDI Server:  "<delProperty device=\"Pegasus UPB\"/>"
[2020-06-16T14:04:02.985 EDT DEBG ][           org.kde.kstars.indi] - INDI Server:  "2020-06-16T18:04:02: Driver indi_pegasus_upb: Terminated after #0 restarts."
[2020-06-16T14:04:02.985 EDT DEBG ][           org.kde.kstars.indi] - INDI Server:  ""
[2020-06-16T14:04:02.985 EDT CRIT ][           org.kde.kstars.indi] - INDI driver  "indi_pegasus_upb"  crashed!
[2020-06-16T14:04:03.011 EDT DEBG ][           org.kde.kstars.indi] - INDIListener: Removing device "Pegasus UPB"
[2020-06-16T14:04:03.012 EDT INFO ][           org.kde.kstars.ekos] - "Pegasus UPB is offline." [attachment=8072]log_14-03-45.txt

File Attachment:

File Name: log_14-03-...6-16.txt
File Size:19 KB
3 years 10 months ago #55663
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 57
  • Thank you received: 4
Sorry - I forgot to mention that one possibility is that I changed the variable voltage setting to '8.2' instead of '8' in the Indi driver. Looking at the windows UPB utility, it appears that it only can accept whole integers 1-12 (volts) - maybe related?
3 years 10 months ago #55664

Please Log in or Create an account to join the conversation.

  • Posts: 1067
  • Thank you received: 140

You also have the older 1.3 firmware, 1.4 has been out for a while, so you should update, on a windows machine....
3 years 10 months ago #55671

Please Log in or Create an account to join the conversation.

  • Posts: 220
  • Thank you received: 27
Hi,

even if you have set 8.2 the driver should send 8 to the box (formatted as integer, so will not send real numbers)
- How are you running Indi? Locally from Kstars (local) or with hostname (and webserver). Is driver tracting enabled? Don't see ant logs from commands to the box, so it looks as if the driver is not even starting correctly.
Did you do any Indi updates, because a mix of version can show such behaviour, also check if the settings file pegasus_upb.xml (in ~/.indi) is not corrupt.

Paul
3 years 10 months ago #55704

Please Log in or Create an account to join the conversation.

  • Posts: 57
  • Thank you received: 4
OK, so I updated Indi last night and now it seems to be connecting fine again. So it probably was a mixed version or corrupted file like PDB suggested. I will double check the firmware version, but I'm pretty sure I did update to 1.4 already. Maybe this was a symptom of a corrupted file also. Big thanks to you guys for helping!
3 years 10 months ago #55726

Please Log in or Create an account to join the conversation.

Time to create page: 0.670 seconds