Shop OBEX P1 Docs P2 Docs Learn Events
Evaluating P2 performance/capabilities — Parallax Forums

Evaluating P2 performance/capabilities

RJSMRJSM Posts: 68
in Propeller 2
Title says it all. In the course of learning about the P2 I've been collecting information together in a document (pdf attached) that perhaps others may find useful.
pdf
pdf
P2-EVALB_Evaluation.pdf
3M

Comments

  • cgraceycgracey Posts: 14,155
    Thanks for making this, RJSM.
  • evanhevanh Posts: 15,916
    "vi" is an old text editor for terminals/consoles that's typically integral to Linux deployments. That doesn't seem to fit your use of the name though. You are using the term a lot, so an introduction would be in order.
  • ozpropdevozpropdev Posts: 2,792
    Very nice work Richard! :)
  • RJSMRJSM Posts: 68
    The Wikipedia entry for LabVIEW under the heading Graphical Programming explains the use of a "vi" - which stands for virtual instrument. Yes I do remember using the vi editor many, many years ago...
  • potatoheadpotatohead Posts: 10,261
    edited 2019-12-18 07:36
    I came here to say the same thing. A "vi" is just a LabView setup.

    I used vi just a few days ago. Linux print server, needed to hack a quick init script edit.

    Thanks for this great info @RJSM
  • evanhevanh Posts: 15,916
    Ah so the "National Instruments LabVIEW vi " didn't mean version six then.

  • Bob Lawrence (VE1RLL)Bob Lawrence (VE1RLL) Posts: 1,720
    edited 2019-12-18 08:26
    LabVIEW Community Edition ( Beta ) is now available at : http://www.ni.com/support/beta-program/

    The first full release ( Community Edition )is also scheduled for May 2020. You can learn more by viewing NI’s Software Technology Preview website.
  • ReinhardReinhard Posts: 489
    Thank you for this great evaluation report.
    This will make things a lot clearer.
    How do you send the serial data from P2 to the LabView host and vice versa?
    In LabView I know the serial vi's.
    Do you have serialin/serialout routines in p2asm ?
    Or do you use a Spin - Objekt or a C-wrapper with printf's.

    It is planned to publish the source code for the individual issues?
  • RJSMRJSM Posts: 68
    Some more information -:

    I used LV2017 to build the vi's shown in my evaluation report. Current version is LV2019 but I've not migrated to this yet. As a now retired university Chemistry prof I've maintained my academic licence which gives me a deep discount - and this allows me to build run time executables that are distributable with no licencing fees. Without that discount LV is expensive - however see Bob Lawrence's earlier post. There's a low cost student edition too.

    I have serial tx and rx routines in my P2asm code using smart pins - pretty standard.

    A number of years ago FTDI (makers of FT23x/FT245 series chips) made a suite of vi's available to access their chips from LV as standard COM ports. I'm not sure if these are online any more but I've maintained these through the evolving LV versions and they are easy to use and are very reliable.

    I've attached a jpeg showing an assignment of an ADC pin using a Pn, command. The P2 monitor code parses this to set the pin. The icon at the far left is an FT_Init vi that sets up the comms - I typically set a 3M baud rate. The Init code gets a handle to the port and this is used every time there is some interaction with it. There are other vi's to send and receive data buffers that just need a Port Handle and # of bytes to transfer, so sending chunks of data LV <---> P2 is very straightforward.

    And yes, I do have plans to make all my code and LabVIEW available - but realistically it will be into the New Year before I can begin to do this.
    Serial_example.JPG
    776 x 149 - 30K
Sign In or Register to comment.