I have somewhat similar issue although it's not as severe. But it's related to the diablo. With string going around the diablo, my wise head struggles a bit to get to the set tension, takes 5-10 secs. If I skip the diabo, no issue whatsoever. I read on here somebody said diablo was not really needed for badminton tension range but just to be safe, I still use it. It only slows me down on mains so adds around 2-4 mins in total. That's not a big deal, I still can do 20 mins. Perhaps I should try to update FW as well.
The diablo is important for even for badminton. the main purpose of the diablo is to spread out the amount of contact between the gripper and the string coating. badminton string is thin and the coat is delicate and easily torn by the gripper surface. winding it through the diablo means that the gripper doesn't need to grip as hard and also it will grip in a straighter angle so the corner of the gripper won't cut into the string.
when you string a racket does the wise always jumps for every string being tensioned ? can you tension the 1st 2 mains together and tell me if the racket handle is directly on top of the gripper ? a video would be nice
@khoai It seems to be much more stable than before. But the reading seems to be much less sensitive to the tension variation. @Marlboro No, it jumps from time to time. Sometimes, it is rock solid, sometimes it can jumps more or less as seen in the video. What do you mean by on top of the gripper? If you meant the alignment then yes it is.
try this tilt the wise to your left by 5 to 10mm. you can do this by adding washers (or any other means) to the base ("L"mounting bracket) on the right side edited: angle of pull is the problem, something to do with load sensor not being happy with the angle or alignment. fact that you don't see it jumping while testing tension { you can test this 10000 times, and i bet that the wise be rock solid) fact that when you are stringing a racket it only jumps from time to time, is be'cos the angle where the string existed the grommet is diff.
I will keep that in mind. For now, after the firmware update, it seems to be alright. If it happens again, I will experiment your solution Thanks !
