2022-11-19 (Sa) PoweredInlineSkatesRev2 Problem after problem

I was finally ready to develop my calibration and speed measurement program with most of the hardware built. When I connected a battery power, I saw runaway motor speed when the motor should have been still. I thought the interrupt code could interfere with the motor signals and saw two ways to combat that problem. The first solution I considered was adding the dedicated servo board, which wouldn't be bogged down with the Arduino's processes. The second solution was to rewrite the code so that interrupts couldn't have much effect, and that's where I started. The motor pulses take so little time to transmit, one to two milliseconds, that I halted the program during those breaks, and it worked all right before. The new attempt replaced the delays with empty while() loops that expired when the controller reached a preset time. Nothing changed after the code update, and when I enabled some debugging code, I saw a lot of unwanted data coming from the data line, as though the BT module was picking up stray data streams.
Cool underlight

The rest of the posts for this project have been arranged by date.
First time here?

Completed projects from year 1
Completed projects from year 2
Completed projects from year 3
Completed projects from year 4
Completed projects from year 5
Completed projects from year 6
Completed projects from year 7
Completed projects from year 8

Disclaimer for http://24hourengineer.blogspot.com and 24HourEngineer.com

This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.

All information on this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property, or similar, is the responsibility of those involved in the replication.

All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by  Brian McEvoy, cannot be used to claim property or assets.

Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.

This blog, including pictures and text, is copyright to Brian McEvoy.