You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 20, 2019. It is now read-only.
In parallel though, if I read the async packets, I can get the real value:
orb.on("async", function(response){
var xField = {from: 0, to: 2, type: 'signed'};
var yField = {from: 2, to: 4, type: 'signed'};
var x = Packet.prototype._parseField(xField, response.data); // x is 255
var y = Packet.prototype._parseField(yField, response.data);
console.log('pos:', x, y);
});
Not sure whether it matters but I am using a Ollie.
Does anyone know what might be going on, why am I getting the wrong data in the readLocator but correct position in the streaming/async packets?
The text was updated successfully, but these errors were encountered:
This might not answering your question, but I am calling the odometer to get the x and y positions [1]. I was fiddling with readLocator before but found that they gave the same values for xpos and ypos; although calling the odometer seems way simpler.
Hi!
I've got some troubles with the readLocator response data.
Let's say I set the configuration as:
I will get a
2
asxpos
value the when I do:I've looked at the response from ollie on the readLocator and the response itself looks wrong. It has the xpos set to 2 and xvel is to 25 (
0x19
):In parallel though, if I read the async packets, I can get the real value:
Not sure whether it matters but I am using a Ollie.
Does anyone know what might be going on, why am I getting the wrong data in the readLocator but correct position in the streaming/async packets?
The text was updated successfully, but these errors were encountered: