Rolf Meyerhoff replied to the topic 'Supporting development, buying stellarmate os?' in the forum. 4 weeks ago

Cool, I didn't know that the OS could be bought separately. I've always stepped back from SM because I already have more than enough neglected Raspis in my drawer. Now it's actually an option for my next build. :)

Read More...

Rolf Meyerhoff replied to the topic 'USB3 may force me to move off of Raspberry Pi' in the forum. 5 months ago

Maxchess wrote: ROCKPro64 2x2 MIMO Dual Band WIFI 802.11AC/BLUETOOTH 4.2 MODULE $15.99


I've read that this module will only work with Android and not with the typical Linux distributions. I don't know how old this message was so please report back if it works or not.

This was really putting me off because I need an ethernet port to control my mount and I don't want to add a switch or hub on top.

Read More...

Rolf Meyerhoff replied to the topic 'Initialization of Sesto Senso' in the forum. 5 months ago

Great work. Thank you very much. B)

Now I just need a way to fix the compatibility issues between the weather conditions and my available spare time. :(

Read More...

Rolf Meyerhoff replied to the topic 'USB3 may force me to move off of Raspberry Pi' in the forum. 5 months ago

I have a cooled ASI 294MC Pro and I tried it on the Raspi with USB2 and on an Intel NUC with USB3. I didn't see any difference in image quality but the speed difference was enormous. I still use the Raspi because it's light, compact and has enough USB ports for my needs. The NUC plus USB hub would be too much for my mount.

The Rock64Pro looks like a good alternative, especially because it runs on 12V power and it has an RTC.

Read More...

Rolf Meyerhoff replied to the topic 'Initialization of Sesto Senso' in the forum. 5 months ago

Thank you very much. :)

I have the original probe for the Sesto Senso. I agree that it is a bit overpriced but it is delivering very reasonable temperature values. The major downside for me is the long cable (~1m). I had to wrap it around my scope several times to get out of the way.

Read More...

Rolf Meyerhoff replied to the topic 'Initialization of Sesto Senso' in the forum. 5 months ago

I've debugged the code and the problem is in the TimerHit() method. The temperature frequency counter is increased and then compared against the update frequency. When they match then the temperature is updated. In this case it only works once as the counter is never set back to zero. I've added the last line in the if statement and now it works as expected:

    if (m_TemperatureCounter++ == SESTO_TEMPERATURE_FREQ)
    {
        rc = updateTemperature();
        if (rc)
        {
            if (fabs(lastTemperature - TemperatureN[0].value) >= 0.1)
            {
                IDSetNumber(&TemperatureNP, nullptr);
                lastTemperature = TemperatureN[0].value;
            }
        }
        m_TemperatureCounter = 0;  // <- Was missing.
    }

Maybe someone with access to the repository can add this to the code .

Read More...

Rolf Meyerhoff replied to the topic 'Initialization of Sesto Senso' in the forum. 6 months ago

Maybe it is the ";" that is causing the issue? The GoTo command doesn't need them either.

Read More...

Rolf Meyerhoff replied to the topic 'Initialization of Sesto Senso' in the forum. 6 months ago

I've tried to take INDI out of the equation for a while and communicated with the focuser just with a terminal (screen in my case).

After a fresh boot without INDI the focuser behaves the same as we've seen it here in the thread: #GT10000! moves inward.

I've recalibrated the focuser again under Windows and reconnected it to the Raspi. When I sent a #GT10000! then the tube moved outward as it should.

Now I started INDI and the focuser moves inward again. Not just in INDI but also in the terminal.

It seems like INDI is doing something that the firmware of the Sesto Senso doesn't like at all.

Read More...

Rolf Meyerhoff replied to the topic 'Initialization of Sesto Senso' in the forum. 6 months ago

Thank you for the commands. I've looked at the code of the driver and at a first glance it doesn't do anything fancy. The driver just passes the position to the device as it is so it should just work. And the result of position query suggests that it indeed works fine, so #QP! is equal to #GT! Just the physical rotation direction of the motor is wrong.

So I think that there is either a reverse switch missing somewhere or the driver needs weird commands (like negative positions) when reversed. Maybe I will attach Wireshark to my Windows/Sesto Senso setup later to see what the driver is doing there.

Read More...