rdamon We won't hear "Spider too slow", boy she works fast.
We won't hear "Spider too slow", boy she works fast.
Somebody needs to read this about how to keep spiders off of security cameras. Easiest thing to do is turn off the IR LEDs if they are on: https://www.vueville.com/blog/how-to-keep-spider-webs-off-your-security-camera-lens/
Looks like BNSF has a track gang working on the bad joint on the side track. At the same time UP has a form B at the diamonds.
MikeF90 With all of the activity going on, I fired up the audio feed and heard something I'd Never heard before. On the BNSF (Aurora sub MP 56 I think) the detector reported 'Train too slow'. What are the thresholds that trigger this?
With all of the activity going on, I fired up the audio feed and heard something I'd Never heard before. On the BNSF (Aurora sub MP 56 I think) the detector reported 'Train too slow'.
What are the thresholds that trigger this?
Carl
Railroader Emeritus (practiced railroading for 46 years--and in 2010 I finally got it right!)
CAACSCOCOM--I don't want to behave improperly, so I just won't behave at all. (SM)
Johnny
Links to my Google Maps ---> Sunset Route overview, SoCal metro, Yuma sub, Gila sub, SR east of Tucson, BNSF Northern Transcon and Southern Transcon *** Why you should support Ukraine! ***
MKT Dave just caught the BNSF local headed for it's stops north side of Rochelle. Yes, it crossed the diamonds. someone mentioned that it never does.
just caught the BNSF local headed for it's stops north side of Rochelle. Yes, it crossed the diamonds. someone mentioned that it never does.
This job, the 476, often goes to flag center and takes the wye usually the signaled east leg to run around its consist. It also sometimes interchanges a car here with the Illinois Railway, which operates an ex-BN branch to Rockford.. Infrequently they run out west a bit; I've heard Polo as a destination over the last few months. Mostly they work BNSF's yard, located on the railroad south side of the main tracks. They also interchange with the Bulington Junction Railway, which operates the City of Rochelle Railroad. BJR operates railroad north of BNSF and south of UP. BNSF interchanges traffic via a switch off of main #1 referred to as "Wiscold" UP connects with this trackage via a switch off of its #2 main referred to as "Cold Storage" about a mile east of the diamonds. BNSF also interchanges with BJR via the "199" switch visible in the web cam. UP reaches this trackage via a switch located off of #2 main immediately adjacent to CPY076, the east connection into Global 3. The engine usually ties up on the a track referred to as the "house track" and is located off of #1 main a few blocks east of the diamond. Typical call time is 9:00 but has varied some from time to time. If things go smoothly they can tie up around 11:00, but often run longer, especially if they have to go west, or, like today, when the track work is delaying an attempt to service BJR at 199, which has not had service from BNSF since the switch was replaced last week.
I have not had that freeze, but I have to refresh to get the sound going again..
Caught the regulator doing a pivot..
Nice SP DPU ...
xjqcf First BNSF eastbound on #1 just got permission through form B limits.
First BNSF eastbound on #1 just got permission through form B limits.
Heard some interesting conversations today between the BNSF local's conductor and the BNSF people doing further surfacing on the tracks (as is UP on theirs... intersting meets on the diamonds). The bottom line is that a bad joint is the problem. The the track guy offered to walk the local over the joint but the conductor demurred. He stated he would make some calls to determine how hot the cars were. A further point was raised as to who was responsible for fixing the joint and there was no clear immediate answer; at one point there was speculation that Burlington Junction, the operator of the City of Rochelle's trackage might be responsible, but that was quickly determined not to be the case so it's back to a game of finger pointing between BNSF and UP.
The issue of responsibility came up a few months ago when a BNSF track inspector condemned the spring from on the switch. By coincidence UP track forces were working on the diamonds. He walked over to get a fix rolling but was refused with UP asserting it was BNSF's responsibility. BNSF had to bring in their own track gang a few hours later to fix it. Nevertheless it appears most people (perhaps mostly BNSF) do not clearly know who is responsible for what; perhaps someone will have to fish out the governing agreement to get a better answer, and that's assuming there is no ambiguity.
Looks like a little more tamping and regulating going on ...
I read somehwere, either in TRAINS or the net about plastic pads bolted under frogs to cushion the blow from the wheelsets. It is possible this why the sound is much lower.
rdamon The google aerial view was updated and shows the new diamonds. https://www.google.com/maps/@41.9199718,-89.0759166,241m/data=!3m1!1e3
The google aerial view was updated and shows the new diamonds.
https://www.google.com/maps/@41.9199718,-89.0759166,241m/data=!3m1!1e3
I dunno, but that link gives me an image that looks like the image on Google Earth dated September 2013 to me. The current Google Earth image is from April this year and shows the new diamonds staged west of the crossings. This is from GE Mac.
Hmmmmm...I opened the page in Explorer in W7 and find the image updated there, but Safari still has the old image. Even changing user agents in Safari still gives me the 2013 image. A puzzlement, I guess.
BTW, all of this stuff is running on a MacBook Pro.
MemphisBlue rdamon It looks like they are moving a little faster.. did they raise the 10/15 MPH restriction? Diamond definitely not as loud as it was. Is the UP track super-elevated at all there?
rdamon It looks like they are moving a little faster.. did they raise the 10/15 MPH restriction?
It looks like they are moving a little faster.. did they raise the 10/15 MPH restriction?
Diamond definitely not as loud as it was.
Is the UP track super-elevated at all there?
I have listened intently to several trains now on all the tracks... Hardly a sound coming from the diamonds. I don't think I have ever heard (not heard?) a crossing so quiet. Did they install some sort of new fangled frogs that don't go bump in the night (and day)?
Semper Vaporo
Pkgs.
BtrainBob cefinkjr I'm still curious about the CITIRAIL unit. Citicorp Railmark Inc (trading as Citirail Express or CREX) is known for leasing locomotives to the BNSF Railway because of their crisis to move oil trains starting in 2013 https://en.wikipedia.org/wiki/Citicorp_Railmark_Inc._(Citirail)
cefinkjr I'm still curious about the CITIRAIL unit.
Citicorp Railmark Inc (trading as Citirail Express or CREX) is known for leasing locomotives to the BNSF Railway because of their crisis to move oil trains starting in 2013
https://en.wikipedia.org/wiki/Citicorp_Railmark_Inc._(Citirail)
Thank you.
ChuckAllen, TX
Defintely faster on both BNSF Main One and UP Main One.
Thanks to everyone for their reports and pictures on the replacement this morning.
That was some job!
Bruce
So shovel the coal, let this rattler roll.
"A Train is a Place Going Somewhere" CP Rail Public Timetable
"O. S. Irricana"
. . . __ . ______
So what's the story on the EB stack train now passing over the diamonds on BNSF #2? It's headed by a single unit and, as if that's not odd enough, that unit was lettered "CITIRAIL".
Added as it cleared at 1219: There was a single BNSF DPU on the rear. Nothing unusual about that but I'm still curious about the CITIRAIL unit.
Looks to me like a fairly good sized pile of ballast ON the spur. I don't believe I'd want to run my train down there if I were the engineer or conductor.
Now an eastbound BNSF has been given a speed restriction of 10 mph on #2 track, which will be the first movement on #2 actually over the diamonds
Looks like the maintainers are looking at the siding as well. Quite a breeze blowing.
Westbound BNSF has form B permission on track #1. Also BNSF track inspector looking over the diamonds
rdamon I do not recall seeing the tamper go down the siding after they dumped ballast on Sunday. Not sure if that was the reason for the abort by the local.
It didn't. When the crew briefed with track forces after going on duty they seemed to indicate it would be ok to proceed with the understanding that the track had not been surfaced. What changed when they reached the switch I did not catch. All I heard, apparently from one of the track guys, was that he would have to make a phone call. The crew then indicated they would not proceed past the switch and reversed back to the yard.
WP & MP Units
Our community is FREE to join. To participate you must either login or register for an account.