Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > sci.electronics.design > #489364 > unrolled thread

Rigol scope settings

Back to article view | Back to sci.electronics.design

Contents

  Rigol scope settings bitrex <bitrex@de.lete.earthlink.net> - 2017-12-26 20:54 -0500
    Re: Rigol scope settings bitrex <bitrex@de.lete.earthlink.net> - 2017-12-26 20:55 -0500
    Re: Rigol scope settings mpm <mpmillard@aol.com> - 2017-12-26 18:47 -0800
      Re: Rigol scope settings Piotr Wyderski <peter.pan@neverland.mil> - 2017-12-27 16:53 +0100
      Re: Rigol scope settings bitrex <bitrex@de.lete.earthlink.net> - 2017-12-27 10:59 -0500
    Re: Rigol scope settings Cursitor Doom <curd@notformail.com> - 2017-12-27 15:39 +0000
      Re: Rigol scope settings krw@notreal.com - 2017-12-27 11:54 -0500
      Re: Rigol scope settings M Philbrook <jamie_ka1lpa@charter.net> - 2017-12-30 09:47 -0500
    Re: Rigol scope settings Hul Tytus <ht@panix.com> - 2017-12-27 22:11 +0000
    Re: Rigol scope settings George Herold <gherold@teachspin.com> - 2017-12-27 17:16 -0800
      Re: Rigol scope settings bitrex <bitrex@de.lete.earthlink.net> - 2017-12-30 10:27 -0500
        Re: Rigol scope settings Lasse Langwadt Christensen <langwadt@fonz.dk> - 2017-12-30 08:08 -0800
          Re: Rigol scope settings krw@notreal.com - 2017-12-30 12:24 -0500
            Re: Rigol scope settings Lasse Langwadt Christensen <langwadt@fonz.dk> - 2017-12-30 09:53 -0800
              Re: Rigol scope settings krw@notreal.com - 2017-12-30 14:39 -0500
                Re: Rigol scope settings Lasse Langwadt Christensen <langwadt@fonz.dk> - 2017-12-30 12:02 -0800
                Re: Rigol scope settings bitrex <bitrex@de.lete.earthlink.net> - 2017-12-31 10:33 -0500
                  Re: Rigol scope settings Lasse Langwadt Christensen <langwadt@fonz.dk> - 2018-01-01 03:49 -0800
                    Re: Rigol scope settings krw@notreal.com - 2018-01-01 12:01 -0500
              Re: Rigol scope settings bitrex <bitrex@de.lete.earthlink.net> - 2017-12-31 10:35 -0500
            Re: Rigol scope settings "tom" <tmiller11147@verizon.net> - 2017-12-30 12:59 -0500
              Re: Rigol scope settings krw@notreal.com - 2017-12-30 14:50 -0500
            Re: Rigol scope settings mpm <mpmillard@aol.com> - 2017-12-30 10:34 -0800
              Re: Rigol scope settings krw@notreal.com - 2017-12-30 14:54 -0500
              Re: Rigol scope settings Michael A Terrell <mike.terrell@earthlink.net> - 2018-01-01 01:34 -0500
        Re: Rigol scope settings krw@notreal.com - 2017-12-30 11:20 -0500
    Re: Rigol scope settings M Philbrook <jamie_ka1lpa@charter.net> - 2017-12-30 09:51 -0500
      Re: Rigol scope settings bitrex <bitrex@de.lete.earthlink.net> - 2017-12-30 10:16 -0500

Page 1 of 2  [1] 2  Next page →

#489364 — Rigol scope settings

I have a shiny new Rigol DS1102E on the bench that I'm trying
to set up to view transmissions on an i2c bus. There's a burst of
data on the bus about once a second that I'd like to look at.

Pretty sure some folks here are familiar with this series and have 
probably used it for this purpose before; can you recommend some 
settings to capture that effectively on this scope? I know, RTFM and all 
but the included "Quick Start" guide doesn't give enough info to help, 
and jeez the full manual (available only as PDF) is nearly 200 pages long.

[toc] | [next] | [standalone]

#489365

On 12/26/2017 08:54 PM, bitrex wrote:
> I have a shiny new Rigol DS1102E on the bench that I'm trying
> to set up to view transmissions on an i2c bus. There's a burst of
> data on the bus about once a second that I'd like to look at.
> 
> Pretty sure some folks here are familiar with this series and have 
> probably used it for this purpose before; can you recommend some 
> settings to capture that effectively on this scope? I know, RTFM and all 
> but the included "Quick Start" guide doesn't give enough info to help, 
> and jeez the full manual (available only as PDF) is nearly 200 pages long.

Apologies for any formatting issues on the above post ;-)

[toc] | [prev] | [next] | [standalone]

#489366

On Tuesday, December 26, 2017 at 8:54:48 PM UTC-5, bitrex wrote:
> I have a shiny new Rigol DS1102E on the bench that I'm trying
> to set up to view transmissions on an i2c bus. There's a burst of
> data on the bus about once a second that I'd like to look at.
> 
> Pretty sure some folks here are familiar with this series and have 
> probably used it for this purpose before; can you recommend some 
> settings to capture that effectively on this scope? I know, RTFM and all 
> but the included "Quick Start" guide doesn't give enough info to help, 
> and jeez the full manual (available only as PDF) is nearly 200 pages long.

I have the DS2072A.
Assuming it's similar (enough), I believe the SDA goes on CH-1, and SCL on CH-2.
Then, go into the Decode menu.  Serial.  Then I2C.

The above is from memory, fading fast this time of evening.  :)
Good luck.   Nice scope for the money!

[toc] | [prev] | [next] | [standalone]

#489400

mpm wrote:

>  Nice scope for the money!

DS1054Z + the hack is even better.

	Best regards, Piotr

[toc] | [prev] | [next] | [standalone]

#489401

On 12/26/2017 09:47 PM, mpm wrote:
> On Tuesday, December 26, 2017 at 8:54:48 PM UTC-5, bitrex wrote:
>> I have a shiny new Rigol DS1102E on the bench that I'm trying
>> to set up to view transmissions on an i2c bus. There's a burst of
>> data on the bus about once a second that I'd like to look at.
>>
>> Pretty sure some folks here are familiar with this series and have
>> probably used it for this purpose before; can you recommend some
>> settings to capture that effectively on this scope? I know, RTFM and all
>> but the included "Quick Start" guide doesn't give enough info to help,
>> and jeez the full manual (available only as PDF) is nearly 200 pages long.
> 
> I have the DS2072A.
> Assuming it's similar (enough), I believe the SDA goes on CH-1, and SCL on CH-2.
> Then, go into the Decode menu.  Serial.  Then I2C.
> 
> The above is from memory, fading fast this time of evening.  :)
> Good luck.   Nice scope for the money!
> 
> 

I don't think the series the 1102E is from has any protocol decoding 
functionality, best I can hope for is to set it up the holdoff/timebase 
appropriately so it triggers consistently on the burst pattern I guess

[toc] | [prev] | [next] | [standalone]

#489399

On Tue, 26 Dec 2017 20:54:44 -0500, bitrex wrote:

> I know, RTFM and all
> but the included "Quick Start" guide doesn't give enough info to help,
> and jeez the full manual (available only as PDF) is nearly 200 pages
> long.

200 pages? I've just bought a wristwatch with a thicker manual than that!



-- 
This message may be freely reproduced without limit or charge only via 
the Usenet protocol. Reproduction in whole or part through other 
protocols, whether for profit or not, is conditional upon a charge of 
GBP10.00 per reproduction. Publication in this manner via non-Usenet 
protocols constitutes acceptance of this condition.

[toc] | [prev] | [next] | [standalone]

#489406

On Wed, 27 Dec 2017 15:39:57 -0000 (UTC), Cursitor Doom
<curd@notformail.com> wrote:

>On Tue, 26 Dec 2017 20:54:44 -0500, bitrex wrote:
>
>> I know, RTFM and all
>> but the included "Quick Start" guide doesn't give enough info to help,
>> and jeez the full manual (available only as PDF) is nearly 200 pages
>> long.
>
>200 pages? I've just bought a wristwatch with a thicker manual than that!

Counting the forty languages.  ;-)

[toc] | [prev] | [next] | [standalone]

#489734

In article <p20esd$f5b$1@dont-email.me>, curd@notformail.com says...
> 
> On Tue, 26 Dec 2017 20:54:44 -0500, bitrex wrote:
> 
> > I know, RTFM and all
> > but the included "Quick Start" guide doesn't give enough info to help,
> > and jeez the full manual (available only as PDF) is nearly 200 pages
> > long.
> 
> 200 pages? I've just bought a wristwatch with a thicker manual than that!

you know, I've always tried to keep my manuals with the equipment, and I 
am sure you try to practice the same, hows the arm holding out?

Jamie

[toc] | [prev] | [next] | [standalone]

#489415

I had similar trouble with Rigol's DS1074z and got some good advice from 
the people on this news group. If you can find a historical listing, try 
searching for "Rigol DS1074Z" & my name. January of 2016 roughly.

Hul

bitrex <bitrex@de.lete.earthlink.net> wrote:
> I have a shiny new Rigol DS1102E on the bench that I'm trying
> to set up to view transmissions on an i2c bus. There's a burst of
> data on the bus about once a second that I'd like to look at.

> Pretty sure some folks here are familiar with this series and have 
> probably used it for this purpose before; can you recommend some 
> settings to capture that effectively on this scope? I know, RTFM and all 
> but the included "Quick Start" guide doesn't give enough info to help, 
> and jeez the full manual (available only as PDF) is nearly 200 pages long.

[toc] | [prev] | [next] | [standalone]

#489425

I know nothing of i2c, but how 'bout setting 'scope for 
single shot and f'ing around with the time base and memory
depth until you can see what you want.  

George H. 

[toc] | [prev] | [next] | [standalone]

#489739

On 12/27/2017 08:16 PM, George Herold wrote:
> I know nothing of i2c, but how 'bout setting 'scope for
> single shot and f'ing around with the time base and memory
> depth until you can see what you want.
> 
> George H.
> 

Ya, I find myself missing my old Kik sometimes when using this one for
single-shot type measurements. The low-end Rigol DSO is great for 
storage/snapshots/looking at detail but for long timebases the analog 
scope seemed superior; its delayed sweep and holdoff controls were 
bang-on accurate. First thoughts were "Ugh, I wish I'd sprung for a DSO 
with more memory." Sometimes I got confused as to whether the i2c bus 
was even functioning because I was having trouble finding the burst in
the long periods of it doing nothing in the DSO memory, that's a breeze 
with the analog.

Wonder if I could link the two somehow, the Kik (once its PSU problem is 
fixed) has a bunch of outputs on the back. Use the analog for the "big 
picture" and the DSO to see the detail

[toc] | [prev] | [next] | [standalone]

#489746

Den lørdag den 30. december 2017 kl. 16.27.59 UTC+1 skrev bitrex:
> On 12/27/2017 08:16 PM, George Herold wrote:
> > I know nothing of i2c, but how 'bout setting 'scope for
> > single shot and f'ing around with the time base and memory
> > depth until you can see what you want.
> > 
> > George H.
> > 
> 
> Ya, I find myself missing my old Kik sometimes when using this one for
> single-shot type measurements. The low-end Rigol DSO is great for 
> storage/snapshots/looking at detail but for long timebases the analog 
> scope seemed superior; its delayed sweep and holdoff controls were 
> bang-on accurate. First thoughts were "Ugh, I wish I'd sprung for a DSO 
> with more memory." Sometimes I got confused as to whether the i2c bus 
> was even functioning because I was having trouble finding the burst in
> the long periods of it doing nothing in the DSO memory, that's a breeze 
> with the analog.
> 
> Wonder if I could link the two somehow, the Kik (once its PSU problem is 
> fixed) has a bunch of outputs on the back. Use the analog for the "big 
> picture" and the DSO to see the detail

use a logic analyser?

[toc] | [prev] | [next] | [standalone]

#489762

On Sat, 30 Dec 2017 08:08:28 -0800 (PST), Lasse Langwadt Christensen
<langwadt@fonz.dk> wrote:

>Den lørdag den 30. december 2017 kl. 16.27.59 UTC+1 skrev bitrex:
>> On 12/27/2017 08:16 PM, George Herold wrote:
>> > I know nothing of i2c, but how 'bout setting 'scope for
>> > single shot and f'ing around with the time base and memory
>> > depth until you can see what you want.
>> > 
>> > George H.
>> > 
>> 
>> Ya, I find myself missing my old Kik sometimes when using this one for
>> single-shot type measurements. The low-end Rigol DSO is great for 
>> storage/snapshots/looking at detail but for long timebases the analog 
>> scope seemed superior; its delayed sweep and holdoff controls were 
>> bang-on accurate. First thoughts were "Ugh, I wish I'd sprung for a DSO 
>> with more memory." Sometimes I got confused as to whether the i2c bus 
>> was even functioning because I was having trouble finding the burst in
>> the long periods of it doing nothing in the DSO memory, that's a breeze 
>> with the analog.
>> 
>> Wonder if I could link the two somehow, the Kik (once its PSU problem is 
>> fixed) has a bunch of outputs on the back. Use the analog for the "big 
>> picture" and the DSO to see the detail
>
>use a logic analyser?

Does anyone use those anymore?  I don't think I've used one in 25
years.

[toc] | [prev] | [next] | [standalone]

#489770

Den lørdag den 30. december 2017 kl. 18.24.06 UTC+1 skrev k...@notreal.com:
> On Sat, 30 Dec 2017 08:08:28 -0800 (PST), Lasse Langwadt Christensen
> <langwadt@fonz.dk> wrote:
> 
> >Den lørdag den 30. december 2017 kl. 16.27.59 UTC+1 skrev bitrex:
> >> On 12/27/2017 08:16 PM, George Herold wrote:
> >> > I know nothing of i2c, but how 'bout setting 'scope for
> >> > single shot and f'ing around with the time base and memory
> >> > depth until you can see what you want.
> >> > 
> >> > George H.
> >> > 
> >> 
> >> Ya, I find myself missing my old Kik sometimes when using this one for
> >> single-shot type measurements. The low-end Rigol DSO is great for 
> >> storage/snapshots/looking at detail but for long timebases the analog 
> >> scope seemed superior; its delayed sweep and holdoff controls were 
> >> bang-on accurate. First thoughts were "Ugh, I wish I'd sprung for a DSO 
> >> with more memory." Sometimes I got confused as to whether the i2c bus 
> >> was even functioning because I was having trouble finding the burst in
> >> the long periods of it doing nothing in the DSO memory, that's a breeze 
> >> with the analog.
> >> 
> >> Wonder if I could link the two somehow, the Kik (once its PSU problem is 
> >> fixed) has a bunch of outputs on the back. Use the analog for the "big 
> >> picture" and the DSO to see the detail
> >
> >use a logic analyser?
> 
> Does anyone use those anymore?  I don't think I've used one in 25
> years.

some scopes have it as an option, and you can get a lot of channels/memory depth  
for next to nothing and it can be a great tool for tracing code 

debug a spi bus and you have already run out of analog channels on most scopes

[toc] | [prev] | [next] | [standalone]

#489788

On Sat, 30 Dec 2017 09:53:21 -0800 (PST), Lasse Langwadt Christensen
<langwadt@fonz.dk> wrote:

>Den lørdag den 30. december 2017 kl. 18.24.06 UTC+1 skrev k...@notreal.com:
>> On Sat, 30 Dec 2017 08:08:28 -0800 (PST), Lasse Langwadt Christensen
>> <langwadt@fonz.dk> wrote:
>> 
>> >Den lørdag den 30. december 2017 kl. 16.27.59 UTC+1 skrev bitrex:
>> >> On 12/27/2017 08:16 PM, George Herold wrote:
>> >> > I know nothing of i2c, but how 'bout setting 'scope for
>> >> > single shot and f'ing around with the time base and memory
>> >> > depth until you can see what you want.
>> >> > 
>> >> > George H.
>> >> > 
>> >> 
>> >> Ya, I find myself missing my old Kik sometimes when using this one for
>> >> single-shot type measurements. The low-end Rigol DSO is great for 
>> >> storage/snapshots/looking at detail but for long timebases the analog 
>> >> scope seemed superior; its delayed sweep and holdoff controls were 
>> >> bang-on accurate. First thoughts were "Ugh, I wish I'd sprung for a DSO 
>> >> with more memory." Sometimes I got confused as to whether the i2c bus 
>> >> was even functioning because I was having trouble finding the burst in
>> >> the long periods of it doing nothing in the DSO memory, that's a breeze 
>> >> with the analog.
>> >> 
>> >> Wonder if I could link the two somehow, the Kik (once its PSU problem is 
>> >> fixed) has a bunch of outputs on the back. Use the analog for the "big 
>> >> picture" and the DSO to see the detail
>> >
>> >use a logic analyser?
>> 
>> Does anyone use those anymore?  I don't think I've used one in 25
>> years.
>
>some scopes have it as an option, and you can get a lot of channels/memory depth  
>for next to nothing and it can be a great tool for tracing code 

Sure, but does anyone really use them?  I don't think we even have one
in the building.  I've never seen one, anyway.

>debug a spi bus and you have already run out of analog channels on most scopes

It depends on what one's trying to fix.  If you're looking at signal
integrity, a two channel scope is usually enough.  If you're trying to
see what the software droid is really sending, a bus analyzer
(Aardvark, or some such thing) is a better tool than a generalized
logic analyzer.

[toc] | [prev] | [next] | [standalone]

#489792

Den lørdag den 30. december 2017 kl. 20.39.52 UTC+1 skrev k...@notreal.com:
> On Sat, 30 Dec 2017 09:53:21 -0800 (PST), Lasse Langwadt Christensen
> <langwadt@fonz.dk> wrote:
> 
> >Den lørdag den 30. december 2017 kl. 18.24.06 UTC+1 skrev k...@notreal.com:
> >> On Sat, 30 Dec 2017 08:08:28 -0800 (PST), Lasse Langwadt Christensen
> >> <langwadt@fonz.dk> wrote:
> >> 
> >> >Den lørdag den 30. december 2017 kl. 16.27.59 UTC+1 skrev bitrex:
> >> >> On 12/27/2017 08:16 PM, George Herold wrote:
> >> >> > I know nothing of i2c, but how 'bout setting 'scope for
> >> >> > single shot and f'ing around with the time base and memory
> >> >> > depth until you can see what you want.
> >> >> > 
> >> >> > George H.
> >> >> > 
> >> >> 
> >> >> Ya, I find myself missing my old Kik sometimes when using this one for
> >> >> single-shot type measurements. The low-end Rigol DSO is great for 
> >> >> storage/snapshots/looking at detail but for long timebases the analog 
> >> >> scope seemed superior; its delayed sweep and holdoff controls were 
> >> >> bang-on accurate. First thoughts were "Ugh, I wish I'd sprung for a DSO 
> >> >> with more memory." Sometimes I got confused as to whether the i2c bus 
> >> >> was even functioning because I was having trouble finding the burst in
> >> >> the long periods of it doing nothing in the DSO memory, that's a breeze 
> >> >> with the analog.
> >> >> 
> >> >> Wonder if I could link the two somehow, the Kik (once its PSU problem is 
> >> >> fixed) has a bunch of outputs on the back. Use the analog for the "big 
> >> >> picture" and the DSO to see the detail
> >> >
> >> >use a logic analyser?
> >> 
> >> Does anyone use those anymore?  I don't think I've used one in 25
> >> years.
> >
> >some scopes have it as an option, and you can get a lot of channels/memory depth  
> >for next to nothing and it can be a great tool for tracing code 
> 
> Sure, but does anyone really use them?  I don't think we even have one
> in the building.  I've never seen one, anyway.
> 
> >debug a spi bus and you have already run out of analog channels on most scopes
> 
> It depends on what one's trying to fix.  If you're looking at signal
> integrity, a two channel scope is usually enough.  If you're trying to
> see what the software droid is really sending, a bus analyzer
> (Aardvark, or some such thing) is a better tool than a generalized
> logic analyzer.

most of the cheap usb based ones can do both, the protocol decoding is 
just software

I can see the advantage of a scope with build in LA in that you can get both
analog and logic/protocol on the same picture   

[toc] | [prev] | [next] | [standalone]

#489869

On 12/30/2017 02:39 PM, krw@notreal.com wrote:
> On Sat, 30 Dec 2017 09:53:21 -0800 (PST), Lasse Langwadt Christensen
> <langwadt@fonz.dk> wrote:
> 
>> Den lørdag den 30. december 2017 kl. 18.24.06 UTC+1 skrev k...@notreal.com:
>>> On Sat, 30 Dec 2017 08:08:28 -0800 (PST), Lasse Langwadt Christensen
>>> <langwadt@fonz.dk> wrote:
>>>
>>>> Den lørdag den 30. december 2017 kl. 16.27.59 UTC+1 skrev bitrex:
>>>>> On 12/27/2017 08:16 PM, George Herold wrote:
>>>>>> I know nothing of i2c, but how 'bout setting 'scope for
>>>>>> single shot and f'ing around with the time base and memory
>>>>>> depth until you can see what you want.
>>>>>>
>>>>>> George H.
>>>>>>
>>>>>
>>>>> Ya, I find myself missing my old Kik sometimes when using this one for
>>>>> single-shot type measurements. The low-end Rigol DSO is great for
>>>>> storage/snapshots/looking at detail but for long timebases the analog
>>>>> scope seemed superior; its delayed sweep and holdoff controls were
>>>>> bang-on accurate. First thoughts were "Ugh, I wish I'd sprung for a DSO
>>>>> with more memory." Sometimes I got confused as to whether the i2c bus
>>>>> was even functioning because I was having trouble finding the burst in
>>>>> the long periods of it doing nothing in the DSO memory, that's a breeze
>>>>> with the analog.
>>>>>
>>>>> Wonder if I could link the two somehow, the Kik (once its PSU problem is
>>>>> fixed) has a bunch of outputs on the back. Use the analog for the "big
>>>>> picture" and the DSO to see the detail
>>>>
>>>> use a logic analyser?
>>>
>>> Does anyone use those anymore?  I don't think I've used one in 25
>>> years.
>>
>> some scopes have it as an option, and you can get a lot of channels/memory depth
>> for next to nothing and it can be a great tool for tracing code
> 
> Sure, but does anyone really use them?  I don't think we even have one
> in the building.  I've never seen one, anyway.
> 
>> debug a spi bus and you have already run out of analog channels on most scopes
> 
> It depends on what one's trying to fix.  If you're looking at signal
> integrity, a two channel scope is usually enough.  If you're trying to
> see what the software droid is really sending, a bus analyzer
> (Aardvark, or some such thing) is a better tool than a generalized
> logic analyzer.
> 

Yeah, one might have been able to use a logic analyzer to trace/debug 
code. In 1987. It's not the 80s anymore; at the low end everything is 
integrated on-die, at the high end the processor is connected to a 
couple sticks of DDR4 at bus clocks pushing 1 GHz through a bajillion 
tiny traces.

[toc] | [prev] | [next] | [standalone]

#489960

Den søndag den 31. december 2017 kl. 16.34.04 UTC+1 skrev bitrex:
> On 12/30/2017 02:39 PM, krw@notreal.com wrote:
> > On Sat, 30 Dec 2017 09:53:21 -0800 (PST), Lasse Langwadt Christensen
> > <langwadt@fonz.dk> wrote:
> > 
> >> Den lørdag den 30. december 2017 kl. 18.24.06 UTC+1 skrev k...@notreal.com:
> >>> On Sat, 30 Dec 2017 08:08:28 -0800 (PST), Lasse Langwadt Christensen
> >>> <langwadt@fonz.dk> wrote:
> >>>
> >>>> Den lørdag den 30. december 2017 kl. 16.27.59 UTC+1 skrev bitrex:
> >>>>> On 12/27/2017 08:16 PM, George Herold wrote:
> >>>>>> I know nothing of i2c, but how 'bout setting 'scope for
> >>>>>> single shot and f'ing around with the time base and memory
> >>>>>> depth until you can see what you want.
> >>>>>>
> >>>>>> George H.
> >>>>>>
> >>>>>
> >>>>> Ya, I find myself missing my old Kik sometimes when using this one for
> >>>>> single-shot type measurements. The low-end Rigol DSO is great for
> >>>>> storage/snapshots/looking at detail but for long timebases the analog
> >>>>> scope seemed superior; its delayed sweep and holdoff controls were
> >>>>> bang-on accurate. First thoughts were "Ugh, I wish I'd sprung for a DSO
> >>>>> with more memory." Sometimes I got confused as to whether the i2c bus
> >>>>> was even functioning because I was having trouble finding the burst in
> >>>>> the long periods of it doing nothing in the DSO memory, that's a breeze
> >>>>> with the analog.
> >>>>>
> >>>>> Wonder if I could link the two somehow, the Kik (once its PSU problem is
> >>>>> fixed) has a bunch of outputs on the back. Use the analog for the "big
> >>>>> picture" and the DSO to see the detail
> >>>>
> >>>> use a logic analyser?
> >>>
> >>> Does anyone use those anymore?  I don't think I've used one in 25
> >>> years.
> >>
> >> some scopes have it as an option, and you can get a lot of channels/memory depth
> >> for next to nothing and it can be a great tool for tracing code
> > 
> > Sure, but does anyone really use them?  I don't think we even have one
> > in the building.  I've never seen one, anyway.
> > 
> >> debug a spi bus and you have already run out of analog channels on most scopes
> > 
> > It depends on what one's trying to fix.  If you're looking at signal
> > integrity, a two channel scope is usually enough.  If you're trying to
> > see what the software droid is really sending, a bus analyzer
> > (Aardvark, or some such thing) is a better tool than a generalized
> > logic analyzer.
> > 
> 
> Yeah, one might have been able to use a logic analyzer to trace/debug 
> code. In 1987. It's not the 80s anymore; at the low end everything is 
> integrated on-die, at the high end the processor is connected to a 
> couple sticks of DDR4 at bus clocks pushing 1 GHz through a bajillion 
> tiny traces.

you cat get a lot of info by toggling a few spare IOs

[toc] | [prev] | [next] | [standalone]

#489974

On Mon, 1 Jan 2018 03:49:18 -0800 (PST), Lasse Langwadt Christensen
<langwadt@fonz.dk> wrote:

>Den søndag den 31. december 2017 kl. 16.34.04 UTC+1 skrev bitrex:
>> On 12/30/2017 02:39 PM, krw@notreal.com wrote:
>> > On Sat, 30 Dec 2017 09:53:21 -0800 (PST), Lasse Langwadt Christensen
>> > <langwadt@fonz.dk> wrote:
>> > 
>> >> Den lørdag den 30. december 2017 kl. 18.24.06 UTC+1 skrev k...@notreal.com:
>> >>> On Sat, 30 Dec 2017 08:08:28 -0800 (PST), Lasse Langwadt Christensen
>> >>> <langwadt@fonz.dk> wrote:
>> >>>
>> >>>> Den lørdag den 30. december 2017 kl. 16.27.59 UTC+1 skrev bitrex:
>> >>>>> On 12/27/2017 08:16 PM, George Herold wrote:
>> >>>>>> I know nothing of i2c, but how 'bout setting 'scope for
>> >>>>>> single shot and f'ing around with the time base and memory
>> >>>>>> depth until you can see what you want.
>> >>>>>>
>> >>>>>> George H.
>> >>>>>>
>> >>>>>
>> >>>>> Ya, I find myself missing my old Kik sometimes when using this one for
>> >>>>> single-shot type measurements. The low-end Rigol DSO is great for
>> >>>>> storage/snapshots/looking at detail but for long timebases the analog
>> >>>>> scope seemed superior; its delayed sweep and holdoff controls were
>> >>>>> bang-on accurate. First thoughts were "Ugh, I wish I'd sprung for a DSO
>> >>>>> with more memory." Sometimes I got confused as to whether the i2c bus
>> >>>>> was even functioning because I was having trouble finding the burst in
>> >>>>> the long periods of it doing nothing in the DSO memory, that's a breeze
>> >>>>> with the analog.
>> >>>>>
>> >>>>> Wonder if I could link the two somehow, the Kik (once its PSU problem is
>> >>>>> fixed) has a bunch of outputs on the back. Use the analog for the "big
>> >>>>> picture" and the DSO to see the detail
>> >>>>
>> >>>> use a logic analyser?
>> >>>
>> >>> Does anyone use those anymore?  I don't think I've used one in 25
>> >>> years.
>> >>
>> >> some scopes have it as an option, and you can get a lot of channels/memory depth
>> >> for next to nothing and it can be a great tool for tracing code
>> > 
>> > Sure, but does anyone really use them?  I don't think we even have one
>> > in the building.  I've never seen one, anyway.
>> > 
>> >> debug a spi bus and you have already run out of analog channels on most scopes
>> > 
>> > It depends on what one's trying to fix.  If you're looking at signal
>> > integrity, a two channel scope is usually enough.  If you're trying to
>> > see what the software droid is really sending, a bus analyzer
>> > (Aardvark, or some such thing) is a better tool than a generalized
>> > logic analyzer.
>> > 
>> 
>> Yeah, one might have been able to use a logic analyzer to trace/debug 
>> code. In 1987. It's not the 80s anymore; at the low end everything is 
>> integrated on-die, at the high end the processor is connected to a 
>> couple sticks of DDR4 at bus clocks pushing 1 GHz through a bajillion 
>> tiny traces.
>
>you cat get a lot of info by toggling a few spare IOs

I connect an 0603 LED to at least one spare I/O of each programmable
chip and others that have spare (or re-use another) GPIOs. Software
types appreciate them and they can be deleted from the final BOM, so
cost nothing.

[toc] | [prev] | [next] | [standalone]

#489870

On 12/30/2017 12:53 PM, Lasse Langwadt Christensen wrote:
> Den lørdag den 30. december 2017 kl. 18.24.06 UTC+1 skrev k...@notreal.com:
>> On Sat, 30 Dec 2017 08:08:28 -0800 (PST), Lasse Langwadt Christensen
>> <langwadt@fonz.dk> wrote:
>>
>>> Den lørdag den 30. december 2017 kl. 16.27.59 UTC+1 skrev bitrex:
>>>> On 12/27/2017 08:16 PM, George Herold wrote:
>>>>> I know nothing of i2c, but how 'bout setting 'scope for
>>>>> single shot and f'ing around with the time base and memory
>>>>> depth until you can see what you want.
>>>>>
>>>>> George H.
>>>>>
>>>>
>>>> Ya, I find myself missing my old Kik sometimes when using this one for
>>>> single-shot type measurements. The low-end Rigol DSO is great for
>>>> storage/snapshots/looking at detail but for long timebases the analog
>>>> scope seemed superior; its delayed sweep and holdoff controls were
>>>> bang-on accurate. First thoughts were "Ugh, I wish I'd sprung for a DSO
>>>> with more memory." Sometimes I got confused as to whether the i2c bus
>>>> was even functioning because I was having trouble finding the burst in
>>>> the long periods of it doing nothing in the DSO memory, that's a breeze
>>>> with the analog.
>>>>
>>>> Wonder if I could link the two somehow, the Kik (once its PSU problem is
>>>> fixed) has a bunch of outputs on the back. Use the analog for the "big
>>>> picture" and the DSO to see the detail
>>>
>>> use a logic analyser?
>>
>> Does anyone use those anymore?  I don't think I've used one in 25
>> years.
> 
> some scopes have it as an option, and you can get a lot of channels/memory depth
> for next to nothing and it can be a great tool for tracing code
> 
> debug a spi bus and you have already run out of analog channels on most scopes
> 
> 
> 

There's a reason logic analyzers sell for next to nothing

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | sci.electronics.design

csiph-web