Date   

Re: Parking

Khalid Baheyeldin
 

Then, what you are seeing should not be "forgetting to set the time/date before unparking", a question that we get sometimes.

Two other possibilities:

1. There was a bug in Parking where the EEPROM would get into a state where unparking cannot be done. A kind of a loop. This is fixed in the latest 3.16, so try upgrading to that, if you were able to park but now you can't. You need to redo the configuration to be the newer (and much better) format.

2. You are trying to park in the Astro-Physics Park 5 position. This position has the advantage that you can use a bubble level to recreate it. People use it for portable mounts to have as much accurate alignment as possible. I am not sure if that position is valid as a parking position as far as OnStep is concerned. We've had discussions previously on it with users saying they can't park like that. However, I can't remember if these queries were answered positively or not. Howard will advise here. A simple test you can do is use another parking position, near (but not at) the celestial pole, and see if your mount accepts that and works normally.


Re: User focuser on SHC and

Jamie Flinn
 

Yup….it is also more finely grained with the large range of steps per micron…once you get the initial steps for autofocus in the right range for your motor it is very exacting

I have started making universal connections to my different “focusers” (one is Nema 14…two other are tincan stepper with gearbox liberated form old Celestron CG5)

 

 

 

From: main@onstep.groups.io On Behalf Of Khalid Baheyeldin
Sent: Friday, July 17, 2020 1:14 PM
To: main@onstep.groups.io
Subject: Re: [onstep] User focuser on SHC and

 

The nice thing about OnStep with INDI is that the focuser just works.
With ASCOM, it requires going through hoops, like POTH to multiplex the connection for the same controller.
INDI's design allows multiple connections to the same driver from different programs.


Re: Failed to init device yet again

Khalid Baheyeldin
 

Here is another long shot at this ....

Compile the blink sketch, then note where the blink.ino.bin file is from the output of the IDE.

Copy that file somewhere.

Download the STM32 Windows Flasher from here https://www.st.com/en/development-tools/flasher-stm32.html

Place the jumper in the FLASH position.

Then using the Windows Flasher, try to flash the above blink.ino.bin, and see if
a) flashing is successful
b) the LED on the STM32 flashes (or not).

I am trying to side step the IDE as the flashing method.


Re: User focuser on SHC and

Khalid Baheyeldin
 

The nice thing about OnStep with INDI is that the focuser just works.
With ASCOM, it requires going through hoops, like POTH to multiplex the connection for the same controller.
INDI's design allows multiple connections to the same driver from different programs.


Re: Failed to init device yet again

Gerry Byrne
 

Drew,
re-installed OnStep, preserved the Config.h file. No change.
Gerry

On 17/07/2020 14:33, Drew 🔭📷🚴 ♂ wrote:
Let me know what redoing OnStep does, that is the next step. Do that and only that so we can control the variables.


--
Copernicus


Re: OnStep from Instein.eu

George Cushing
 

There is a group https://groups.io/g/InsteinOnstepDrive but I see no messages or other activity. 

Pretty sure Instein's controllers were all Mega2650 based. If my experience with the success of the OnStep concept means anything. Instein could have easily got over-whelmed with orders.

I accepted Khalid's offer to take over distribution of the STM32 kits last August or September. Since then over 260 STM32 PCBs have left here. Most were complete kits may 20 PCBs only and a dozen assembled. Knowing China likes to go away for a month during Lunar New Year I had built up my parts inventory before Covid hit. But I went though that in about 7 weeks and the supply chains have only just started to function again. Just got a some pulleys order about 5 months ago.

I had also built up a small inventory of parts for the MiniPCBv2 as due to an error in a PCB order I had 150 PCBs for them. My mistake turn into a blessing as it gave me something to offer folks during the drought. As the Teensys come from PJRC a U.S. supplier, I can get an order filled in 3-4 days. I usually order 10 at a time. They last about the same number of days. Somewhere between 30-35 have gone out.

I'm shipping STM32s again, but keeping the RTCs in stock is touch and go. I have a pending order made May 13 from OZ with DHL shipping, don't have any idea where that is. Another pending since 6/23 that's still in China and one that was made 7/2 that's 30 miles down the road. so it's safe to say orders are arriving in inverse order of the dates they were made. Jia Li Chuang, which supplies the PCBs has never faltered to deliver in under 10 days.


Re: User focuser on SHC and

Jamie Flinn
 

Once you have the focuser motore operating via the app…in INDI you can UNCONFIGURE any prevous focuser and then juts select the Onstep one listed in the focuser tab (do not add in profile – it juts comes along fo re ride with the mount)

 

 

From: main@onstep.groups.io On Behalf Of Frans Lowiessen
Sent: Friday, July 17, 2020 9:42 AM
To: main@onstep.groups.io
Subject: [onstep] User focuser on SHC and

 

Hello.

I finally got my SHC 1.8f working with onstep 3.16i I turned out to be a defect STM32 after replacing and flashing everything works fine.
See https://onstep.groups.io/g/main/message/20800 for the reason we already thought it was broken, but it took some time to get the STM32

But there is always a next thing ;-)
O connected a stepper motor to Axis 4 but how can I control this motor to for focuser
IS there some kind of indilib driver for this focuser ?

Cheers Frans


Re: Problem connecting to wemos d1 mini pro with android devices

Drew 🔭📷🚴‍♂️
 

On Fri, Jul 17, 2020 at 10:17 AM, Howard Dutton wrote:
The master branch has been reverted to the WiFi initialization
All of this is under WiFi 1.14.b? Do we need a patch level increase?


Re: Problem connecting to wemos d1 mini pro with android devices

Howard Dutton
 

On Wed, Jul 15, 2020 at 09:56 AM, Howard Dutton wrote:
I'm getting to the point where I don't like either change and may very well revert to the original design.
Hopefully with disconnect calls early in the boot so users don't get to join the AP before they should.
The master branch has been reverted to the WiFi initialization order as used with release-3.16 (and 2.22 I'm pretty sure.)  It seems to be the most trouble free overall.

I also added the early disconnect at startup since I feel there are some troubles and confusion caused by connecting to the WiFi before it's really ready.
With the prior design the WiFi/SSID comes up immediately and looks good when powered on but the ESP hasn't connected to OnStep yet and the WiFi mode will still be re-configured later.  When it does that re-configuration anything that's connected remains connected but stops working.

Now at boot it turns the AP mode off/disconnects so there is nothing to connect to until it's ready.  So, with this change as soon as you see the OnStep SSID it's good to connect to.  As for the ESP libraries it's 2.7.2 with possible fixes but not well tested/proven vs. the tried and true version 2.4.2 take your pick.  Other versions exist but these are the two most trusted ones as far as I'm concerned.


User focuser on SHC and

Frans Lowiessen
 

Hello.

I finally got my SHC 1.8f working with onstep 3.16i I turned out to be a defect STM32 after replacing and flashing everything works fine.
See https://onstep.groups.io/g/main/message/20800 for the reason we already thought it was broken, but it took some time to get the STM32

But there is always a next thing ;-)
O connected a stepper motor to Axis 4 but how can I control this motor to for focuser
IS there some kind of indilib driver for this focuser ?

Cheers Frans


Re: SHC with OLED 0.9" no display

Dave Schwartz
 

Aside from the first being in mixed case and the other two being spelled incorrectly (and I hope they are not also commented out as you have in your message), the SSD1306 should work as long as the pins on the display module are in the correct order.

The pin order of most modules I have seen is GND/VCC/SCL/SDA but there are some with VCC/GND/SCL/SDA order.

You don't say what type of SHC it is, ESP32-based or Teensy-based. The ESP32 can accommodate either order by using the jumpers on either side of the display connector (the paragraph in the ESP32 SHC Assembly instructions https://docs.google.com/document/d/1Yqapj0lpiI2ryzUzsBS99wqcaYcddTj4RX0LUBaBIEE/edit?usp=sharing above the picture of the PCB with these jumpers circled in red tells you how). The Teensy-based SHC can only use modules with the GND/VCC/SCL/SDA order although some modules that have the other order can be changed to this order by rearranging some soldered jumpers on the back.

On 2020-07-17 3:15 a.m., Kokoro San wrote:
Hi guys.. was adding OLED 0.96" SSD1306"  display was not light up, but the ESP32S is able to upload code and it also have red light ones ST4 was plug in to Onstep. any idea what missing...

//define Display_OLED  SSD1306
//define SERIAL_INTERFAE  SerialST4
//define SERIAL_BUD_DEFAULT 9600


Re: Failed to init device yet again

Drew 🔭📷🚴‍♂️
 

Let me know what redoing OnStep does, that is the next step. Do that and only that so we can control the variables.


Re: Failed to init device yet again

Gerry Byrne
 

Drew,
Driver Tab and Driver File Details Tab attached.
Gerry


On 17/07/2020 13:18, Drew 🔭📷🚴 ♂ wrote:
Redoing the OnStep directory is the first thing you should have done. Save your Config.ino file in a safe place and delete the OnStep directory. Download and unzip the latest OnStep Master and install it to the Arduino directory. Rename the directory to OnStep and copy your saved Config.ino over the existing one. That is all you should need to do.

There are several versions of the CP210x driver out there. Please do  a screen shot of the driver tab. There are some issues with specific chips and driver versions.

You should not ever need to fool around with the speed settings, restore them  to default. The driver migration message and the incomplete installation messages may or may not be part of the problem. Often with Windows 10 these errors just indicate problems with the driver writers following Windows 10 code methods and the drivers are fine.

Do the above, we are getting there.


--
Copernicus


Re: Failed to init device yet again

Drew 🔭📷🚴‍♂️
 

BTW, the file is config.h not config.ino. Brain fart.

I wouldn't do any of that. I don't think you need to reinstall the Adduino IDE just yet. It is very time consuming and probably not the problem. Going back to Windows XP is not advised, ever with this hardware or software.


Re: Failed to init device yet again

Gerry Byrne
 

Drew,
Thanks, I'll get down to that now. BTW, if I have time I was also going to install Arduino and Onstep on an old Laptop and try flashing from that as a way of eliminating hardware problems in my newer (or should I say, less old!) laptop. Will that combo work on Windows XP?
Gerry

On 17/07/2020 13:18, Drew 🔭📷🚴 ♂ wrote:
Redoing the OnStep directory is the first thing you should have done. Save your Config.ino file in a safe place and delete the OnStep directory. Download and unzip the latest OnStep Master and install it to the Arduino directory. Rename the directory to OnStep and copy your saved Config.ino over the existing one. That is all you should need to do.

There are several versions of the CP210x driver out there. Please do  a screen shot of the driver tab. There are some issues with specific chips and driver versions.

You should not ever need to fool around with the speed settings, restore them  to default. The driver migration message and the incomplete installation messages may or may not be part of the problem. Often with Windows 10 these errors just indicate problems with the driver writers following Windows 10 code methods and the drivers are fine.

Do the above, we are getting there.


--
Copernicus


Re: Failed to init device yet again

Drew 🔭📷🚴‍♂️
 

Redoing the OnStep directory is the first thing you should have done. Save your Config.ino file in a safe place and delete the OnStep directory. Download and unzip the latest OnStep Master and install it to the Arduino directory. Rename the directory to OnStep and copy your saved Config.ino over the existing one. That is all you should need to do.

There are several versions of the CP210x driver out there. Please do  a screen shot of the driver tab. There are some issues with specific chips and driver versions.

You should not ever need to fool around with the speed settings, restore them  to default. The driver migration message and the incomplete installation messages may or may not be part of the problem. Often with Windows 10 these errors just indicate problems with the driver writers following Windows 10 code methods and the drivers are fine.

Do the above, we are getting there.


Re: Has anyone put Onstep on a Losmandy AZ8?

Christoph Frommen
 

John,

yes, the motors are bolted directly on to the end of the worms. No additional pulleys or belts needed.The kit is  supplied by instein Astro this way.
When I turn in Azimuth the two motors don't manage to clear each other. I will have a look if I can rotate one of them slightly so that the plastic cover doesn't protrude so much. I will have to drill new holes in the plastic though but maybe this will help. Good luck with your project.

Regards
Christoph


Re: Failed to init device yet again

Gerry Byrne
 

Guys,
 I'm at a loss what to try next, apart from re-building the Onstep software.

I think I would like to eliminate potential technical problems first. For example, see the pictures of the Properties of my CP2101. I re-installed the drivers (again) and, even though properties (via Device Manager)  says the device is working perfectly (Pic1), looking under other headings appears to tell a different story.

(Pic2) Events tells me the device needs further installation and scrolling through the history here shows several instances of "device not migrated". (I re-installed this driver several times).

(Pic3) shows I have adjusted the Transmit and Receive settings downwards in an effort to achieve connection, to no avail. Is the FIFO setting correct? Under Power Management (no picture) the setting for turning this device off to save power remains unticked.

You guys are being really patient with me. I appreciate that very much.
Gerry






On 17/07/2020 00:54, Drew 🔭📷🚴 ♂ wrote:
On Thu, Jul 16, 2020 at 07:23 PM, Gerry Byrne wrote:
get exactly the same as it Pic1 earlier. The little box saying unknown board comes up.

Yes , that is what we want. The contents are immaterial, its presence tells us that the Arduino IDE is talking  to the chip. The bottom line is just showing you the hardware device that you selected. Change the device and it will change to match your selection.


--
Copernicus


SHC with OLED 0.9" no display

 

Hi guys.. was adding OLED 0.96" SSD1306"  display was not light up, but the ESP32S is able to upload code and it also have red light ones ST4 was plug in to Onstep. any idea what missing...

//define Display_OLED  SSD1306
//define SERIAL_INTERFAE  SerialST4
//define SERIAL_BUD_DEFAULT 9600


Re: Problem connecting to wemos d1 mini pro with android devices

Tong
 

The HUAWEI P30pro Android 10 problem has not been solved. P30pro can normally connect to Onstep and obtain the IP address. When opening Sky Safari and Onste app, it is reported that the connection failure cannot obtain the IP address.Another HUAWEI Honor 8 Android 8.0 made 4 years ago can be used normally.Same problem with P30pro Onstep and TeenAstro.