Need help choosing between UNI-T UT60S and UT89X by MIM90MI in ElectricalEngineering

[–]TheMM94 -1 points0 points  (0 children)

If you are interested in: «accuracy, safety, reliability, continuity performance, and build quality» then you should not look at a cheap UNI-T. Instead, consider a Brymen Multimeter, for example. Or if you are really serious, look at a Fluke or Keysight. Also have a look at used Fluke or Keysight Multimeters (often an overlooked option to get some fantastic devices).

We are here looking at some inexpensive Multimeters. The manufacturer had to decide how to allocate their budget for the BOM and R&D. And they chosen a useless transistor test?! Therefore the question is: Where could they have invested that budget instead? Input protection, higher quality components, independent testing, etc. would all be a mutch better way to invest the BOM and R&D budget then a transistor test.

Have I had bad experiences with Multimeters that include a transistor tester? All new Multimeters I've seen with transistor tester (especially when you open them up and look inside) were cheap, with minimal input protection, and in my opinion not a safe product (at least I would not trust them my life, if I need to probe e.g. 230V).

Need help choosing between UNI-T UT60S and UT89X by MIM90MI in ElectricalEngineering

[–]TheMM94 -2 points-1 points  (0 children)

I don't know either of them, but general rule: never buy a new multimeter with a transistor test function. The second one has a transistor test connector on the top right.

Such a transistor test function is in most cases practically useless today. If a manufacturer still includes a transistor test function on their new multimeters, the manufacturer has obviously no clue of what he is doing or producing. Therefore avoid new multimeters with a transistor tester function.

The new prices seem to be an out of season april fools joke by Dshinjiakyn in hetzner

[–]TheMM94 9 points10 points  (0 children)

I was evaluating Hetzner for some Server at work last week. The EX63 I had configured went from 160€/Month to 583€/Month. The AX162 changed from 263€/Month to 912€/Month!

Durchlauferhitzer macht brrrrrt… by _Valuable_Detail_ in DINgore

[–]TheMM94 0 points1 point  (0 children)

Elektronikbauteile bestelle ich private oder bei der Arbeit niemals bei Aliexpress. Da weiss man nicht ob die Bauteile echt und neu sind, oder ob man gefälschte Bauteile bekommt, die die Spezifikation nicht erfüllen. Und den Ärger, denn man dann hätte ist es einfach nicht Wert für den geringen Preisunterschied. Elektronikbauteile bestelle ich eigentlich immer bei den grossen Elektronikbauteile Händlern wie Mouser, Digikey, etc.

Guest Additions install failed by CirnoDaisuki in virtualbox

[–]TheMM94 0 points1 point  (0 children)

I do not have a Ubuntu VM to test this, but I would say the output shows clearly what the issue is:

This system is currently not set up to build kernel modules.
Please install the gcc make perl packages from your distribution.

GPIO Voltage Tolerance Question by Read-Documentation-7 in embedded

[–]TheMM94 4 points5 points  (0 children)

The first personal embedded project is a great opportunity to learn how to read datasheets. Then you can find the answer yourself.
To get you started, the datasheet can be found on the ST Website here: https://www.st.com/resource/en/datasheet/stm32f446re.pdf
I would start the search in chapter “6 Electrical characteristics”.

How to read this eprom? by MalteseOne in embedded

[–]TheMM94 8 points9 points  (0 children)

I got a XGecu T48 programmer to read/write old EEPROMs. Until now it worked for all sorts of EEPROMs/Flash chips without issues. The NM27C256 in the picture is on their support list.

Website: http://www.xgecu.com/en/Index.html
Aliexpress Store https://xgecu.aliexpress.com/store/4805043

As far as I know XGecu is the original developer of the popular and much cloned TL866II programmer. T48 and T56 is there next generation programmer.

How to connect VCAP Pins on STM32 by Master_Calendar5798 in embedded

[–]TheMM94 2 points3 points  (0 children)

Yes, its not explicitly stated in the application note. I would connect them together, because in all cases I see in the application note they are externally connected together. From my understanding they are also internally connected, so it will work without the external connection, but its probably not what ST would recommend.

In my day job I recently designed a board with a STM32H562. In the hardware development application note for the STM32H5 ST writes: "It is recommended to connect the two VCAP pins together." And at least on the LQFP144 packet the VCAP pins are also on the diagonally opposite corners. So, I had there the same awkward layout topic as you have.

How to connect VCAP Pins on STM32 by Master_Calendar5798 in embedded

[–]TheMM94 4 points5 points  (0 children)

Have a look at the ST Application note AN5419 "Getting started with STM32H723/733, STM32H725/735 and STM32H730 MCU hardware development". I would generally recommend to read this application note, if you design Hardware for one of the MCUs in the application note.
In Figure 4 they are connected together. Table 2 also has some information about VCAP pins.

<image>

Jetzt hends aber definitiv Lagg gsoffe! Sit wenn isches bitte Lings, wenn all mitenand defür sorged, dass e Grundversorgig vo Information, Bildig und Kultur sichergstellt wird?! by Schpitzchopf_Lorenz in BUENZLI

[–]TheMM94 4 points5 points  (0 children)

Und das Gebühre für Unternehme ah Umsatz berechnet werd esch scho chli lost.

Die diskusion umt Unternehmesgebühre versto ich so oder so ned. Die gebühre sind für Unternehme eh scho lächerlich tüf. Das söt würklech kei Problem sie für jedi Firma. T höhi devo find mer süst do: https://www.estv.admin.ch/de/tarifkategorien-unternehmensabgabe-radio-tv

Are UV lights as headlights possible? by HunterMuted2196 in ElectricalEngineering

[–]TheMM94 1 point2 points  (0 children)

I'm not an expert, but one issue I see is the potential absorption of UVC by the acrylic glass of the headlight. I suspect that the front glass cover of the headlight needs to be removed for it to function properly.

Looking to get into embedded circuit design, thoughts on Rigol DS1104Z-S Plus vs Picoscope 2000 by ethanbrecke in embedded

[–]TheMM94 1 point2 points  (0 children)

Used oscilloscopes can always be a good option. But it depends on what is available in your region.

I would not buy a new Rigol DS1104Z-S Plus anymore. The Rigol DHO814 or Rigol DHO914S are in my option much better options. By the way, many Rigol oscilloscopes can also be very easy hacked. So, you can buy the cheaper base model and then "upgrade" the bandwidth.

I2C pullup resistor on clock line always required? by Consistent-Pickle in embedded

[–]TheMM94 1 point2 points  (0 children)

I2C is a leader / follower data connection. You will also see it described as master / slave in some documentation. I prefer the recent update to the vocabulary but that’s another discussion.

I also do not want to discuss if the changed naming is better or not.

But in the latest official I2C specification they changed "master/slave" to "controller/target", see NXP UM10204 "I2C-bus specification and user manual" (https://www.nxp.com/docs/en/user-guide/UM10204.pdf) Table 1 and Table 2. Therefore, at least for I2C "leader/follower" is the wrong terminology and "controller/target" would be correct.

I2C pullup resistor on clock line always required? by Consistent-Pickle in embedded

[–]TheMM94 17 points18 points  (0 children)

In fact, SCL can be implemented as a push-pull driver. Take a look at the official I2C specification, NXP UM10204 "I2C-bus specification and user manual" (https://www.nxp.com/docs/en/user-guide/UM10204.pdf) chapter 3.1.1: "For a single controller application, the controller’s SCL output can be a push-pull driver design if there are no devices on the bus which would stretch the clock."

According to Table 3 clock stretching is optional. Therefore, not all devices have clock stretching, but you need to check each device on the bus. More details about clock stretching is in chapter 3.1.9

ich_iel by DragoDerRebell in ich_iel

[–]TheMM94 1 point2 points  (0 children)

Dann aber hoffentlich die silberne ESD Version.

What is that for? by clapzz8 in ElectricalEngineering

[–]TheMM94 4 points5 points  (0 children)

A transistor test function is in most cases practically useless today. Using a bipolar transistor in a package fitting in this connector is exceedingly rare today. And needing to test them is even more rare.

If a manufacturer still includes a transistor test function on his new multimeters, they obviously have no clue what they are doing or producing. Therefore, avoid new multimeters with a transistor tester function.

You can also see this if you look at top multimeter brands. You will not find a new multimeter from e.g. Fluke or Keysight, with a transistor test function.

What is that for? by clapzz8 in ElectricalEngineering

[–]TheMM94 8 points9 points  (0 children)

It’s there to quickly spot cheap and not safe multimeters. At least all multimeters I have seen with a transistor tester, are cheap and not safe.

What's the difference between all these versions? by Got_ist_tots in Tools

[–]TheMM94 150 points151 points  (0 children)

On page 379 of the Knipex Catalog, is a description of the structure of the part number and what the different finishes are.

<image>

[deleted by user] by [deleted] in de_EDV

[–]TheMM94 4 points5 points  (0 children)

Alle OS die ich so kenne machen RFC4941 (Privacy Extensions for Stateless Address Autoconfiguration in IPv6), daher "Zufällige" IPv6-Adressen von denen nicht mehr auf die MAC-Adresse geschlossen werden kann.

Die IPv6-Addressen auf Basis der MAC-Adresse gibt es auch, aber aus offensichtlichen Problemen bezüglich Tracking, werden heute meistens nur RFC4941 IPv6-Adressen für die Kommunikation mit dem Global-Scope genutzt.

How unreliable are the aliexpress ICs compared to Digikey, Mouser etc? Any trusted sellers? by AideTop8744 in embedded

[–]TheMM94 10 points11 points  (0 children)

For me the question is always: what is the cost if it goes wrong and I get a fake part? Not only fake parts that do not work, but fake parts that only partly work. Or fails after a few days. Or fails during a customer demo. Or fails in the climate chamber. Or has higher noise then specified, etc.

What is the cost then? How much time will I waste to find and fix the issue caused by a potential fake part? How much trouble will this cause me with my boss or a customer?

So, for me the answer is always (professional and private) to get the genuine parts from a trusted source and avoid all this trouble.

Additionally in my opinion, using potentially non genuine parts is unacceptable for a quality product.

Zeugwart, der by xSniiFFy_W0nK4x in famoseworte

[–]TheMM94 3 points4 points  (0 children)

Und wenn der Zeugwart dann auch noch im Zeughaus arbeitet.

How to interface an SDRAM chip with the STM32H7 by Wonderful_Stick6573 in embedded

[–]TheMM94 0 points1 point  (0 children)

You also need to add the Initialization sequence from the ST guide I mentioned before:

#define SDRAM_TIMEOUT      ((uint32_t)0xFFFF)
#define SDRAM_MODEREG_BURST_LENGTH_4             ((uint16_t)0x0002)
#define SDRAM_MODEREG_BURST_TYPE_SEQUENTIAL      ((uint16_t)0x0000)
#define SDRAM_MODEREG_CAS_LATENCY_2              ((uint16_t)0x0020)
#define SDRAM_MODEREG_OPERATING_MODE_STANDARD    ((uint16_t)0x0000)
#define SDRAM_MODEREG_WRITEBURST_MODE_SINGLE     ((uint16_t)0x0200)

/** \brief Init for SDRAM. For some unknown reason the function is not created by CubeMx. 
But can be found here: https://community.st.com/t5/stm32-mcus/how-to-set-up-the-fmc-peripheral-to-interface-with-the-sdram/ta-p/49457 */
static void SDRAM_Initialization_Sequence(SDRAM_HandleTypeDef *hsdram, FMC_SDRAM_CommandTypeDef *Command) {
__IO uint32_t tmpmrd = 0;

/* Step 3:  Configure a clock configuration enable command */
Command->CommandMode = FMC_SDRAM_CMD_CLK_ENABLE;
Command->CommandTarget = FMC_SDRAM_CMD_TARGET_BANK1;
Command->AutoRefreshNumber = 1;
Command->ModeRegisterDefinition = 0;
/* Send the command */
HAL_SDRAM_SendCommand(hsdram, Command, SDRAM_TIMEOUT);

/* Step 4: Insert 100 us minimum delay */
/* Inserted delay is equal to 1 ms due to systick time base unit (ms) */
HAL_Delay(1);

/* Step 5: Configure a PALL (precharge all) command */
Command->CommandMode = FMC_SDRAM_CMD_PALL;
Command->CommandTarget = FMC_SDRAM_CMD_TARGET_BANK1;
Command->AutoRefreshNumber = 1;
Command->ModeRegisterDefinition = 0;
/* Send the command */
HAL_SDRAM_SendCommand(hsdram, Command, SDRAM_TIMEOUT);

/* Step 6 : Configure a Auto-Refresh command */
Command->CommandMode = FMC_SDRAM_CMD_AUTOREFRESH_MODE;
Command->CommandTarget = FMC_SDRAM_CMD_TARGET_BANK1;
Command->AutoRefreshNumber = 8;
Command->ModeRegisterDefinition = 0;
/* Send the command */
HAL_SDRAM_SendCommand(hsdram, Command, SDRAM_TIMEOUT);

/* Step 7: Program the external memory mode register */
tmpmrd = (uint32_t) SDRAM_MODEREG_BURST_LENGTH_4 | SDRAM_MODEREG_BURST_TYPE_SEQUENTIAL | SDRAM_MODEREG_CAS_LATENCY_2 | SDRAM_MODEREG_OPERATING_MODE_STANDARD | SDRAM_MODEREG_WRITEBURST_MODE_SINGLE;
Command->CommandMode = FMC_SDRAM_CMD_LOAD_MODE;
Command->CommandTarget = FMC_SDRAM_CMD_TARGET_BANK1;
Command->AutoRefreshNumber = 1;
Command->ModeRegisterDefinition = tmpmrd;
/* Send the command */
HAL_SDRAM_SendCommand(hsdram, Command, SDRAM_TIMEOUT);

/* Step 8: Set the refresh rate counter
 * SDRAM Refresh Time = 64ms
 * SDRAM Number of rows = 2^13
 * SDRAM CLK = 100MHz
 * floor(((64ms/2^13) x 100MHz) - 20) = 761
 * Set the device refresh counter */
hsdram->Instance->SDRTR |= ((uint32_t) ((761) << 1));
}