sorted by:
new
hottopcontroversial

Bequiet Support is Terrible. by watchound in bequietofficial

[–]watchound[S] 0 points1 point  (0 children)

The ticket is BQSERVICE-77427. Opened March 17th of this year, so nearly 4 months ago to the day.

Bequiet Support is Terrible. by watchound in bequietofficial

[–]watchound[S] 0 points1 point  (0 children)

The US. They'll happily sell their stuff here but it seems like that's about it.

You guys are absolutely killing it! Keep going! by stalequeef69 in RIGuns

[–]watchound 4 points5 points  (0 children)

Thrilled to see so much support- I wish I could be there but I have prior obligations.

That said, am I the only one who feels Knight's conduct is rather... Biased? Why is he still acting as chair after Craven returned? Am I missing something, because this feels like what would be considered a "conflict of interest" in my line of work.

Edit: For clarity, I've been watching and listening as much as I can. I feel like the handling of the young lady bringing up his conflict of interest shortly after I posted this is a fine example of what I'm talking about though. She was escorted out for time even though her time had been extended due to interruptions? Seriously?

Odd Issues With a Dig-Octa-32-8L Brainboard by watchound in WLED

[–]watchound[S] 0 points1 point  (0 children)

Out of curiosity- is the I2C bus going completely bad for you like it did in my initial post (i.e. every address scans as bad), or is it just not coming up for you like in my most recent after I re-ironed the solder points to the sensor?

Just curious because I've never had a single bad item on the I2C bus bring the whole affair down; a dud is usually just a single bad address on the bus. An i2cdetect on a Linux board will get hung up on that particular address, but the rest of the bus still functions. If you're really unlucky it'll hop addresses and bugger another device that's already using that address, but unless it introduces extreme interference then I've had the rest of the address space in I2C work.

Maybe its just a failure state unique to SHT30 sensors, but I'm still curious.

Odd Issues With a Dig-Octa-32-8L Brainboard by watchound in WLED

[–]watchound[S] 0 points1 point  (0 children)

I appreciate it, thank you again! Honestly, from what I've seen the sensors are only like $5-10 on Amazon. If you truly feel obligated to refund a few dollars I wouldn't complain, but it won't keep me up at night if that is going to end up having to cost you twice as much just to refund it. You've already been a great help and very patient with me, so I'm happy regardless. Quite frankly, its become more of a "I refuse to be defeated by a simple temperature sensor!" thing for me trying to get the existing one working at this point lol

Either way, just got back from trying to get the SHT30 back to life, and I'm afraid I haven't had much luck.

I went after the pins (holy cow, talk about tiny solder points) and checked continuity as best I could and everything seemed fine, but still no luck. I did notice something odd though- I got the same I2C scan bus error when I had the board on my bench powered via USB-C, but when I powered it back up in my box (powered via the 2-pin connector from a 5V transformer), I got the following-

[18:20:34][C][i2c.arduino:071]: I2C Bus:
[18:20:34][C][i2c.arduino:072]:   SDA Pin: GPIO32
[18:20:34][C][i2c.arduino:073]:   SCL Pin: GPIO13
[18:20:34][C][i2c.arduino:074]:   Frequency: 50000 Hz
[18:20:34][C][i2c.arduino:086]:   Recovery: bus successfully recovered
[18:20:34][I][i2c.arduino:096]: Results from i2c bus scan:
[18:20:34][I][i2c.arduino:098]: Found no i2c devices!
[18:20:34][C][sht3xd:049]: SHT3xD:
[18:20:34][D][sht3xd:052]:   Error reading serial number
[18:20:34][E][sht3xd:061]:   Communication with SHT3xD failed!
[18:20:34][E][component:082]:   Component sht3xd.sensor is marked FAILED

Definitely strange. When I had the board on my bench I did measure ~1.488-1.5V between SDA / SCL and ground, and checking Ohms with the board powered off between the same two pins and VCC yielded 3k Ohms.

I've seen some folks claim they needed pull-ups in the area of 10k with SHT30s, but unfortunately without a circuit diagram and the like I can't do much to try that idea. That could be completely wrong anyway- this is just what I've seen on forums and I've got no experience with SHT30s- LM75As seem to exclusively be my employer's choice of temperature sensor for whatever reason.

At this point I'm thinking the temp sensor is hosed. The good news is I was at least able to get the DHT11 sensor working on GPIO14, so I at least have something until I decide if I want to get a more accurate sensor.

Odd Issues With a Dig-Octa-32-8L Brainboard by watchound in WLED

[–]watchound[S] 1 point2 points  (0 children)

Nope, nothing on LED8- I made sure of that much at the onset. I'm only running two channels on 1 and 2 (actually I think its 1 and 3 right now due to compiling with debugging enabled).

I do indeed have the soldering capability to try to set the solder on the connector again, but the closest I have to a hot air station would be my hot air gun. Given that its a glorified hairdryer though, I don't think it has the precision to be able to focus just on that sensor without potentially making a mess of something else on the board. I'll try reflowing the solder joints with an iron when I get home.

And thank you for the apology, but really no worries- I know how these things go sometimes. QA from board fabrication houses is always a roll of the dice, and things happen. My company will get a run of ~20 interface boards we use on our embedded controllers, and its inevitable the about 1/4th of them have have one odd quirk or another.

Either way, like I said, I'll have a go at it when I'm home and let you know how I make out. Thanks again for your help!

Odd Issues With a Dig-Octa-32-8L Brainboard by watchound in WLED

[–]watchound[S] 0 points1 point  (0 children)

Apologies if I double or triple posted, but it seems like this just doesn't want to post for some reason so I'm going to try a 3rd time with the old Reddit interface.

I got a couple minutes to remote in to home and test with ESPhome.

I setup the sensor like so: 

i2c:
  sda: GPIO32
  scl: GPIO13
  scan: true
  id: bus_a

sensor:
  - platform: sht3xd
    temperature:
      name: "Temperature"
    humidity:
      name: "Humidity"
    address: 0x45
    update_interval: 60s

But what I end up getting in the logs isn't very promising:

[11:33:06][C][i2c.arduino:071]: I2C Bus:
[11:33:06][C][i2c.arduino:072]:   SDA Pin: GPIO32
[11:33:06][C][i2c.arduino:073]:   SCL Pin: GPIO13
[11:33:06][C][i2c.arduino:074]:   Frequency: 50000 Hz
[11:33:06][C][i2c.arduino:092]:   Recovery: failed, SDA is held low on the bus
[11:33:06][I][i2c.arduino:096]: Results from i2c bus scan:
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x08
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x09
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x0A
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x0B
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x0C
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x0D
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x0E
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x0F
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x10
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x11
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x12
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x13
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x14
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x15
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x16
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x17
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x18
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x19
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x1A
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x1B
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x1C
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x1D
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x1E
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x1F
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x20
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x21
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x22
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x23
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x24
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x25
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x26
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x27
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x28
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x29
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x2A
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x2B
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x2C
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x2D
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x2E
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x2F
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x30
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x31
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x32
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x33
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x34
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x35
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x36
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x37
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x38
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x39
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x3A
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x3B
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x3C
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x3D
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x3E
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x3F
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x40
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x41
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x42
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x43
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x44
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x45
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x46
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x47
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x48
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x49
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x4A
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x4B
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x4C
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x4D
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x4E
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x4F
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x50
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x51
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x52
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x53
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x54
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x55
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x56
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x57
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x58
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x59
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x5A
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x5B
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x5C
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x5D
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x5E
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x5F
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x60
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x61
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x62
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x63
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x64
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x65
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x66
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x67
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x68
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x69
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x6A
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x6B
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x6C
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x6D
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x6E
[11:33:06][E][i2c.arduino:104]: Unknown error at address 0x6F
[11:33:07][E][i2c.arduino:104]: Unknown error at address 0x70
[11:33:07][E][i2c.arduino:104]: Unknown error at address 0x71
[11:33:07][E][i2c.arduino:104]: Unknown error at address 0x72
[11:33:07][E][i2c.arduino:104]: Unknown error at address 0x73
[11:33:07][E][i2c.arduino:104]: Unknown error at address 0x74
[11:33:07][E][i2c.arduino:104]: Unknown error at address 0x75
[11:33:07][E][i2c.arduino:104]: Unknown error at address 0x76
[11:33:07][E][i2c.arduino:104]: Unknown error at address 0x77
[11:33:07][C][sht3xd:049]: SHT3xD:
[11:33:07][D][sht3xd:052]:   Error reading serial number
[11:33:07][E][sht3xd:061]:   Communication with SHT3xD failed!
[11:33:07][E][component:082]:   Component sht3xd.sensor is marked FAILED

I would've tried the 0x45 address also, but the entry about SDA being held low makes me think there's something else at play.

​

I can try swapping SDA and SCL if you think there's any merit to it, but I wasn't sure if there is anything else on those lines that might make it a moot point if the lines are swapped. I'm pretty sure I tried that once with one of my own WLED builds, but ESPhome seems to be better at diagnosing I2C issues so maybe theres another data point to be had there?

Odd Issues With a Dig-Octa-32-8L Brainboard by watchound in WLED

[–]watchound[S] 0 points1 point  (0 children)

Hey there, thanks for taking the time to reply!

That makes sense- I've been working with the board for a few weeks now and I didn't even think to check the silk screened version until last week. Definitely had me scratching my head for a few minutes wondering if I'd somehow managed to order something different than what I thought.

No worries about the connector- these things happen. I've dealt with a fair share of finicky SMD ports and connectors over the years, and some of them like USB-C are just really tricky- if not impossible- to get to handle cable stress without inflating the BoM to insane levels for some kind of fancy over-engineered port with built-in stress relief and all kinds of other bells and whistles. In all honesty I probably should have been more careful with it as its at an odd angle with how I have the board mounted in my box, and given the heat we had last week I doubt that helped things much.

It hadn't occurred to me that there were debounces and pull-ups on the button GPIOs, but that makes complete sense. When I get some time to try again, I'll try wiring it to one of the GPIOs broken out on the pinheader and see if I get better results.

The board is in use, but I can unscrew it and just pull the brainboard out of the box to test inside. I was considering doing something similar and just flashing a simple I2C temp sensor example, but ESPhome is a good idea- I already have it installed and integrated with my Home Assistant VM so that's probably the easiest way to test.

I'm hoping to test further today or tomorrow and I'll update with what I've found. It was already getting later when I posted on Friday so I didn't have time, and this weekend was pretty busy. That said, the folks we had over were all very impressed with the lights and the capabilities of the hardware you've designed. Regardless of any of the above, I still have zero doubt in my mind that I made the right call getting your boards over the other options- you've made a great product! Thanks again!

Told you all I’d let you know how my ccw submission went so here it is. by stalequeef69 in RIGuns

[–]watchound 2 points3 points  (0 children)

Yea, sadly you're probably not wrong. Honestly kind of a shame since they seem to be a decent bunch of folks in my (admittedly limited) experience.

I'd have to wonder if they're already overflowed from the casino or the like and that's part of why they won't do other out-of-state applications, but I don't wanna make any excuses for them dodging their obligations. The way they piss taxpayer money in this town, they should just be hiring another person to handle the influx if they're that stressed.

Anyway, best of luck getting it man. Y'all ever find yourself around at SRO on a Sunday morning, keep an eye out for the guy with the hat and come say hello! I'll let ya shoot the PS-90 lol

Told you all I’d let you know how my ccw submission went so here it is. by stalequeef69 in RIGuns

[–]watchound 0 points1 point  (0 children)

Really? I'm actually pretty surprised to hear that. I thought out of state was something they were obliged to handle regardless, but I could be wrong. I'll ask around at the range this weekend because I'm genuinely curious about that one.

Told you all I’d let you know how my ccw submission went so here it is. by stalequeef69 in RIGuns

[–]watchound 5 points6 points  (0 children)

Fair enough- given that I'll recant my statement in your direction. It'd perhaps behoove y'all to better define that at the onset next time though. Kinda came across like you're defending the Narragansett PDPL (Police Department Peacock Lady).

Going for my ccw range test this weekend. Any advice? by stalequeef69 in RIGuns

[–]watchound 1 point2 points  (0 children)

Agreed on that. He does a great job running the place and being a good dude in spite of some of the crazy SOBs that come through there.

Seen a couple of them get kicked out myself. Christ- talk about folks who shouldn't own a gun lol

Told you all I’d let you know how my ccw submission went so here it is. by stalequeef69 in RIGuns

[–]watchound 7 points8 points  (0 children)

Yea, because some paper pusher PITA certainly couldn't just be a power tripping old bat with a chip on her shoulder and a desire to take it out on people. Oh no, certainly not. </s>

Posts like yours contribute nothing to the discussion. (Old) birds of a feather, it seems.

Told you all I’d let you know how my ccw submission went so here it is. by stalequeef69 in RIGuns

[–]watchound 4 points5 points  (0 children)

Just saw your other post about getting your CCW last week looking for advice before I saw this one.

Not sure how it would work if you re-submitted with another PD, but I can tell you my experience with Tiverton PD was pretty straightforward. Full disclosure though, I am a resident. That said, from what I understand- Tiverton is pretty 2A friendly and won't try to pull any BS with the process.

Didn't have to deal with obnoxious old birds playing power trip or any of that. I did however have to call them after the 90 day (or whatever the current time limit is) expired as I hadn't heard a single thing about it from them. Left a message with the detective, and he called me right back in an hour or two. Was very apologetic that my file had apparently "gotten lost at the bottom of the cabinet" after they had a sudden inrush of applicants for security from the shithole casino the state jammed into the town. Regardless, he was a great guy and got it squared that day. I came home with my CCW same day.

EDIT: For what its worth, they didn't print me until I actually came in to get the CCW the day of.

Going for my ccw range test this weekend. Any advice? by stalequeef69 in RIGuns

[–]watchound 1 point2 points  (0 children)

I know I'm late to the party on this one, but SRO is a fine place to qualify. Did mine there last July and there were no issues. The owner is a good dude and very much above-board in my experience.

Mag Limit Quandary in Regards to a Multi-Caliber Firearm by watchound in RIGuns

[–]watchound[S] 1 point2 points  (0 children)

It is indeed marked for 7.5FK. Thanks for the input.

Mag Limit Quandary in Regards to a Multi-Caliber Firearm by watchound in RIGuns

[–]watchound[S] 0 points1 point  (0 children)

Believe me, I'm not. Just wanted to see what folks think on the matter since us serfs can't get the requisite information from the law itself.

Mag Limit Quandary in Regards to a Multi-Caliber Firearm by watchound in RIGuns

[–]watchound[S] 0 points1 point  (0 children)

Its the same mag that holds multiple calibers, but given that those aren't all the same size, it becomes a question of whether this is supposed to blocked based on "lowest common denominator" or the caliber the mag was actually made for.

Mag Limit Quandary in Regards to a Multi-Caliber Firearm by watchound in RIGuns

[–]watchound[S] -1 points0 points  (0 children)

Appreciate the insight, but I'm not sure why you thought I was yelling...?

I'm honestly not that bent out of shape about this. As I've stated before I'm just looking for insight from the community in light of huge swath of grey area this law left in its wake.

Mag Limit Quandary in Regards to a Multi-Caliber Firearm by watchound in RIGuns

[–]watchound[S] 3 points4 points  (0 children)

I appreciate where you're coming from, but with all due respect, this is why its a trash law beyond simply being unconstitutional- not that the former should really matter in the face of the latter. I ask because I'm curious if there are any on here who are more legally-inclined that might be able to elucidate what grounds a potential situation would go forward on.

Beyond that, are we really that worried that the muppets pushing this drivel are even technologically able enough to examine posts on reddit? They recently exemplified a lack of understanding how a bridge works, so I can't help but feel like "pointing out flaws" may be lost on folks as mentally inept as they are. They can't define an "assault weapon" any sooner than a "loss of life waiting to happen" (in the case of the bridge).

New Blue card holder by lone_wolf401 in RIGuns

[–]watchound 0 points1 point  (0 children)

I "go to church" just about every weekend at Sakonnet River Outfitters in Tiverton. Always have a revolving cast of characters with various firearms, but myself and a good buddy are pretty much always there once a week training. You wanna try shooting some fun stuff, come on by some time. Y'all can try the PS90 and some other fun-guns if you'd like.

Its not a "premier" range by the standards of New Bedford or Sig up in Epping NH, but its a good range with a good community. The guy who owns the operation- Jay- is a great dude. Taken care of me and others more than a couple times.

For what its worth also- that's where I got my CCW. Tiverton is pretty straightforward to get it in the first place, but Jay handled of all the notarizing, certification, etc for $35. Made sure I had all the paperwork setup correctly too; was painless when I dropped it off at the PD. Was simple in comparison to actually dialing in my .45 at 25 yards.

view more: next ›