Date   

Re: MaxPCB V2 information

Gianluca Galloni <gianluca.1997.29@...>
 

Hi everyone, forgive the absence but I was sick.
Before answering all the tests you have done in the meantime we have another problem, we have installed the latest version of the indi drivers and we no longer have the problem of delay, unfortunately another problem with the declination engine was born: when I click to sending it north sometimes goes north and others south, does the same thing when we try to send it south.
We have already checked the connections and tested the driver and everything is working properly, so it seems like a software problem.


Re: Current beta config file changes..

John Scherer
 

Thank you Khalid, That tells me what I need to know and where to look if I want more ;-)


Re: Current beta config file changes..

Khalid Baheyeldin
 

On Sun, Aug 25, 2019 at 11:01 PM, John Scherer wrote:
First, I don't see "Define MaxRate" anywhere. 
The MaxRate is now calculated internally depending on the microcontroller used.
You can still specify MaxRate, so your configuration is backward compatible.

I also see "define STEP_WAVE_FORM SQUARE". 
This is one of the 'exotic' parameters that you would not really need.

They were discussed in this thread

https://github.com/hjd1964/OnStep/issues/106

Howard tested it and it worked, but I never bothered to. Not sure if anyone else tried it to see if there is tangible improvement.

I'm sure there are other new settings, but I can't seem to find and posts mentioning these changes.  Are the new features in the current beta documented anywhere?
Not really.

But you can get a list of all the changes using the command in the Changelog section on the project page

https://github.com/hjd1964/OnStep


Current beta config file changes..

John Scherer
 

I downloaded the current (as of today) beta and  I'm noticing some changes to the Config_MaxPCB.h file.  First, I don't see "Define MaxRate" anywhere.  I also see "define STEP_WAVE_FORM SQUARE".  I'm sure there are other new settings, but I can't seem to find and posts mentioning these changes.  Are the new features in the current beta documented anywhere?


Re: MaxPCB V2 information

James Lancaster
 

It is an issue with forks, and if you guys can try this out: https://github.com/james-lan/indi/tree/OnStep It should show as version 1.8 of OnStep, and not have issues. If it does, can you please enable mount logging and report it on the INDI forum?

Once I get verification that it's good, then I'll see about pushing that up to the main INDI repository.

On Sun, Aug 25, 2019 at 3:27 PM Khalid Baheyeldin <kbahey@...> wrote:
On Sun, Aug 25, 2019 at 04:23 PM, Wayne Hilliard wrote:
A fork.
I think we are getting somewhere finally.

It seems the latest indi-bin package 1.8.0 introduces a bug for mount
types other than equatorial.

For the sake of verifying my theory, change this:

#define MOUNT_TYPE_FORK

To

#define MOUNT_TYPE_GEM

Then try again and see if there is a delay.

If there is none, then a fix is needed in INDI for this case.

ASCOM is not affected.


Re: Can´t Connect to Onstep STM32

Kevin Dorsey-Tyler <kevindt@...>
 

If I understand the progress so far, you can successfully do all of these with the STM32, RTC and serial USART (CP2102) in place on the board, and using the USART board to flash the STM32.
   - flash and run a blink sketch with the STM32 in place on the board
   - flash and run the I2C finder sketch and identify the two I2C addresses on the RTC board, for the RTC chip and the EEPROM
   - flash and run the sketch to erase the EEPROM chip

   - You can also compile and flash a copy of the beta version of OnStep, but it is not running. 

   - The wifi board is powering up but is not receiving start-up information from OnStep 

All of these suggest that the STM32 is powered OK and able to run, and that the problem is not in the circuitry around the STM32 controller, RTC board or USART board.  Something is preventing the ONStep sketch from running.

Here are a few suggestions:

  - Have you tried removing all of the stepper driver boards, and trying to run the OnStep sketch?  If one is inserted wrongly, or if one is faulty it may be pulling a STM32 pin that OnStep is using as an output hard to ground or to the +ve line.

  - Will the board boot up without the driver boards and without the wi-fi board inserted, and without the SHC connected? 

  - Have you tried running a clean copy of the OnStep sketch, with the basic config file for the STM32 enabled with no other edits (i.e. just edit the ConfigSTM32.h line that says #define STM32Blue_OFF to #define STM32Blue_ON, leaving everything else alone) ?

  Kevin.  

On Sunday, August 25, 2019, 01:11:28 PM PDT, Khalid Baheyeldin <kbahey@...> wrote:


Sorry. I meant the 'master' branch, which used to be called Alpha.

It is here

https://github.com/hjd1964/OnStep/archive/master.zip

I don't think it will make a difference.

For the PCB, STM32, I meant check the soldering that you did
when attaching the pins to the component, and when soldering
the female headers and male pins to the PCB. Sometimes, there
is a small solder bridge by mistake.

What about temperatures? Anything uncomfortable to touch?


Re: MaxPCB V2 information

Khalid Baheyeldin
 

On Sun, Aug 25, 2019 at 04:23 PM, Wayne Hilliard wrote:
A fork.
I think we are getting somewhere finally.

It seems the latest indi-bin package 1.8.0 introduces a bug for mount
types other than equatorial.

For the sake of verifying my theory, change this:

#define MOUNT_TYPE_FORK

To

#define MOUNT_TYPE_GEM

Then try again and see if there is a delay.

If there is none, then a fix is needed in INDI for this case.

ASCOM is not affected.


Re: MaxPCB V2 information

Wayne Hilliard
 

A fork.


On Sunday, August 25, 2019, Khalid Baheyeldin <kbahey@...> wrote:
On Sun, Aug 25, 2019 at 08:05 AM, Wayne Hilliard wrote:
What is the URL for Jasem's repository?
See Bram's answer.

 My MKS install has a significant delay as well.
Is your mount equatorial, fork or AltAz?


Re: Can´t Connect to Onstep STM32

Khalid Baheyeldin
 

Sorry. I meant the 'master' branch, which used to be called Alpha.

It is here

https://github.com/hjd1964/OnStep/archive/master.zip

I don't think it will make a difference.

For the PCB, STM32, I meant check the soldering that you did
when attaching the pins to the component, and when soldering
the female headers and male pins to the PCB. Sometimes, there
is a small solder bridge by mistake.

What about temperatures? Anything uncomfortable to touch?


Re: Can´t Connect to Onstep STM32

sonny.waxmo@...
 

The LM2596 give 5.06V with no motors attached, only 3pcs of DRV8825.
I have checked all the 3.3 and 5V connections on the other modules.

If have dubblechecked the PCB but I can´t see anything bad, I have seen a lot of Chinese borads a lot worse.

I have checked the Run-Flash switch and there are full connection in both positions.

I have updated the Arduino IDE to 1.8.9 and reloaded Onstep.

Kalid, you said I should test the Alpha bransh. But where do I find it?

Regards
Sonny


Re: Can´t Connect to Onstep STM32

Khalid Baheyeldin
 

On Sun, Aug 25, 2019 at 02:37 PM, <sonny.waxmo@...> wrote:
But still no signs of life or LED exept the first time withe the new STM32, after restart it´s also dead......
The steps you did are correct.

Maybe there is a power issue, or a short in the PCB?

Did you check the temperature of the STM32, or any components on it?
If you have an IR thermometer, check to see if anything is above 45C or so.

To check for a short, e.g. soldering bridge, disconnect power and do continuity
testing on all pins of the STM32 while it is in the PCB, with the adjacent pins.

Another thing is power output from the LM2596 module: is it 5V?


Re: Can´t Connect to Onstep STM32

sonny.waxmo@...
 

I have tried the jumpers in this positions.

With the cable connector for the RUN-FLASH switch remowed

Both jumpers close to the micro USB port.

When Im programing I move the Jumper closeest to the edge one step away from the micro USB. The jumper closest to the Reset button stays in place.

I connect the power and USB-CP2101 but to upload with Arduino IDE I have to puch RESET on the STM32 bluepill.

Result in Arduino IDE is as Follows...

Sketch uses 14588 bytes (11%) of program storage space. Maximum is 131072 bytes.
Global variables use 2568 bytes (12%) of dynamic memory, leaving 17912 bytes for local variables. Maximum is 20480 bytes.
stm32flash 0.4
 
http://stm32flash.googlecode.com/
 
Using Parser : Raw BINARY
Interface serial_w32: 115200 8E1
Version      : 0x22
Option 1     : 0x00
Option 2     : 0x00
Device ID    : 0x0410 (Medium-density)
- RAM        : 20KiB  (512b reserved by bootloader)
- Flash      : 128KiB (sector size: 4x1024)
- Option RAM : 16b
- System RAM : 2KiB
Write to memory
Erasing memory
 
Wrote address 0x08000100 (1.75%) 
Wrote address 0x08000200 (3.51%) 
Wrote address 0x08000300 (5.26%) 
Wrote address 0x08000400 (7.02%) 
Wrote address 0x08000500 (8.77%) 
Wrote address 0x08000600 (10.53%) 
Wrote address 0x08000700 (12.28%) 
Wrote address 0x08000800 (14.04%) 
Wrote address 0x08000900 (15.79%) 
Wrote address 0x08000a00 (17.55%) 
Wrote address 0x08000b00 (19.30%) 
Wrote address 0x08000c00 (21.06%) 
Wrote address 0x08000d00 (22.81%) 
Wrote address 0x08000e00 (24.57%) 
Wrote address 0x08000f00 (26.32%) 
Wrote address 0x08001000 (28.08%) 
Wrote address 0x08001100 (29.83%) 
Wrote address 0x08001200 (31.59%) 
Wrote address 0x08001300 (33.34%) 
Wrote address 0x08001400 (35.10%) 
Wrote address 0x08001500 (36.85%) 
Wrote address 0x08001600 (38.61%) 
Wrote address 0x08001700 (40.36%) 
Wrote address 0x08001800 (42.12%) 
Wrote address 0x08001900 (43.87%) 
Wrote address 0x08001a00 (45.63%) 
Wrote address 0x08001b00 (47.38%) 
Wrote address 0x08001c00 (49.14%) 
Wrote address 0x08001d00 (50.89%) 
Wrote address 0x08001e00 (52.65%) 
Wrote address 0x08001f00 (54.40%) 
Wrote address 0x08002000 (56.16%) 
Wrote address 0x08002100 (57.91%) 
Wrote address 0x08002200 (59.67%) 
Wrote address 0x08002300 (61.42%) 
Wrote address 0x08002400 (63.18%) 
Wrote address 0x08002500 (64.93%) 
Wrote address 0x08002600 (66.68%) 
Wrote address 0x08002700 (68.44%) 
Wrote address 0x08002800 (70.19%) 
Wrote address 0x08002900 (71.95%) 
Wrote address 0x08002a00 (73.70%) 
Wrote address 0x08002b00 (75.46%) 
Wrote address 0x08002c00 (77.21%) 
Wrote address 0x08002d00 (78.97%) 
Wrote address 0x08002e00 (80.72%) 
Wrote address 0x08002f00 (82.48%) 
Wrote address 0x08003000 (84.23%) 
Wrote address 0x08003100 (85.99%) 
Wrote address 0x08003200 (87.74%) 
Wrote address 0x08003300 (89.50%) 
Wrote address 0x08003400 (91.25%) 
Wrote address 0x08003500 (93.01%) 
Wrote address 0x08003600 (94.76%) 
Wrote address 0x08003700 (96.52%) 
Wrote address 0x08003800 (98.27%) 
Wrote address 0x080038fc (100.00%) Done.
 
Starting execution at address 0x08000000... done.

But still no signs of life or LED exept the first time withe the new STM32, after restart it´s also dead......

PLEASE, my whife say I´m doing somtething wrong!!!

Regards
Sonny


Re: Can´t Connect to Onstep STM32

Khalid Baheyeldin
 

On Sun, Aug 25, 2019 at 01:47 PM, <sonny.waxmo@...> wrote:
I had a brand new STM32 laying so I put it in and uploaded Onstep Beta.

And guess what the LED PC13 started to Flash  and the handcontroller reported Connection OK and started to show some data!!!

I put the switsh in Run position and restarted everything, and it is also dead as a stone no LED, hand controller connection failed.

When I put the switsh in flashposition and try to upload again arduino IDE report 100% upload OK restartring running - But the new STM32 Onstep is still dead.......
Let us stay with the STM32 that was flashing. Ignore the other one for now.

From your tests, it may be that the Flash-Run switch, or its wiring is bad.
So when you put it in Run, it is not really wired correctly, and therefore the program in flash never gets loaded or run.

Disconnect the wires from the pins on top of the STM32 board, and use the jumper switches.
Put them in flash mode (per the Wiki page for the STM32), and flash OnStep.
Disconnect power, move the jumper back to the normal position, and power on.

Now see if the LED is on or flashing.

If that works, then the wires from the Flash-Run or the switch itself are bad.

Once you finish troubleshooting the STM32 that works, you can move on to the other one.


Re: Can´t Connect to Onstep STM32

sonny.waxmo@...
 

To make things even more strange........

I had a brand new STM32 laying so I put it in and uploaded Onstep Beta.

And guess what the LED PC13 started to Flash  and the handcontroller reported Connection OK and started to show some data!!!

I put the switsh in Run position and restarted everything, and it is also dead as a stone no LED, hand controller connection failed.

When I put the switsh in flashposition and try to upload again arduino IDE report 100% upload OK restartring running - But the new STM32 Onstep is still dead.......

Please I going crazy...
Any Idea??

Regards Sonny


Re: iOptron iEQ45 (old version) with new OnStep

Khalid Baheyeldin
 

Good to see that RefinePA is now proven to benefit autoguiding, via better polar alignment ...

Did you use APT for alignment via plate solving?
When you have a chance, test more stars in the alignment (5 or more).


Re: MaxPCB V2 information

Khalid Baheyeldin
 

On Sun, Aug 25, 2019 at 08:05 AM, Wayne Hilliard wrote:
What is the URL for Jasem's repository?
See Bram's answer.

 My MKS install has a significant delay as well.
Is your mount equatorial, fork or AltAz?


Re: Can´t Connect to Onstep STM32

Khalid Baheyeldin
 

On Sun, Aug 25, 2019 at 12:23 PM, <sonny.waxmo@...> wrote:

The PC13 LED is compleatly dead at all time.
That is very strange.
This means that the OnStep firmware crashed and is not running.
The only time I saw this is when the EEPROM on the DS3231 chip
was bad.

But in your case, you said that the two test sketches confirm it is
responding and writing normally.

Can you try the current alpha? I don't think it will make a difference
but just want to compare to what I use.

Another thing is: how did you generate your config file? Did you
use the OCG?


Re: Can´t Connect to Onstep STM32

sonny.waxmo@...
 

Thank, you for all your support Dave!
But sorry no success.
I did run the "eeprom-wipe" the serial monitor gave somthing like the following information. 

Erasing eeprom.
a lot of ...............
and erasing success complete.

Then I re uploaded Onstep beta.

The PC13 LED is compleatly dead at all time.

I dubble checked the Flash-Run switch, it is in run position.

I checed the Voltage on every pin for the ST-4 handcontroller connection , it is 2,3V on all tabs.

Do you have any more trix?

Regards
Sonny


Re: Can´t Connect to Onstep STM32

Dave Schwartz
 

You have to have communication with the Arduino IDE serial monitor... otherwise, how did you see the i2c-scanner output?

I discussed the user LED in the previous reply.

The buzzer is only used at the beginning and end of a GoTo and in a few places during handbox commands (but without your handbox connecting yet you wouldn't be getting there).

On 2019-08-25 8:19 a.m., sonny.waxmo@gmail.com wrote:
Sorry I forgot, no serial communication with serial monitor.
No LED bllighting, I only use the onboard LED PC13.
No Buzzer making any noice.

Regards
Sonny


Re: MaxPCB V2 information

bram.slagmolen@...
 

Please follow the steps for the stable release here https://indilib.org/download/ubuntu.html

Assuming you running some sort of Ubuntu, that is how I installed indi on my RPi.
cheers,
Bram