Answers are grounded in this paper and cite their sources.
Background A variety of different neuromuscular electrical stimulation (NMES) waveforms are used in clinical practice, yet limited data are available that have examined the fatigue response (FR) of muscle to these waveforms. Even less is known regarding the effects of resistance training on FR during NMES.Purpose This study was designed to examine FR in resistance trained versus untrained subjects, using two common NMES waveforms.Methods Twenty young adults (13 male, 7 female; 23 ± 2 y/o) were assigned to resistance‑trained (RT, n = 10) or untrained (UT, n = 10) groups. FR of the dominant quadriceps was calculated as the percentage decrease in electrically elicited force (EEF) between the highest and lowest repetitions over a single set of 10 repetitions using both Russian and symmetrical biphasic pulsed (SBP) waveforms. A two‑way repeated measures ANOVA was used to examine if training status or waveform affected the FR of the quadriceps.Outcomes Training status was not a significant factor in FR (F = .532, p = .475), with RT subjects showing an average FR of 49.1% across both waveforms versus 52.7% in the UT. NMES waveform was not a significant factor in the FR (F = 2.816, p = .111) showing an average FR of 55% with Russian across both groups and 47% FR with SBP. Training status was also not a significant factor in peak EEF (F = .0433, p = .838), with an average 29.9 lb in the RT group and 28.5 lb in the UT. However, waveform was a significant factor in peak EEF, with SBP showing an average of 40.57 lb vs. 17.9 lb for Russian (F = 25.203, p < .001).Discussion Resistance training nor NMES waveform affected FR of the quadriceps over repeated electrically elicited contractions. Additionally, these data support previous studies reporting significantly less EEF with Russian versus SBP current.
No takes yet. Share an insight, caveat, or question.
Bellew et al. (2026) studied this question.
Synapse has enriched 10 related papers. Consider them for comparative context: