Changing acceleration rate gives BAD_REQUEST on Movesense for Xamarin
up vote
2
down vote
favorite
I would like to change the acceleration rate on my Movesense device via Xamarin API.
I already tried the following, but it just gives me a BAD_REQUEST:
string NEW_ACC_CONFIG = "{"config":2}";
var op = await Plugin.Movesense.CrossMovesense.Current.ApiCallAsync<string>(
Name,
Plugin.Movesense.Api.MdsOp.PUT,
"/Meas/Acc/Config/",
NEW_ACC_CONFIG
);
It seems that the contract which is sent is empty.
Thanks for the help!
xamarin movesense
add a comment |
up vote
2
down vote
favorite
I would like to change the acceleration rate on my Movesense device via Xamarin API.
I already tried the following, but it just gives me a BAD_REQUEST:
string NEW_ACC_CONFIG = "{"config":2}";
var op = await Plugin.Movesense.CrossMovesense.Current.ApiCallAsync<string>(
Name,
Plugin.Movesense.Api.MdsOp.PUT,
"/Meas/Acc/Config/",
NEW_ACC_CONFIG
);
It seems that the contract which is sent is empty.
Thanks for the help!
xamarin movesense
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I would like to change the acceleration rate on my Movesense device via Xamarin API.
I already tried the following, but it just gives me a BAD_REQUEST:
string NEW_ACC_CONFIG = "{"config":2}";
var op = await Plugin.Movesense.CrossMovesense.Current.ApiCallAsync<string>(
Name,
Plugin.Movesense.Api.MdsOp.PUT,
"/Meas/Acc/Config/",
NEW_ACC_CONFIG
);
It seems that the contract which is sent is empty.
Thanks for the help!
xamarin movesense
I would like to change the acceleration rate on my Movesense device via Xamarin API.
I already tried the following, but it just gives me a BAD_REQUEST:
string NEW_ACC_CONFIG = "{"config":2}";
var op = await Plugin.Movesense.CrossMovesense.Current.ApiCallAsync<string>(
Name,
Plugin.Movesense.Api.MdsOp.PUT,
"/Meas/Acc/Config/",
NEW_ACC_CONFIG
);
It seems that the contract which is sent is empty.
Thanks for the help!
xamarin movesense
xamarin movesense
edited Nov 9 at 15:56
asked Nov 9 at 12:10
Srh
164
164
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
BAD_REQUEST means that the NEW_ACC_CONFIG you are giving is not in a correct format or that the values are incorrect. Comparing it to the acc.yaml shows that the parameter config is not an integer (2) but an object of format AccConfig i.e. the following JSON should work:
{
"config":
{
"GRange":2
}
}
Full Disclaimer: I work for the Movesense team
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
BAD_REQUEST means that the NEW_ACC_CONFIG you are giving is not in a correct format or that the values are incorrect. Comparing it to the acc.yaml shows that the parameter config is not an integer (2) but an object of format AccConfig i.e. the following JSON should work:
{
"config":
{
"GRange":2
}
}
Full Disclaimer: I work for the Movesense team
add a comment |
up vote
0
down vote
BAD_REQUEST means that the NEW_ACC_CONFIG you are giving is not in a correct format or that the values are incorrect. Comparing it to the acc.yaml shows that the parameter config is not an integer (2) but an object of format AccConfig i.e. the following JSON should work:
{
"config":
{
"GRange":2
}
}
Full Disclaimer: I work for the Movesense team
add a comment |
up vote
0
down vote
up vote
0
down vote
BAD_REQUEST means that the NEW_ACC_CONFIG you are giving is not in a correct format or that the values are incorrect. Comparing it to the acc.yaml shows that the parameter config is not an integer (2) but an object of format AccConfig i.e. the following JSON should work:
{
"config":
{
"GRange":2
}
}
Full Disclaimer: I work for the Movesense team
BAD_REQUEST means that the NEW_ACC_CONFIG you are giving is not in a correct format or that the values are incorrect. Comparing it to the acc.yaml shows that the parameter config is not an integer (2) but an object of format AccConfig i.e. the following JSON should work:
{
"config":
{
"GRange":2
}
}
Full Disclaimer: I work for the Movesense team
answered Nov 20 at 8:56
user1987093
27819
27819
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53225469%2fchanging-acceleration-rate-gives-bad-request-on-movesense-for-xamarin%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown