Wim van Berlo replied to the topic 'Valid Alternatives to rpi3b+' in the forum. 2 months ago

+1 for the Rock64. I use it for indiserver and phd, and have just installed astrometry.net on it. I have it with a 32 Gb card, but would beed to upgrade to 64. I believe that I was one of the furst people to use thus sbc. There were a lot of issues in the beginning, but now it's well supported and very stable.
I use it with ubuntu 16.04

Read More...

Wim van Berlo replied to the topic 'Pegasus Focuscube has timeout errors' in the forum. 2 months ago

I did this when I tested with another power supply. It made no difference. The issue seems related to temperature.

Read More...

Wim van Berlo replied to the topic 'Pegasus Focuscube has timeout errors' in the forum. 2 months ago

This evening I tested the cube in my observatory. Again, it wouldn't connect. The only difference since yesterday is the outside temperature: -5 ... -7 C. Is it possible that the unit stops working in the cold? The cube even refused to be connected to the standalone controller on windows.

Does anyone have experience with this product in cold (sub zero) weather?

Read More...

Wim van Berlo replied to the topic 'SOLVED - Pegasus Focuscube has timeout errors' in the forum. 2 months ago

Tonight I took the telescope inside and removed the focuser. I then tested it with INDI, and it suddenly worked.
Now I've reattached it and it still works. I don't know exactly what happened, but my guess is that the focuser wasn't connected properly and the stepper motor had to work too hard, drawing current. This then caused the voltage to drop enough for the FTDI chip to stop working properly. I've had issues before with a too low voltage causing communication errors, so this is my best guess.
Hopefully it will also work outside in my obsy.

The configuration that works:
Rock64 with Ubuntu 16.04
INDI 1.7.5 stable release
Clients: Ekos/Kstars on Rock64 and on Windows, PixInsight INDI client on Windows
(no USB hub)

Read More...

Wim van Berlo replied to the topic 'Pegasus Focuscube has timeout errors' in the forum. 2 months ago

That's one option I haven't really tried yet: connecting through a powered hub. I was hoping to avoid that; one more power connection needed.
When I connect to a raspberry pi, I get fewer timeouts than with a rock64. Also a speed of 19200 works. More testing.

Read More...

Wim van Berlo replied to the topic 'Pegasus Focuscube has timeout errors' in the forum. 2 months ago

In the ekos controlpanel where you connect to indi, in the connection tab, you need to enter the port as /dev/focus (or whatever you called it). Then disable port scanning, and save the configuration. (Options tab, I believe. I'm not at my computer right now.)

Read More...

Wim van Berlo replied to the topic 'Pegasus Focuscube has timeout errors' in the forum. 2 months ago

You need to make sure that there can be no port conflict between your mount and the cube. Both have an ftdi usb serial chip.
Here's what I did
indilib.org/forum/focusers-filter-wheels...just-a-heads-up.html
It allows you to connect both eqmod and focuscube.

Read More...

Wim van Berlo replied to the topic 'Pegasus Focuscube has timeout errors' in the forum. 2 months ago

Yes, I've seen that list. Unfortunately it's for the upb driver on indigo. The focus cube is supposed to be supported by the new indi library. Also, the cube connects, and does get som data over, but then it just keeps timing out.
I checked if it could be a power problem, so I replaced my power box (Meanwell 12 V poser supply with enough amps) with a wal adapter. Also replaced the usb cable, in case that was faulty. No luck.
When I first tested the focuscube, it worked. But then it suddenly stopped. The only thing different that I can think of is that I updated the nightly build.
Anyway, I have uninstalled the nightly build, and reverted to the latest stable build, since that has focuscube support. Now I just need to check if this works. Will do that tomorrow.
I also have a Raspberry Pi lying around, which uses armhf. Will see tomorrow if that works. Otherwise I'm completely out of options.
In the mean time, I've also contacted Pegasus Astro. Maybe they have a sollution.

Cheers,

Read More...

Wim van Berlo created a new topic ' Pegasus Focuscube has timeout errors' in the forum. 2 months ago

I've run into problems with my Pegasus Focuscube.
I can connect to it from Ekos (Windows, Indi on Rock64), but all I get is timeout errors after connecting. The focuser may get a temperature reading, but other than that it's completely unresponsive.
Here's my setup:
Ekos on Windows (I have also tried Ekos locally)
Indi on a Rock64 (arm64) with Ubuntu 16.04
I use the nightly build for indi: 1.7.5 from nov 18
I also have an eqmod mount connected, but I have tried without the mount (only focuser) without any difference.
The usb cable is connected directly to the sbc, no hubs used.
Symbolic names for the usb ports: /dev/focus for the focuser and /dev/telescope for the mount
The mount connects fine when I use this symbolic name in Ekos, but the focuser doesn't. It needs the proper ttyUSB name (/dev/ttyUSB0 on my latest try), and no port scanning. Any other setting and it won't connect.
Under these settings the focuscube will connect (although it may take 2 tries)
After that I only get GetFocusParams timeout errors.

Does anybody have a sollution for this? Is it a timing problem somewhere?
I tried to set the baudrate to anything other than the standard 19200 b/s, but that won't let me connect at all.
Btw, when I check the device with indi_getprop two things can happen:
1. when the mount is also connected (and simulator ccd), the focuser doesn't even show up in the properties list
2. when only the focuser is connected, this is (some of) the listing

Pegasus DMFC.CONNECTION.CONNECT=Off
Pegasus DMFC.CONNECTION.DISCONNECT=On
Pegasus DMFC.DRIVER_INFO.DRIVER_NAME=Pegasus DMFC
Pegasus DMFC.DRIVER_INFO.DRIVER_EXEC=indi_dmfc_focus
Pegasus DMFC.DRIVER_INFO.DRIVER_VERSION=1.0
Pegasus DMFC.DRIVER_INFO.DRIVER_INTERFACE=8
Pegasus DMFC.DEBUG.ENABLE=On
Pegasus DMFC.DEBUG.DISABLE=Off
Pegasus DMFC.POLLING_PERIOD.PERIOD_MS=500
...
Pegasus DMFC.CONNECTION_MODE.CONNECTION_SERIAL=On
Pegasus DMFC.CONNECTION_MODE.CONNECTION_TCP=Off
Pegasus DMFC.DEVICE_PORT.PORT=/dev/ttyUSB0
Pegasus DMFC.DEVICE_BAUD_RATE.9600=Off
Pegasus DMFC.DEVICE_BAUD_RATE.19200=On
Pegasus DMFC.DEVICE_BAUD_RATE.38400=Off
Pegasus DMFC.DEVICE_BAUD_RATE.57600=Off
Pegasus DMFC.DEVICE_BAUD_RATE.115200=Off
Pegasus DMFC.DEVICE_BAUD_RATE.230400=Off
Pegasus DMFC.DEVICE_AUTO_SEARCH.ENABLED=On
Pegasus DMFC.DEVICE_AUTO_SEARCH.DISABLED=Off
Pegasus DMFC.DEVICE_PORT_SCAN.Scan Ports=Off
Pegasus DMFC.SYSTEM_PORTS./dev/ttyUSB0=Off
Pegasus DMFC.SYSTEM_PORTS./dev/ttyUSB1=Off

Any help would be appreciated

Read More...

Wim van Berlo replied to the topic 'Pegasus FocusCube and Eqdir - just a heads up' in the forum. 2 months ago

This turned out to be a short fix. Atm I can't connect using the symbolic name, and using the usb device name (/dev/ttyUSB0) connects, but results in timeout errors.
I'll start a new topic for this, and contact pegasus.

Read More...

Wim van Berlo replied to the topic 'Pegasus FocusCube and Eqdir - just a heads up' in the forum. 2 months ago

AstroNerd wrote: Very strange, now that the new driver is available for the Pegasus UPB I have been using that, which also has the FTDI chipset for the focuser part, and I also use a FTDI EQMOD cable, and yet no such issues at all....It just worked straight away, wonder why this works and the focus cube did not..
Anyway glad you sorted.... :) :)

Is that driver included in indi? I use the one that is included. The only thing I did to get the focuser working, was installing the nightly build. When I went back to the stable release after the port "assignment", it stopped working.

Read More...

Wim van Berlo created a new topic ' Pegasus FocusCube and Eqdir - just a heads up' in the forum. 2 months ago

I recently bought a Pegasus Focuscube to replace my simple DC focus motor / Arduino homebuild. Installation went fine, and worked with the simulator telescope. But when I had the chance yesterday to connect it to my AZ-EQ6 (Eqdir) telescope, I got timeout errors and the focuser didn't work.
It turned out that the focuser uses a FTDI usb chip, the same as my eqdir cable. This causes a conflict in USB ports.
This is how I fixed it:
I created a new rules file in /etc/udev/rules.d called 99-usb-serial.rules
The file contains two lines:

SUBSYSTEM=="tty",ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001" SYMLINK+="telescope"
SUBSYSTEM=="tty",ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6015" SYMLINK+="focus"

(Note that for this to work, you need to enter the correct vendor and product ID. If these aren't unique, you may need to add some sort of serial number. Anything so you can differentiate between the eqdir and focuser.)
Then I updated the rules:

sudo udevadm trigger

Rebooted the mount computer (Rock64), just to reset everything, and started indi

indiserver -v indi_eqmod_telescope indi_dmfc_focus indi_asi_ccd indi_asi_wheel

Connected to the drivers from Ekos/Kstars on my windows machine, started up indi and connected. In the Connection tab of the focuser I set the usb port as

/dev/focus

and in the Connection tab of the mount (telescope) I set the usb port as

/dev/telescope

Then save the configurations.
Done.

I hope this can be of use to someone.

Read More...

Wim van Berlo replied to the topic 'Re:Ekos plate solver woes' in the forum. 3 months ago

I used to have a time out problem to. I solved it by decreasing the search radius. If you know that the scope is close to the target, decreasing the search radius can help.
Just a thought.

Wim

Read More...

Wim van Berlo replied to the topic 'subpixel accuracy - autoguiding' in the forum. 4 months ago

If you set the correct FL and pixel size in your guider software, guiding error will be displayed in arcsevonds. Otherwise it will be displayed as pixels.
I'm not aware of any books, specific on guiding. Two general books on astrophotography are
Making Every Photon Count, by Steve Richards, and
Long Exposure Astrophotography, by Allan Hall.
A good online resource is Craig Stark's website:
www.stark-labs.com/craig/articles/articles.html
Stark is the original developer of PHD guiding software.
As for best guiding fl, a general rule of thumb is that the guiding pixel scale shouldn't be more than about 2 times the imaging pixel scale. In practice, if your guiding is too coarse, you can't get good pictures, while if it's too fine, you'll be guiding the noise.
Hope this helps.

Read More...