Back to The tech awesomeness
Table of contents
Endeavor chapters

The article for today.

There are two types of batteries of different standards(AA, AAA, others) avaibable in the locality: one time ones with no recharging possibility and accumulating ones with recharging possibility.

The rechargers available are mostly the devices whuch wrap the accumulating batteries and contacting them to transfer the charge. Most of which are contacting them for getting the charge.

There are no accumulating batteries available for getting the charge for them wirelessly.

There are no accumulating batteries available for getting the charge for them via some port, for example, USB, Lightning, Thunderbolt.

There are no phones and smart telephones available for getting the charge for their accumulating batteries by changing their accumulating batteries.

I do not charge the phone and smart telephone and other devices, I charge the accumulating battery. It seems like that I am charging the phone and smart telephone and other devices, however I charge the accumulating battery inside by connecting the cords from the power source. Those accumulating battery and batteries inside are charging the phone.

There are three types of devices available in the locality.

The first type is the devices which does not have the possibility to have the power from accumulating batteries, such stationary devices.

The second type is the devices which have the the possibility to have the power from changeable accumulating batteries(and also from one time batteries), such mobile, portable, autonomous devices.

The third type is the devices which have the the possibility to have the power from non-changeable accumulating batteries, such also mobile, portable, autonomous devices.

One peculiarity for me is the following two cases. The first one is that with the second type of devices, I do easily recharge the accumulating batteries, I almost always either recycle the old one time batteries or I am searching and using a third specific wrapping charging device to recharge accumulating batteries.

So I was charging device availability locked in this case.

And the second one is that with the third type of devices, I easily recharge the device with accumulating batteries wirelessly and using wires and when it is not charging I am searching and using the third specific service to have the device chargeable again and to change the accumulating battery, so that I do not easily change that accumulating battery, batteries inside.

So I was service availability locked in this case.

There are no phone, smart telephone, other device in the locality where it is possible to change for example two out of seven wire and wireless recharging accumulating batteries while phone is operating to recharge such phone, smart telephone, other device with no extra connection of any cords inside such device.


←  up           device                                  down→
.............................................................
.                       ok         ok                       .
.                       for        for                      .
.  ok      ok      ok   recharge   recharge ok      ok      .
.   .       .       .    .          .        .       .      .
.  ...     ...     ...  ...        ...      ...     ...     .
.  ...     ...     ...  ...        ...      ...     ...     .
.  ...     ...     ...  ...        ...      ...     ...     .
.  ...     ...     ...  ...        ...      ...     ...     .
.  ...     ...     ...  ...        ...      ...     ...     .
.  ...     ...     ...  ...        ...      ...     ...     .
.  ...     ...     ...  ...        ...      ...     ...     .
.                                                           .
.                                                           .
.                                                           .
.............................................................

or

←  up           device                                  down→
.............................................................
.                                  ok                       .
.                                  for                      .
.  ok      ok      ok    empty     recharge ok  ok          .
.   .       .       .               .        .       .      .
.  ...     ...     ...             ...      ...     ...     .
.  ...     ...     ...             ...      ...     ...     .
.  ...     ...     ...             ...      ...     ...     .
.  ...     ...     ...             ...      ...     ...     .
.  ...     ...     ...             ...      ...     ...     .
.  ...     ...     ...             ...      ...     ...     .
.  ...     ...     ...             ...      ...     ...     .
.                                                           .
.                                                           .
.                                                           .
.............................................................

←  up           device                                  down→
.............................................................
.                                                           .
.                                                           .
.  ok      ok      ok    empty     empty    ok      ok      .
.   .       .       .                        .       .      .
.  ...     ...     ...                      ...     ...     .
.  ...     ...     ...                      ...     ...     .
.  ...     ...     ...                      ...     ...     .
.  ...     ...     ...                      ...     ...     .
.  ...     ...     ...                      ...     ...     .
.  ...     ...     ...                      ...     ...     .
.  ...     ...     ...                      ...     ...     .
.  not     not     not                      not     not     .
.  for     for     for                      for     for     .
.  removal removal removal                  removal removal .
.............................................................




    .........
 ................
 ..................
  ..................
   ..................
    ..................
     ..................
      ..................
       ..................
         ................
          ......  ..  .....
            ...............


Оновлення від 2021-06-20.

The update from 2021-06-20.

After 5 years I finally grasped which problem I encountered with Raspberry Pi 2, its instance, його зразком.

It really implies that you do not need only to think about software, but also about Watts and Volts and Ampers. But that is not all. You also need to think about IO.

It reminds a bit that situation in the C++ software, where you need to think about pointers and others.

So that it does not abstract you from that one as some layer after introdution abstract it from pointers in Java software.

No idea, how that situation is with NVidia and Arduino products.

Even more to do it all, especcially if you are sending some signals wirelessly.

So once again such situation leads to:

And such one:


                               _
    /\                        / \ 
    \/  <-------------------> \_/

And such one:



                            
     кіт; кішка; 😼 <-------------------> 🐌; вулик

And also it reminds such distibution:


↑
|                 .
|                 .
|                .
|               .
|             .
|           .
|        .   
|.  .                          
------------------->
                5500.

with a more 5500 as a proper value there than other one.

Гадаю транзит до цієї технології тут теж має місце як приклад.

Тож знов.

https://en.wikipedia.org/wiki/Grand_Central_Dispatchвцр;GCD;libdispatch та https://en.wikipedia.org/wiki/Automatic_Reference_Counting у https://en.wikipedia.org/wiki/Memory_management формують шаблон: коли існує багато чогось і багато чогось і вони попередньо оброблялись не автоматично і вони повторювані.

Any ideas on that or question about labels near horizontal and vertical axes? +380661907243; тоді +380 63 553 1264; Global System for Mobile Communications(GSM).

Оновлення від 2021-06-21.

The update from 2021-06-21.

Згадуючи досвід, в есенції там в створенні чогось з частин і Raspberry Pi 2 там теж є крокі схожі на компіляцію і з'єднання в якомусь програмному забезпеченні.

Але якщо це робиться якимись ввідними пристроями для програмного забезпечення там це робиться руками.

Але ось в чому відмінність: якщо я щось не так скомпілював чи з'єднав в програмному забезпеченні я отримую повідомлення про провал компіляції.

А якщо я щось не так "скопілював" чи "з'єднав" з частин і Raspberry Pi 2, наприклад 20 ват там де 2 ват і згідно якогось процесу вмикнув таку "компіляцію" вмиканням живлення, то я не отримаю повідомлення про провал "компіляції" у тій такій формі, я отримаю не працюючу частину чи сам Raspberry Pi 2.

Проте перевага, що це дуже гнучко як процес. І налаштування теж.

А висновок такий, що воно потребує більше пильності. Незважаючи чи я використовую ~ чи - струм.

А висновок такий, що якщо я людина з якимось розладом, коли пильність менше, ніж зазвичай, таке завдання майже дуже складне для мене.

А наслідок такий, щоб повторити таку "компіляцію" з іншою конфігурацією, я маю продати кота і кішку якщо він є в доступності, хоча коту і кішці це може і не сподобатися, і придбати іншу ту таку частину чи Raspberry Pi 2. Для цього ще треба знайти яку саме частину перед цим. А ще ту частину потрібно утілізувати і краще щоб не в океан.

Якщо у межах процесу від його створювання до його використання до його сміттєзнаходження, не інкаше навпаки як у межах процесу від його сміттєзнаходження до того як воно опинилося там.

Або бути більш пильним.

А ось у випадку для людини з якимось розладом, бути більш пильним не спрацює так гладко.

Тому той конвертер чи обмежувач, чимось схожий на компілятор ПЗ, який забезпечує безпеку повідомленнями про провал компіляції там. Хоча це і повільніше і не так гнучко ніж в інтерпретованих мовах програмування.

Refreshing the experience, in essense there in creation of something from parts and Raspberry Pi 2 there are steps similar to compilation and linking in some software.

But if it is by some input devices for software it is by hand in there.

But here is the difference: if I do not compile or link something in software I get a message about compilation failure.

But if I do not "compile" or "link" something with parts and Raspberry Pi 2, for example I have put 20 Watts where it is for 2 Watts and according to some process I turn on such "compilation" by power both ones, parts and Raspberry Pi 2, then I will not get a message about "compilation" failure in that such form, I will get the non functional part or Raspberry Pi 2 itself.

But and advantage, that it is a pretty flexible process. And its configuration too.

And the conclusion is, that it requires more accuracy. No matter whether I use AC or DC for it.

And the conclusion is, that as a human with some disorder, when the accuracy is lower than usually, such task is almost very complex for me.

And the consequence is, that to repeat such "compilation" with other configuration, I have to sell a cat if it is available, but the cat can dislike it, and to buy another such part or Raspberry Pi 2. For that one it requires to find which that part before that. And that part requires utilisation and it is better not in the ocean. All that takes time.

If in scope of the process from its making to its usage to its debris, not else vice versa in scope of the process from its debris to how it appeared there.

Or to be more accurate.

But in a case with a human with some disorder, to be more accurate it is not suitable as smoothly.

That's why that converter or limiter, in some similar to software compiler, which provides safety by the messages about compilation failures there. But it is slowlier and not as flexible as in computer languages with interpreters.