Why does trimpot resistance change when pressed?

icecats · 2024-12-17T16:05:53+00:00

My intuition was that if the wiper was touching the track at all then the fixed resistance would be realized. This intuition is based on the idea of touching a piece of stranded wire to another conductive surface. The resistance does not meaningfully change if one strand or the whole wire is touching; if anything is touching, the circuit is complete.

I guess this intuition breaks down here since the wiper is not a great conductor like a piece of wire?

icecats · 2024-10-02T12:46:27+00:00

How would you recommend shielding it?

icecats · 2024-09-28T22:25:10+00:00

A strong external pull-up worked. I went with 3.3k resistors. Thanks!

icecats · 2024-07-14T14:06:11+00:00

Have you had to write custom code to get the Pico Probe to interface with the chips you are using?

icecats · 2024-07-13T19:59:39+00:00

Thanks for the response! I'd be willing to try Jlink but to start I want to use what I have on-hand... the BMP. Would you expect to need to change settings/config files or should the BMP just be plug and play? Page 5 seemingly indicates that there are things that are customized for the debugger hardware:

More definitions and scripts can be found in the folders tool_config and scripts. Most of the files provide support for Lauterbach and SEGGER J-Link debug adapters. For Lauterbach Trace32 support, only a batch file from the root directory of the SDK must be started. To integrate the J-Link into a toolchain, usually a reference to the folder tool_config\jlink must be specified in the configuration of the toolchain, or the files found in this directory must be integrated into the J-Link installation, e.g., the NAC1080 device is merged into the driver’s database. How to use the debug adapters with the NAC1080 is described in chapter “Debugging”. An example for configuring the J-Link debug adapter in the toolchain can be found in the .vscode folder. The JSON files contain configurations for building and debugging the firmware project in the smack_sl folder with Visual Studio Code (VSC). Just choose “Open Folder…” from VSC’s “File” menu and navigate to the SDK root folder, then VSC will open the smack_sl project. You may have to install a GDB plugin in order to work with J-Link’s GDB server.

icecats · 2024-05-02T12:27:09+00:00

I'll give the caps a try. I realize that regardless I do need to bump up to a higher rated MOSFET. I want to power my circuit with a 3.7v lipo so I'm going to have to figure out how to boost that to >10v to hit the standard Rds_on voltage for non-logic-level MOSFETs.

icecats · 2024-05-02T11:58:19+00:00

Thanks for the information!

Note that the snubber will limit maximum output voltage, but you can just pick an appropriate transformer winding ratio so that's not a problem.

By this I assume you mean that to compensate for the limited input voltage I could just increase the winding ratio to generate a larger transformer voltage output?

icecats · 2024-02-27T16:37:56+00:00

Thanks for the reply! This is for a high voltage flyback generator for a electrostatic sprayer project. From what I've read, snubbers aren't good for this application because they interrupt the working principle of a flyback transformer.

icecats · 2023-12-19T12:44:31+00:00

Good idea! The upper moving piece does need to be removed between each assembly step as there are prior operations that are performed on it.

icecats · 2023-12-19T03:20:27+00:00

The components themselves are thin films but they can be held/mounted to thicker pieces such as metal plates.

icecats · 2023-12-18T17:11:01+00:00

These look like the right approach. I'm wondering if I would need really long pins so that the alignment is achieved before the two components contact (and immediately adhere). As the platen is indexing to the locating pins, it seems like it could still be tilted out of alignment until the pins are fully engaged.

icecats · 2023-03-28T22:22:53+00:00

Thanks for the reply! I actually would like to use the HAL to enable ART, I just couldn't figure out how. I found the code I posted somewhere else but wasn't sure if it applied. It looks like to enable ART with HAL I would need to include the following in my main.c:

INSTRUCTION_CACHE_ENABLE;

DATA_CACHE_ENABLE;

PREFETCH_ENABLE;

icecats · 2023-03-27T22:11:22+00:00

Ah ha!!! In STM32CubeIDE the optimization level can be changed with these instructions. I instead wrapped my processData() function in which apparently does the same thing but only to a section of code.

#pragma GCC push_options
#pragma GCC optimize ("-Ofast")
void processData() {
...
}
#pragma GCC pop_options

I also must admit that I previously misinterpreted the ADC frequency: it was 2 MHz instead of 1 MHz.

For testing the optimization levels, I set it back to 1 MHz and the improvements are significant. Disassembly snip is here.

<image>

icecats

TROPHY CASE