Recent Posts

1

Repair / Re: fluke 112 eeprom error

« Last post by Shock on Today at 10:25:05 am »

My understanding is that Fluke service mostly part swap (unless it's a clean or calibration). This model can go cheap online as they aren't so common or obvious that it's a nice model. Might have to wait a bit for firmware, in the meantime you could provide details on the part your programming and board revision.

Some other details like how it got that error is also useful. As meters get contaminated by old batteries I'd have checked that first. If you break a leg often you can carefully excavate the package to expose enough to connect a wire on. See if it's essential for programming in the datasheet. You may have to wire it to a sacrificial socket/pcb in order to read/program easily.

2

Test Equipment / Re: Magnova oscilloscope

« Last post by mubes on Today at 10:24:19 am »

My word, in the absence of much useful signal yet the AGC certainly has amplified a lot of noise in here.

Batronix should be judged by their actions, not whatever prejudices any of us choose to hold. Let's wait and see what they tip up with.  Personally I'm excited to see a new entrant into the market trying to stir things up...with the background and experience across a whole range of existing products to know what works and what doesn't. Given where they're positioning this there's a decent chance they might actually listen to people and add in features that the big players simply don't have....I already messaged them privately about one such feature I'd love to see - I'd even help them implement it!

It could be crock, it could be fantastic. Based on my interactions with the company in the past I've hopeful it's the latter, but none of us can know until the dammed thing turns up.

3

Test Equipment / Re: SDS800X HD Wanted Features

« Last post by hansibull on Today at 10:23:14 am »

Good suggestion for the entire platform range and one I believe could be accomplished quite simply by adding a menu View (type) option in the Decode List comprising of a Bytes or Frames choice, Bytes being the current list default view.

Ideally, they should also add a "packet timeout" value so that closely spaced packets/bursts of data can easily be separated. but the RTB2004 doesn't have such functionality, and I've never had any issues with UART "packets" being interpreted as one single packet.

4

Test Equipment / Re: SDS800X HD Wanted Features

« Last post by 2N3055 on Today at 10:20:37 am »

Just unboxed my new scope and getting to grips with it - apologies if this is just a setting which can be changed somewhere, but it seems unintuitive and a limitation...

I'm probing a CAN signal - actually one of the training outputs from my MSOX3104A - and before I can decode it, I need to know the bit rate.

I couldn't find an automated measurement that gives this quickly and easily. IIRC it was added in firmware after release on the Agilent, and it's handy. I think it just measures the minimum observed pulse width (either positive or negative) within the captured data.

Feature request 1: bit rate measurement, please!

In the absence of an automatic measurement, I figured I'd just do it the old-fashioned way. Capture a packet, find the narrowest pulse and assume it's 1 bit wide. Then, put the cursors on the edges as accurately as possible, and measure their separation.

The odd behaviour is that the delta-X measurement on screen doesn't show the distance between the cursors if one of them is off screen; instead, it 'clips' to the edge of the screen, and if both are off screen then it just reports the width of the screen, or zero if both cursors are off to the same side.

That's really misleading. It clearly remembers the correct cursor positions if they're pushed off screen, because they come back to the right place if I adjust the time base to bring them back.

If I were feeling unkind, I'd call this a bug, though it's clearly intentional behaviour. I just can't think of any circumstances when I'd want to measure between a cursor and the edge of the display, as opposed to between the two cursors.

Feature request 2: delta-X time measurement actually measures the time between X1 and X2 even if one or both of them is off screen - not between a visible cursor and the edge of the screen.

(Example photos: both cursors on screen, showing delta-X = 8.01us, and the effect of just speeding up the time base 1 click; this pushes X1 off the left side of the screen, and the delta-X readout becomes 6.77us which is effectively meaningless).

I asked about Bit rate measurement long time ago... Will repeat...
In meantime depending on signal being idle high or low, i enable +Pulse Width or +Pulse Width and stats and look for minimum value. 1/t gives frequency i.e baud rate.
But yeah I miss that too, coming from Keysight. Not really needed (you can do what I explained, or just use cursors on visually shortest pulse) but a giant time saver.
Especially if you are doing µC work and doing custom baud rates etc...

As for cursor behaviour it is not a bug.
Scope's capture ENDS with the end of screen.
So it will remember what you set for cursor, because you can magnify the portion of screen to set cursor more accurately, magnify other event set that one, and then st time base to have both cursors on the screen to measure.

5

Power/Renewable Energy/EV's / Re: How to test an IR2104/2111?

« Last post by DELTA67 on Today at 10:15:25 am »

I thought that photo was from your real scope? 

Sorry if I've not been clear on that point.
The scope picture is from the simulation on PROTEUS.
If it was from the real device then there's no need to open this thread!!!

Now I've changed the power Vcc to 14V, the chip get's very hot.
Can the uC drive directly the chip or I must use a buffer?
are these chips(IR2104/2111) cloned?

6

Test Equipment / Re: Hacking the Rigol MSO5000 series oscilloscopes

« Last post by BTO on Today at 10:14:01 am »

Try to uninstall all options first, wait for reboot, then install with regen private key flag.

I tried as described, first uninstalled and after reboot I installed with regen private key. Tried it several times but the oscilloscope only replies with "remaining attempts" as described by zauberpilz, now only 2 attempts left. What am I doing wrong? Could you please help?

Hey mate, Just wondering, How are you going with unlocking the scope.
Have you tried the method that i stated ?
You can keep persisting the method that you're doing or
You can do the method that i've put forward that we know works.

Just making sure everyone is up to date

7

Beginners / Re: good/cheap headphone aplifier/dac?

« Last post by BeBuLamar on Today at 10:08:19 am »

If you like the Bose QC25 why not just buy another?

8

Repair / Re: Artesyn LPT42 SMPS repair

« Last post by zkrx on Today at 10:06:33 am »

Thank you so much. I still have a few incandescent bulbs lying around.

Any tip for testing IC1 (3842) or should I just blindly swap & test?

9

Projects, Designs, and Technical Stuff / Re: Automotive hardening?

« Last post by coromonadalix on Today at 10:05:08 am »

dont forget humidity and vibrations

10

Beginners / Re: Any help? Raspberry Pi prod counter w/ reflective sensors - output concerns

« Last post by BeBuLamar on Today at 10:05:06 am »

With a PLC it's simple to have the PLC record 2 count values and store it in the PLC however to read these values you need to use the software that you use to program the PLC to read them or you have to use an HMI software or a hardware HMI which is more costly and and involved. However, I think you have all the parts and tools needed to use the PLC for counting I think it's a good idea to just do that first and see if the count values help you then develop something else.