2022-11-05 (Sa) PoweredInlineSkatesRev2 Hardware problems

I revised most of my Arduino sketch to accommodate ramping. Instead of instantly sending timing pulses to the ESC, it will gradually increase, so I shouldn't feel any acceleration jumps. I created a couple of variables to make tuning more manageable, like how great a span I will cover and how much to increase each cycle. My span started at 0 to 1000, which is 1:1 for the microsecond delay inherent in the timing pulses. I did some bench testing with the servo and changed the rate/cycle until it seemed reasonable.

Carrying the battery, Arduino, and ESC in one hand was cumbersome, so I got a leg bag to hold the hardware. I extended the wires of my potentiometer and went for a test. I felt some awful acceleration jerkiness, so I headed back. One problem could be that if I applied a low-speed signal to a quickly spinning motor, it would cause disruption. I added a minimum speed so it would jump to 20%, which seemed like a reasonable starting place. I also capped the rate at 80% to keep things safer during testing. Again, lots of stuttering during my test.

If I left the Arduino running by my computer, I saw issues where the servo would jump, which probably correlated to the erratic speed. My extra-long potentiometer wires were perhaps picking up interference, and I confirmed this by connecting the Arduino, ESC/battery, and computer to monitor the throttle. I saw much interference, especially when the unshielded wires were near the current-carrying wires. I will try for a wireless controller to keep my potentiometer wires short.
Thigh bag for battery and controls

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.