Print

[kaito83]

I've flashed the new firmware, after ConfigUtility  the motors wont move and also eqmod coordinates wont change.
With older 8.05-8.11 everything is ok, mega2560 with custom pins, I'll double checked them.
8.14-8.19 motors move except the DEC wont go with desired speed.
Flashed with M Studio and also Arduino IDE same issue.
Windows, Ascom 6.6, eqmod 2.00w
What Im doing wrong or what causes the issue?

[TCWORLD]

Can you confirm that your board matches the schematic here, including the 1k resistor (R21) between Arduino digital pins D21 and D23?

[kaito83]

As I see the R21 resistor serve for the ST4 inputs, its not actually used for drivers. But its not match, i dont need ST4.

[kaito83]

Its look like with newer version 8.2X the firmware doesnt get the, ratio, Ival and etc after flashing with Utility, I got the similar issue if miss the Config utility when I use the 8.05 firmware

[kaito83]

I made a little video, as I said if I miss the config utililty after flashing 8.05fw I got same issue like with the 8.2X.
Motors didnt active after connection, maybe stay in emergency stop?
Those are pre complied hex files to with same PINout to mega2560

https://drive.google.com/file/d/1VHHn7L5B1bQvZxeRpwa9-n9ygM6s40GR/view?usp=sharing
By the way success full connection is always on the second time, its not a big deal but its frustrating

[TCWORLD]

What is the status LED doing on the board when it is not responding to EQMOD?

I've attached a debug version of the config utility. Could you attach the console output from when writing the configuration.

[kaito83]

Here is the 8.21 log, no led blink, when command sent to MCU

[kaito83]

Here is my pinout:

//GPIO Pins:
//VCC (Header Pin 5)
#define gpioPin_0_Define 33  //IO0 (Header Pin 4) - GPIO Pin
#define gpioPin_1_Define 35  //IO1 (Header Pin 3) - GPIO Pin
#define gpioPin_2_Define 37  //IO2 (Header Pin 2) - GPIO Pin
//GND (Header Pin 1)

//PWM Pin:
#define pwmPin_Define 2

//Status Pin:
#define statusPin_Define 13

//E-Stop Pin:
#define estopPin_Define 11

//Motor Driver Pins:
#define resetPin_0_Define 55 //Analog 1
#define resetPin_1_Define 54 //Analog 0

#define dirPin_0_Define 30
#define dirPin_1_Define 18

#define enablePin_0_Define 20
#define enablePin_1_Define 8

#define stepPin_0_Define 28
#define stepPin_1_Define 16

#define modePins0_0_Define 26
#define modePins1_0_Define 24
#define modePins2_0_Define 22
#define modePins0_1_Define 10
#define modePins1_1_Define 12
#define modePins2_1_Define 14

//ST4 Pins:
#define ST4AddPin_0_Define 50
#define ST4AddPin_1_Define 51
#define ST4SubPin_0_Define 53
#define ST4SubPin_1_Define 52

[TCWORLD]

Right, so this is a custom pinout.

I see that you are using pins 30-37. As per the Arduino Mega schematic, these 8 pins must NOT be used.
The registers that drive them are being used as fast access register flags in the interrupt routines (the 2560 lacks the general registers that the 162 has, so I had to get creative).

So the GPIO pins are going to be messed around with, which may cause weird mis-detection of hand controllers, as is the direction pin for the RA axis.

Also, how are you compiling the custom firmware? I've only tested with Atmel Studio 7. The Arduino IDE does all sorts of weird preprocessing so I have no idea whether that will work.

Is there any particular reason why you are using a custom pinout rather than the tried and tested one?

[kaito83]

I didnt guess, with this pinout no problem with fw 8.05-8.11, and also the 33,35 etc pins not not connected to my custom pcb or any other components

Connected pins to only to drivers (nothing else):
#define dirPin_0_Define 30
#define dirPin_1_Define 18

#define enablePin_0_Define 20
#define enablePin_1_Define 8

#define stepPin_0_Define 28
#define stepPin_1_Define 16

#define modePins0_0_Define 26
#define modePins1_0_Define 24
#define modePins2_0_Define 22
#define modePins0_1_Define 10
#define modePins1_1_Define 12
#define modePins2_1_Define 14

Analog (resetPin_0_Define) doenst required for drivers, I mean it works without analog.

Complied with Aruino IDE and Atmel Studio, same issue.

Its a very little and compact pcb, size about 5x8cm, only for motor drivers with mega2560mini. I didnt need any special like st4 and others.
And it fits well into eq6 mount.

Probarly its not hardware problem, this should be work without any pcb.
I compared fw 8.05 and 8.21 and there is no "significant" change in astroeq.c some const, and some functions are "different" etc.

[kaito83]

And also If i set the pinout to ramps nothing happen in eqmod like in the video

[TCWORLD]

Could you follow the instructions here:

https://www.astroeq.co.uk/forum/index.php/topic,141.msg946.html#msg946

(You may need the new version of SerialEcho, attached to this post: https://www.astroeq.co.uk/forum/index.php/topic,275.msg1941.html#msg1941)

This should give a log of communications between EQMOD and the AstroEQ which will help debug communications problems.

[kaito83]

Hi, I made the test here is the log, otherwise there is an option in the EQMOD to log the serial communication

[kaito83]

Here is a video about the error, this is freshly opened mega2560 no other components attached to it just the board, flashed with ATML studio, uploaded with config utility, no pinout modification just the clear 8.21 firmware download from https://github.com/TCWORLD/AstroEQ

[TCWORLD]

Right, so that's very weird. The mount responding to the `:F1` command with `!04` means that it is in programming mode, not run mode. As a result it won't enable the motors (a protection feature when using the config utility).

There are only two ways of entering programming mode, sending `:O2` twenty times (which isn't happening), or otherwise failing to read its EEPROM (e.g. if corrupt or blank). Would you be able to run the Arduino "eeprom_read" sketch to dump the contents of the EEPROM, and upload the result here?