_Ozzee_

Guys, please tell us how the servo mode works in the new update 1.4? Does anyone have a problem with it?

Congratulations with the release of the application Powered Up 3.0. It is just wonderful! (Not)

Enjoy it) I want to take short rest, and will bring some more features)

Hello! A lot of news) The update is almost done. It remains to do a couple of little things, conduct tests and it will be possible to publish. I think the publication will take place this week. I will publish the list of changes and screenshots of the application a little later, because something may be added, but something may not be included in the update.

Some information for Russian speaking peoples: Для русскоговорящих пользователей, так же есть тема в группе LTR в вк: VK

A bit of development news. I made a servo implementation, in my opinion, a copy like the original application, it works fine, I’m not ashamed of it. I made profiles of smooth acceleration, deceleration of motors, now the model stops with inertia, as it should. C ++ code was rewritten again and cannot be directly integrated into the current application, so I will reassemble the application. I also thought UI and have thoughts on optimizing the interface in terms of convenience. I need a time to build the next version, I did not forget and did not abandon this project. if someone wants to support the development of the project, here is the link: Support page ( I want to raise funds will go for the purchase of other systems, like buwizz, and the development of ios version. )

Accepted. I'll see what I broke there)

I can do it. I’ll tell you a little about how it is arranged now: now there are 3 gradations of vibration, light, medium, hard. They differ only in action time, easy 20ms, used when touching the control, average 50ms, used for tactile feedback when moving the slider, hard is not used anywhere. From my remarks, different phones work out the same vibration differently, my s8 works fine with a soft and the test huawei gives almost nothing with a soft. I see the force setting in the coefficients for the current values, I will do in the next update. At the moment I took a break in development, as there are basic tasks for my job.

When testing, everything worked well. A couple of days ago I controlled my model using the horizontal buttons in servo mode, everything was fine. Maybe something I do not understand from your words? Perhaps you are talking about the fact that if you first turn on the run mode of the motor, and then change the mode to servo, then when you press the motor starts to spin like during a run? This is quite possible, since I did not completely understand the encoder positions and after changing the mode, I need to do the calibration. I'll do it in the future. Usually after a run, the motor becomes in 0 position and the servo mode is working normally, this can create a problem for an already assembled model. It's a bit complicated I wrote) But I don’t know how to describe it more simply)

Glad you like it! Servo mode is available for only two items. None of the vertical elements should have a servo angle switch. if you can, take screenshots of what you consider a bug and send it to maksim.nemna.dev@gmail.com

Absolutely true, at the moment it is not so scary. Now there are things more important) Just need to switch from saving in binary format to text, this will allow you to exchange profiles in the future. Thanks for the support!

Yes, everything is exactly as you said) all components have one data structure at the base, this is necessary for unification, in this update new features and new controls were added that required expanding the data structure, which led to incompatibility of the saves. maybe I'm using the wrong approach in data storage, but at the moment, this is what I can do)

With updates this is not a bug, often i have to make changes in the controls data structure, this breaks the saves. I understand that i can’t do this every update) I’ll try to think over this point in the future) I apologize for the broken saves)

Updated my message.

1.3.1 version available in Google Play: Controlz -Added servo mode for horizontal buttons. -Redesigned palette of controls. -Added display of connected hub ports. -In the control settings, you can select only connected ports. -Added element "Tilt monitor".

In my experience, controlling a gyro is not convenient. I’ll do this when I introduce the main functions, and I have a lot of them in mind.

Thx! About next update: For horizontal buttons, add servo mode, 3 positions, without discrete (like PF servo with IR receiver and remote control) is added. I tried, the mode is good and can be used. The list of elements has been redesigned, since some elements now have dual functionality, the list is made in the form of cards, with a description of the functions of the element. At the moment, I’m doing a functional that will show which hub ports are connected to the motors, they will also be available for selection in the settings of the item (prohibiting the choice of a port if it is not connected to the device). I also understood how to get data from the gyroscope, it remains to describe this and make an element for output to the main screen.

1.3 update available in Google play. Added binding to the grid.

Finished work on binding elements to the grid, you can move with the binding and as in the current version. I will add this in the next update. I also think about optimizing the loading of profiles and connecting to hubs.

Open a user profile immediately after starting the program? Or open the program on the profile selection page?

Plans for further updates, not the next. ---GUI------------------------------------------------------ - Set a name for the control. - Binding controls to the grid. - Adding a new control 2 axis joystick. - Extension of the control settings functionality (for example: set a different polarity for the selected ports of one element). - Port management of multiple hubs from a single control. ---HARDWARE------------------------------------------- - Servo mode adjusting. - Output of information from the accelerometer. Suggest your options below. The pace of updates will become slower, since I have the job, which takes the main time. The common I think has already been done, the application is ready for use. A big request for those who use my app, please rate it in Google Play, I do not ask for good reviews, I ask for real reviews, write what you liked and what not. Your reviews help to display the application when searching. I put a lot of work into this application without asking for anything in return. I just want to convey it to the lot of people who do not know about it. It's a shame to have 42099 or 42100 and not be able to do something of your own, because you can not manage it.

The star button has two states, filled, contour. the filled one says that the hub is added to favorites, it will always be displayed, even if it is not connected, if it is not connected, the card has transparency and there is no battery indicator. You can change the name of the favorite hub by clicking on its name. When searching for devices, the favorite hubs are with the saved name. the second icon is an indicator of signal strength, I think it’s worth removing it altogether.

Change log: Now you can close the application. Now the application does not need permission to read and write your storage. Improved application layout. Added battery info to main screen.

1.2.1 update avalaible!

Thank you for feedback. 1. Profiles can be deleted from the first version, just swipe the profile card to the left. I apologize, maybe this is not obvious. 2. Unfortunately, I could not repeat the bug with the size of the slider, for me they are zoom our to a minimum. Give me more information about you steps to repeat slider bug. The size of the elements was chosen so as to cover the maximum number of screens, it may be necessary to adjust these sizes. Thanks! I will it. 3. I observed a flickering bug on one of the tested devices, most likely this is due to a specific graphic chip on a specific device. I will try to do something with it.