The Smell of Molten Projects in the Morning

Ed Nisley's Blog: Shop notes, electronics, firmware, machinery, 3D printing, laser cuttery, and curiosities. Contents: 100% human thinking, 0% AI slop.

Tag: Rants

And kvetching, too

  • Forester: TPMS FTW, Sorta-Kinda

    According to the Forester’s manual, the Tire Pressure Monitoring System kicks in after the car reaches 25 mph. It evidently takes a while to figure things out after that, because the TPMS light blinked on a mile from home on the way to Mary’s Vassar Farms garden. I pulled into the next parking lot, measured 20 psi in the left rear tire, then found this staring me in the eye:

    Forester - left rear tire with screw
    Forester – left rear tire with screw

    Well, that certainly simplified the diagnosis!

    I unloaded two bags of shredded leaves and a pile of hoses, swapped in the (limited use, donut-style) spare tire, and continued the mission.

    The TPMS light wasn’t on when I drove to Squidwrench the previous evening. Judging from the wear, that screw appeared during the various errands following our 800 mile road trip, which is good news of a sort, and depressurized the tire over the course of a day or two.

    The receipt from the fix-it folks cautions that a plug is a temporary fix, because “the injury has compromised the integrity of the tire”. On the other paw, the Forester manual tells me “All four tires must be the same in terms of manufacturer, brand (tread pattern), construction, and size. You are advised to replace the tires with new ones that are identical to those fitted as standard equipment” and then provides a checklist:

    When you replacing or installing tire(s), all four tires must be the same for following items.
    (a) Size
    (b) Circumference
    (c) Speed symbol
    (d) Load index
    (e) Construction
    (f) Manufacturer
    (g) Brand (tread pattern)
    (h) Degrees of wear

    There’s absolutely no way to get an identical replacement tire, let alone one with the same tread wear, but I am so unready to replace all four tires after 12 k miles / 2 years.

    We shall see how this works out…

  • Kohl’s Guest WiFi Terms & Conditions: The Short Version

    I enjoy exposing my tired old Kindle to random assaults, so I’m always on the lookout for FREE WIFI! hotspots:

    Kohls Guest WiFi - login screen
    Kohls Guest WiFi – login screen

    You can’t resize the text, there are no linkies to the details of the Kohl’s Terms or Kohl’s Privacy Policy (viewing them would presumably require a browser, which would require using the WiFi, which you haven’t yet been approved to use), leaving a decision between “Hit me!” and, oh, maybe re-reading The Martian.

    In the local Sears some months ago, I spent the better part of 20 minutes scrolling their lengthy T&C, following the links (which they provide through the same peephole!), and generally admiring their legal department’s sophistry.

    I’m not a formal member of The Society for the Easily Amused, but I support their cause and, obviously, don’t get out nearly enough.

  • Sony 64 GB MicroSDXC Card: The Final Failure

    The fourth Sony MicroSDXC card went into service in late September 2015 and has now failed after about 60 sessions in my Sony HDR-AS30 Action Camera. This one sported a U3 speed rating and I had hopes that would improve its longevity, but that doesn’t seem to be true.

    The defunct Sony card (marked in red to avoid confusion) will join its defunct compadre and the Sandisk Extreme Pro card goes in the camera:

    Sony 64 GB MicroSD SR-64UX - failure
    Sony 64 GB MicroSD SR-64UX – failure

    The 16 bike rides in December added up to 220 GB; call it 13.75 GB/trip. January 2016 shows only three rides and it failed after two February rides: barely 60 rides for a total of 825-ish GB of video data. The three previous Sony cards failed after less than 1 TB of data, putting this one in the same ballpark.

    I have no way to measure the actual write speed, but the camera shuts down after recording less than a minute of 1920×1080 @ 60 f/s video. Previous cards worked fine at lower video resolutions and recording speeds; I’ll assume this one behaves similarly. It might make a capacious “disk” for a Raspberry Pi.

    When the previous card failed, Sony’s “customer support” decided that there might be something wrong with the camera’s firmware causing it to trash the cards, so there was no point in replacing the card under warranty and I should send the camera in for a checkup. When I pointed out that they’d strung me along for a year, until the camera was out of warranty, without mentioning even the possibility that the camera might be at fault and asked whether they’d pick up the $100+ bill for having the camera “examined”, the Nice Man said Level 2 would get back to me after “48 working hours”. When prodded, he agreed that “48 working hours” equaled “6 working days” and didn’t include weekends; when we had that settled, I knew they had no further interest in this matter.

    Sony hasn’t called back and, by now, I don’t expect they ever will. It’s not worth my time to pursue this any further, but if you’re wondering how well Sony MicroSD cards work in Sony cameras and how well they support the failures, now you know.

    So, starting with this riding season, we’ll see how long a Sandisk Extreme Pro card survives…

     

     

  • Autodesk Privacy Statement: “Do Not Track” and Similar Mechanisms

    Autodesk just Borged Netfabb and, in the process of merging their address lists, asked me to update my info and agree to their very detailed Privacy Statement. You should take a look at it; the link will open in a new tab / window / whatever, so you don’t lose your place here.

    Have you noticed how those “statements” always have a very long and firmly fixed line width that doesn’t adapt to your window size, use various shades of light-gray-on-white typefaces in the smallest sizes, and continue for pages and pages. I don’t believe in coincidences, either.

    Here’s what they think of my Do Not Track browser setting (emphasis added):

    “Do not track” and similar mechanisms

    Some web browsers may transmit “do-not-track” signals to websites with which the browser communicates. Because of differences in how web browsers incorporate and activate this feature, it is not always clear whether users intend for these signals to be transmitted, or whether they are even aware of them.

    Participants in the leading Internet standards-setting organization that is addressing this issue are in the process of determining what, if anything, websites should do when they receive such signals. Autodesk currently does not take action in response to these signals. If and when a final standard is established and accepted, we will reassess how to respond to these signals.

    For information about cookies, web beacons and similar technologies, please read our Cookie Policy.

    After plowing through much of their “statement”, I decided Autodesk doesn’t do anything I need to know about and, seeing as how Netfabb gradually faded from my attention when their web service joined Microsoft’s Azure cloud, I declined to “confirm my preferences” and didn’t click the big blue button. I doubt such inaction will remove my email address from their list, but it’s the only choice they offer.

    Because I can’t tell if a website really wants to track me, I block ads, disable Flash, and destroy all cookies when I leave their site, Just In Case they inadvertently deployed all that crap. I’m sure they never intend to serve malware through an ad slot brokered on their site, but mistakes do happen, and I’m glad to assist them.

    If you’re seeing ads on this page right now, they come from WordPress and I get a small cut. You should start using an ad blocker right now; if your browser doesn’t permit you to block ads, change browsers. If you worry that reducing my advertising revenue will compromise the quality and quantity of what you see here, send me a sack of money through Paypal. Fair enough?

    Also: Linux, dammit.

  • Traffic Signal Timing: NYSDOT Responds

    On 12 July 2015, I sent a report to NYSDOT about how the traffic signals at Burnett Blvd / Rt 55 greenlighted opposing traffic when our bicycles were still in the intersection:

    Can you increase the minimum green and yellow times on the signals from Burnett Blvd to Rt 55?

    The current settings are too short for bicycle traffic making a left turn across six traffic lanes.

    The pictures show key points from our ride on 2015-07-10, returning from the Balloon Festival in Poughkeepsie. We took the DCRT around Poughkeepsie, went through Arlington to Rt 376 at Collegeview, then took Rt 376 Red Oaks Mill.

    The image sequence numbers identify frames extracted from video files. The Front camera runs at 60 fps and the Rear camera at 30 fps.

    The red signals are in the process of turning off in Front 0196.

    Burnett at Rt 55 Signal - Front 0196
    Burnett at Rt 55 Signal – Front 0196

    One second later in Front 0260, the car and our bikes are starting to roll. Given the number of drivers blowing through red signals at full speed, devoting one second to watching for oncoming traffic seems prudent.

    Burnett at Rt 55 Signal - Front 0260
    Burnett at Rt 55 Signal – Front 0260

    The yellow signals are turning on in Front 0633, seven seconds after the green. The car has reached the pedestrian ladder across Rt 55, but we’re still crossing the westbound lanes of traffic. We may not be the fastest riders on the road, but we’re not the slowest, either.

    Burnett at Rt 55 Signal - Front 0633
    Burnett at Rt 55 Signal – Front 0633

    We’ve reached the far side of the intersection in Front 1142, just under 16 seconds from the green.

    Burnett at Rt 55 Signal - Front 1142
    Burnett at Rt 55 Signal – Front 1142

    However, Rear 0408 shows that the opposing signals turned green while we’re still crossing the eastbound lanes of Rt 55. That’s about 15 seconds after the Burnett Blvd signals went green.

    Burnett at Rt 55 Signal - Rear 0408
    Burnett at Rt 55 Signal – Rear 0408

    About 2.7 seconds later, Rear 0490 shows cars accelerating across the intersection toward us as we cross the pedestrian ladder. They started rolling immediately after their signal went green; waiting a second isn’t a universal practice.

    Burnett at Rt 55 Signal - Rear 0490
    Burnett at Rt 55 Signal – Rear 0490

    Setting the minimum Burnett green to 12 seconds, the minimum yellow to 10 seconds, and the minimum delay from Burnett green to Rt 55 green to 30 seconds would help cyclists (just barely) reach the far side of the intersection before opposing traffic starts rolling.

    Also: can you adjust the sensor amplifiers on Burnett to respond to bicycles and mark the coil locations on the pavement in both lanes? That would help us through the intersection during low-traffic-volume times, as our bikes seem unable to trip the signals.

    Thanks…

    This reply from the NYSDOT autoresponder was all I ever got from them:

    Thank you for your inquiry.  We will respond to your email message as soon as possible.

    On 2 August 2015, I sent a report to NYSDOT about how the traffic signals at Old Post Rd – Spring Rd at Rt 9 greenlighted opposing traffic when our bicycles were still in the intersection:

    The minimum green-to-opposing-green signal timing from Old Post Road across Rt 9 to Spring road is about 18 seconds: not long enough for bicycles to safely cross an intersection with eight traffic lanes.

    The “Green” picture shows our starting position as the signal turned green: behind the first car in line. There’s another car behind us, which ensures the loop sensor will trip; it does not detect bicycles.

    Spring Rd - Rt 9 - 2015-08-01 - Green
    Spring Rd – Rt 9 – 2015-08-01 – Green

    The “Yellow” picture shows the signal changing after 12 seconds, with the car from behind us now in the middle of the northbound lanes. We’re still in the middle of the southbound lanes.

    Spring Rd - Rt 9 - 2015-08-01 - Yellow
    Spring Rd – Rt 9 – 2015-08-01 – Yellow

    The “Opposing Left Green” from the rear camera, 18 seconds from the first picture, shows green left-turn arrows for Spring Road. The opposing cars began rolling with Mary lined up with the northbound right-turn lane and me lined up with the right travel lane.

    Spring Rd - Rt 9 - 2015-08-01 - Opposing Left Green
    Spring Rd – Rt 9 – 2015-08-01 – Opposing Left Green

    The car behind blew through the red signal on Old Post Rd; I think that’s why the opposing left-turning cars didn’t start sooner.

    In the other direction, I often use the left turn from Spring Rd to southbound Rt 9 to reach the South Road Square strip mall. Similarly short yellow and overall cycle times apply in that direction.

    Can you add (at least!) five seconds to the yellow and perhaps ten seconds to the minimum cycle time for both directions? That would help us clear the intersection before opposing traffic starts moving again.

    Can you also mark the sensor loop locations in all those lanes so cyclists can find them and adjust the amplifier sensitivity / dwell to respond to bicycles? We’ve lined up atop the quadrupole loop pavement cuts on Old Post Road to no avail, but there’s not even a hint of the loop positions under the new Spring Rd paving.

    Thanks…

    This reply from the NYSDOT autoresponder was all I ever got from them:

    Thank you for your inquiry.  We will respond to your email message as soon as possible.

    On 5 January 2016 I posted a description of our encounter with a car at the Burnett Blvd intersection and sent the link to the NYSDOT Bicycle and Pedestrian Coordinator. If you search for Burnett Blvd, you’ll find a few other mentions of that intersection.

    On 6 January 2016, this email message arrived from the same email address that never responded to my reports (emphasis added):

    Dear Mr. Nisley:

    This is in response to your correspondence regarding your experiences as a bicyclist at the intersections of Route 55 at Burnett Boulevard and Route 9 at Spring Road in the Town of Poughkeepsie, Dutchess County.

    The New York State Department of Transportation (NYSDOT) is in the process of investigating alternate detection types and inductance loop patterns that would detect a wider range of vehicles.  As alternate detection types are tested and approved, they will be integrated into the next traffic signal upgrade at both intersections.  The distance varies based on geometry.  The loops are centered in each lane and the front loop is a quadrapole, so there are wires down the middle of the loops.

    A new timing program was implemented at Route 9 at Spring Road in August, and the yellow and red clearance times meet the current standards.  The timing at Route 55 at Burnett Boulevard is in the process of being updated, and the clearance times will be updated as necessary to meet the current standards.  Clearance times are determined based on speed, intersection dimensions, grade, and reaction time and cannot be adjusted.  The sensitivity on all loops will also be adjusted, so they are as sensitive as possible without causing cross talk between the loops.

    We appreciate and share your interest in making our highway systems safe and functional for all users.

    If you have any questions or need additional information, please feel free to contact our Regional Traffic Safety & Mobility Group at (845) 437-3396.

    NYSDOT Hudson Valley Region

    I don’t regard that date a coincidence; NYSDOT was not responding to my reports. I sent a further note to clarify a few points:

    On 01/05/2016 02:18 PM, dot.sm.r08.nysdot wrote:
    Clearance times are determined based on speed,intersection dimensions, grade, and reaction time and cannot be adjusted.

    That seems to mean the times can be adjusted, but you won’t adjust them to allow cyclists enough time to clear the intersection.

    We appreciate and share your interest in making our highway systems safe and functional for all users.

    So, giving opposing traffic a green light while we’re still in the intersection NYSDOT’s way of “making our highway systems safe and functional for all users”.

    Do I understand your statements correctly?

    No reply, as I’ve come to expect by now.

    I think the emphasis on “meet(ing) the current standards” is how NYSDOT will attempt to defend against claims that road conditions caused or contributed to a car-on-bike collision. I find it surprising that contemporary “standards” would allow greenlighting opposing traffic against bicycles, but perhaps they simply choose a standard that excludes bicycles.

  • Tools for Ladies

    Wandering through the Sears tool department, I found this corner:

    Sears Pink Box Tools
    Sears Pink Box Tools

    Neither of the Ladies in my life favor pink, so I wasn’t even tempted…

    Mary wonders if the designers scaled the grips and spring tensions to suit women’s hands. Her experience shows that “tools for men” are too big and require too much grip strength for her comfort; applying pink plastic won’t improve them in the least.

  • Time Warner RoadRunner vs. SSH: Help Wanted

    So Time Warner updated the infrastructure upstream of Mary’s folks and installed a new cable modem / router, which killed my remote access using ssh (with RSA keys, passphrases, nonstandard ports, fixed internal IP addresses, port forwarding, port triggers, and all the Right Stuff). I just spent a harried pair of days trying and failing to figure out how to make this work again.

    My laptop can ssh into my file server from our house network, both wired and wireless. Ditto when it’s on the Squidwrench Operating Table. Ditto from the low-quality Hampton Inn WiFi near her folks. Plunked on their desk and jacked into their router, however, that outbound ssh times out somewhere between their bits and my basement.

    I dinked with the TW Surfboard modem / router, added the appropriate port forwarding & triggers, dialed back the firewall intensity, and ssh flat out doesn’t work in either direction from any PC (all running various Linus flavors). No diagnostics, no logs, nothing that I could find.

    From the outside (our house or the Hampton), there’s no response from the PCs inside (on their desk). I’m not trying a loopback from inside to inside, which I know doesn’t work with consumer-grade routers. I’d planned to ssh from there to my basement file server, then ssh back to verify that the connections worked, but the outbound connection doesn’t work.

    Probably unrelated, but equally frustrating: trying to configure Thunderbird’s outbound SMTP with their email server flat-out doesn’t work. Either the username / password isn’t valid (it is), various combination of ports / security / encryption (including the ones in the TW FAQs) don’t survive the configuration test, or a seemingly valid configuration doesn’t actually transmit email. Incoming email works only in IMAP mode, not POP3.

    I finally set up outbound TW email to bankshot through his Gmail account, which will probably have unforeseen side effects.

    The usual Google searches were unavailing, other than several notes suggesting that if you have any other choice of ISP or email provider than TW, do that. But it’s not like they have any choice; Verizon provides 1 Mb/s (!) DSL in that area and satellite Internet isn’t going to happen in an apartment.

    Obviously, I’m doing several things wrong, but I have no idea what else to try. I’ve set up email and remote access often enough to get a whole bunch of things right, but that sure didn’t help with TW.

    Any suggestions?