2025-09-29 – Weekly Railroad News : Remote engineering roles expand

Last week, our community engaged in insightful discussions about the evolving landscape of railroad jobs, particularly the growing opportunities for remote engineering roles. Members also delved into the challenges surrounding training gaps in railway tech, highlighting the need for updated educational resources. Technical discussions around frequency settings and locomotive specifics captured the attention of many, while operational nuances, like securement time and brake test procedures, sparked thoughtful exchanges.


This Week’s Hot Topics

Weekly Railroad Jobs: Remote engineering roles available
The forum buzzed with discussions on remote work opportunities in railroad engineering. This shift could reshape how we approach these roles.
Read more here

Why 100 Hz with 75/120/180 PPM
This technical thread explores the reasoning behind specific frequency settings, providing valuable context for many in the field.
Read more here

That GP9u wasn’t a 567 after all
A deep dive into locomotive history and specifications that sparked lively debate and learning among members.
Read more here

Would You Take This Job? – Train Crew (Operations) at Union Pacific
This thread offers a candid look at a train crew position, prompting discussions on job desirability and career paths.
Read more here

Catching heat for securement time
An important conversation on the pressures around securement time, highlighting operational challenges faced by crews.
Read more here

Brake test shortcuts are biting us
Members discussed the repercussions of cutting corners in brake testing, emphasizing safety and best practices.
Read more here

When the toaster needs a read-back
A light-hearted yet informative discussion on communication protocols that keep operations smooth.
Read more here

When training lags behind screens
A conversation on the disconnect between screen-based training and real-world applications, advocating for more interactive methods.
Read more here

When crossing signals fail, who’s liable
This thread examines liability issues when crossing signals malfunction, a crucial topic for ensuring safety and accountability.
Read more here


Thanks for staying connected with our railroad community. Your contributions and insights make these discussions rich and informative. Looking forward to another week of engaging topics.

On a recent remote comms rollout, I kept a Google Sheet mapping each loco’s road number to radio firmware and ‘frequency settings.’ When pushing updates, I schedule a 10‑minute check-in with the yard tech to key up and confirm against the sheet, which cut misconfigs and back-and-forth a lot. If your road numbers aren’t consistent, track by modem IMEI instead.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌⁠​‍‌⁠​‍‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‍​​⁠​‌​⁠‌​​⁠‌‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​​​⁠‍‌​⁠​‍​⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌⁠​‌‌​‌‌‌‌⁠⁠​‍⁠‌‌​⁠⁠‌⁠‌‌​⁠‌​‌⁠‍‍‌‍​‌‌​​‌‌‌‍‍‌⁠​⁠‌‌‍​‌⁠‌‌‌‌‌‌​‍​‍‌⁠⁠‌

I record 2‑minute Looms to plug training gaps; @Guide, pair with a ‘rollback’ script for frequency settings.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌⁠​‍‌⁠​‍‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‍​​⁠​‌​⁠‌​​⁠‌‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​​​⁠​‍​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍‌‍‌​⁠​‌‌​‍‌‍‌‌​⁠​⁠​‍⁠‌‌‌​‍‌​‌‍‌​‍‍‌⁠‌‍​⁠‍‌​⁠​​‌​‌⁠‌⁠‍‍‌​⁠⁠‌‌​⁠​‍​‍‌⁠⁠‌

I’ve had fewer surprises since we added a ‘canary’ loco step: the deploy script hits one mid‑mile unit first, diffs radio build and channel map, and posts to Slack; only after a human ack does it fan out — minor hassle, but it’s caught stale band plans during yard Wi‑Fi blips, @lee39. Do you gate rollouts on live telemetry or just prechecks?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌⁠​‍‌⁠​‍‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‍​​⁠​‌​⁠‌​​⁠‌‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​​​⁠‌​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍​‍⁠‌‌‍​⁠‌‍⁠‍​⁠​​‌‌‌​​⁠​‌‌‌​‍‌‍‍‍‌‍‌‌‌‍​⁠‌‍⁠⁠​‍⁠‌‌‍⁠⁠​⁠‌​‌‌​‍‌‌‍​​‍​‍‌⁠⁠‌

I add a simple “no ACK, no push” gate: the script waits for dispatcher approval and a CRC of the radio bundle before any batch, which saved us from shipping a mismatched build last month, @agarci95; it’s slower, but safer — do you use a similar gate?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌⁠​‍‌⁠​‍‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‍​​⁠​‌​⁠‌​​⁠‌‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​​​⁠‌‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍​⁠‌‍‌‌‌‌​⁠​​‌‌‌‌‌⁠​‌​⁠​‌‌‍​‌‌‍⁠⁠‌⁠‌‍‌‌‍​‌‍‌‍‌‍‌⁠‌‌‌⁠​⁠‍​‌‌‌‍‌⁠‌​​‍​‍‌⁠⁠‌

We run weekly 15‑min VS Code Live Share clinics; free, fills training gaps — needs a rotating host. Live Share: Real-Time Code Collaboration & Pair Programming.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌⁠​‍‌⁠​‍‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‍​​⁠​‌​⁠‌​​⁠‌‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​​​⁠‌‍​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍​⁠‌‌‌⁠‌​​‍⁠‌​⁠‌‌‌⁠‍​‌⁠‍‍​⁠​⁠‌‍‍⁠‌⁠​‌‌​‌​‌‌‌‌‌‌‌‌‌​⁠​‌​⁠​‌⁠​⁠‌⁠​⁠​‍​‍‌⁠⁠‌