PRSAlpha Indexer Unit Value

[Justin G]

I'm curious to hear what you think is the culprit. I remember speaking with support a year or so ago when I got my indexer before erasing my setup by accidentally loading a different custom configuration and they told me the indexer motorwas not programmed at the factory. Or something to that effect.

This morning I turned on the indexer with the 140.0000 value I had been using. Typing a 360 command output about 180 degrees of rotation real world. So no idea why it magically changed but I doubled it so my b unit value was around 280.0000. I then proceeded to trial and error using a square and a couple notches on the top of the indexer motor bracket and Chuck. I started with mb 360 and made adjustments to the value until it was as close as I could detect. I then did a mb 3600, and then MB 5400, and every time fine tuning going back and forth between mb 0 and MB multiples of 360. This is obviously not the most scientific way but after 60 rotations or so, the marks are as close as I can tell dead on. Unit value isn't in front of me but it was somewhere in the 277.7500 range.

[Brady Watson]

Don't know about that one...Why would the UV suddenly change from around 140 to 280? Yes, multi-rotations for checking the UV is the proper way to sneak up on it.

-B

[Justin G]

yup neither do I. The only thing I could think would be some kind of VS command changed the speed so dramatically it threw the rotation off? I had managed to finish a whole slew of orders and had a day of downtime to mess with the indexer again. The only thing I changed between testing it was working on a custom zzero program so unless I am missing something (which anyone that knows me would say...) could it be that?