Gesendet: Montag, 24. Februar 2020 um 08:11 Uhr
Von: "François Desvallées" <fdesvallees@...>
An: TeenAstro@groups.io
Betreff: Re: [TeenAstro] Building from Sources and Configure for Motors and Motor Controllers?

Hi Lukas:

I use Linux too, welcome to the community!
One of the nice things about TeenAstro is that most parameters can be changed at run time, so a single binary will work for most configurations. The exception is the stepper driver: You need to choose either 2130 or 5160 for the main unit. Also, (in the beta only), the SHC has one binary per language (French, English, German). If you only use english, then you need a single binary.

Now to change the runtime parameters, the easiest by far is to use the web server provided by the SHC. Just point your browser to the SHC's IP address, and change motor speed etc. It will be stored in EEPROM and you never need to worry about it unless you change the software version.

Another possibility is TeenAstroConfig, which is Windows-only. I started writing a Python program with the same functionality. It is not quite finished, but I can work on it if you need.

Concerning the LX200 commands that are supported, have a look at this: https://groups.io/g/TeenAstro/attachment/965/0/TeenAstro%20INDI%20device%20driver.pdf

I advise to use the exact hardware, including motors, described in the project pages, because it works fine "out of the box". You can try to change later.

Hope this helps
François






> On 23 February 2020 23:21 luzilu@... wrote:
>
>
> I already posted that I had assembled a TeenAstro Mini and it looks like working.
>
> As I am a Linux guy and want to be able to hack on the software, I don't want to use the prebuilt firmwares and cannot use the flashing tool for Windows.
> No problem so far, as I already have the Arduino IDE installed and the installation of the Teensyduino extension ran smoothly. I can compile (with only one warning about "enumeration value 'NODRIVER' not handled in switch") the current github head and flash it to the Teensy.
>
> Now a few questions arise regarding building from source and setting up for the mechanical properties of the telescope mount (by not using Windows, I cannot use TeenAstroConfig.exe, which aside from that, seems to be closed source):
>
> I had set CPU speed to 72MHz and Optimize to "Faster", is that right?
> As there is no other branch nor any tag set, I used the git master head; is that reasonable for trying out?
>
> I dug into the sources a bit and it seems that the only compile time configuration is in "Pins.TeenAstro.h" and it seems that all is already set up correctly there, for the TeenAstro Mini with TMC5160 drivers out of the github master head. Am I correct with that?
>
> All of the other configurations can be made via LX200 and are stored in EEPROM, is that correct?
>
> I played around with the settings that can be done via LX200 protocol. For this I browsed through the sources implementing the LX200 command processing. This is a bit tedious and the commenting is not always clear enough for me to understand right away, what the command parameters represent.
> So another question is, whether there exists a list of the supported LX200 commands, comparable to the one about OnStep (http://www.stellarjourney.com/index.php?r=site/software_telescope)?
> If there is not, I would consider to compose such a list, but I probably needed help with some of the commands.
>
> For playing around, I have connected a stepper motor to the TeenAstro and I can turn the shaft by M-commands, but the turn is very slow and the motor gets quite hot even when standing still. By increasing the $G setting I can increase the turning rate, but still it stays quite slow.
> From what I can see in the sources, according to the comments, the command "SXE1" should "Set the MaxRate in sideral Speed" but there is no code executed at all on decoding that command.
> There seems to be an acceleration/deceleration ramp when commanding a move, but the ramp is very slow, maybe a minute or so. I would expect a ramp up/down in a few seconds.
>
> To summarize: I do not understand, what to do for that motor to work properly. Maybe I have a totally inadequate motor?
> I hope that somebody can give me some hints on what could cause the observed motor behaviour.
>
> By the way, I tried with the INDI driver as well and can observe the exact same unexpected behaviour.
>
> thank you and best regards
> Lukas
>
>