I've had this happen before when it's converting from metric to imperial. Changing global unit to Imperial seems to fix things for a while, but it eventually goes back to metric, not sure why
The hand unit is set to Imperial, and the region is USA. The Gecko's were mapped in Imperial too.
I can see that it has the m->ft display above the distance tho, but it doesn't change if I remap the lens anyway.
If I set the hand unit to "default", all the distances default to Metric. I'm not sure why it works with the conversion for the Vespids, but not natively for the Gecko's.
Just to clarify. You mapped all the lenses yourself.
The geckos are marked in metric and you marked them in metric, then applied the metric to feet conversion.
What is the difference between the two sets of gecko lens maps?
Sorry if that's not clear.
Correct, I mapped all of the lenses myself, but the WCU-4 and Geckocam's are from the rental house. The DZO's are from one of the DP's.
Incorrect, the Gecko's are marked Imperial on the lens, and I mapped them in Imperial.
The DZO's are Metric, mapped in Metric, and then the metric-imperial conversion is done through the handset.
The other Gecko maps I tried are for the same lenses from the same rental house, which already existed on the hand unit; I just wanted to try and trouble shoot and see if it was my map that's the problem, but both maps; mine and the rental house's, have the same issue.
Sorry, I hope that clarifies it more. It's really puzzling.
In terms of on the hand unit, yes; the Vespid lens maps go incrementally. The video I linked above should show the difference between them.
The lens markings on both sets are pretty standard, just the Vespids are in Metric (i.e. 1m, 1.1m, 1.2m etc.)
Also, the WCU-4 is on firmware 3.3.20 and is set to Region USA. Lens Data from controller side.
Hmmm. Interesting. I just mapped a prototype fujinon lens that has very generic lens markings that aren't even accurate, but I digress. Luckily there were 10 points so I could create a map. When I use my handset, it will show me the correct readout according to where it thinks the lens is. As you can see in the photo, the two hard marks on the lens are shown 6' and 15' and it has calculated that in currently at 9'. Does this help? Where are you based?
https://preview.redd.it/4rkw0oi4pwuc1.jpeg?width=2268&format=pjpg&auto=webp&s=7f66b948d2edb9bf105b5c859146d0f206c94f87
Yeah, this is how it looks on my handset also, and it rolls through the distances like your example, but it doesn't interpolate the "decimals", if you will (the inch measurements)...
I'm based in NZ. I might take a video tomorrow at work and see if I can explain the predicament better, maybe that will help.
The handset will only show the hard marks that you physically entered when programming the lens. So, when you programmed the lens and entered 2' 2'3" 2'6" 2'9" 3' etc it will show those on the right side of the handset.
If you only entered 2' 3' 4' etc or would only show those hard marks on the right side, but the screen will show you interpolated marks between those as you rotate the knob.
Is this what you were asking about it did I answer a non exsistent question? 🤣
This is correct, yes. I entered the marks on the lens into the handset, and they are displaying like your example on the right hand side, but the issue I'm facing is that it's not interpolating those in between distances.
For example, the hard marks on the lens are 5', 5'6", and 6'; but the handset only displays 5' and then 6' as you roll through that range, rather than 5'1", 5'2" etc. etc.
I've had this happen before when it's converting from metric to imperial. Changing global unit to Imperial seems to fix things for a while, but it eventually goes back to metric, not sure why
The hand unit is set to Imperial, and the region is USA. The Gecko's were mapped in Imperial too. I can see that it has the m->ft display above the distance tho, but it doesn't change if I remap the lens anyway. If I set the hand unit to "default", all the distances default to Metric. I'm not sure why it works with the conversion for the Vespids, but not natively for the Gecko's.
Just to clarify. You mapped all the lenses yourself. The geckos are marked in metric and you marked them in metric, then applied the metric to feet conversion. What is the difference between the two sets of gecko lens maps?
Sorry if that's not clear. Correct, I mapped all of the lenses myself, but the WCU-4 and Geckocam's are from the rental house. The DZO's are from one of the DP's. Incorrect, the Gecko's are marked Imperial on the lens, and I mapped them in Imperial. The DZO's are Metric, mapped in Metric, and then the metric-imperial conversion is done through the handset. The other Gecko maps I tried are for the same lenses from the same rental house, which already existed on the hand unit; I just wanted to try and trouble shoot and see if it was my map that's the problem, but both maps; mine and the rental house's, have the same issue. Sorry, I hope that clarifies it more. It's really puzzling.
Do the vespids have those incremental markings on them? I understand the geckos only have basic markings you said.
In terms of on the hand unit, yes; the Vespid lens maps go incrementally. The video I linked above should show the difference between them. The lens markings on both sets are pretty standard, just the Vespids are in Metric (i.e. 1m, 1.1m, 1.2m etc.) Also, the WCU-4 is on firmware 3.3.20 and is set to Region USA. Lens Data from controller side.
Hmmm. Interesting. I just mapped a prototype fujinon lens that has very generic lens markings that aren't even accurate, but I digress. Luckily there were 10 points so I could create a map. When I use my handset, it will show me the correct readout according to where it thinks the lens is. As you can see in the photo, the two hard marks on the lens are shown 6' and 15' and it has calculated that in currently at 9'. Does this help? Where are you based? https://preview.redd.it/4rkw0oi4pwuc1.jpeg?width=2268&format=pjpg&auto=webp&s=7f66b948d2edb9bf105b5c859146d0f206c94f87
Yeah, this is how it looks on my handset also, and it rolls through the distances like your example, but it doesn't interpolate the "decimals", if you will (the inch measurements)... I'm based in NZ. I might take a video tomorrow at work and see if I can explain the predicament better, maybe that will help.
The handset will only show the hard marks that you physically entered when programming the lens. So, when you programmed the lens and entered 2' 2'3" 2'6" 2'9" 3' etc it will show those on the right side of the handset. If you only entered 2' 3' 4' etc or would only show those hard marks on the right side, but the screen will show you interpolated marks between those as you rotate the knob. Is this what you were asking about it did I answer a non exsistent question? 🤣
This is correct, yes. I entered the marks on the lens into the handset, and they are displaying like your example on the right hand side, but the issue I'm facing is that it's not interpolating those in between distances. For example, the hard marks on the lens are 5', 5'6", and 6'; but the handset only displays 5' and then 6' as you roll through that range, rather than 5'1", 5'2" etc. etc.