skybadger

Thats what I would do for a few , a few hundred I was thinking you might have optimised a pipeline somehow. I guess you drop all the vids into AS3 for it to do its stuff overnight. I've moved onto Maxim to do wavelets since R6 is so flaky (on my laptop) . thanks for the answer.

Thanks for this. I was aware of the ability to stack multiple files but never have understood how it could stack to the percentages for each file without setting a reference manually. I guess we are dependent on being confident as3 can select the reference as well or better than I can on a per-picture basis.

i use OTA updates - the point is that the OTA installs a web handler that can receive and blow new firmware images. Just browse to the URL in your browser, upload the firmware blob and hit submit. Key dependencies are that your device is on the network, is discoverable, etc,, so problematic if your device falls off the network for a programming reason, then you will need serial access . I don't / haven't done it from the IDE though.

Hi , I'm really interested in what you mean by this . Can you elaborate please ?

I have two of these, Vlad to see you got the date sorted. The erratic motion thing is always about cables, typically the encoder signal is dropping.

Sheer effort! What's your process to reduce all that ? Really nice result.

Thanks Paul. I had sharp fraunhofer lines this afternoon using an eyepiece in the camera opening but I will go back and check the collimator next. mike ta

Are you sending in empty topics occasionally/by accident. There are means of resetting them using the msg object you might be doing unintentionally.

Possibly starting a coding war, but using status1 && status 2 will fail if status1 is not TRUE. because the compiler spec is to check them in order and fail as necessary. For clarity and the next person, obtain the status of the things you are interested in first and then do the logic and reporting.

On the Esp you can have two wires (maybe more) running and point each instance at a set of pins. You do need to do Wire.begin( SCL=x, SDA=Y, optionalLocalMasterAdd) in setup but Adafruit sometimes hides this inside the library because its a bit noddy and assumes you only have one device. I pull these bits out and do something like bme280.begin( address, twowire& myref) so I can tell it what wire interface to use. Otherwise these libraries often assume default pins and only one instance.

I'm looking for a post-assembly setup guide for the alignment of the optics in the lowspec specifically. In my mind it might be easier now i have all the opticis assembled and working Focus guider on slit wheel. Done. Fairly easy since there is dust and specks on the wheel regardless of the care you applied. Align guide mirror to project centre of slit into guider . Done. Surprisingly minor, though the realtive position of the slit in teh field of view of the guider does move dependnig which slit you put it on. Suspect that the centre of the disk is not concentric with the centre of the wheel. Align grating to n=0 . Used sun to find order=1 position - assumed its the brightest spectrum position. How do I focus the entry collimator so I know it's fully illuminating the grating with parallel light ? Mirror behind and look for focused slit projected back onto the wheel ? Align grating in holder - no real adjustment possible. Place camera in camera port and focus using dial. No alignment adjustments possible with output collimator lens. Is that about it ? cheers

You do need a separate bme object per device otherwise you will always read he one you have stored the address for last. e.g BME280 bme76; BME280 bme77; status1 = bme76.begin( 0x76 ); etc. Where is wire being initialised and set to use the right pins ?

Did anyone post a link to a setup guide ? I am sure I have read one but can;t for the life of me find it again! It doesn't appear amongst the thingiverse files. So where did I read it ?

As far as bad readings go. I would check my loop timings. I'v had sensors that are quite sensitive to both i2c timings - too slow and they get upset and to polling timings, too short or too long compared to acquisition time and they get upset. The worst one for timing has been the HTU21D and the worst one for default readings has been the BMP280 due to i2c timings. Setting i2c speed back to 100KHz from 50 KHz solved that.

Here's an example from mine.

The ESP stack is sensitive to needing reconnects and has historic issues with connections being dropped, so your code needs to check the client connection is still viable and remake it if necessary. A reboot typically fixes this until the next drop, which may be hours or minutes away. The ESp8266 needs a combination of LWIP 1.4 and high bandwidth settings to enable client connections and in the loop coding to reconnecti on drop. The MQTT broker will have capacity for hundreds or thousands of connections, limited principally by memory since there is no timing guarantee on messages.

I have the Ender 3 pro. I bought it 3 weeks ago for printing the lowspec spectrometer. The drawbacks are That the bed isn't very flat and you need to flatten it after hearing and that the magnetic sheet on the bed won't easily release large objects . I out a nuisance crease in mine trying to lift it off the plate withe model on. The SD card slot is also fiddly, mine doesn't eject. I have to pull it out. That said its been very good at printing, successfully printing a 2.5 day print of the main body part. Used with Cura seems to be the way to go.

I'm the op. I eventually used a compact camera on a separate tripod , the zoom on the camera let me get a reasonable image size but still not frame filling. I think the lensless approach worked since you are imaging the ronchi or slit using the primary and that implies you can only image the slit if the slit is inside focus, placing the image of the slit and the camera outside nominal focus. Or I'm making it up since we are talking CoC here rather than focal length. I haven't been back to this since making a small bracket with a tripod thread in it and using the web cam glued to this to image the fringes. Afterwards I moved to dual pass auto collimation process which is a different kettle of fish. I do know that others have imaged the fringe pattern using the zoom feature of compact cameras. Also the use of the word infinity above is wrong , I meant imaging at CoC. Which is why the Webcam telephoto lens wouldn't come to focus in the mount I had and needs an extension. HTh

ditto.. theres a CdC support forum Geoff - that might be the place to ask. Patrick is quite responsive.

I was having a similar problem. I measured the aperture of the openings in the body design as 47.5 mm which is just short of the thread body maximum diameter expected for M48 but will glue in fine for purchased metal rings. My solution so far is to rub a metric thread gauge around the threaded parts thread using a spot of suitable oil, enough to form the thread shape and remove any joins or overhangs. That has done the trick so far. The gauge to use is the 0.75 mm pitch tool. Use it like a thread chaser. Should that ring break off, I'll chuck it up on the lathe, machine it out and put a m48 thread on it with a metal insert.

sounds like my ascom switch driver.

Basing stoke astro are still active but mostly over zoom.. two monthly meetings and informal whatsapp keeps everyone connected.

Id have had that synta grease. Its perfect for wormwheels. Not so much use on axles though.

Just to chip in that I too am building this, being at the 2/3 printed state and with optics waiting on the bench. Looking forward to getting home and completing the build. I will probably turn up the threads on the lathe though, from recent posts.

They also included the standard weather icons.