Jump to content



  • Posts

  • Joined

  • Last visited

Everything posted by jnp

  1. Vast improvement in the new procedure to not stipulate that an XP machine is required. I managed to get it to work eventually , there were some issues that I have mentioned below in case it helps others: 1: The system would not autodetect the QHY16000Driver when reconnecting the device after adding my hardware id to the QHY16000.inf file. The step did work when I manually specified the driver location in the C:\Program Files (x86)\QHYCCD\QHY16000Driver\driver folder. 2: The screenshot in picture 3 only shows 7 of 8 byte values. I assume hidden last value was 00. 3: Kept getting errors downloading the Vend_Ax.hex file. Eventually pointed the file dialog box at the existing Vend_Ax.hex file in the path of the "driver&hex" folder and it worked. QHY seemed to have engineered this failure by design when you consider how poorly the USB connector fits! Happy New Year John
  2. Thanks Martin and Julian. Wont get a chance to do this today, but will let you know
  3. Thanks again Marci, useful to know, but I have an XP machine running. The new problem is that the files are corrupted on download from the QHYCCD post. The post url is http://qhyccd.com/bbs/index.php?topic=2702.msg16130#msg16130 . (If link doesn't work search for "qhy5 reports usb device when plugged in" on http://qhyccd.com/bbs/index.php?board=10.0 ). Here are download urls from the post: http://qhyccd.com/bbs/index.php?action=dlattach;topic=2702.0;attach=2756 http://qhyccd.com/bbs/index.php?action=dlattach;topic=2702.0;attach=2757 http://qhyccd.com/bbs/index.php?action=dlattach;topic=2702.0;attach=2758 Does anyone have working copies, or can download and successfully extract?
  4. Thanks for that Marci. I have found this procedure http://qhyccd.com/bbs/index.php?topic=2702.msg16130#msg16130 that I will try first once I get an old XP machine running . Fingers crossed
  5. My old QHY5 just died. It now won't work on either of my laptops (Win7 64bit and Win732bit). It shows as 'device unknown' in Device Manager. The hardware id's are: USB\VID_EA18&PID_0901&REV_0000 USB\VID_EA18&PID_0901 Swapped cabled and tried reinstalling software and drivers, but no joy. I am hoping that flashing the eprom will sort it but cant find any info on how its done. (There is a link in the thread below but it doesn't work anymore). Help appreciated! thanks John
  6. Hi Chris, The instructions are in this PDF link https://dl.dropboxusercontent.com/u/87095951/Spectro/BASS Project/ Project Installation Notes 1.9.4.pdf in your case, download the 1.9.0 Msi file and run. You then overwrite the executable with 1.9.4. Regards John
  7. Hi Tim, Nice results. Don't underestimate the achievement of detecting gases from the outer planets, historically this was once thought to be impossible. If I understand correctly then you are using an eyepiece and 50mm lens to collimate the spectra, but without a slit? In this case the smaller angular size of Neptune could account for the better resolution despite the fact that Neptune is fainter. The reason for the differences could be with: shift in focus, staking/processing (check the individual subs for Uranus to see if more detail is there in some shots), different binning regions, change in 'seeing'? You could improve the resolution of your existing setup by adding a slit. This will however create the new issue of how to get and hold the target on the slit. This is typically achieved using autoguiding with a reflective slit, adjustable slit or beam splitter. A crude slit will allow you to take lunar spectra. best regards John
  8. I run the Yahoo group fine on my iPad (Safari) with no issues. Have you made sure cookies are enabled? As William suggests, try Firefox or Chrome on your MAC. Incidentally, how are you running the BASS app on your mac, emulation? Sometimes web sites have temporary glitches, yesterday I couldn't create Dropbox links with Chrome, today it's fine. John
  9. Hi Chris, I'm the author of BASS Project. I haven't been on SGL for quite a while. What browser (& version) are you using. If you haven't already, try Chrome? Not sure what links Ken provided. Let me know if you still need direct links to the documentation and software. The latest version is 1.9.4. Drop me a line, with more details on the issues, if you are still stuck. You can also try post to the group by sending your email to astrobodger@yahoogroups.co.uk regards John
  10. The top spectrum calibration looks OK judging by the H alpha and H beta emissions. The others will be ok if you used the same dispersion (grating spacing & orientation and use zero order as reference etc). Stacking and/or longer exposures would reduce noise. They look pretty good for "first serious shots". regards John
  11. There is also the Bulk Image manipulation screen in BASS to do flips and math operations to multiple fits. You are spoilt for choice!
  12. Hi Steve, This could also be affected by how tilt and active binning was applied. cheers John
  13. Robin - "normalising so that the continuum equals 1 at all wavelengths is commonly called rectification" Thanks - managed to avoid or forget that one. Must not take electronic parallels of AC/DC rectification too literally, I don't think negative peak areas under the continuum (akin to DC level) are made positive. However, it wouldn't surprise me if someone did just that to sum all 'energy' absorbed and emitted excluding the continuum. Steve - you seem to be having a lot of fun with the profiles, but you got there . Just a tip in BASS. By default profiles autoscale to fit the chart area. The second profile will therefore have its own scale that differs from the first. Look at the 'Y axis' options in 'Profile properties' screen and adjust to get meaningful comparisons. For example set profile 2 to 'scale as 1st profile' so it uses the same scaling as the first profile. thanks John
  14. Indeed "normalisation" confusion comes up too frequently. Within BASS there is a 'Normalise Flux scale' screen - this keeps the shape of the profile unchanged but adjusts the values so that flux=1 at a small range you specify (don't confuse this will the profile range). For example if the average flux was "5" between 600 to 602 nm (or wherever you can avoid a peak/line/trough). Then the original values will all be divided by 5/1 = 5. One reason we do this is to be able to get an idea of the size of a feature/line at a glance. You could see the top of BetaLyr change from 5 to 10 for example. Perhaps this should be called "Continuum Unity Scaling" or similar. The problem is that some refer to removing the continuum as normalising. I refer to this as 'Continuum Removal', this produces a flat overal profile (except for the peaks/lines/troughs). For showing relative movement/activity of BetaLyr I would Remove the continuum of each profile.Normalise Flux scale to 1 for each profile so flat continuum flux is about 1This doesn't account for changes in overall brightness (you need photomentric data added and it gets complex). Hope this helps John
  15. Hi Steve, Interesting, thanks for posting, That's more movement than I expected over the 2 consecutive nights. Comparing spectra over successive nights can be a challenge. Different conditions, perhaps different position on the slit etc. may affect the results, especially using the same instrument correction. Removing the continuum and normalising the flux to 1 on the flat continuum is a reasonable and simple way to present this type of data. thanks John
  16. Hi Steve, I think the Pickles reference spectra dont include the tellurics. Interesting Helium activity at 5875A BTW The calibration in BASS and ISIS differ in method but, should be the same once converted to ID profile. regards John
  17. Hi Steve, It' a good start into a complex area. I wasn't sure if the Alpy had sufficient resolution, but it shows the Helium 6678 region nicely. This changes quite dramatically over the 13 day period. You may need to recheck the calibration. The dips before 6900A are telluric Oxygen at 6869A and should line up (as unaffected by doppler shifts). Were you using Neon lamps? The doppler equation calculates speed from wavelength. The velocity you measure depends on positions relaive to the Earth solar orbit and the Earth's rotation. BASS will show velocity on axis and report values if you setup the xaxis tab (in Chart Settings) to Show doppler shift and enter 6562.85 as the Rest wavelength. There is no heliocentric calcuation in BASS yet. You can increase the number of decimal places in the Measurement Options tab of Measurements screen to help with rounding issues. Can you confirm how you are taking the 'measurements'. Using the Measurements screen, you select a range before and after the Ha region (like during a calibration). The app will then report values it detects. For Vega read against 'Min' result values, or betaLy read against 'Max' values. These will show doppler shift if enabled. No need to pick the points yourself. cheers John
  18. It's unlikely I can make Sidmouth. Are you going, that's quite a trek from York! cheers John
  19. Good stuff Steve Now try Beta Lyrae (Shelyak) over 13 days. That will show plenty of change
  20. Hi Steve, The Devil is in the detail. Could you possibly list the steps that you followed in ISIS & BASS and show the dodgy profile etc. regards John
  21. Hi Steve, Welcome back to spectro! I am not aware of any reason why you would get that peak in the moons. Perhaps you have made a discovery. The main spectral features, like telluric and balmer lines line up (using the Alpy?). Would take a better guess if I could look at the FITS images, say for hot/cosmetic pixels NB I think Jupiter is possibly a little saturated, judging by the shape of the continuum. cheers John
  22. Excellent start Andrej. You can already get a feel of how the stars get hotter and see the major lines, especially Hydrogen Balmer. Not sure what process you followed, but, so far so good. The common slitless spectra processing steps are: stack imagescorrect for rotation/tiltset binning and sky subtraction regions.calibrationinstrument response correction Would expect to see emission lines specific to the metals/salts mixed with the gunpowder (red=strontium, blue=copper, yellow=sodium etc). I agree spectro opens the door to plenty of science. Much more than taking pretty pictures. Happy New Year! John
  23. Hi Steve, Thanks for that. It's getting there but I'm sure there could be more scrutiny applied. The first velocity values are not fitting the variation I expected. My R values were a bit hit and miss (somewhere between 1500 and 2200) due to the use of an adjustable slit and an ,'expedient rather than optimal', spectroscope design using Wikes 65mm guttering . There were times when reflective guiding would have helped. Definitely worth a go, I expect you should see something varying at Alpy resolution (R=600+?). You'd cover the whole visible spectrum too with more repeatable results. thanks John
  24. Hi Folks, Been quite a while so thought I post up some Beta Lyrae (Shelyak) spectra when I managed to take advantage of several clear nights in succession at the end of July. There is too much data to show, so here's an animation showing Hydrogen Alpha and Helium (6678 A) over 10 nights spanning 2 weeks. The next images show an analysis of the Si line to measure radial velocity, (Shelyak is a binary system). The image strips show the Si lines moving relative to the static telluric water line at 6516. Finally here is the chart of radial velocity over time. (Heliocentric correction has not been applied). Thanks for looking John
  25. Hi Steve, Shame it's so far away for me. Would be very interested to hear Robin's talk. regards John
  • 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.