AstroEQ Discussion Board

AstroEQ Forum => AstroEQ Support => Topic started by: pterodyne on April 05, 2018, 06:02:39

Title: Read failed
Post by: pterodyne on April 05, 2018, 06:02:39
Strange new error now that Im trying to put in my TMC2100 drivers.  I can't configure using the latest utility, it times out.  Strangely if I run "update firmware" it seems to go through all the motions and avrdude reports complete.

Any suggestions?  I had a similar problem a while back and Tom asked me to upload a specific hex file to troubleshoot, but I never did because it magically started working again.

I have a manufactured 4.4 astroeq.
Title: Re: Read failed
Post by: pterodyne on April 06, 2018, 04:14:41
I followed the instructions to upload a config checker to the astroeq via avrdude.exe from a couple years ago.  here is the output.

So it seems like something is working, just can't change the config, or load eqmod.

AEQ8.11
RA Reverse = 0
DEC Reverse = 1
Driver Version = [1] = DRV882x
Microstep Mode = [32] = 1/32
RA aVal = [0,64,56,0] = 3686400
DEC aVal = [0,64,56,0] = 3686400
RA bVal = [207,51] = 13263
DEC bVal = [207,51] = 13263
RA sVal = [0,100] = 25600
DEC sVal = [0,100] = 25600
RA IVal = [54,1] = 310
DEC IVal = [54,1] = 310
RA Goto Encoded = [1]
DEC Goto Encoded = [1]
Title: Re: Read failed
Post by: pterodyne on April 06, 2018, 05:26:51
put the normal hex back on.  still not working... Tried a different computer, nothing.  Went back to the original computer.  Now it's working.

Hmm

well now I can try the TMC2100 drivers at least.  Not sure if something is dying on my board..  I guess I should get a different cable to try too.  MiniUSB not so common anymore..
Title: Re: Read failed
Post by: pterodyne on April 08, 2018, 19:00:30
Ok, I lied.  I put everything back up on the roof (semi permanent setup), and it's not working again.  Ill try a different cable, but I think something is wrong with my board somewhere.

Back to the original problem on the first post.
Title: Re: Read failed
Post by: pterodyne on April 09, 2018, 00:09:11
tried different cable and usb port in the computer.  still no dice
Title: Re: Read failed
Post by: pterodyne on April 11, 2018, 17:40:15
and tried again on a different computer.  Just back to read failed.  Before I could update the firmware even though I couldn't configure.  Now I can't even update the firmware.

See attachement.
Title: Re: Read failed
Post by: TCWORLD on April 11, 2018, 18:37:02
Sorry for the lack of responsiveness, I've got lots of work to do.

It sounds like there is a hardware failure somewhere, but hard to say where.

I would start by removing the ICs and plugging them back in again. V4.4 puts you somewhere back in early 2015 if I'm not mistaken, so after 3 years it's quite possible that the contacts on the IC sockets have oxidised. This could cause weird intermittent failures.

If that doesn't help, have a quick look over the solder joints to see if there are any that look cold.

Let me know how it goes.
Title: Re: Read failed
Post by: pterodyne on April 11, 2018, 18:44:18
I get being busy!

Thanks for the reply.  Ill reseat the chips, and I can drop an iron on each solder joint as well.
Title: Re: Read failed
Post by: pterodyne on April 11, 2018, 18:53:46
I Removed the chips and put them back in.  Now it's letting me configure and update the firmware.

Thanks.  I can test out the TMC2100 drivers now.
Title: Re: Read failed
Post by: Washy on April 12, 2018, 08:44:00
So I've just built a new mega2650/tmc2100 based box (didn't want to disturb my old 8825 one in case we get a clear sky!), and I cant read the eeprom - it was working at first (well the motors didn't do anything), so I configured it again with 4ustep rather than 16ustep and that worked but really high pitched noises and wrong speeds so I tried to configure again...

... I thought I'd give the advanced h/c button a go, bad idea that's bricked my eeprom I can read and write sketches to the board, and upload the astroeq firmware but I can't configure because eeprom reading fails - I suspect the bootloader is at fault and I will put that right today and see if I can't get it working...
Title: Re: Read failed
Post by: TCWORLD on April 12, 2018, 08:54:54
When you plug in a H/C it detects the speed button shorting one of the ST-4 pins to GMD and then switches from EQMOD mode to standalone mode. You can't program in standalone mode.
To change back, simply unplug the H/C and either power-cycle the board or for Mega press the reset button.
Title: Re: Read failed
Post by: Washy on April 12, 2018, 09:05:48
When you plug in a H/C it detects the speed button shorting one of the ST-4 pins to GMD and then switches from EQMOD mode to standalone mode. You can't program in standalone mode.
To change back, simply unplug the H/C and either power-cycle the board or for Mega press the reset button.

I don't actually have a h/c though, when I get to the office I'll see whats what and if I can interface with the eeprom with a normal sketch or if I've broken something and put the correct bootloader on the board either way.
Title: Re: Read failed
Post by: TCWORLD on April 12, 2018, 09:19:43
Ahh. Ok.

How long ago did you build the Mega? Do you have R21 (shown here (https://www.astroeq.co.uk/doku/lib/exe/fetch.php?media=astroeq-arduino-schematic.pdf))? If not, place a 1k resistor between digital pin 21 and digital pin 23. Without that resistor it will always think a hand controller is connected.
Title: Re: Read failed
Post by: Washy on April 12, 2018, 10:46:07
I only built it yesterday - but I only have the motor drivers - dont really need the other bells and whistles...  As you recommend however the resistor has fixed the issue and I've now disabled the HC again...  Thanks :)

So when I get home I can get back to making it work properly...

... I'm getting that sinking feeling one of the config jumpers on the TMC2100 isn't soldered properly, and I've soldered them onto a protoboard, and of course they are on the bottom  :o :(
Title: Re: Read failed
Post by: pterodyne on April 12, 2018, 16:34:24
So, even though it can write the config now and update the firmware, eqmod keeps disconnecting over and over.

Probably I need some new chips..  Or there is some other fault in the board.  I guess I could try to go back to the DRV8825 drivers and see if the problem still occurs.
Title: Re: Read failed
Post by: Washy on April 12, 2018, 18:26:48
So, even though it can write the config now and update the firmware, eqmod keeps disconnecting over and over.

Probably I need some new chips..  Or there is some other fault in the board.  I guess I could try to go back to the DRV8825 drivers and see if the problem still occurs.

As in it doesn't even launch, just flicks up and disappears, or, connects, works for a while and disconnects?  Have you checked the vref on the drivers?

For the bigtreetech motor drivers I soldered the cf1, 2 and 3 jumpers and have these settings in the configurator and I'm now in silent running mode - its startling the difference in noise!

Title: Re: Read failed
Post by: pterodyne on April 12, 2018, 18:55:57
Eqmod pops up and then goes away a few moments later.  MaximDL still shows connected, but it's not.  The telescope position indicator is gone from the sky display.

I haven't checked Vref actually, I probably should but Im used to it working in the sense that it tries to slew at least.  I have official TMC2100 drivers from filastruder in the USA.  They are labeled watterot.  I think they have the jumbers in the correct state from the factory.
Title: Re: Read failed
Post by: pterodyne on April 12, 2018, 18:59:33
Just looked at your jpeg.  My settings are the same except i have .9 degree steppers.  and my motor/gear are different.

but what is going on with your motor reduction?  Isn't that like 57 billion?  Or is there a decimal to the left of what can be seen?
Title: Re: Read failed
Post by: Washy on April 12, 2018, 20:22:12
My belt drive is 52/14, I just copy and paste the number from the calculator ....

3.7142857142857142857142857142857

But its rather too long for the text box :)

I think it'd be interesting to measure your vref, vin and 5v see if you're getting browned out or anything.
Title: Re: Read failed
Post by: pterodyne on May 01, 2018, 22:56:00
Ok, I can confirm a  few things.  The problem seems to be with the TMC2100 modules.

The astroeq will not configure with the TMC2100 5V modules installed. If I put the DRV8825 back in, everything works as expected.  Except see my hunts at end of slews.  That happens.

Anyway, Id love to get the TMC2100 5v modules working.  Thoughts as to why I can't connect or configure with the modules connected? Ive verified that they are plugged in the correct direction.  If I bend the 3 config pins out of the way, I can connect and configure using the utility, but eqmod locks up shortly after connecting, and if you manage to start a slew, you get a message about timeout exceeded.

My TMC2100 modules are the true 5v variety and from watterott (Silentstepsticks). 
Title: Re: Read failed
Post by: Jonesdee on May 06, 2018, 09:38:53
I have been having issues with TMC2100 drivers also.  My first ones from BigtreeTech behaved inconsistently, so I purchased some Watterot versions.  I followed the recommendation not to solder the pins to the 3 config sockets, which puts the motor in 16 microstep, 256 interpolation stealth chop mode. The motors are 0.4 A, 0.9 degree step angle.

The motors run very smoothly and quietly, but slew extremely slowly.  The mount also only moves a fraction of the distance it should (e.g. a command to move 90 degrees results in 3 - 4 degrees of travel.

EQMOD runs happily enough (no errors reported).

One thing that concerns me, is that each time I configure the board (a new genuine Arduino Mega 2560 running 8.11), the 'Goto Rate (x sidereal)' parameters show different values.  These vary from 102 through 460 to 507, despite the input parameters beingthe same (I loadthe EQ5 modified pulley config and change the driver to TMC2100, 16 ustep, and 0.9 degree angle, then update both axes.  I am going to try this on a different PC to see if that helps, or possibly set the angle in the config to 1.8 degrees to see if that speeds it up.  Sidereal tracking rate looks to be about right, but have not yet tried it on a star as there is obviously something amiss at the moment which needs to be rectified. 

Using jumpers, I can set the drivers to 16 ustep, no interpolation mode - will give this a try when I get a chance.

Meanwhile, my 8825 setup with diode matrix runs happily in the observatory . . . .

Dave