tekkydave

In case anyone is unaware of AppImage and how it works see this explanation.

Is it set executable in its permissions?

Just had a look at the github site. If you download the file with the .AppImage extension it should run by double-clicking directly on the file.

Strange - they seem to have removed the old Slic3r PE downloads. Looks like its now up to your Linux distro's maintainer to provide a packaged app. Or , as you say compile it yourself. Shouldn't be a problem if you have all the dev tools installed.

You may have downloaded the sources by mistake. There is a compiled application on the prusa slic3r website Here

Have a look at persistent-serial-port-mapping on the indilib.org site. I have made it work with my mount so it always appears as /dev/mount regardless of which port it is plugged into. I dont know if it will work with 2 ZWO cameras but worth investigating.

For PETG I generally use 250C extruder and 80C bed. No cooling fan except for bridges. I was under the impression that cooling was not good for PETG. Also dont 'squish' the first layer too much like you would with PLA.

How long do the PEI sheets last and are they easy to remove & replace.

Make that +2 The main thing to obtain when getting in to 3D printing is a huge box of patience

Ha ha - we were watching BH whilst having our lunch.

I guess the answer is good ol' experimentation 🙂

Anywhere in the open where it wont get dripped into should be good.

I've not posted in this topic for about 2 1/2 years, however: I have recently installed Indi on the new Rapberry Pi 4 and suprise - the ASI120MC works fine with it now. Whether this is due to improvements in the Pi hardware/firmware, OS (Raspbian) or Indiserver who knows but it's working now. I'm in half a mind to start tinkering with Astronomy again 🤯 😮

Maybe I'll ask on the INDI forum.

What device do you remote in from? If it's a PC then it makes sense to me to run the resource-heavy parts locally and just have the pi controlling the hardware. It's a personal choice, I suppose and determined by how and where you are connecting from.

It's all Ascom and Indi compliant. The issue is to do with doing the initial alignment remotely. I don't have an obsy so the scope has no alignment when it is first powered up. The starsense accessory will do this for me automatically but it needs to be initiated from the HC. Everything else works remotely just fine. I don't think the mount can be aligned fully by the plate-solving in Indi. In celestron SLT a-z mounts the pointing model is held in the HC which has to remain connected to the mount.

It got hot during the compilation but that only lasts a few minutes. I don't run Kstars/Ekos on the pi. I access the pi remotely from a PC running Ubuntu 19.04. I haven't found a way of getting full remote operation of my scope yet (Nexstar SLT alt-az). I have the Starsense camera which does the initial align automatically but this can only be initiated from the HC or Celestron's CPWI application. CPWI only runs on Windows and needs either a USB, Serial via HC, or WiFi via their own device (SkyPortal).

If you follow the instructions here you can install indilib on a pi from the source code. I have it installed on a pi4 using the latest Raspbian (Buster).

Some things I have discovered about the new Pi 4: There is currently NO version of Ubuntu / Ubuntu Mate that will run on it. You will need to stick at Pi 3B+ for now if you want an easy install route. Raspbian Buster is the only Raspbian version that will run on it. Not an issue in itself but I tried installing the version from the indilib website and got piles of errors. I think their release expects Raspbian Jessie which will not run on the Pi 4. I have managed to install the latest release of indilib on a Pi 4 running Buster by compiling from source. Follow the instructions on the github page at the link. I haven't compiled any 3rd party drivers as yet. I have installed KStars/Ekos on my Ubuntu 19.04 PC and can connect to the Pi 4 remotely no problem. If I can compile the 3rd party drivers I need for my scope (Celestron Nexstar) and get a focuser driver going I should be good to go. I have used the Astroberry focuser in the past and it works ok. I even have the electronics for it already built from a Previous experiment with an RPi remote controller Update - the celestron driver seems to be already compiled & ready to run on the Pi 4: indiserver -vv indi_simulator_ccd indi_simulator_focus indi_celestron_gps

I have a 2Gb version on order from PiHut. One thing to watch out for is the USB-C power inlet and the micro-HDMI monitor connectors.

Just checked my config.g and mine is 100 so the pulleys must be 16T.

My D-Bot uses 20t pulleys. Check your steps/mm is still correct.

Swap them over and see if the shape is different.

Hmmm, looks like a problem with the printer. Either the frame isn't square (unlikely) or belt tensions are unequal.

You need to isolate where the problem is - Duet or printer. Lift the belts off the motors and make a pencil mark on each spindle. Then use the UI to make a fixed move in X or Y. Both motors should move the same as it is a diagonal move. If they move the same then the issue is with the printer, otherwise with the Duet.