What Are You Doing Right Now
-
Hanging out with the wife before heading off to bed.
-
@Pete-S said in What Are You Doing Right Now:
@scotth said in What Are You Doing Right Now:
What am I doing right now?
Arguing with our tech about attaching the shield in shielded wire to source ground while leaving the other end open.I can see the problem as both shielding and grounding is complicated. Probably because there are several different reasons for both and the best option in one situation is the worst in another. Was it network cabling or something else?
Just straight up comms. tx rx common shield.
-
@scotth said in What Are You Doing Right Now:
@Pete-S said in What Are You Doing Right Now:
@scotth said in What Are You Doing Right Now:
What am I doing right now?
Arguing with our tech about attaching the shield in shielded wire to source ground while leaving the other end open.I can see the problem as both shielding and grounding is complicated. Probably because there are several different reasons for both and the best option in one situation is the worst in another. Was it network cabling or something else?
Just straight up comms. tx rx common shield.
So RS232 I assume. What did he want to do? Ground the shield in both sides?
-
@Pete-S said in What Are You Doing Right Now:
@scotth said in What Are You Doing Right Now:
@Pete-S said in What Are You Doing Right Now:
@scotth said in What Are You Doing Right Now:
What am I doing right now?
Arguing with our tech about attaching the shield in shielded wire to source ground while leaving the other end open.I can see the problem as both shielding and grounding is complicated. Probably because there are several different reasons for both and the best option in one situation is the worst in another. Was it network cabling or something else?
Just straight up comms. tx rx common shield.
So RS232 I assume. What did he want to do? Ground the shield in both sides?
1st -- since "the shield doesn't really do anything, anyway", he wouldn't connect it to anything.
2nd -- connect both ends
3rd -- connect it in the endpoint device.
4th -- after I passed along as much information as I could, they finally connected it correctly. I'm sure that someone will take credit for it. I'm ok with that. Just get the damned job done.
And, oh yes, they blew the comm driver chip on the 1st try in the endpoint device. Nice little hole in it.I'm done with this. Hopefully, they'll have learned. Time will tell.
EDIT: They blamed the issue on overhead wires. The owner and I had a little talk. I'm not interested in getting anyone fired, but I won't let the same bunch hook up the next one without supervision. -
@scotth said in What Are You Doing Right Now:
@Pete-S said in What Are You Doing Right Now:
@scotth said in What Are You Doing Right Now:
@Pete-S said in What Are You Doing Right Now:
@scotth said in What Are You Doing Right Now:
What am I doing right now?
Arguing with our tech about attaching the shield in shielded wire to source ground while leaving the other end open.I can see the problem as both shielding and grounding is complicated. Probably because there are several different reasons for both and the best option in one situation is the worst in another. Was it network cabling or something else?
Just straight up comms. tx rx common shield.
So RS232 I assume. What did he want to do? Ground the shield in both sides?
1st -- since "the shield doesn't really do anything, anyway", he wouldn't connect it to anything.
2nd -- connect both ends
3rd -- connect it in the endpoint device.
4th -- after I passed along as much information as I could, they finally connected it correctly. I'm sure that someone will take credit for it. I'm ok with that. Just get the damned job done.
And, oh yes, they blew the comm driver chip on the 1st try in the endpoint device. Nice little hole in it.I'm done with this. Hopefully, they'll have learned. Time will tell.
EDIT: They blamed the issue on overhead wires. The owner and I had a little talk. I'm not interested in getting anyone fired, but I won't let the same bunch hook up the next one without supervision.I wouldn't keep my hopes up. We do a lot of work in factories and such so we have seen a lot of serial communication. Usually avoiding RS232 though and using RS422 or 485 because of all the interference. Nowadays it's a lot of industrial ethernet and fiber. It's easier to install but we still have double check that the shielding on CAT6 is connected - every time.
-
Trying to find information on what RDS/DEVICE/USER Cal's we have.
-
The company cleaned out a storage locker yesterday. Mostly junk from an old office but one"decent" find is a Shuttle DS-81 mini PC that says "monitoring port" on it. It's a celelron so not much CPU but has dual gig nic's. Might put PFSense on it to play.
-
Work-from-home day due to being on-call this week. It's tempting to just spend the day practicing Linux Academy stuff and tinkering with home lab server.
-
Good morning all.
-
Trying to get a Grafana server working.
-
@scottalanmiller Let us know how the progress goes with this
-
Debating on Ordering Sushi for my lunch today .
-
@StuartJordan said in What Are You Doing Right Now:
@scottalanmiller Let us know how the progress goes with this
It's up and running. But doesn't show much good data and seems pretty flaky.
-
Looking at a houses online. I think @scottalanmiller will appreciate this. Wife wants to move. Simply because we do not have room for another refrigerator or freezer and our current 2 fridge/freezer and 1 full freezer are filled up. I'm actually game for that as I would love to have a work area/home lab area again.
-
Reviewing PCI compliance Failure at a site who had a "Potential Breach"
-
@WrCombs said in What Are You Doing Right Now:
Reviewing PCI compliance Failure at a site who had a "Potential Breach"
How is something a "Potential Breach"? They called you because something occurred, right? So they must've been breached.
-
@DustinB3403 said in What Are You Doing Right Now:
@WrCombs said in What Are You Doing Right Now:
Reviewing PCI compliance Failure at a site who had a "Potential Breach"
How is something a "Potential Breach"? They called you because something occurred, right? So they must've been breached.
Because it hasn't been confirmed - they received a letter along with 10 other business in the same area.
-
@WrCombs said in What Are You Doing Right Now:
@DustinB3403 said in What Are You Doing Right Now:
@WrCombs said in What Are You Doing Right Now:
Reviewing PCI compliance Failure at a site who had a "Potential Breach"
How is something a "Potential Breach"? They called you because something occurred, right? So they must've been breached.
Because it hasn't been confirmed - they received a letter along with 10 other business in the same area.
10 cards were breached, all 10 cards were in that restaurant + the other 10 ; They don't know where they were breached. but it's a potential Breach.
-
@WrCombs said in What Are You Doing Right Now:
@WrCombs said in What Are You Doing Right Now:
@DustinB3403 said in What Are You Doing Right Now:
@WrCombs said in What Are You Doing Right Now:
Reviewing PCI compliance Failure at a site who had a "Potential Breach"
How is something a "Potential Breach"? They called you because something occurred, right? So they must've been breached.
Because it hasn't been confirmed - they received a letter along with 10 other business in the same area.
10 cards were breached, all 10 cards were in that restaurant + the other 10 ; They don't know where they were breached. but it's a potential Breach.
So it is a suspected breach? Everyone is a potential breach that we just don't know about. A suspected breach implies that someone actually suspects that it might have happened.
-
@scottalanmiller said in What Are You Doing Right Now:
@WrCombs said in What Are You Doing Right Now:
@WrCombs said in What Are You Doing Right Now:
@DustinB3403 said in What Are You Doing Right Now:
@WrCombs said in What Are You Doing Right Now:
Reviewing PCI compliance Failure at a site who had a "Potential Breach"
How is something a "Potential Breach"? They called you because something occurred, right? So they must've been breached.
Because it hasn't been confirmed - they received a letter along with 10 other business in the same area.
10 cards were breached, all 10 cards were in that restaurant + the other 10 ; They don't know where they were breached. but it's a potential Breach.
So it is a suspected breach? Everyone is a potential breach that we just don't know about. A suspected breach implies that someone actually suspects that it might have happened.
That's the word I was looking for -
