January 7, 20188 yr So I got really fed up with the communication module in my Brultech GEM. It's crap. It's a cheap USR-WIFI232-B serial to net converter that half-worked at best: Will likely never see a KRACK patch Setup was absolutely non-intuitive Security hole where the AP Wi-Fi could leak through Ethernet. Had to set my switch to force 100Mbit cause it broke @ 1000Mbit 3 of 4 times I'd request a webpage it failed Constant issues with corrupt data being received So, I added serial port support to NodeLink's GEM module and connect a USB-Serial adapter from my Pi to the COM port on the GEM. I even physically removed the GEM Wi-Fi chip - good riddance. Been running for about 12h, zero issues with corrupt data and the GEM web config is way smoother. Since I'm back to a RPi (instead of Synology Docker) I'm also going to move the 1-wire back to a hardware chip and OWFS instead of the GEM bit-banging. Win-Win.
January 7, 20188 yr io_guy, Can I ask why you ditched the Synology Docker and went back to RPi? Was it just to be able to use the USB-Serial adapter more easily? I actually just did the opposite with my NodeLink setup (i.e. from RPi to Synology Docker).
January 7, 20188 yr Author Yep, cause my Pi is 5' from the GEM and Synology is 50' across a drywalled basement. Also, the majority of people use a Pi so it helps me debug issues. The Synology is a way better way to go (vs. the Pi), the location just didn't work. I run a dozen dockers, it's fantastic (and so much faster).
January 7, 20188 yr Whew! You had me worried that I was going in the wrong direction. Sent from my iPhone using Tapatalk
Archived
This topic is now archived and is closed to further replies.