Parameter glitch?

I am not sure if this is the right forum to post this...if not, please advise and I'll move it.  I am an Iris owner...original Iris, not Iris+.  However, I am updating my Iris to the + with the upgrade kit.  In advance of actually installing the kit, I was playing around with the Iris+ parameters.  Iris+ has redirected flight modes from the original Iris.  When selecting the Iris+ parameters, the flight modes are modified to match those of the Iris+, which is what I would expect.  

However, then I decided to put my copter back to the original Iris parameters.  In doing so, the flight modes did not change back to those of the original Iris, but remained as they were for the Iris+...is this the way it should work?  Doesn't seem right, but not sure if this is a glitch, bad code, intended, or what.  I can manually put these back, so that part is really not that big a deal, but I have to wonder, if the flight modes do not follow the assigned parameter template, what other parameters remained in the Iris+ model versus the original Iris template.  Since I didn't think it necessary to save my original Iris parameters, I don't have those to compare to.  Anyway, in that I will have installed the Iris+ upgrade kit before the end of tomorrow, not a huge problem, but if this is a glitch, I thought I'd bring it out for comment.

TIA

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Replies

  • Developer

    The parameter files are intended to be applied against the defaults to configure a vehicle, not to swap between vehicle configurations.  We do it that way because it uses less memory.  The flight modes will change when you load a new parameter file.  If they did not then something else happened.  Perhaps you forgot to save the parameters to the vehicle.

This reply was deleted.

Activity

DIY Robocars via Twitter
Oct 23
DIY Robocars via Twitter
RT @_JonMyer: 🏎 We need your help in naming my #AWS DeepRacer Underground Track 🏎 @davidfsmith's track is going to be referred to as 𝗔𝗪𝗦 𝗗…
Oct 22
DIY Robocars via Twitter
RT @gclue_akira: 仕事もおわったし、電脳化にとらい #マリオカートハック https://t.co/4IU90hCLgm
Oct 22
DIY Robocars via Twitter
This is the hashtag to follow all the people in Japan who are hacking the new Nintendo Mario Kart with the real AR… https://twitter.com/i/web/status/1319281354664677376
Oct 22
DIY Robocars via Twitter
RT @gclue_akira: @chr1sa @diyrobocars jupyter mario https://t.co/P0oHdjlCRq
Oct 22
DIY Robocars via Twitter
RT @_JonMyer: 🚨Our 1st AWS DeepRacer Community Race is Underway on http://twitch.tv/aws 🚨 Join us to find out which member of your commu…
Oct 20
DIY Robocars via Twitter
Oct 19
DIY Robocars via Twitter
RT @BackyardRobotcs: After an admittedly long wait, the new Tinymovr R3.3 motor controller is now available https://tinymovr.com 🥳
Oct 19
DIY Robocars via Twitter
RT @_JonMyer: 🏎 1 hr left before the #AWS #DeepRacer Community 🏎 Top 5 Race tomorrow LIVE on Twitch 1st Place = $50 Amazon GC or AWS Credit…
Oct 19
DIY Robocars via Twitter
Oct 16
DIY Robocars via Twitter
Oct 15
DIY Robocars via Twitter
Oct 14
DIY Robocars via Twitter
RT @davidfsmith: Race virtually with The AWS DeepRacer Community Race and then join us on the track to see how your times compare on the ph…
Oct 14
DIY Robocars via Twitter
Oct 14
Hiroki Tanaka liked Hiroki Tanaka's profile
Oct 13
DIY Robocars via Twitter
RT @breadcentric: It's now!
Oct 13
More…