Shop OBEX P1 Docs P2 Docs Learn Events
Anybody got the Event Driven LSA (Logic State Analyzer) ViewPort democode working? — Parallax Forums

Anybody got the Event Driven LSA (Logic State Analyzer) ViewPort democode working?

StefanL38StefanL38 Posts: 2,292
edited 2011-10-12 02:57 in Propeller 1
Hi,

I tried democode of the Event Driven LSA (Logic State Analyzer) ViewPort-object
with ViewPort 4.5.3 but I only get an errormessage

But the Eventlogger-Client-Screen stays empty after clicking start capture.

Did anybody got this thing working?

best regards

Stefan

Comments

  • mojorizingmojorizing Posts: 249
    edited 2011-10-11 09:16
    Stefan,
    Works for me VP ver.4.6.3 on win7 machine

    Kevin
  • StefanL38StefanL38 Posts: 2,292
    edited 2011-10-11 10:24
    Hi, Kevin

    thank you for answering. VP4.6.3 is still a beta right?

    Can you attach a working example-code that is triggered by PIN30 to a posting?

    Thank you very much in advance.

    best regards

    Stefan
  • 4x5n4x5n Posts: 745
    edited 2011-10-11 10:31
    StefanL38 wrote: »
    Hi,

    I tried democode of the Event Driven LSA (Logic State Analyzer) ViewPort-object
    with ViewPort 4.5.3 but I only get an errormessage

    But the Eventlogger-Client-Screen stays empty after clicking start capture.

    Did anybody got this thing working?

    best regards

    Stefan

    I didn't do so well with viewport at all! :-( I reached out to hanno <SP?> and found that the source of my problem was that since I don't have any machines running windows natively I ran it using an XP instance running in virtualbox. Word is that viewport doesn't work well running in virtualbox.
  • mojorizingmojorizing Posts: 249
    edited 2011-10-11 11:17
    In Event Logger click "view" , "configuration wizard" , and make sure setup pin mask, trigger mask and trigger state for pin #30. Also make sure "plot legend control" is setup. Then "start capture"


    I see VP ver. 4.6.4 is available on the post regarding VP and PropBasic
  • HShankoHShanko Posts: 402
    edited 2011-10-11 12:05
    StefanL38.

    I've been running the LSA for several years now. Using Windows XP via Parallels on an iMac! Cool tool, imho. I'd be lost without it. Can't say it didn't take a bit of effort to get it working; might seem obvious to Hanno, but to get it right from the user manual, not easy. But once working, soooo useful for PASD and Spin.
  • StefanL38StefanL38 Posts: 2,292
    edited 2011-10-11 15:11
    @Kevin,

    where did you download VP4.6.3??
    If I go to www.hannoware.com download-section of viewport the offical version is VP4.6.2

    The link to betaversion tells only things about VP4.6.2 too???

    Anyway if I download the Eventlog-Test.spin to the propeller
    the lower-left-corner of viewport looks like the second screenshot
    then I use the config-wizard in the Eventlogger-client like shown in the fourth picture.
    then I click write to propeller and the lower left corner of Viewport looks like third picture
    trace-IDs see screenshot 1

    I recognized that the viewport variables elog ReDo E1, E2, etc always look the same regardless of what bits I configure to be trigger or Event-pin.

    I guess there is something wrong with the DDE-communication

    keep the hints coming
    best regards

    Stefan
    568 x 524 - 20K
    861 x 353 - 21K
  • StefanL38StefanL38 Posts: 2,292
    edited 2011-10-11 15:46
    OK I got it working. I had to do with ViewPort and the eventlogger-client what is windows most favorite thing it wants to do: RESTARTING :lol:

    Now it works like expected. Though it uses COG-RAM for capturing and has only space for 99 events.

    More academic than real interest. How much money would I have to spend on a digital storage oscilliscope that would be able to sample at a resolution of 0,5 microseconds for a time of 200 milliseconds = 400.000 samples?

    Maybe I have to write my own LSA that writes to HUB-RAM. Am I calculating right that writing a long to hub-ram needs 22/80 = 0.275 microseconds. So a resolution of 1-2 microseconds look realistic for writing to HUB-RAM?

    keep the questions coming
    best regards

    Stefan
  • kuronekokuroneko Posts: 3,623
    edited 2011-10-11 16:16
    StefanL38 wrote: »
    Am I calculating right that writing a long to hub-ram needs 22/80 = 0.275 microseconds. So a resolution of 1-2 microseconds look realistic for writing to HUB-RAM?
    The best you can do with a single cog is one long per hub window. Problem is hub space, you can only store 8K samples, i.e. 1.6ms at this speed.
  • mojorizingmojorizing Posts: 249
    edited 2011-10-11 23:24
    Go to http://hannoware.com/viewport/viewport464.exe

    Hanno has VP downloads as http://hannoware.com/viewport/viewportXXX.exe where XXX is the version.
  • HannoHanno Posts: 1,130
    edited 2011-10-12 02:57
    Sorry I'm late to the party- busy coding all day- "stay tuned". Sounds like you have Bob's analyzer working now?
    I'm getting close to unveiling my open protocol analyzer- it uses ViewPort's new "download array" feature to properly solve exactly this type of problem. You'll be able to use pre-existing protocol adapters for popular protocols or write your own. Events are timestamped with microsecond resolution, cached locally and then merged into ViewPort's database for realtime visual filtering and triggering. I'll post some screenshots tomorrow...
    Hanno
Sign In or Register to comment.