Applied robotics without years of programming experience, in-depth knowledge of hardware?

Updated: Jul 5

So, How is this possible: Applied robotics without years of programming experience, in-depth knowledge of hardware with experience in building verbal algorithms.

Instrumental platforms in robotics and automation.

Today it is a stumbling block with a large set of questions like this:

How to automate the programming process?

How to reduce development time?

How to save costs and cost of finished products?

How to get rid of coding errors?

How to make a quick start from an idea to a ready-made solution?

How to expand and democratize the developer audience? The programming and prototyping process looks like an intuitive set of instructions.

You just need to have a behavior algorithm and set up its operation in a logical sequence, taking into account emergency situations. BEEPTOOLKIT is a new logarithmic platform for the development of robotics, automatics and intelligent systems. How it works:

Instructions are set visually on a graphical instruction entry console.

The console allows developers to perform simulations with or without hardware connection, perform parametric settings including communications, calibrations, etc.

Finally, after a satisfactory simulation, there is the possibility of external automated logging of your project (in the future, you have the opportunity to share this protocol with other corporate development groups, perform editing, etc.)

Thus, you get the source code of the project that can function in its development environment.

As for the external graphical wrapper for such protocols, such a possibility is provided so far in cooperation with the developer of the platform's instrumental environment.

From the moment the project protocol is provided and the design has been agreed with the designer, the construction of the interface takes from several hours to several days.

The speed and efficiency of the development process of robotics v.u. platform is 70 - 90% higher compared to classical methods and tools for the same tasks.

Regarding this particular concept, you can ask me any questions and if I don't give you a satisfying look then that's great, I love rebuses and puzzles, there is work to do. A very simple and illustrative example:

The fly analog computing device - slide rule

which allows people without deep thinking and mathematical education to perform calculations such as multiplication and division of numbers, exponentiation (usually square and cube), calculation of all square and cube roots, calculation of logarithms, potentiation, calculation of trigonometric and hyperbolic functions and some other operations. If we divide the calculation into three stages, then using a slide rule it was possible to actually raise the numbers to any real power and extract the root from any real power.

Before the advent of pocket calculators, this tool served as an indispensable computing tool at the level of schoolchildren, students, engineers and professors. All they needed were instructions and methods for working with the ruler. The accuracy of the calculations is about 3 significant figures.

A similar example - japanese abacus soroban

what Japanese students in elementary grades demonstrate today looks mesmerizing and grandiose.

They can do incredibly complex instant calculations in their head. They also know how to create them visually in their imagination and "virtually" move their elements.

This technique has today a large army of admirers and is being adopted by teachers of specialized schools.

Do you catch the line of reasoning?

This abstract example clearly demonstrates my paradigm - automated (autonomous) coding using a "logarithmic" software environment with a set of specific instructions (tools) that are not required from developers of deep theoretical knowledge, with a clear goal of one or another instruction required to achieve the final goal.

Of course, such a developer (without an encoder) must have an idea of ​​a binary signal, he must also have a sufficient level of understanding of ready-made hardware modular assemblies in terms of their parameters and their purpose, based on which he must be able to create software and hardware behavior algorithms for his ideas. These abstract examples clearly demonstrate the right to exist of a paradigm - automated (autonomous) coding by means of a "logarithmic" software environment with a set of specific instructions (tools) that do not require deep theoretical knowledge from developers, while clearly understanding the purpose or instructions necessary to achieve the final goal.

If, for example, you ask me a question about what the actual source code will look like, say controlling a stepper motor under such a tool?

Very simple:

* And its control algorithm is as follows:

1. Run the framework in automatic mode by default 15 seconds after downloading the program to the PC;

2. Supply power to the stepper motor driver in standby 12V;

3. Apply 5V to the PWM generator with power + CLK, clockwise rotation;

4. After 10 seconds, disconnect the 5V power supply from the PWM, the motor will go into hold mode>;

5. Apply 5V PWM signal to motor drive -CLK left rotation;

6. Disconnect 5V from PWM. After 1 hour, stop the engine by holding the mode;

7. Disconnect the 12V motor driver;

We also see the function of saving the protocol of the project code (source code) with all parametric settings in a binary format. * Scenario does not include feedback from angle resistive sensors. If they are included in the algorithm, then the trigger value sets the angles of rotation of the motor in the range from 0.001 to 3.300 V. An additional graphical console for setting is provided, which is called during debugging.

During development, we will be able to create libraries from such configurations (intermediate or final), access them, make changes and save them under a new name. All acquisition values ​​from each input can be recorded in real time over a full cycle or specific cycles from each trigger. This is an educational video for a quick start.

Chris Wanstrath, Co-Founder, CEO of GitHUB: "Coding is not the main event anymore. Building software is the main event."

124 views0 comments

Recent Posts

See All