Topics created by hairy_kiwi

Apologies for my stony-silence since opening this thread - I've been out and about without a spare moment.

@dc42:

Looks good! Would you care to upload it to Thingiverse? If you do then I'll add a link from the IR sensor fitting instructions.

@Roland:

Nice one. Do you have any provision to stop the duct rotating on the heatsink to prevent the back of the IR probe PCB shorting against the heater block - assuming no/defective silicone sock?

Thank you both.

Now published on Thingiverse as: E3Dv6 fan duct for dc42 IR height sensor V1 | http://www.thingiverse.com/thing:2250394

Although I don't currently have an absolute solution to the issue of the duct rotating on the heatsink, there are a few factors that give me peace of mind that the risk of the PCB shorting is minimal:

With the PCB fixed to the side of the mounting tabs furthest from the heater block, it would be possible to rotate the PCB greater than ±45° with (IMHO) no significant risk of either the PCB or supplied screws touching the heater block. The same is not true if the sensor PCB is fixed to the inside of the mounting tabs - though for the PCB to be able to rotate through the 45° position would likely require the almost complete breakdown of the E3D silicon sock along a vertical edge, Along with dc42's own fitting instructions, I'm advocating the use of Kapton tape on the back of the PCB, On my own printer, the location of the duct between the X-carriage linear shaft bearings physically prevents significant rotation,
Other thoughts: Addition of an anti-torque grub-screw or extra clamp to the design ought to be possibile, Five of the six ducts I've printed have all gripped the E3D Heatsink much more firmly than the original E3Dv6 duct ever did. For a more detailed explanation, visit the Thingiverse page and read the Note under Print Settings regarding higher print speed resulting in firmer grip characteristics.

Any thoughts appreciated - especially if you think I'm being over optimistic in my assumptions.

@T3P3Tony:

I frequently create an access point on my android phone ( WiFi hotspot). I then connect the WiFi to that, along with laptop/tablet. It's easy and does not require anything i don't already have with me.

Many thanks Tony, I'll give it a go.

@T3P3Tony:

Thanks for the feedback. I will consider how to restructure the documentation to make it easier to navigate - the Wiki has grown a lot over the last few months, maybe the frontpage/table of contents layout is not the best.. Any thoughts on alternative structures?

Also you mention it loads slowly - is that all ages or just the front page?

Hi Tony, the slow loading issue no longer exists today. I'm not sure if it could have been a result of your server load or simply my overloaded PC yesterday, with many tabs open in Chrome.

Regarding the wiki structure, hopefully there are some lurking web interface gurus who can share their expertise - burtoogle for one, perhaps, and at least another MS tech writer I've seen lurking here - whose handle I forget, sorry 🙂 In the meantime I found some good introductory guidance at Wikipedia:
https://en.wikipedia.org/wiki/Wikipedia:Summary_style

As a case in point, I like the fact I can read much more on that one page. I'm not suggesting that structure is appropriate for all the Duet Wiki pages, but an ideal in terms of making it quicker to skim read to ensure all pertinent information is obtained (in order to prevent or at least reduce possibility of equipment damage, or seemingly-going-round-in-circles type frustration).
The following section in that wikipedia page seems to provide a good overview on balancing page size and detail:
1 Rationale
1.1 Article size
1.2 Levels of detail

Youtube seems a little lacking on the subject, but I did find this informative though slightly slow-paced webinar: https://youtu.be/wwi8s5VdHH0

I only have a couple of thoughts from my experience of the Duet wiki that might be of interest:
If keeping the same contents system, navigation might be improved by adding contents navigation to each subsection - to remind the reader what else exists under that particular heading - and to avoid the round trip back to the contents (Home) page.

Where a subsection contains only a paragraph, for example: https://duet3d.com/wiki/Prerequisites_for_using_the_Duet_WiFi
It would ultimately be quicker - and just as manageable as far as assimilating info - to read that as part of a longer piece of text. I didn't check out the entirety of that section, but I wonder if it could be completely flattened into a single page?