The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 2,482 other followers

Archive for September 16th, 2021

Windows and the current state of S.M.A.R.T. tooling that understands NVMe

Posted by jpluimers on 2021/09/16

I had trouble with two Intel 600p NVMe SSD devices: read-errors.

It appeared only few tools understand how to get S.M.A.R.T. health information from them, and even then they did not explain the read errors.

I’m going to RMA them, but in case anyone else needs to get health information from NVMe SSD devices, here is which tools do what:

So basically, CrystalDiskInfo and HD Tune are my first line of checking for drive issues, followed by smartmontools to get text output, then by vendor specific tools to assist with the RMA.

In the past, I used another smartmontools wrapper, but it was discontinued and had an even older version than GSmartControl: Source: Closed: HDD Guardian – Home.

On Intel 600p becoming locked in read-only mode after failure:

Start of Intel RMA procedure via [Wayback] Warranty Information.

My case looks remarkably similar to [Wayback] Full Diagnostic Scan always fails during Read Scan on my SSD 600p Series 256GB – Intel Community.

A few screenshots of the tools I used for health information:

Read the rest of this entry »

Posted in Hardware, NVMe, Power User, SSD, WayBack machine | Leave a Comment »

AgileTD Keynote | Happiness is Quality

Posted by jpluimers on 2021/09/16

Hopefully this becomes available on-line, as this will be a great talk, but Potsdam is out of my reach in my current physical condition.

[Wayback] AgileTD Keynote | Happiness is Quality

In Gwen Diagram’s keynote go on a journey of looking at how to improve happiness in teams for the goal of building quality systems.


How can we build teams that strive to build quality systems? By building in happiness early and often.

Each organisation has a culture which directly affects the quality of their work. Organisations with a lower level of quality; that is, systems that fail more often, longer times to fix and longer times to build often have a few things in common; frustration, apathy and cynicism.

On the other side of the coin, teams with slack, time to learn and time to reflect also have the space to improve their systems. Quality is everyone’s responsibility is an oft quoted phrase. But, how do you actually engage people to build quality systems?

Improving quality should not weigh heavy on the shoulders of the test specialist. Their main role should not be attempting to convince people that unit tests should exist, that systems should be testable and observable or that automated tests will speed up development. Instead, we should be building teams that want to find out together how to build a system that breathes quality.

The way to do this is by improving the happiness of the engineers on the team with learning, autonomy and coaching. So, how can we build teams that strive to build quality systems? By building in happiness early and often. In this talk, we will go on a journey of looking at how to improve happiness in teams for the end goal of building quality systems.

Via: [Wayback] Agile Testing Days on Twitter: “☀️ Here comes the happiness! ☀️ @gwendiagram will take us on a journey of looking at how to improve happiness in teams for the end goal of building quality systems. ➡️ Learn more about the keynote and the speaker: … “

–jeroen

Posted in Agile, Conferences, Development, Event, Power User, Software Development, Testing | Leave a Comment »

BMW E46 How To Code Module Options – YouTube

Posted by jpluimers on 2021/09/16

For my link archive: E46, INPA and NCS Expert videos.

And

  • [WayBack] NCS Dummy – Taking the expert out of NCS Expert
  • Nice video! But since i do code several vehicles per week for different customers, i would like to point a few things out. 1st. For people who don’t know anything about coding: The central coding key (ZCS) or vehicle order(FA or VO) is like the DNA of the car. The build date, basic equipment and optional equipment are listed inside here. It’s saved redundant in 2 modules and has one simple funcion.. The computer that’s going to program or code the module(s) reads it and then determines how to deploy the software/coding to suit that specific car. 2nd. Because of the vehicle order only being changed for manual transmission, you should only code the relevant module(s) after you write the FA to the modules storing it, so in this case you should have only coded the kombi (AKMB) instead of the whole car and you would be all set. Processing the whole car can be quite dangerous. As failure to communicate with a module during coding actually can destroy a module.. ask me how i know ;) Because of that you should only code modules that actually need to be coded and leave the rest alone, to reduce the risk :) 3rd. Just leave the car running while coding, you won’t hurt anything ;) If battery voltage dips too hard it might cause communication problems and the consequences of that can be really bad for your module. 4th. Regarding the E46ZST file… There are 2 types reference files actually, one E46AT and one E46ZST. If your car has a central coding key (ZCS) , use the E46ZST file for reference of what to add or distract from the strings. If your car has a vehicle order, use the E46AT file. Within the AT file, the options will be listed, and the option codes to add will be in front of the description in the following format: Wxxx , in which case you should enter it like this in NCS expert: $xxx The newer chassis that only have a vehicle order will only have a ExxAT file in the DATEN folder. Lastly, You should (in theory) also program (not coding, flashing the module actually) the DME after a manual swap. You could do this by any programming tool of choice like WINKFP, ISTA /P or an external scan tool with module programming capability. The reason for this is that the software for an AT DME is different to that of a MT. The software in the DME for an AT actually retards the timing a little bit when the transmission should shift, thus reducing torque and enhancing the life of the clutches inside your transmission. Don’t feel offended by my criticism, I really do like all of your videos and i myself learned quite a bit from them! Keep up the good work man ;) If you ever need help with coding or programming any BMW, old or new, feel free to contact me. I love helping the BMW community :) Greetings from Belgium!

Read the rest of this entry »

Posted in cars, E46 320i touring, E46 330xd touring BMW, LifeHacker, Power User | Leave a Comment »

 
%d bloggers like this: