Working night shift, operating my crane. She's just a little thing, but it gets the job done.
Printable View
Working night shift, operating my crane. She's just a little thing, but it gets the job done.
I'm fading fast... two weekends ago it was an all nighter (client caused outage)
Too f u c k i n g old for this
Damn TPS reports are piling up.
Ha.Quote:
Originally Posted by Grant H.
Got the server to run and stay stable finally. Started with a simple default page, and now I have to build the pages that I want to have public for the hosted content.
Not as late as I was expecting, but not as simple as I hoped.
Now to finish to my movie, build a webpage or three, and then get to bed for snowboarding tomorrow...
I suppose this EPR isn't going to write itself... [Roll1]
The weekend begins in less than an hour. Oh yeah.
Guess I never noticed a "night crew" thread before. I work nights, deep nights! 8:30pm to 6:30am, four nights a week. We manage maintenance work and splicing on fiber optic cables nationwide, which can only be done at night, not a day job at my end of the stick, maybe years down the road.
Well, welcome! I'll be here for the next few nights, if you want to check in and chat.Quote:
Originally Posted by rondog
I guess this is as good a time as any to check in! [Dunno]
Time to make the dohnuts?
sent from my electronic ball and chain
My schedule got kind of screwed up and I didn't really work today. Is that the same as working nights?
No.
Getting home when the sun is rising or already rose (risen?) is working nights. [Coffee]
Oh I know. I text adjusters the night before to confirm appointments, and some of them start texting me back at 4:30am and calling before 6am. That's also kind of like working nights.
bed by 2030 and up at 0430 isn't exactly working nights...Quote:
Originally Posted by Irving
Pretty sure I posted the event in here, don't recall as I was pretty wiped out.Quote:
Originally Posted by GilpinGuy
3-26 through 3-27, I helped resurrect a VIP system that was dead dead dead. I told them they should rename it Jesus Christ as it arose from the dead. On Easter Sunday no less. How weird is that?
Not to bring on the pity party here since I actually made my schedule myself, but I go in at 5AM two days a week and get off at 5AM two days a week. Talk about f-ed up. Sleep is a "get it when you can" thing.
It works out for the family though. Better this than the $700 a month we were paying for babysitters. Plus, the Night Crew thread![Beer]
Still sounds better than my schedule! [LOL]Quote:
Originally Posted by GilpinGuy
I work from 0600-1400 for 2 days, then from 1400-2200 for 2 days, then 2200-0600 for 2 days. Then I get 4 days off, but I usually spend most of my time off just trying to get back on a normal schedule. Oh well. I guess I'll sleep lots when I'm dead. [zombie1]
zzzzzzzZZZZZZZZZZZ
ZZZZZZZZZZZZZzzzzzzzzzzz
memememememem
ZZZZZZZZZZZZZzzzzzzzzzzz
memememememem
Zzzzzzzz
OK, I'm not kidding, I'm going to bed now.
I think my work is finally done. This new system has been kicking my ass for a few days now.
With this, I'm going to bed.....
https://www.youtube.com/watch?v=9HpLqqH2tkw
That's exactly how my week has gone.
I was NOT supposed to be working late this weekend.
[Bang]
Damnit!
[Bang]
Stupid projects...
Working on an RF pathstudy for an O/G customer.
Hurray for 1.5Gbps Microwave links, tying a hole batch of 1-2Mbps SCADA networks back to the office. Holy details though... Quoting/Spec'ing towers for wind loading and future growth, quoting RF hardware, and quoting about 6 months of labor...
Oh well... At least it's work...
I think this an english only forum. [ROFL2]Quote:
Originally Posted by Grant H.
Yay! The weekend just began. This PBR tastes good.
Mmmmmm SCADA
Aside from the misspelling of "whole" [facepalm] (stuff happens when you've been on the road all week, and then up till 4:30) that seems like English to me.... [Neene1]Quote:
Originally Posted by GilpinGuy
SCADA stands for Supervisory Control and Data Acquisition. Basically we build wireless communication networks that allow our customers (Oil and Gas, Water/Waste Water, Electric Power, etc) to see what all their devices are doing in the field remotely. These are generally poll/response systems, and have the ability to remote start/stop on command, and usually have the logic to emergency stop a process when something is out of whack.
In the case of this customer we are quoting and building a high speed wireless backbone ring (data can get routed either way, so even if a link goes down, the data can get back still) throughout their field, and then we are breaking off with much slower radios to go out to their end devices. Also on the main backbone towers we will have wifi access points for their field guys to get onto the corporate network from the field. With the access points we will put up, and the truck wifi kits that we usually sell to go with it, they can be up to 10 miles from the towers and still get good wifi access.
Sorry for the book, just thought I would share.
So these are all time shared links right? So what modulation and baud rates do you utilize ?
For the backbone links we are using one of three bands depending on the situation. 5.8GHz, 11GHz, or 24GHz microwave shots, ranging anywhere between 16-2048QAM modulation rates. The 5.8GHz and 24GHz are license free, but the 11GHz is licensed. Depending on the customers preference, there are a host of options for this. I haven't found a need for one suppliers 4096QAM, nor a customer that wants to spend for it.Quote:
Originally Posted by wyome
The last mile communication links are all Xetawave 900MHz unlicensed radios running multispeed multipoint, with an allowed range of 884kbps - 2651kbps (BPSK, QPSK, and 8PSK). We used to use FreeWave radios, but have since moved away from them.
This end users devices are a mix of Totalflow's, ROC's, and a few small name PLC/well controllers. Other customers have Allen Bradley, Bristol, Siemens, Ferguson, PCS, etc... (We see a lot of random gear due to being in so many vertical markets. We focus on being the experts on the wireless side and work/partner with people that know the PLC/RTU side better, if no one wants to partner we can do most of it, but it's not our forte. This brings a much better solution to the end user.)
Generally for serial devices in the field (old PLC's/RTU's/Flow computers), we run them at the max serial baud rate they are capable of. A few fields we have radios in still have devices that are limited to 1200bps. With RS485, we generally run 19200-38400, depending on the radio link (the better the link the faster we'll run). With RS232, if we have a full complement of control lines available on the device (they are all there on the radio), we'll run 115200.
I was just kidding. I get loopy after a 13 hour graveyard shift. Probably should refrain from posting at that time.
It's all good. I was just kidding with my response.Quote:
Originally Posted by GilpinGuy
I was just kidding when I read this thread and didn't post anything.
Thanks for the scada setup explanation....in a previous life I used to do rf analysis, and every know and then some of that stuff would pop up...
Sure.Quote:
Originally Posted by wyome
The RF world is still fun for me (15+ years later), since I get to design big stuff like this, and then implement it.
Older Picture, but the most interesting immediately available. In this one, I'm hanging out at 120' working on a PTMP 3.65GHz Access Point.
https://farm2.staticflickr.com/1481/...7122f503_z.jpg0918141517 by ARNEWB, on Flickr
Awesome. I want to try something that high.
Hey Night Crew. [Beer]
Does this count as night crew?
Probably be up for a while. Then I have a meeting with a customer at 6, an hour from my house... Maybe I should try the napping thing from the other thread... LOL.
Making a Raspberry Pi 3 into an OpenVPN server. Should be straightforward, but who knows. The last time I played with OpenVPN I never could get a client to connect properly...