Have commented on this on specific item re various “issues”, however, overall, documentation is Sienci’s weak point, IMO. Far too much effort spent on tech support which could have been avoided with better documentation. Latest - have offered to go through the documentation step-by-step with Sienci on CLSM upgrade - they are too busy…
Hey Borys,
We love feedback, thanks for the offer to help us improve our resources so everyone can benefit. We’ve made a couple tweaks to the CLSM kit thanks to user feedback and we’d love to hear yours too. Unfortunately, as I think the team has already communicated, we are not really setup to do phone call ‘step by step’ feedback session with the resource team. If you could provide us with a bit more detail on where you think we could improve, we are all ears. If you want to record yourself speaking and send it over, that would work too!
Our small team’s priority right now is on the new ATC releasing next month, and the soon to be released MK3.
Looking forward to your feedback,
Stephen & the resource team
1 Like
@StephenCampbell FWIW, my comments. As I don’t have the kit, I am only going on what I see to be inconsistencies in the document.
In the second paragraph of the Install new motors section, you say:
“Let’s begin by sliding each M5-50mm bolt into a matching 40mm spacer.”
The picture shows that the spacers are slid over the bolts AFTER the bolts are pushed throught the holes in the motor. I assume that the picture is correct.
In the third paragraph of the SLB EXT section, you say:
“Now with the SLB installed …”. This should read: “Now that you have the SLB Ext installed …”
1 Like
Hey Grant,
Thanks for the great feedback, SLB - EXT is now cleared up (I had missed it in a couple spots) and I’ve clarified that the bolts go through the motor, then into the spacers.
Changes are live now.
Cheers,
Stephen
1 Like
Hi Stephen. When I went through the CLSM upgrade a couple of months ago, my comment to Tech Support was that the documentation required a significant effort to address the errors and omissions, and I was prepared to assist as I indicated. It was clear that the documentation had not been properly tested prior to release. I am glad to hear there have been some updates to the documentation, however, I am not prepared to put in the time and effort to review the current version of the documentation in detail and provide notes as you suggest. As a comment, you indicate that your team’s priority currently is “on the new ATC releasing next month, and the soon to be released MK3”. What about the quality of documentation for your current products?