Jump to content

Banner.jpg.b89429c566825f6ab32bcafbada449c9.jpg

tekkydave

Members
  • Posts

    1,798
  • Joined

  • Last visited

Everything posted by tekkydave

  1. I have the following: pi@indiserver:~ $ ifconfig eth0 Link encap:Ethernet HWaddr b8:27:eb:2d:bd:b2 inet6 addr: fe80::1c7f:22a8:3643:ebe2/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:26 errors:0 dropped:0 overruns:0 frame:0 TX packets:26 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:14712 (14.3 KiB) TX bytes:14712 (14.3 KiB) wlan0 Link encap:Ethernet HWaddr b8:27:eb:78:e8:e7 inet addr:192.168.1.95 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::fcb6:1f2b:7869:f2e4/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:623 errors:0 dropped:195 overruns:0 frame:0 TX packets:359 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:75719 (73.9 KiB) TX bytes:58798 (57.4 KiB) pi@indiserver:~ $ sudo cat /etc/wpa_supplicant/wpa_supplicant.conf ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev update_config=1 country=GB network={ ssid="ssssssss" psk="pppppppp" key_mgmt=WPA-PSK } pi@indiserver:~ $ sudo cat /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) # Please note that this file is written to be used with dhcpcd # For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf' # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d auto lo iface lo inet loopback iface eth0 inet manual allow-hotplug wlan0 iface wlan0 inet manual wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf allow-hotplug wlan1 iface wlan1 inet manual wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf I have used the advanced config in my Homehub to tie the RPi IP address to the same address every time. Not foolproof but I haven't tried setting up a static address yet.
  2. Still cant get the ASI120MC working via Indi. I have doubled the usb current to 1.2A but no luck.
  3. Yes, nothing else to change to get it working. If you are 100% sure it is connected up ok then it could be the HC05. I know there are lots of different types out there and a lot of variation. Also my sketch will only work if the device is initially setup as a slave. A brand new one should be by default. I can only suggest swapping out various components (nano, hc05, transistor etc) one at a time to try to isolate the issue. These are the pages I got most of my ideas from if you want to test the HC05 separately: http://phillipecantin.blogspot.co.uk/2014/08/hc-05-bluetooth-link-with-zero-code.html http://www.martyncurrey.com/arduino-with-hc-05-bluetooth-module-at-mode/ Can you post some shots of both sides of the HC05 so I can see if it is similar to mine. Thanks. Has anyone else added a HC05 to the focuser following my schematic & sketch?
  4. Are you using the v2.5.0 version of the sketch?
  5. The Ticks setting in the autofocus part is the initial ticks to use when autofocusing . Hover over the control labels to get a description.
  6. Thats what I meant really - the way you are doing it. There must be an issue with the 120MC and the driver as your camera is ok with it. When I press Preview it starts doing something then just hangs. The camera should be ok but I'll test it on my PC tomorrow to double check.
  7. Can you get an image via the 'Preview' button in Ekos, running on a separate machine?
  8. Is the aim to reduce or increase the speed of the usb2 connection? There is an option in the /boot/config.txt to double the usb current to 1.2A. I'll try that tomorrow.
  9. How do I modify it from command line? Thanks.
  10. I tried getting my venerable ZWO ASI120MC working with the RPi3. It is recognised by indiserver and Ekos connects no problem. I can't get a preview image to come across though. It just hangs. Maybe it needs to be connected via a powered hub. I also tried a normal webcam with the indi_v4l_ccd driver and that produces an image ok.
  11. I haven't connected anything to the MS1,2 & 3 pins - don't know if that would affect the driver's behaviour or not. Measuring with the DVM they are all pulled low internally. Or the ENA pin.
  12. My PSU reports about 230mA current draw on the 12V supply when the motor is moving continuously.
  13. Sorry for delay. I measure 316mV on the pot.
  14. I have kept the 12V motor voltage GND separated from the RPi power GND. Both come from a dual bench PSU with floating outputs. Probably not relevant.
  15. I just rotated the pot clockwise from minimum until I got a good strong rotation. Very unscientific
  16. Is the 12V definitely getting to the driver pins?
  17. That had crossed my mind. Also check that the GND rails on both sides of the board are indeed connected. Are the 4 motor pins 1A,1B,2A,2B connected correctly (they look ok to me) and are they pulsing at all?
  18. Ok, I wasn't sure from the photo which rail it went to. I can't see any problems with the wiring at all.
  19. Have you got the RESET pin pulled high? I missed that and it didnt do anything until I fixed it.
  20. I wish I'd put mine that way round now. It makes the GPIO wiring shorter. Are you using 5V for Vdd? I used 3.3V as it should work on 3V to 5V. Makes no odds really I suppose.
  21. Maybe the designer expects auto-focussing to be the normal use.
  22. There is a Ticks setting in the autofocus settings (set to 100 by default) but I couldn't find where to set it for manual operation either.
  23. I got that sometimes but it found stars now & again.
  24. If you have the ccd simulator running it uses a fake image for the auto-focus.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. By using this site, you agree to our Terms of Use.