Welcome, Guest. Please login or register.

Username: Password:

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Washy

Pages: [1] 2
1
AstroEQ Support / Re: Read failed
« 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.

2
AstroEQ Support / Re: Read failed
« 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!


3
AstroEQ Support / Re: Read failed
« 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 :(

4
AstroEQ Support / Re: Read failed
« 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.

5
AstroEQ Support / Re: Read failed
« 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...

6
AstroEQ Support / Re: latest firmware hunting at end of slews
« on: April 11, 2018, 23:33:55 »
Does it hunt on straight slews? 

If I slew to a target for example using CdC it goes straight there and stops.

To get the hunting behaviour you describe (and I do get it) I have to be using plate solving and be close to the target after the initial slew.  What is happening I think is this, camera takes a shot, plate solves, off target, syncs, re-slews to target, takes a shot etc....

Now the issue (for me) appears to occur when the target is close but not within the plate solving threshold so it has to capture and resolve, but the new required slew is tiny but the motors accelerate to the a slew speed beyond what is required which coupled with the deceleration puts the scope off target, so it solves and overshoots back again ad infinitum.

I've found the easiest fix for this issue is simply to plate solve to a new target a few degrees away, then back again with model points close to your target you tend to land bang on your objective and the plate solving sequence will end without hunting.

7
Oh and you can avoid unplugging the cable by either rebooting the computer or disabling the USB hub in device manager.

8
What's your definition of "right away", 1s, 5sec?  How are you powering the 2650?  There's a couple of things that happen when you disconnect and reconnect the serial with resetting the processor.

If you power your 2650 using USB as the power source I believe you will not get the symptoms you describe as every time the serial reconnects it should cause the Arduino to reset thus the motors should not hold.

The "correct" solution I believe should be a 50uF capacitor between reset and ground.

9
DIY AstroEQ / Re: AstroEQ + INDI tracking problem
« on: March 30, 2018, 12:17:33 »
As I posted in my old thread - I have this problem also with DRV8825/2650 setup, i.e. sidereal tracking will not start unless I manually move the mount first with the ekos mount control keypad... not a huge issue though.

TMC2100's on order - be great to get rid of the pitchy buzzy noises!

10
DIY AstroEQ / Re: EQ5 speed issues
« on: March 30, 2018, 12:13:32 »
This was a god send, I've just transitioned to a RaspberryPi setup and it wasn't working right - wanted to try upgrading the firmware which worked but bricked me eeprom - so I got my ratios back from here since the computer I originally used is long dead and no back up and I didn't fancy counting teeth today much!!

I input all the same data, but it wouldn't accept the same 808 rate as before so the params computed all different - I uploaded it anyway and am just doing a tracking test to make sure its now working properly.

Sidereal tracking still wouldn't engage when pressing start in ekos but after manually slewing the mount and trying again it appears to work just fine now!

11
DIY AstroEQ / Re: EQ5 speed issues
« on: March 24, 2016, 15:08:29 »
Yeah I've just read through that - I put my drivers into fast decay and they run smoothly and continuously now - just a bit pitchy.

Hopefully that will improve my imaging as running a pulse a second or so made my stars go a bit soft.

12
DIY AstroEQ / Re: Astoeq tracking pause every seconds.
« on: March 24, 2016, 15:06:49 »
Hehehehe I bridged to the pin the other side mistakenly - it was direction so I only ran in one.  Have fixed it now and my motors apart from noisy now do run smoothly at 32nd stepping, I guess I'll have to have another go at current limiting but I just think part of fast decay is noise.

http://s15.postimg.org/l30tlwdbf/20160324_122026.jpg

I saw some various sites talking about diodes, but I think that's only going to fix an issue if the steppers can't take the full VMOT voltage which mine can because they are 24v rated?  Is my understanding correct?


13
DIY AstroEQ / Re: Standalone Operation
« on: March 14, 2016, 18:23:52 »
Sorry if I'm being dense but couldn't one simply write an eqmod like android app that interfaces with AstroEQ via Bluetooth using the protocol?

Its no mean feat I'm sure, but the smart phone is infinitely more capable than writing a new hand controller with 18x2 LCD and more ubiquitous?

14
DIY AstroEQ / Re: EQ5 speed issues
« on: March 14, 2016, 12:39:36 »
Yeah the 38% difference is of course the pulley config you used and put in the custom pulley config file and mine.

I tested everything out last night and primarily it all works nicely! :)

 I still get the same RA behaviour when tracking sidereal the motor only moves for about 0.3 - 0.4 seconds per second - it tracks the sky well but I guess it might be noticeable if I used a long focal length??  Is this the decay mode issue?  Or is that just the normal run cycle?  Maybe I'll put a scope on it later and measure more precisely the on/off timings....

15
DIY AstroEQ / Re: EQ5 speed issues
« on: March 13, 2016, 07:32:20 »
Of course in the morning its blindingly obvious why its not working.

So I write a quick arduino sketch to full step the motor round 360 degrees and it works AOK, its 106971.4 full steps but 32x that != the numbers in AstroEQ they are 39% different

my calc = 3423086   
astroeq calc = 2457601
% diff = 1.392856576

Now I can't explain that - but I hit the update button in AstroEQ and the calcs on both axes became good and the scope now moves as intended :)  Happy days!

I guess I didn't realise I had to click the update button on the configurator  :-[

Pages: [1] 2