Stackshot controller bug

seta666 · Post by **seta666** » Tue Jun 05, 2012 12:33 pm

Hello,
There is a bug in stackshot controller, when trying to set step size to 10mm it jumps to maximum value.

here is a video of this bug
http://www.youtube.com/watch?v=AEuvZwBd ... detailpage

Regards
Javier

rjlittlefield · Post by **rjlittlefield** » Tue Jun 05, 2012 12:57 pm

Interesting! I cannot reproduce the problem with my unit, which has a slightly different firmware version. I suggest working with Cognisys to narrow down exactly what's causing the difficulty.

--Rik

seta666 · Post by **seta666** » Tue Jun 05, 2012 1:03 pm

rjlittlefield wrote:Interesting! I cannot reproduce the problem with my unit, which has a slightly different firmware version. I suggest working with Cognisys to narrow down exactly what's causing the difficulty.

--Rik

I know of one more person with this problem; the firmware was updated with one sent to my by cognisys. Is yours a newer version or older?
Jotafoto has an older version (without high precission mode) and it does not have this bug

I will contact cognisys right now
regards
Javier

rjlittlefield · Post by **rjlittlefield** » Tue Jun 05, 2012 7:54 pm

Mine says this on bootup:

Code: Select all

  == StackShot ==
SW Rev&#58; 1.0.06
Apr 17, 2011
11&#58;23&#58;53

Your video shows:

Code: Select all

  == StackShot ==
SW Rev&#58; 1.0.06 1W
Apr 17 2011
11&#58;24&#58;06

Note: I have to revise my report. I can reproduce your problem, by resetting my configuration to be the same as shown in your video:

Code: Select all

Dist/Rev&#58; 3.175 mm

With that setting, I see the same sort of funny jumps that are shown in your video. This condition persists until eventually I hold the Down key continuously pressed for long enough that the step size drops to 1 micron, at which point everything behaves sanely until I increase the step beyond 9.999 mm again, in which case it immediately jumps to 40.00.

If I reset to

Code: Select all

Dist/Rev&#58; 1.587 mm

then the behavior changes, but still it's not right. In that case, incrementing by one press of Up starting at 9.990 gives 9.991, 9.992, 9.993, 9.994, 9.995, 9.996, 9.997, 9.994, 9.995, 9.996, 9.997, etc, repeating cyclically between 9.994 and 9.997 by 0.001 on each quick press. In this case pressing and holding Up leaves the value stuck between 9.994 and 9.997, but there's no problem going back Down.

If I reset to

Code: Select all

Dist/Rev&#58; 1.588 mm

then the behavior changes, but again it's not right. In that case, incrementing Up through 10.00 works OK but pressing Down then gets stuck at 10.00. Once it's stuck at 10.00, apparently no number of quick presses of Down will get it unstuck. (I quit at 100 presses.) However, holding Down pressed for about 9 seconds will break through the stuck-point and then things are fine again until the next time back Up to 10.00.

Correct operation can be restored by resetting the StackShot controller to default settings by holding the Down button while cycling power. There is also a sequence using Zerene Stacker to set the default value of 1.5875 mm/rotation (25.4 mm in 16 rotations), then forcing the configuration to be saved to non-volatile memory by changing the maximum rail speed. In either case, after the reset the StackShot controller's display shows 1.588 mm per rev, but the Up/Down behavior around 10.00 seems to be correct again, obviously different from setting 1.588 mm per rev via the StackShot controller's buttons. At the moment I'm speculating that the default value of 1.5875 mm/rotation is somehow magical.

--Rik

Edit: to add info about resetting with Down+power.

seta666 · Post by **seta666** » Wed Jun 06, 2012 2:04 am

I have contacted cognisys and they were not aware of this bug; they are working on a new version of the software to add new features and will also address this bug.
As you say it has something to do with the dist/rev values; different values give different conditions equally not good

I guess they did not test other values when they made the firmware and somehow that 1.5875 value is magical as you say

I left mine at 3.175mm/rev, which is 10x the real travel distance

This allows me to make 0,1um steps (1um/10) and up to 0,99mm steps with out problem (9,9mm/10) because problems start when setting 10mm value

I had also noticed this problem before as I had the dist/rev value set to 15,875 which would allow me to give 0.5um steps (5um/10)

Regards
Javier