Forum Rule: Always post complete source code & details to reproduce any issue!
Page 3 of 3 FirstFirst 1 2 3
Results 51 to 71 of 71

Thread: Web site could use a few updates :)

  1. #51
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    12,719
    p#32 - Windows Perf Issues? Without a specific case - and not knowing a single cause ... perhaps link the doc pjrc.com/teensy/td_download.html#antivirus_performance_issue to the posts here on this thread in case they lead to a solution

  2. #52
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    23,061
    Added under "Other Libraries".


    Quote Originally Posted by boxxofrobots View Post
    When will audioEffectRectifier be added to the ASD tool?
    Added some time ago...

    https://www.pjrc.com/teensy/gui/?inf...ffectRectifier


    Quote Originally Posted by kd5rxt-mark View Post
    I've made some preliminary screen captures from Windows Defender as requested.
    I've put these instructions and 6 screenshots on the download page.

    https://www.pjrc.com/teensy/td_downl...formance_issue

    Thanks for taking the time to make these screenshots! I really appreciate help with Windows stuff, as I mostly use Linux and occasionally Macintosh.


    Quote Originally Posted by kd5rxt-mark View Post
    Just to be safe, it would probably be best to add both methods/changes to the webpage !!
    I'd be happy to add this too, but it needs some editing....


    Quote Originally Posted by KurtE View Post
    Also related: The USB Host adapter cable: https://www.pjrc.com/store/cable_usb_host_t36.html
    Should be updated to say that this works on T4.1 as well.
    Updated to state Teensy 4.1 compatibility, and explain bottom side pads on Teensy 4.0.
    Last edited by PaulStoffregen; 10-21-2020 at 12:05 PM.

  3. #53
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    23,061
    @Degragster - Any chance I can talk you into re-writing the guidance in msg #24 in a step-by-step style?

    I want to put this on the download page. But the conversational style of msg #24 isn't a good fit for the web page. It really needs a brief and clear description of why to use this approach rather than Mark's 8-step process, and then a set of specific steps to follow to accomplish it.

    Remember, I don't use Windows. I'm really looking for text & images to copy verbatim into the web page, so I don't mess up some subtle but important Windows detail.

  4. #54
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    23,061
    Quote Originally Posted by KurtE View Post
    Fixed

    T4 product page on memory usage: https://www.pjrc.com/store/teensy40.html
    Fixed FLASHMEM for code usage, added EXTMEM.


    And wish the T4.1 page would refer users to the T4 page for memory stuff or a copy of it also showing external memory...
    Added a link under "Memory Expansion".

    Eventually I want to move that memory layout stuff to a dedicated page and expand it with examples. But hopefully this helps until I can put more time into the website.

  5. #55
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    23,061
    Quote Originally Posted by embedded-creations View Post
    https://www.pjrc.com/teensy/td_libs_OctoWS2811.html

    No mention of Teensy 4: "OctoWS2811 requires the DMA (Direct Memory Access) engine which is available only in Teensy LC & 3.x."
    Updated, now says "Teensy LC & 3.x & 4.x".


    Also, it appears from skimming your OctoWS2811 Teensy 4 code and reading between the lines on some forum posts you made that OctoWS2811 running on the Teensy 4 can drive more than 8 outputs, but there's no documentation to that effect.
    Under "Hardware Requirements" the page does say:

    Teensy 4.0 and Teensy 4.1 can use any group of pins, even groups smaller or larger than 8 pins! In Arduino, open File > Examples > OctoWS2811 > Teensy4_PinList for details. If a custom pin list is not specified, the same group of 8 pins as Teensy 3.x will be used by default.
    I've added "Teensy 4.x boards support use of any set of pins, not limited to only 8 fixed pins. See the Teensy4_PinList example for details." near the top of the page to hopefully make this more visible.

  6. #56
    Senior Member
    Join Date
    Jul 2014
    Posts
    2,903
    on https://www.pjrc.com/store/teensy41.html

    in
    "Teensy 4.0 can be programmed using the Arduino IDE with Teensyduino add-on."
    change 4.0 to 4.1

  7. #57
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    23,061
    Quote Originally Posted by WMXZ View Post
    change 4.0 to 4.1
    Fixed it just now

  8. #58
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    12,719
    Quote Originally Posted by PaulStoffregen View Post
    @Degragster - Any chance I can talk you into re-writing the guidance in msg #24 in a step-by-step style?
    ...
    yes I'll look at that batch of screen shots and see if I can make some step-wise sense of them ...

  9. #59
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    12,719
    Just saw this page has a "Key Features:" table missing T_4.0 and 4.1:
    pjrc.com/teensy/index.html

    In fact "Key Features:" table entry for T_3.1 is there not 3.2

  10. #60
    Junior Member
    Join Date
    Nov 2019
    Posts
    15
    I added the 3.2, 3.5, 3.6, 4.0 and 4.1 to that table:
    Code:
    <table border=1 cellpadding=2 align=right>
    <tr><th>Specification</th><th>Teensy 2.0</th><th>Teensy++ 2.0</td><th>Teensy 3.0</th><th>Teensy 3.1</th><th>Teensy 3.2</th><th>Teensy 3.5</th><th>Teensy 3.6</th><th>Teensy 4.0</th><th>Teensy 4.1</th></tr>
    <tr><td>Processor</td><td>ATMEGA32U4<br>8 bit AVR<br>16 MHz</td><td>AT90USB1286<br>8 bit AVR<br>16 MHz</td><td>MK20DX128<br>32 bit ARM<br>Cortex-M4<br>48 MHz</td><td>MK20DX256<br>32 bit ARM<br>Cortex-M4<br>72 MHz</td><td>MK20DX256VLH7<br>32 bit ARM<br>Cortex-M4<br>72 MHz</td><td>MK64FX512VMD12<br>32 bit ARM<br>Cortex-M4F<br>120 MHz</td><td>MK66FX1M0VMD18<br>32 bit ARM<br>Cortex-M4F<br>180 MHz</td><td>iMXRT1062<br>32 bit ARM<br>Cortex-M7<br>600 Mhz</td><td>iMXRT1062<br>32 bit ARM<br>Cortex-M7<br>600 Mhz></td></tr>
    <tr><td>Flash Memory</td><td>32256</td><td>130048</td><td>131072</td><td>262144</td><td>256k</td><td>512k</td><td>1024k</td><td>1984k</td><td>7936k</td></tr>
    <tr><td>RAM Memory</td><td>2560</td><td>8192</td><td>16384</td><td>65536</td><td>64k</td><td>256k</td><td>256k</td><td>1024k</td><td>1024k</td></tr>
    <tr><td>EEPROM</td><td>1024</td><td>4096</td><td>2048</td><td>2048</td><td>2048</td><td>4096</td><td>4096</td><td>1080</td><td>4284</td></tr>
    <tr><td>I/O</td><td>25, 5 Volt</td><td>46, 5 Volt</td><td>34, 3.3 Volt</td><td>34, 3.3V, 5V tol</td><td>34, 3.3V, 5V tol</td><td>58, 3.3V, 5V tol</td><td>58, 3.3V</td><td>40, 3.3V</td><td>55, 3.3V</td></tr>
    <tr><td>Analog In</td><td>12</td><td>8</td><td>14</td><td>21</td><td>21</td><td>27</td><td>25</td><td>14</td><td>18</td></tr>
    <tr><td>PWM</td><td>7</td><td>9</td><td>10</td><td>12</td><td>12</td><td>20</td><td>22</td><td>27</td><td>31</td></tr>
    <tr><td>UART,I2C,SPI</td><td>1,1,1</td><td>1,1,1</td><td>3,1,1</td><td>3,2,1</td><td>3,2,1</td><td>6,3,3</td><td>6,4,3</td><td>7,3,2</td><td>8,3,2</td></tr>
    <tr><td>Price</td><td><a href="/store/teensy.html">$16.00</a></td><td><a href="/store/teensypp.html">$24.00</a></td><td><a href="/store/teensy3.html">$19.00</a></td><td><a href="/store/teensy31.html">$19.80</a></td><td><a href="/store/teensy32.html">$19.80</a></td><td><a href="/store/teensy35.html">$24.25</a></td><td><a href="/store/teensy36.html">$29.25</a></td><td><a href="/store/teensy40.html">$19.95</a></td><td><a href="/store/teensy41.html">$26.85</a></td></tr>
    </table>
    Last edited by towe; 11-12-2020 at 10:30 AM. Reason: erroneous ">"

  11. #61
    Junior Member
    Join Date
    Aug 2018
    Posts
    5

    Post

    1. The libraries page only shows Teensy 2.0 through 3.x
    2. The code in the section "Pushbuttons To Control LED Colors" of tutorial 3 has the comment "// use mode one when the first button is pressed" which should read "second button"

  12. #62
    Senior Member+ Frank B's Avatar
    Join Date
    Apr 2014
    Location
    Germany NRW
    Posts
    7,088
    https://www.pjrc.com/teensy/pins.html

    This page is for Teensy 2 only, but there is no indication that it is not valid for Teensy 3/4 which leads to misunderstandings: https://forum.pjrc.com/threads/64702...ntrol-register

  13. #63
    The Teensy 4.1 card back side isn't published, in either image or PDF:

    https://www.pjrc.com/teensy/pinout.html

  14. #64
    Senior Member+ KurtE's Avatar
    Join Date
    Jan 2014
    Posts
    7,923
    Quote Originally Posted by embedded-creations View Post
    The Teensy 4.1 card back side isn't published, in either image or PDF:

    https://www.pjrc.com/teensy/pinout.html
    Actually it would be nice to update the back of the card to have some similar information like the back of the card T4 and T3.6 with maybe showing the USB Pins, The internal: ON/OFF, Program, ... pins,


    Another minor web page thing is the T4 page (https://www.pjrc.com/store/teensy40.html) starts off saying: Teensy 4.0 is the latest Teensy, offering ...
    But now the T4.1 is the latest

  15. #65
    Senior Member+ MichaelMeissner's Avatar
    Join Date
    Nov 2012
    Location
    Ayer Massachussetts
    Posts
    3,887
    Quote Originally Posted by KurtE View Post
    Another minor web page thing is the T4 page (https://www.pjrc.com/store/teensy40.html) starts off saying: Teensy 4.0 is the latest Teensy, offering ...
    But now the T4.1 is the latest
    And of course there are rumors of a new Teensy using the same chip but with a new form factor (micromod) that might show up some time.

    That is always the problem of labeling something 'new'. I recall when I was an exchange student during the summer of 1978 in the Netherlands, of seeing a church built in 1380-1408 and rebuilt a few times afterwards labeled Nieuwe Kerk (new church). The Oude Kerk (old church) was built in 1213-1306 (and renovated a few times) is evidently still standing. I would have to imagine there are newer churches built since then.

  16. #66
    Senior Member PaulStoffregen's Avatar
    Join Date
    Nov 2012
    Posts
    23,061
    I'm planning to rewrite the product pages "soon". The Teensy 4.1 pinout card back side will come later, probably late December or early January. Most of the website is a work in progress, but at this moment I'd like to talk about what to put on the product pages.

    In prep, I started a lengthy outline / template list of sections and sub-sections I want to include on all the product pages. I also spent some time looking at the product pages on Sparkfun, Adafruit and Arduino. Adafruit's page are most similar to what we have now, usually just a list of specs, some description & photos, and links to other pages on the site. Arduino & Sparkfun use tabs, but some are long info that requires scrolling anyway. I'm feeling inspired by some of Arduino's pages where the "documentation" tab lists all the hardware features briefly. For Teensy 4.0 & 4.1 that would become a very long list, but maybe long is good if the info is clearly arranged?

    So my open-ended question at this point is what info should go onto those product pages. And a lesser question is how detailed should it be on those pages, versus a brief mention and links to other pages with more in-depth coverage?

  17. #67
    Senior Member+ MichaelMeissner's Avatar
    Join Date
    Nov 2012
    Location
    Ayer Massachussetts
    Posts
    3,887
    It would be useful to mention what are the specific defines for each chip to use with #ifdef.

    One thing that would be useful in the web document, but it probably doesn't need to be at the top is a brief list for each of the boards of what shields work without modification, which work with some modification, and which don't work at all. Or possibly links to a common meta page about shields.

    For example, with the prop shield:
    • Teensy LC: DAC output works for the Teensy LC, but a lot of the audio library does not work;
    • Teensy 3.2: Works great;
    • Teensy 3.5 & 3.6: Works great, for sound you need to run a wire from DAC0 (A21) to the DAC pin on the prop shield, and you don't need to connect the other back 4 pins;
    • Teensy 4.0 & 4.1: Sound does not work at all, no need to connect the 5 back pins.


    It may be useful to have a meta page of useful example pages, starting with the ever popular blink, and then listing a few examples to show off what the Teensys could do (i.e. pointing off to the audio example, etc.). You don't want a long list, but it would be helpful to have maybe a top 10 list of things that can be done.

  18. #68
    Junior Member
    Join Date
    Aug 2018
    Posts
    5
    Brief specs and details are good to start with, but there should definitely be links to more detailed information either on separate pages or further down the same page.

  19. #69
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    12,719
    @Paul - check New Supplier page : protosupplies.com/product/teensy-4-1/

    A good page of T_4.1 info as I saw it. My ISP won't allow me to view it at this time ...

    It seemed to have an exhaustive list - like AdaF perhaps - on a single page. Clear bright page and nice pics.

    The one thing I saw missing and pointed out was link to info on the T_4.0 page on memory mapping - not sure if Ken got to updating that yet as my ability to see the web IP is intermittent.

    The rear of the T_4.1 with details will be a significant and welcome addition.

    Oh - and the page/tab :: pjrc.com/teensy/pins.html

    may as well be labelled : "Teensy AVR How-To Tips"
    Code:
     How-To Tips
    selected I/O Pins
     Interrupts
     Analog Input
     Other Languages
     3.3 Volts
     External Power
     Low Power
     Clock Speed
     Jump Bootloader
     Troubleshoot

  20. #70
    Senior Member+ KurtE's Avatar
    Join Date
    Jan 2014
    Posts
    7,923
    @Paul - I am sort of torn, as if you were to say you have full time staff to add lots of content, that would be great. But if it is just you, then may not as much as I would guess there are still lots of software/hardware projects and capabilities that you could take up a bit of your time

    You mentioned Sparkfun and Adafruit, the interesting thing of these sites are often more in their WIKI pages than the main product pages.

    One of the main thing I believe that the website needs is more interconnection between pages and the like and to gear more of it toward ARM based products instead of the older AVR proecuts.

    For example Suppose I heard about a Teensy 4.1. So I go to the main site. I see the T4.1 on the left hand side of the page and click on it and order it. And it arrives... Now what?
    The card says see the Getting started page. I don't see that. I click on the T4.1... I look at the page and I still don't see any information. I then maybe noticed that the card mentioned pjrc.com/teensy... There is a clickable thing near the top of the main page that says Teensy... Click there, and finally I see a clickable text on the left hand that talks about getting started, which takes me to a page that Is setup for a T1 or T2... Talks about halfkey loader... Still nothing that mentions you need to install Teensyduino. The follow on page talks about the Teensy app.

    So personally I think there needs to be some links in the main product pages, that maybe takes you to things like: getting started, hardware, Tutorials...
    And the Getting started needs to be updated to probably mostly cover the newer boards: TlC, 3.x, 4.x... and either second part for older boards or two sections or ...
    And then maybe if there was some like an Emanual or Wiki..., where to download documents...

    As for more extensive website documentation possibilities, one of the other boards I have played with are from Robotis.... like their cheap OpenCM9.04 board: https://www.robotis.us/opencm9-04-a-...ctors-onboard/
    They highlight, plus then have links to things like Arduino IDE, ... And their EManual for this product: https://emanual.robotis.com/docs/en/...ler/opencm904/

    Likewise the RPI stuff has something similar as well.

    But I can imagine that this would be labor intensive to produce and maintain... So I would probably not dive too deep and not have time to do more fun things!

  21. #71
    I'm with KurtE on this.

    1. Go after the very low hanging fruit first like cleaning up the navigation in the menus and adding links on product pages to make it easier to find the other info that applies to that product. I still click on both Products and Teensy in the top menu randomly trying to find what I am looking for.

    2. A second easy step would be to cut and paste some of the info directly into the product pages to make it easier to find, like the stuff on the 4.0 page that also applies to the 4.1 page or perhaps the relevant schematics and things of that nature.

    3. Consolidate and update the basic getting started info and make it very easy to find.

    Past that I think you would probably want to decide if you want to sell direct as much as possible (maximize margins and deal with more shipping overhead) or leverage your resellers to sell more in bulk (lower margins, less shipping overhead). That would kind of determine which direction you'd want to grow the website. In the case of the former, you'd probably want to work more on the overall look, ease of purchase and sales pitch. In the case of the latter, you would focus more on providing solid technical information to facilitate the success with the product like the Adafruit Wiki stuff. I'm biased, so I'd chose the latter.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •