Congratulations!

[Valid RSS] This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: https://forums.parallax.com/categories/propeller-1-multicore-microcontroller/feed.rss

  1. <?xml version="1.0" encoding="utf-8"?>
  2. <rss version="2.0"
  3.    xmlns:content="http://purl.org/rss/1.0/modules/content/"
  4.    xmlns:dc="http://purl.org/dc/elements/1.1/"
  5.    xmlns:atom="http://www.w3.org/2005/Atom">
  6.    <channel>
  7.        <title>Propeller 1 — Parallax Forums</title>
  8.        <link>https://forums.parallax.com/</link>
  9.        <pubDate>Thu, 18 Sep 2025 06:56:17 +0000</pubDate>
  10.        <language>en</language>
  11.            <description>Propeller 1 — Parallax Forums</description>
  12.    <atom:link href="https://forums.parallax.com/categories/propeller-1-multicore-microcontroller/feed.rss" rel="self" type="application/rss+xml"/>
  13.    <item>
  14.        <title>Platform3 (Concept)</title>
  15.        <link>https://forums.parallax.com/discussion/177849/platform3-concept</link>
  16.        <pubDate>Sun, 14 Sep 2025 14:19:34 +0000</pubDate>
  17.        <category>Propeller 1</category>
  18.        <dc:creator>Rayman</dc:creator>
  19.        <guid isPermaLink="false">177849@/discussions</guid>
  20.        <description><![CDATA[<p>Need a new P1 board for a battery powered full color E-Ink display...</p>
  21.  
  22. <p>Haven't made a P1 board in a very long time, so this is fun.<br />
  23. Here's the concept so far (see image).</p>
  24.  
  25. <p>Think the last "platform" board for P1 that we made was called "Express".<br />
  26. This is an expanded update.</p>
  27.  
  28. <p>USB connectors updated to USB-C<br />
  29. FTDI chip updated to FT231X.<br />
  30. Doing this in Eagle, think was ExpressPCB last time.  That was smaller, this is full size...<br />
  31. Adding a QWIIC connector (cause that's an easy way to add peripherals).<br />
  32. Added two P2 style headers, not sure what will do with those yet.<br />
  33. Adding a middle proto area.  This is where the E-Ink adapter will connect.<br />
  34. Could have two of them...<br />
  35. Adding a second USB-C connector for power only (no serial).<br />
  36. Adding two pull-up resistors to uSD, even though maybe not 100% needed.<br />
  37. Adding a couple blue LEDs.</p>
  38.  
  39. <p>Think that's about it...</p>
  40. ]]>
  41.        </description>
  42.    </item>
  43.    <item>
  44.        <title>CNC - I may be crazy but...</title>
  45.        <link>https://forums.parallax.com/discussion/166716/cnc-i-may-be-crazy-but</link>
  46.        <pubDate>Sat, 20 May 2017 17:20:47 +0000</pubDate>
  47.        <category>Propeller 1</category>
  48.        <dc:creator>ManAtWork</dc:creator>
  49.        <guid isPermaLink="false">166716@/discussions</guid>
  50.        <description><![CDATA[Ok, I have to admit that I've stolen the title from Idbruce. But I couldn't resist. I think I'm at least as crazy as him. Look at this. It's my definition of a CNC machine.<br /><img src="/discussion/download/120521/Schmoll-overview.jpg" alt="Schmoll-overview.jpg" /><br />
  51. It's a "Schmoll Compact". "Compact" means, it's one of the smaller models, weighting over 2 tons <img src="https://forums.parallax.com/resources/emoji/lol.png" title=":lol:" alt=":lol:" height="20" /> . It was actually a PCB drilling machine. The mechanics was in very good condition but I removed the whole controller and the DC servos. I replaced them with MOOG AC servos, 2HP for the X and Y axis and 1HP for the Z axis. I had to rebuild the Z axis because the original axis had too little travel to do any useful work other than drilling PCB holes.<br /><br />
  52. This is the electrical cabinet. Except for the Power supplies and the VFD for the main spindle I build everything from scratch. Guess how many propellers are in there.<br /><img src="/discussion/download/120522/Schmoll-Cabinet1.jpg" alt="Schmoll-Cabinet1.jpg" /><br /><br />
  53. This is one of the servo motors:<br /><img src="/discussion/download/120523/Schmoll-MotorX.jpg" alt="Schmoll-MotorX.jpg" /><br /><br />
  54. Feedback from the servos (resolvers) is already working. I still have to run a few wires through the cable chains to the limit switches and the magnetic brake of the Z motor. I hope I can power up the servo controllers for the first time, next week. ]]>
  55.        </description>
  56.    </item>
  57.    <item>
  58.        <title>SIDcog - The sound of the Commodore 64 !</title>
  59.        <link>https://forums.parallax.com/discussion/118285/sidcog-the-sound-of-the-commodore-64</link>
  60.        <pubDate>Fri, 11 Dec 2009 13:27:25 +0000</pubDate>
  61.        <category>Propeller 1</category>
  62.        <dc:creator>Ahle2</dc:creator>
  63.        <guid isPermaLink="false">118285@/discussions</guid>
  64.        <description><![CDATA[Okey guys here it is, an emulation of the famous sound chip used in the Commodore 64 !<br /><br />
  65. Download the zip file and run "ExamplePlayroutine.spin" and "ExampleSidDumpPlay.spin".<br />
  66. "ExampleSidDumpPlay.spin" needs a SD card and the file "Russian.dmp" in the root of the card.<br /><br /><b>There are two different versions of SIDcog:</b><br />
  67. - If you want a more accurate emulation of the SID use "SIDcog".  (playback of C64 SID dump files)<br />
  68. - If you want a small footprint use "SIDcog_Lite". (uses 63% of the space compared to SIDcog)<br /><br />
  69. The only difference between the two versions at the moment are the combined waveform support in "SIDcog".<br /><br /><b>SIDcog version 0.80 features:</b><br />
  70. - Runs in one cog - totally self contained.<br />
  71. - 31kHz sample rate.<br />
  72. - &gt;16bit resolution.<br />
  73. - Full filter support - any combination of Lowpass, Bandpass and Highpass filter.<br />
  74. - Full envelope support with a logarithmic release/decay curve. ( uses the same logarithmic approximation as a real SID)<br />
  75. - Supports all 4 waveform types<br />
  76. - Combined waveform support ( Not supported in SIDcog Lite )<br />
  77. - 16 steps main volume.<br />
  78. - Waveform reset bit works. (many Rob Hubbard tunes relies on this exact behaviour)<br />
  79. - Ring modulation.<br />
  80. - Oscillator synchronization.<br />
  81. - Can be "programmed" in the EXACT same way as a real SID. (Have a look at the official SID documentation for a better understanding)<br /><br /><b>SIDcog lacks:</b><br />
  82. - Possibillity to smoothly schange the filter resonance amount value  (partly implemented thanks to Ariba)<br /><br />
  83. BTW, if you have missed the initial SIDcog demo have a look at <a href="http://forums.parallax.com/showthread.php?p=855167" rel="nofollow">http://forums.parallax.com/showthread.php?p=855167</a><br />
  84. Here is a link to an archive containing the <a href="http://gadgetgangster.com/scripts/displayasset.php?id=361" rel="nofollow">SID dumper</a> tool.<br />
  85. Download  <a href="http://www.mongofiles.com/file/18079/SIDcog_SerialPlayer.7z" rel="nofollow">SIDcog serial player</a> to play SID-tunes via a serial link to a propeller running SIDcog.<br /><br /><i>Post Edited (Ahle2) : 6/14/2010 6:35:43 PM GMT</i>]]>
  86.        </description>
  87.    </item>
  88.    <item>
  89.        <title>New Game: IMPACT for the Propeller</title>
  90.        <link>https://forums.parallax.com/discussion/166608/new-game-impact-for-the-propeller</link>
  91.        <pubDate>Tue, 02 May 2017 06:40:54 +0000</pubDate>
  92.        <category>Propeller 1</category>
  93.        <dc:creator>zx81vga</dc:creator>
  94.        <guid isPermaLink="false">166608@/discussions</guid>
  95.        <description><![CDATA[Hello Propellerfriends,<br /><br />
  96. i present a new Game for the Propeller:<br /><br /><b>IMPACT v1.0</b><br /><br />
  97. Inspired by the PC-Game IMPACT! by ASL 1988.<br /><br />
  98. Original Game:<br /><br /><img src="http://propeller.ws-nbg.de/images/impact/impact_org.png" alt="impact_org.png" /><br /><br />
  99. My Propeller Version:<br /><br /><img src="http://propeller.ws-nbg.de/images/impact/impact_1.png" alt="impact_1.png" /><br /><br />
  100. Here to find:<br /><br /><a href="http://propeller.ws-nbg.de/main.php" rel="nofollow">http://propeller.ws-nbg.de/main.php</a><br /><br />
  101. Also <a href="http://www.ws-nbg.de/p8x/main.php" rel="nofollow">available</a> for the <a href="https://dev.maccasoft.com/propgame/" rel="nofollow">P8X Game System</a>.<br /><br />
  102. Have Fun...<br /><br />
  103. Greetings from Nuremberg<br /><br />
  104. Werner<br /><br />]]>
  105.        </description>
  106.    </item>
  107.    <item>
  108.        <title>Propeller Power Consumed Based on Code</title>
  109.        <link>https://forums.parallax.com/discussion/132961/propeller-power-consumed-based-on-code</link>
  110.        <pubDate>Wed, 13 Jul 2011 00:48:53 +0000</pubDate>
  111.        <category>Propeller 1</category>
  112.        <dc:creator>Humanoido</dc:creator>
  113.        <guid isPermaLink="false">132961@/discussions</guid>
  114.        <description><![CDATA[For those that have ammeters and can measure the real world current drawn by a Propeller chip, what is the current drawn by different programs?<br /><br />
  115. Is it possible to establish a list of short programs, each with one purpose or method, and then list their corresponding power consumption?<br /><br />
  116. Or is power draw simply related to the number of cogs in use? i.e. how much power is drawn by 1 cog, 2 cogs ...<br /><br />
  117. Actually it appears to involve several variables. The best reference is the Propeller data sheet where it shows current is a function of frequency. (shown as PLL current as a function of VCO frequency.<br /><br /><a href="http://www.parallax.com/Portals/0/Downloads/docs/prod/prop/Propeller-P8X32A-Datasheet-v1.4.0.pdf" rel="nofollow">http://www.parallax.com/Portals/0/Downloads/docs/prod/prop/Propeller-P8X32A-Datasheet-v1.4.0.pdf</a><br /><br />
  118. Even specific pins have varying power draw. See 8.5 Cog and I/O Pin Relationship.<br /><br />
  119. The current is also different for a WAITLOOP, ASSEMBLY,  or SPIN program. So maybe we need to narrow this down to Spin language.<br /><br />
  120. Also the boot sequence profile determines power draw. See 8.6<br /><br />
  121. The objective is to develop some guidelines and references, so that when coding, we can choose the most effective code thereby creating the lowest power consuming devices.<br /><br />
  122. (maybe it appears one chip and a few mA is relatively meaningless, but in either a battery situation or a multi-chip situation, the current consumed can become important and significant)<br /><br />
  123. 8.5 <i>While there can be a 1 to 1.5 ns propagation delay in output transitions between the shortest and longest paths, the purpose of the figure is to illustrate the length of leads and their associated parasitic capacitance. This capacitance increases the amount of energy required to transition a pin’s state and therefore increases the current draw for toggling a pin. So, the current consumed by Cog 7 toggling P0 at 20 MHz will be greater than Cog 0 toggling P7 at 20 MHz. The amount of current consumed by transitioning a pin’s state is dependent on many factors including: temperature, frequency of transitions, external load, and internal load. As mentioned, the internal load is dependent upon which cog and pin are used. Internal load current for room temperature toggling of a pin at 20 MHz for a Propeller in a DIP package varies on the order of 300 μA.</i>]]>
  124.        </description>
  125.    </item>
  126.    <item>
  127.        <title>Activity Board WXs needed</title>
  128.        <link>https://forums.parallax.com/discussion/176254/activity-board-wxs-needed</link>
  129.        <pubDate>Thu, 24 Jul 2025 19:08:44 +0000</pubDate>
  130.        <category>Propeller 1</category>
  131.        <dc:creator>PapaLev</dc:creator>
  132.        <guid isPermaLink="false">176254@/discussions</guid>
  133.        <description><![CDATA[<p>Our local K-8 school made a big committment to Blockly Prop, the Activity Bot 360, and the Activity Board WX since their beginning. Our students have had a lot of fun with them, and I've enjoyed being the STEM Club advisor. We hoped to get more hardware to accomodate more students and projects, but the Activity Board WX is no longer in production. Does anyone have unused boards collecting dust that would like a new home, and thereby give joy to countless 12-16 year olds? If so please PM me, we are interested in buying some. Thank you.</p>
  134. ]]>
  135.        </description>
  136.    </item>
  137.    <item>
  138.        <title>problem in propeller 1 code please help</title>
  139.        <link>https://forums.parallax.com/discussion/176255/problem-in-propeller-1-code-please-help</link>
  140.        <pubDate>Fri, 25 Jul 2025 13:18:53 +0000</pubDate>
  141.        <category>Propeller 1</category>
  142.        <dc:creator>rob26</dc:creator>
  143.        <guid isPermaLink="false">176255@/discussions</guid>
  144.        <description><![CDATA[<p>Hi , i made a simple program, read pressure and temperature values from a HoneyWell pressure sensor type SSCMANV030PA2A3. A Servo puls is generated via de Servo32v9 object.<br />
  145. In the PUB the Servo.Set(Servo_1,1500), is set the servo and works well. But after a delay time in the main loop, Servo.set(Servo_1,1500) is called again, the Sensor data becomes zero. Before that the values are good.  The HoneyWell sensor works well on an other propeller 1.  The combination of both, Sensor and Servo output, on one propeller 1 is new.  The Main program is ServoB_X AD contr v0.01.spin<br />
  146. I have done several tests and combinations but cannot find out what the problem/error is</p>
  147.  
  148. <p>Is there anyone who sees what might be causing this error?</p>
  149. ]]>
  150.        </description>
  151.    </item>
  152.    <item>
  153.        <title>Improved GEAR Emulator</title>
  154.        <link>https://forums.parallax.com/discussion/156347/improved-gear-emulator</link>
  155.        <pubDate>Thu, 03 Jul 2014 20:47:47 +0000</pubDate>
  156.        <category>Propeller 1</category>
  157.        <dc:creator>Gatuno</dc:creator>
  158.        <guid isPermaLink="false">156347@/discussions</guid>
  159.        <description><![CDATA[For who didn't know, <b>GEAR is an Propeller 1 Emulator</b>,  capable to load propeller images (binary/eeprom) compiled by Propeller  Tool or simillar. Their last version was 1.11 in year 2007.<br /><b> Forum thread by the original programmer asterisk: </b><a href="http://forums.parallax.com/showthread.php?p=624986" rel="nofollow">http://forums.parallax.com/showthread.php?p=624986 </a><br /><b>Code repository: </b><a href="http://sourceforge.net/projects/gear-emu/" rel="nofollow">http://sourceforge.net/projects/gear-emu/</a><br /><br />
  160. Then user mirror makes new versions up to 2009, with more improvements and bug fixes.<br /><b>Forum thread "More GEAR" (w/ program &amp; sources) :</b> <a href="http://forums.parallax.com/showthread.php/100380-More-GEAR-Improved-Emulation-of-the-Propeller" rel="nofollow">http://forums.parallax.com/showthread.php/100380-More-GEAR-Improved-Emulation-of-the-Propeller</a><br /><a rel="nofollow" href="/categories/propeller-1-multicore-microcontroller/feed.rss#">Attachment not found.</a><br />
  161. It has not been update in 4 years, until now. I found some bugs using  the counters in logic modes (CTRMODE=%1xxxx) emulation, and decide to  explore what was inside the hook of GEAR. Finally I made many changes  and bug fixes:<br /><br /><u><b> Version V14.07.03:</b></u>
  162. <ul><li>Faster emulation.</li>
  163. </ul><div>
  164. In  my own testing, GEAR runs now about 30% or 35% faster than Gear  V09_10_26, maybe because the executable now use MS .NET framework 4.0  instead of 2.0. The drawback is the need to download the framework, but  in windows 7 or 8, probably it is installed already.<br />
  165. Also, updated  the project files to MS Visual C# 2010 Express (the old proyect was in  MS Visual C# 2005). I use that because it was the only I could find.
  166. </div>
  167.  
  168. <ul><li>Show Cog RAM Special Purpose Registers values.</li>
  169. </ul><div>
  170. Now  the values of special registers in cog memory (between $1F0 - PAR and  $1FF - VSCL) are displayed correctly in memory or PASM view.
  171. </div>
  172.  
  173. <ul><li>Logic modes in counters.</li>
  174. </ul><div>
  175. Logic modes (CTRMODE between %10000 and %11111) didn't work well in past versions of Gear.
  176. </div>
  177.  
  178. <ul><li>Correction to enable PAR register changes.</li>
  179. </ul><div>
  180. As  there was some reports of prop forum users that GEAR was of not capable  to change the PAR cog register (forum thread "PASM simulator /  debugger?"  <a href="http://forums.parallax.com/showthread.php/115909-PASM-simulator-debugger" rel="nofollow">http://forums.parallax.com/showthread.php/115909-PASM-simulator-debugger</a>)  then I enabled it.  They claims that some parallax video drivers in  PASM changes the PAR register, and GEAR didn't emulate that. The  Propeller Manual V1.2 specify that is a read-only register, but if  parallax did that drivers that really run on the real one...
  181. </div>
  182.  
  183. <ul><li>Fixes in Logic View.</li>
  184. </ul><div>
  185. When  you reload a binary or reset it, and you had run it before using pins,  the logic view show a mix between new and old samples.<br />
  186. If you are  using windows in other languages than english, -with other number  formats-, the preset values for time frame and tick mark (with "."  decimal separator) will not work if you press the update button.
  187. </div>
  188.  
  189. <ul><li>Flickering correction on cog view over PASM lines.</li>
  190. </ul><div>
  191. When you were on cog view (PASM code), the tool tip text sometimes flickers.
  192. </div>
  193.  
  194. <ul><li>Tooltips over pins and locks in hub view.</li>
  195. </ul><div>
  196. Added  tooltips on hub view on pins and locks views (IN*, DIR*, Floating, Lock  Free, Locks), to identify easily which pin or lock is.
  197. </div>
  198.  
  199. <ul><li>Plugin editor enhancements.</li>
  200. </ul><div>
  201. Experimental  C# sintax highlighting of code. Now the name of the file is displayed  on the title of the window. Added tooltips to be more self explaining.
  202. </div>
  203. <br /><br /><b>GEAR emulator Attachment:</b>: [FILE]GEAR_V14_07_03.zip[/FILE]<br /><b>GEAR source code (MS Visual C# 2010 Express</b>): [FILE]gear-source-14.07.03.zip[/FILE]<br /><br /><u>Future ideas:</u>
  204. <ol><li>Improve C# sintax highlight on plugin editor (accurate &amp; faster).</li>
  205. <li>Modify  the file format for plugins (add version, description, usage, author,  etc) and show it on screen, keeping compatibility with older plugins.</li>
  206. <li>Better documentation of plugins.</li>
  207. <li>Documentation of C# sources (doxygen?).</li>
  208. </ol>
  209. Please fell free to test it, report bugs, and make comments.<br /><br />
  210. Enjoy better debugging with your propeller!<br /><br /><i>Gatuno.<br /></i><br />
  211. (Edit 2016-02-24): reattached files.]]>
  212.        </description>
  213.    </item>
  214.    <item>
  215.        <title>BNO08x IMU for the P1</title>
  216.        <link>https://forums.parallax.com/discussion/176230/bno08x-imu-for-the-p1</link>
  217.        <pubDate>Tue, 01 Jul 2025 21:40:41 +0000</pubDate>
  218.        <category>Propeller 1</category>
  219.        <dc:creator>JonnyMac</dc:creator>
  220.        <guid isPermaLink="false">176230@/discussions</guid>
  221.        <description><![CDATA[<p>Was telling my buddy Rick -- who builds lots of robots for Star Wars TV shows -- about the BNO08x IMU. He asked if it worked for the P1. I told him I'd convert it as an exercise. This does require a cog for the 115200 baud serial, but it works just like the P2 version.</p>
  222.  
  223. <p><img src="https://forums.parallax.com/uploads/editor/l2/lk80jad3jfzw.png" alt="" title="" /></p>
  224. ]]>
  225.        </description>
  226.    </item>
  227.    <item>
  228.        <title>dual stepper motors</title>
  229.        <link>https://forums.parallax.com/discussion/173757/dual-stepper-motors</link>
  230.        <pubDate>Thu, 02 Sep 2021 05:06:18 +0000</pubDate>
  231.        <category>Propeller 1</category>
  232.        <dc:creator>bbrien</dc:creator>
  233.        <guid isPermaLink="false">173757@/discussions</guid>
  234.        <description><![CDATA[<p>I have a small Mac-Cass telescope which I damaged by plugging into a power source which  was twice the rated voltage and it ate the processor. It uses two stepper motors in the drive system. The original system consisted of four pushbutton switches arranged as a compass , plus a switch controlling one of three speeds. I have a spare board with a Propeller Mini which will be using to run system.  There are two groups of inputs with a total of nine inputs and eight output pins. Six of the outputs will deliver high or low and two will output a frequency pulse. Four inputs will connect to a hand box, and another will connect to a guide camera and the last  will generate four different frequency pulses.  I have two different programs which I would like to combine into one program  .</p>
  235. ]]>
  236.        </description>
  237.    </item>
  238.    <item>
  239.        <title>spin code</title>
  240.        <link>https://forums.parallax.com/discussion/176219/spin-code</link>
  241.        <pubDate>Mon, 16 Jun 2025 19:34:24 +0000</pubDate>
  242.        <category>Propeller 1</category>
  243.        <dc:creator>captainruss</dc:creator>
  244.        <guid isPermaLink="false">176219@/discussions</guid>
  245.        <description><![CDATA[<p>What is needed as far as a programmer to install the program?</p>
  246. ]]>
  247.        </description>
  248.    </item>
  249.    <item>
  250.        <title>spin code</title>
  251.        <link>https://forums.parallax.com/discussion/176218/spin-code</link>
  252.        <pubDate>Mon, 16 Jun 2025 19:30:35 +0000</pubDate>
  253.        <category>Propeller 1</category>
  254.        <dc:creator>captainruss</dc:creator>
  255.        <guid isPermaLink="false">176218@/discussions</guid>
  256.        <description><![CDATA[<p>what ide is needed to program in spin code?</p>
  257. ]]>
  258.        </description>
  259.    </item>
  260.    <item>
  261.        <title>P8X32A Emulation on Tang20K FPGA</title>
  262.        <link>https://forums.parallax.com/discussion/175828/p8x32a-emulation-on-tang20k-fpga</link>
  263.        <pubDate>Tue, 23 Apr 2024 14:54:39 +0000</pubDate>
  264.        <category>Propeller 1</category>
  265.        <dc:creator>ti85</dc:creator>
  266.        <guid isPermaLink="false">175828@/discussions</guid>
  267.        <description><![CDATA[<p>I came across a newer, low-cost FPGA called the Tang20K. I'm wondering if anyone has experience with it and the feasibility of running P8X32A emulation on this platform. Parallax has provided the Verilog files, but I'm unfamiliar with Verilog or hardware coding in general.</p>
  268.  
  269. <p>My question is: what steps would be necessary to get the Propeller 1 running on the Tang20K (if possible at all)? I'm interested in pursuing this because I'd like to explore options for increasing the Propeller 1's processing power, such as expanding hub RAM or adding more cogs.</p>
  270. ]]>
  271.        </description>
  272.    </item>
  273.    <item>
  274.        <title>PST Font problem?... A work around for drawing a grid</title>
  275.        <link>https://forums.parallax.com/discussion/176207/pst-font-problem-a-work-around-for-drawing-a-grid</link>
  276.        <pubDate>Thu, 22 May 2025 15:49:06 +0000</pubDate>
  277.        <category>Propeller 1</category>
  278.        <dc:creator>R Baggett</dc:creator>
  279.        <guid isPermaLink="false">176207@/discussions</guid>
  280.        <description><![CDATA[<p>Hi,<br />
  281. I tried to get fancy and draw a grid with my Calibration routine. I set this string to be printed using Parallax Serial Terminal.</p>
  282.  
  283. <pre spellcheck="false" tabindex="0">DAT
  284. Menu    byte pst#CS,"                           4 channel calibration for 14 bits",13
  285.        byte "                  State",13
  286.        byte "       (G)nd hard",13
  287.        byte "       (P)wr Hard",13
  288.        byte "      (D)ischarge",13
  289.        byte "        (U)ut Pwr",13
  290.        byte "     Short J(O)ne",13
  291.        byte "     Short J(T)wo",13
  292.        byte "  Short J T(H)ree",13
  293.        byte "    Short J(F)our",13
  294.        byte 13
  295.        byte "       RawHi       RawLo       CalHi       CalLo       Raw         Scaled",13
  296.        byte "      ┌───────────┬───────────┬───────────┬───────────┬───────────┬────────────┐",13
  297.        byte "TPI(0)│           │           │           │           │           │            │",13
  298.        byte "      ├───────────┼───────────┼───────────┼───────────┼───────────┼────────────┤",13
  299.        byte "TPI(1)│           │           │           │           │           │            │",13
  300.        byte "      ├───────────┼───────────┼───────────┼───────────┼───────────┼────────────┤",13
  301.        byte "TPI(2)│           │           │           │           │           │            │",13
  302.        byte "      ├───────────┼───────────┼───────────┼───────────┼───────────┼────────────┤",13
  303.        byte "TPI(3)│           │           │           │           │           │            │",13
  304.        byte "      ├───────────┼───────────┼───────────┼───────────┼───────────┼────────────┤",13
  305.        byte " TP(C)│           │           │           │           │           │            │",13
  306.        byte "      ├───────────┼───────────┼───────────┼───────────┼───────────┼────────────┤",13
  307.        byte "TP(A)G│           │           │           │           │           │            │",13
  308.        byte "      └───────────┴───────────┴───────────┴───────────┴───────────┴────────────┘",13
  309.        byte "(M)y number:",0
  310. stops   byte         7,          19,         31,         43,         55,         67
  311. rows    byte 14,16,18,20,22,24
  312. StStop  byte 20
  313. StRows  byte 3,4,5,6,7,8,9,10
  314. </pre>
  315.  
  316. <p>But then it is displayed in PST like this:<br /><img src="https://forums.parallax.com/uploads/editor/5k/qs3p2g6pvnwy.png" alt="" title="" /><br />
  317. I don't see a way to ensure PST is using the Propeller font. <br />
  318. The font is installed and working.. The DAT section above displays properly in Propeller Tool and in notepad when Parallax font is selected.<br />
  319. What am I doing wrong?</p>
  320. ]]>
  321.        </description>
  322.    </item>
  323.    <item>
  324.        <title>Is there a Flip breakout board?</title>
  325.        <link>https://forums.parallax.com/discussion/176195/is-there-a-flip-breakout-board</link>
  326.        <pubDate>Wed, 07 May 2025 07:57:46 +0000</pubDate>
  327.        <category>Propeller 1</category>
  328.        <dc:creator>Jeff Haas</dc:creator>
  329.        <guid isPermaLink="false">176195@/discussions</guid>
  330.        <description><![CDATA[<p>Is there a Flip breakout board, similar to this one?</p>
  331.  
  332. <p><a href="https://www.amazon.com/HiLetgo-Expansion-Sensor-Arduino-Duemilanove/dp/B00OLBDXC6/" rel="nofollow">https://www.amazon.com/HiLetgo-Expansion-Sensor-Arduino-Duemilanove/dp/B00OLBDXC6/</a></p>
  333.  
  334. <p>Ideally with large capacitors for servos.</p>
  335. ]]>
  336.        </description>
  337.    </item>
  338.    <item>
  339.        <title>&quot;Vibe coding&quot; Spin with Gemini</title>
  340.        <link>https://forums.parallax.com/discussion/176189/vibe-coding-spin-with-gemini</link>
  341.        <pubDate>Fri, 25 Apr 2025 07:06:24 +0000</pubDate>
  342.        <category>Propeller 1</category>
  343.        <dc:creator>Jeff Haas</dc:creator>
  344.        <guid isPermaLink="false">176189@/discussions</guid>
  345.        <description><![CDATA[<p>I've been working with LLMs out there in my regular work, and since the Open House is coming, I thought it might be fun to try working with Spin and seeing what one of them can do.  Since Spin has been out a long time and the OBEX is up on GitHub, I figured that everything in it has been absorbed.  On the other hand, I've also found that projects not using common web languages run into all kinds of problems pretty quickly.</p>
  346.  
  347. <p>My demo idea was to use an ultrasonic distance sensor, and a strip of Neopixels.  The Neopixels start out all lit up, and as you move your hand closer to the sensor, they turn off - kind of a manually controlled bar graph.</p>
  348.  
  349. <p>First I tried Claude.  Ugh, it had a hard time getting Spin right.  Eventually it got late and I gave up.</p>
  350.  
  351. <p>A couple of nights later I tried Google's Gemini in Google AI Studio.  It also struggled, but was much better about understanding its errors and fixing them.  I started with having it read the ultrasonic sensor and display the distance.  It had to fix three bugs, like this one:</p>
  352.  
  353. <blockquote><div>
  354.  <p>Error: Expected a constant, unary operator, or "("<br />
  355.  On this line: US_PER_TICK = 1_000_000 / clkfreq</p>
  356. </div></blockquote>
  357.  
  358. <p>It did it pretty fast and then the code worked - the ultrasonic sensor shows the distance on the PST.</p>
  359.  
  360. <p>So it was onto the Neopixels.  It struggled with getting it right - until I gave it the current version of jm_ws2812b.spin from the Obex by pasting it into the chat.  Then it analyzed it and did a new version of the Neopixels, and got it right.</p>
  361.  
  362. <p>Finally I asked to combine the two:</p>
  363.  
  364. <blockquote><div>
  365.  <p>Use the Ultrasonic sensor to read the distance and light up the string of 8 Neopixel LEDs. The ultrasonic sensor should read a hand at 1 meter, and light up the entire string of Neopixels. As you move your hand closer to the ultrasonic sensor, the Neopixels follow it and turn off from the farthest point. So the effect is that the line of lit Neopixels gets shorter as you move your hand closer to the ultrasonic sensor.</p>
  366. </div></blockquote>
  367.  
  368. <p>And it got that right.</p>
  369.  
  370. <p>This is currently sitting on my desk and is fun to play with.  Anyone want me to bring it to the Open House?</p>
  371. ]]>
  372.        </description>
  373.    </item>
  374.    <item>
  375.        <title>Propeller Resource Index</title>
  376.        <link>https://forums.parallax.com/discussion/111166/propeller-resource-index</link>
  377.        <pubDate>Thu, 12 Mar 2009 19:09:09 +0000</pubDate>
  378.        <category>Propeller 1</category>
  379.        <dc:creator>Chris Savage</dc:creator>
  380.        <guid isPermaLink="false">111166@/discussions</guid>
  381.        <description><![CDATA[Greetings everyone! To consolidate sticky threads and keep things more neat and tidy we're going to have thissticky thread where links to all relevant/useful information can be located. To that end if you would like to see something added please follow up in this thread with your comments and/or suggestionsand wewill try to keep this information up to date.<br /><br /><b>Getting Started:</b><br /><br /><a href="http://forums.parallax.com/discussion/89958/propeller-education-kit-labs-tools-and-applications" rel="nofollow">Propeller Education Kit Labs, Tools, and Applications - Andy Lindsay</a><br />
  382. This is a collection of links to Propeller Education Kit labs and discussions.<br /><br /><a href="https://github.com/parallaxinc/propgcc" rel="nofollow">Propeller GCC<br /></a>This project is a GCC port for the <a href="http://www.parallax.com/propeller" rel="nofollow">Parallax Propeller P8x32a Microcontroller</a>.<br /><br /><a href="http://forums.parallax.com/discussion/87722/assembly-code-examples-for-the-beginner" rel="nofollow">Assembly Code Examples for the Beginner - Many contributors</a><br />
  383. A collection of various Propeller assembly code examples and routines.<br /><br /><a href="http://forums.parallax.com/discussion/96594/machine-language-tutorial" rel="nofollow">Machine Language Tutorial - deSilva</a><br />
  384. This link leads to a thread with a PDF file attachment.<br /><br /><a href="http://forums.parallax.com/showthread.php?t=125397" rel="nofollow">Propeller Questions &amp; Answers System<br /></a>A helpful online system with many questions and corresponding answers.<br /><br /><a href="http://www.parallax.com/tabid/766/Default.aspx" rel="nofollow">View Archived Parallax Propeller Webinars</a><br />
  385. This is a collection of video clips from previous Propeller Webinars covering many important topics.<br /><br /><a href="http://firstspin.tv/" rel="nofollow">First Spin - What do you get when you combine an experienced programmer, a self taught programmer, and someone with<b> zero</b> experience programming?  First Spin!</a><br />First Spin is meant for anyone interested in taking a closer look at how to program with the Propeller microcontroller in an <b>unusually easy-to-understand</b> podcast.  This podcast assumes you have extremely little to no experience coding and maybe even little prior interest.<br /><a href="http://tymkrs.tumblr.com/archive" rel="nofollow">http://tymkrs.tumblr.com/archive</a><br /><b>Documentation and Code:</b><br /><br /><a href="https://www.parallax.com/downloads/propeller-p8x32a-documentation" rel="nofollow">Propeller Manual, Propeller Datasheet, Propeller Diagrams, Schematics and Images</a><br />
  386. A comprehensive page with all the media for the Propeller product line.<br /><br /><a href="http://obex.parallax.com/" rel="nofollow">Propeller Object Exchange</a><br />
  387. The Propeller Object Exchange contains many source code objects for the Propeller microcontroller. They are created and submitted by Propeller customers as well as Parallax engineers for use by everyone in the community.<br /><br /><a href="https://www.parallax.com/download-family/propeller-p8x32a-application-notes" rel="nofollow">Propeller Application Notes</a><br />
  388. Get started programming the P8X32A Propeller Microcontroller with our user friendly application notes designed for professional projects and engineers in mind. Located under Downloads &amp; Documentation.<br /><br /><b>Videos:</b><br /><br /><a href="http://www.youtube.com/user/ParallaxInc" rel="nofollow"><img src="http://www.parallax.com/Portals/0/Resources/videos/YouTubeLogo.jpg" alt="YouTubeLogo.jpg" /></a><br />
  389. Our entire offering of videos can be found on our YouTube channel.<br /><br /><a href="http://www.parallax.com/tabid/536/Default.aspx" rel="nofollow">Parallax Video Library</a><br />
  390. A selection of videos featuring our robotics product line and a few videos of customer projects and experiments.<br /><br /><b>Tools:</b><br /><br /><a href="https://www.parallax.com/downloads/propeller-tool-software" rel="nofollow">Propeller Tool Software</a><br />
  391. Includes software, source code, USB driver and Propeller Manual V1.01<br /><br /><a href="https://www.parallax.com/downloads/parallax-serial-terminal" rel="nofollow">Parallax Serial Terminal (Included in Propeller Tool Software)</a><br />
  392. A handy tool for communication with serial-based microcontrollers such as the Propeller. This software is used extensively by the Propeller Education Kit Labs.<br /><br /><a href="http://www.parallax.com/Store/Microcontrollers/PropellerTools/tabid/143/txtSearch/ICCV/List/1/ProductID/546/Default.aspx?SortField=ProductName%2cProductName" rel="nofollow">ViewPort - Standard</a><br /><a href="http://www.parallax.com/Store/Microcontrollers/PropellerTools/tabid/143/txtSearch/ICCV/List/1/ProductID/545/Default.aspx?SortField=ProductName%2cProductName" rel="nofollow">ViewPort - Ultimate</a><br />
  393. ViewPort is the premier debugging environment for the Propeller. The tool combines an integrated debugger with powerful graphics that show you what's going on within the Propeller.<br /><br /><a href="http://forums.parallax.com/showthread.php?t=121946" rel="nofollow">PASD - Propeller Assembly Sourcecode Debugger</a><br />
  394. An Assembly Sourcecode Debugger,it can be very useful for Assembly freaks to find bugs, but also for beginners to learn Assembly. Like Kaio's POD (Propeller OnChip Debugger), the PASD runs an Assembly program on the Propeller chip in real time, it is not a simulator. You can test your code with all the connected hardware for input and output.<br /><br /><a href="http://david.zemon.name/PropWare" rel="nofollow">PropWare</a><br />
  395. C++ HAL (<b>H</b>ardware <b>A</b>bstraction <b>L</b>ayer) for PropGCC; Robust build system using CMake; Instructions for Eclipse and <a href="http://www.jetbrains.com/clion/" rel="nofollow">JetBrain's CLion</a>; Example projects; Doxygen documentation; Integrated <a href="http://learn.parallax.com/propeller-c-set-simpleide/update-your-learn-folder" rel="nofollow">Simple Library</a> and <a href="https://github.com/libpropeller/libpropeller" rel="nofollow">libpropeller</a><br /><br /><a href="http://omniacreator.com/" rel="nofollow">OmniaCreator</a><br />
  396. Cross platform, free, and open source C/C++ IDE for Makers that brings powerful code editing and data visualization capabilities to your fingertips.<br /><br /><a href="https://github.com/libpropeller/libpropeller" rel="nofollow">libpropeller</a><br />
  397. Open source collection of C++ Propeller GCC objects<br /><br /><a href="http://www.fnarfbargle.com/bst.html" rel="nofollow">bst- Brad Campbell</a><br />
  398. bst is a fairly complete Integrated Development Environment that aimsto be eventually comparable and compatible with the Parallax Propeller Tool. All tools available for Windows 32, Linux i386, Mac OS X and PowerPC.<br /><br />
  399. Propalyzer - Steve (jazzed)<br />
  400. [URL="<a href="https://forums.parallax.com/discussion/110762/propalyzer-distribution-new-update-1-0-1-4-available/p1][/URL]" rel="nofollow">https://forums.parallax.com/discussion/110762/propalyzer-distribution-new-update-1-0-1-4-available/p1][/URL]</a><br /><br />
  401. Provide a serial interface logic analyzer GUI for a Propeller running capture code.<br /><br /><b>Hardware Discussion (Forum Threads):</b><br /><a href="http://forums.parallax.com/showthread.php/149671-Current-list-of-Prop-boards-Parallax-and-3rd-Party?p=1203199&amp;viewfull=1#post1203199" rel="nofollow">Current list of Propeller Boards (Parallax and 3rd Party)</a><br /><a href="http://forums.parallax.com/showthread.php/146100-What-is-your-favorite-Propeller-board" rel="nofollow">What is your favorite Propeller Board?</a><br /><br /><b>Technical Considerations:</b><br /><br /><a href="http://forums.parallax.com/showthread.php?p=585920" rel="nofollow">How to safely interface a 5V signal to the Propeller</a><br /><br /><b>Extra:</b><br /><br /><a href="http://forums.parallax.com/showthread.php?t=108626" rel="nofollow">HYDRA Projects Master List<br /></a>A listing of projects using the HYDRA that have been posted to our forum<br /><br /><a href="http://forums.parallax.com/showthread.php?t=121390" rel="nofollow">2009/10 Propeller Design Contest Winners<br /></a>The winning projects of the 2009/10 Propeller Design Contest<br /><br /><a href="http://www.parallax.com/tabid/720/Default.aspx" rel="nofollow">2008 Propeller Design Contest Winners</a><br />
  402. Winning projects were based on originality, professionalism, appropriateness of the Propeller in the design and practicality/usefullness.<br /><br /><a href="http://forums.parallax.com/showthread.php?p=630275" rel="nofollow">Why the Propeller Works - Chip Gracey</a><br />
  403. Chip Gracey explains why you should feel comfortable using the Propeller chip in your designs.<br /><br /><a href="http://forums.parallax.com/showthread.php?p=575479" rel="nofollow">Propeller Tricks &amp; Traps - Phil Pilgrim</a><br />
  404. This is meant to be an unofficial, open-ended, never-to-be-finished compendium of hints and gotchas discovered while learning how to use and program the Propeller.<br /><br /><a href="http://forums.parallax.com/showthread.php?p=609066" rel="nofollow">Good Thread Index - Graham Stabler</a><br />
  405. A collection of useful links.<br /><br /><a href="http://forums.parallax.com/showthread.php?p=722100" rel="nofollow">Best of Propeller Applications - OBC</a><br />
  406. A project listintendedfor those whoare those interested in microcomputer design/hobby, demonstration of capability.<br /><br /><a href="http://robot.tmcp.com.au/buildingblock/guides.html#" rel="nofollow">Building Blocks to the Propeller Chip - Anthony Myatt</a><br /><br /><a href="http://forums.parallax.com/showthread.php?p=680258" rel="nofollow">Propeller FAQ</a>- Still in development<br />
  407. Two FAQ's that summarize the issues discussed and proposed solutions in this thread.<br /><br /><a href="http://forums.parallax.com/showthread.php?p=842885" rel="nofollow">CadSoft Eagle EDA Propeller Library</a><br />
  408. Forum post that haslibrary files that can be used with Cadsoft Eagle EDA software]]>
  409.        </description>
  410.    </item>
  411.    <item>
  412.        <title>What ascii values do these characters represent ?</title>
  413.        <link>https://forums.parallax.com/discussion/176181/what-ascii-values-do-these-characters-represent</link>
  414.        <pubDate>Mon, 14 Apr 2025 10:38:25 +0000</pubDate>
  415.        <category>Propeller 1</category>
  416.        <dc:creator>celtic3</dc:creator>
  417.        <guid isPermaLink="false">176181@/discussions</guid>
  418.        <description><![CDATA[<p>Having trouble trouble shooting my program as I can't figure out what values these represent in ASCII Table. The first 4 values are for variable lRegisterH which is a LONG, and the second is lRegisterL. The Character looking like a space imediatley after K is a square looking character the one next to it is a space character.<br />
  419. Ignore the () they are for showing what the vales are. <br />
  420. lRegisterH ( ªªþ) <br />
  421. lRegisterL  (K  þ)</p>
  422. ]]>
  423.        </description>
  424.    </item>
  425.    <item>
  426.        <title>My RTC clock set program seems to be corrupted</title>
  427.        <link>https://forums.parallax.com/discussion/176171/my-rtc-clock-set-program-seems-to-be-corrupted</link>
  428.        <pubDate>Sat, 29 Mar 2025 19:04:49 +0000</pubDate>
  429.        <category>Propeller 1</category>
  430.        <dc:creator>AGCB</dc:creator>
  431.        <guid isPermaLink="false">176171@/discussions</guid>
  432.        <description><![CDATA[<p>I been using DS3231 RTCs for a long time but now even after a lot of checking I can't seem to make the setting program work. It just wants to read out zeros after programming. Don't know if I accidentally changed something. I had a computer crash in January and been rewriting a lot of things. Help would be appreciated. It is using 5 volts!</p>
  433.  
  434. <pre spellcheck="false" tabindex="0">CON
  435.  
  436.  _clkmode = xtal1 + pll16x      '80 MHz system clock
  437.  _xinfreq = 5_000_000
  438.  
  439.  SCL = 28
  440.  SDA = 29
  441.  
  442.  RTC = %1101000
  443.  
  444.  
  445.  
  446.  
  447. 'Timbuf address registers
  448. Seconds = 0
  449. Minutes = 1
  450. Hours   = 2
  451. Day     = 3
  452. Date    = 4
  453. Month   = 5
  454. Year    = 6
  455.  
  456. 'Useful assignments
  457.  
  458. Sunday    = $01
  459. Monday    = $02
  460. Tuesday   = $03
  461. Wednesday = $04
  462. Thursday  = $05
  463. Friday    = $06
  464. Saturday  = $07
  465.  
  466. January   = $01
  467. February  = $02
  468. March     = $03
  469. April     = $04
  470. May       = $05
  471. June      = $06
  472. July      = $07
  473. August    = $08
  474. September = $09
  475. October   = $10
  476. November  = $11
  477. December  = $12
  478.  
  479. OBJ
  480.  
  481.   PST  :   "Parallax Serial Terminal.spin"
  482.   i2c  :   "I2C SPIN driver v1.4od"
  483. VAR
  484.  byte  Timbuf[7]
  485.  byte answer
  486.  
  487. PUB  init
  488.  
  489. '  rtc.startx(sclpin, sdapin)      'startx(sclpin, sdapin)
  490.  PST.start(115_200)
  491.  waitcnt(clkfreq * 3 + cnt)
  492.  
  493.  I2C.init(SCL,SDA)
  494.  
  495.  
  496.    PST.clear
  497.    PST.str(string("Enter 'y' before 3 seconds if you want to set clock:"))
  498.    answer := PST.CharIn
  499.    if answer == "y"
  500.      Settime
  501.    PST.clear  'clear screen          ?????????
  502.    waitcnt(clkfreq / 100 + cnt)
  503.    time
  504. PUB  settime | Idx, t, n      'probably don't need Idx or t
  505.  
  506.  
  507.  PST.clear     'clear screen
  508.  
  509.  n:= 0
  510.  PST.str(string("Enter year (00-99): "))
  511.  repeat until n == $0D
  512.    n := PST.CharIn
  513.    if n =&gt; "0" and n =&lt; "9"
  514.      Timbuf[year] := Timbuf[year] &lt;&lt; 4 + (n - "0")
  515.  
  516.  
  517.  n := 0
  518.  PST.str(string("Enter month (01-12): "))
  519.  repeat until n == $0D
  520.    n := PST.CharIn
  521.    if n =&gt; "0" and n =&lt; "9"
  522.      Timbuf[month] := Timbuf[month] &lt;&lt; 4 + (n - "0")
  523.  
  524.  n := 0
  525.  PST.str(string("Enter date (01-31): "))
  526.  repeat until n == $0D
  527.    n := PST.CharIn
  528.    if n =&gt; "0" and n =&lt; "9"
  529.      Timbuf[date] := Timbuf[date] &lt;&lt; 4 + (n - "0")
  530.  
  531.  n:= 0
  532.  PST.str(string("Enter hour (01-12) for 12 hr or (01- 23) for 24 hr): "))
  533.  repeat until n == $0D
  534.    n := PST.CharIn
  535.    if n =&gt; "0" and n =&lt; "9"
  536.      Timbuf[hours] := (Timbuf[hours] &lt;&lt; 4 + (n - "0"))
  537.  
  538.  
  539.  PST.str(string("if 12 hour clock desired, press 'y' before 3 seconds:"))
  540.                            'IF NOT PRESS ENTER
  541.    answer := PST.CharIn
  542.    if answer == "y"
  543.      twelve_hour
  544.    Else
  545.      PST.newLine
  546.  
  547.  PST.str(string("if PM, press 'y' before 3 seconds:"))
  548. '                                 'IF NOT PRESS ENTER
  549.    answer := PST.CharIn
  550.    if answer == "y"
  551.      afternoon
  552.    Else
  553.      PST.newLine
  554.  
  555.  n:= 0
  556.  PST.str(string("Enter minutes (00-59): "))
  557.  repeat until n == $0D
  558.    n := PST.CharIn
  559.    if n =&gt; "0" and n =&lt; "9"
  560.      Timbuf[minutes] := Timbuf[minutes] &lt;&lt; 4 + (n - "0")
  561.  
  562.  n:= 0
  563.  PST.str(string("Enter seconds (00-59): "))
  564.  repeat until n == $0D
  565.    n := PST.CharIn
  566.    if n =&gt; "0" and n =&lt; "9"
  567.      Timbuf[seconds] := Timbuf[seconds] &lt;&lt; 4 + (n - "0")
  568.  
  569.  n := 0
  570.  PST.str(string("Enter Day of Week. Sun=01,M=02,T=03,W=04,TH=05,F=06,Sat=07 : "))
  571.  repeat until n == $0D
  572.    n := PST.CharIn
  573.    if n =&gt; "0" and n =&lt; "9"
  574.      Timbuf[Day] := Timbuf[Day] &lt;&lt; 4 + (n - "0")
  575.  
  576.  
  577.  
  578.  Timbuf := I2C.writebytes(RTC,Seconds,@Timbuf[seconds],7) '(device,address,dataAddress,bytes)
  579. ' PST.bin(timbuf,16)
  580.  waitcnt(clkfreq/2+cnt)
  581.  
  582.  
  583. PUB  time
  584.  
  585.  Repeat
  586.    waitcnt(clkfreq/2+cnt)
  587.    PST.clear    'clear screen
  588.    I2C.readbytes(RTC,0,@Timbuf,7) '(device,address,dataAddress,bytes)
  589.    PST.str(lookup(Timbuf[Day]:string("Sunday"),string("Monday"),string("Tuesday"),string("Wednesday"),string("Thursday"),string("Friday"),string("Saturday")))
  590.    PST.str(string(" "))
  591.    if Timbuf[Month] =&gt; $10
  592.      Timbuf[month] -= $06
  593.    PST.str(lookup(Timbuf[Month]:string("January"),string("February"),string("March"),string("April"),string("May"),string("June"),string("July"),string("August"),string("September"),string("October"),string("November"),string("December")))
  594.    PST.str(string(" "))
  595.    PST.hex(Timbuf[Date],2)
  596.    PST.str (string(", "))
  597.    PST.hex($2000 + (Timbuf[year]),4)
  598.    PST.str(string(" "))
  599.    if Timbuf[hours] &amp; %0100_0000   'is true (ie not 0)         'if set for  12-hour time
  600.      PST.hex(Timbuf[hours] &amp; %0001_1111,2)
  601.      PST.str(string(":"))
  602.      PST.hex(Timbuf[minutes],2)
  603.      PST.str(string(":"))
  604.      PST.hex(Timbuf[seconds],2)
  605.      PST.str(string(" "))
  606.      if Timbuf[hours] &amp; %0010_0000
  607.        PST.str(string("pm"))
  608.      else
  609.        PST.str(string("am"))
  610.    else     'if set for 23-hour time
  611.      PST.hex(Timbuf[hours] &amp; %0011_1111,2)
  612.      PST.str(string(":"))
  613.      PST.hex(Timbuf[minutes],2)
  614.      PST.str(string(":"))
  615.      PST.hex(Timbuf[seconds],2)
  616.  
  617. PUB  twelve_hour
  618.  Timbuf[hours] += $40    'for 12 hour clock
  619.  
  620. PUB  afternoon
  621.  Timbuf[hours] += $20      'for PM
  622.  
  623. {
  624. PRI Prompt(msg, CR)
  625.  PST.str(msg)
  626.  if CR
  627.    PSTclear
  628. }
  629. </pre>
  630. ]]>
  631.        </description>
  632.    </item>
  633.    <item>
  634.        <title>Propeller Activity Board WX</title>
  635.        <link>https://forums.parallax.com/discussion/176172/propeller-activity-board-wx</link>
  636.        <pubDate>Wed, 02 Apr 2025 07:25:47 +0000</pubDate>
  637.        <category>Propeller 1</category>
  638.        <dc:creator>Tapperman</dc:creator>
  639.        <guid isPermaLink="false">176172@/discussions</guid>
  640.        <description><![CDATA[<p>I’m back.   After a few years, things sure have changed.  I purchased an Activity board WX.  And I can’t find any examples of how to use the A/D or D/A.  No chip numbers … nothing.</p>
  641.  
  642. <p>Any help would be appreciated.</p>
  643.  
  644. <p>… Tim</p>
  645. ]]>
  646.        </description>
  647.    </item>
  648.    <item>
  649.        <title>P1 giveaway (continental USA only)</title>
  650.        <link>https://forums.parallax.com/discussion/176163/p1-giveaway-continental-usa-only</link>
  651.        <pubDate>Sat, 22 Mar 2025 22:00:45 +0000</pubDate>
  652.        <category>Propeller 1</category>
  653.        <dc:creator>octetta</dc:creator>
  654.        <guid isPermaLink="false">176163@/discussions</guid>
  655.        <description><![CDATA[<p>I have a Propeller manual + a C3 board + a Hydra manual for the first person who asks for them.<br />
  656. Want to keep old but good stuff out of the landfill.</p>
  657. ]]>
  658.        </description>
  659.    </item>
  660.    <item>
  661.        <title>Better code in spin 1</title>
  662.        <link>https://forums.parallax.com/discussion/176161/better-code-in-spin-1</link>
  663.        <pubDate>Wed, 19 Mar 2025 18:30:34 +0000</pubDate>
  664.        <category>Propeller 1</category>
  665.        <dc:creator>AGCB</dc:creator>
  666.        <guid isPermaLink="false">176161@/discussions</guid>
  667.        <description><![CDATA[<p>There must be a shorter way to write something like this. Help! Thanks Aaron</p>
  668.  
  669. <pre spellcheck="false" tabindex="0">IFNOT  secs//15
  670.      ReadRTC
  671.    ELSEIFNOT secs//30      'read RTC 4 times per minute
  672.      ReadRTC
  673.      UpdateTemps            'UpdateTemps once per minute
  674.    ELSEIFNOT secs//45
  675.      ReadRTC
  676.    ELSEIFNOT secs//58
  677.      ReadRTC
  678.    ELSEIFNOT secs//75
  679.      ReadRTC
  680.    ELSEIFNOT secs//90
  681.      ReadRTC
  682.      UpdateTemps
  683.    ELSEIFNOT secs//105
  684.      ReadRTC
  685.    ELSEIFNOT secs//120
  686.      ReadRTC
  687.    ELSEIFNOT secs//135
  688.      ReadRTC
  689.    ELSEIFNOT secs//150
  690. </pre>
  691. ]]>
  692.        </description>
  693.    </item>
  694.    <item>
  695.        <title>Fastest one-way inter-Propeller transfer rate with 8 data lines</title>
  696.        <link>https://forums.parallax.com/discussion/176129/fastest-one-way-inter-propeller-transfer-rate-with-8-data-lines</link>
  697.        <pubDate>Tue, 18 Feb 2025 07:44:10 +0000</pubDate>
  698.        <category>Propeller 1</category>
  699.        <dc:creator>escher</dc:creator>
  700.        <guid isPermaLink="false">176129@/discussions</guid>
  701.        <description><![CDATA[<p>Hello all, here are the facts:</p>
  702.  
  703. <p>I have a 0.5965 ms window in which to transfer 10,368 bytes via 8 data lines directly from one Propeller to another, both running on 104 MHz system clocks (9.6153 ms/cycle).</p>
  704.  
  705. <p>I wrote some code which does a basic bit banging routine (rdlong, mov outa, ror, mov outa,..., rdlong, etc.) that took 76 cycles per long, but that's almost 4x too slow, taking ~1.9 ms to transfer the entire payload.</p>
  706.  
  707. <p>Push comes to shove I can make the transfer window as wide as 0.9143 ms, but no longer. I'd much rather find a novel way to achieve my goals in software, potentially by using a phsa/phsb clock trick.</p>
  708.  
  709. <p>Any help would be greatly appreciated!</p>
  710. ]]>
  711.        </description>
  712.    </item>
  713.    <item>
  714.        <title>use high alarm with DS18B20</title>
  715.        <link>https://forums.parallax.com/discussion/176140/use-high-alarm-with-ds18b20</link>
  716.        <pubDate>Fri, 28 Feb 2025 14:13:12 +0000</pubDate>
  717.        <category>Propeller 1</category>
  718.        <dc:creator>AGCB</dc:creator>
  719.        <guid isPermaLink="false">176140@/discussions</guid>
  720.        <description><![CDATA[<p>Trying to figure out how to sound an alarm if temp is above  TH.</p>
  721.  
  722. <p>Probably need help<br />
  723. Aaron</p>
  724. ]]>
  725.        </description>
  726.    </item>
  727.    <item>
  728.        <title>Programming a propeller I with a raspberry pi pico</title>
  729.        <link>https://forums.parallax.com/discussion/176120/programming-a-propeller-i-with-a-raspberry-pi-pico</link>
  730.        <pubDate>Mon, 10 Feb 2025 16:56:19 +0000</pubDate>
  731.        <category>Propeller 1</category>
  732.        <dc:creator>ti85</dc:creator>
  733.        <guid isPermaLink="false">176120@/discussions</guid>
  734.        <description><![CDATA[<p>Is there a way to program a Propeller I microcontroller with a Raspberry Pi Pico instead of the more expensive Prop Plug?  Since both devices operate at 3.3V, and the Pico should be capable of emulating the Propeller's communication protocol, it seems like this could be a valuable, less expensive alternative.</p>
  735. ]]>
  736.        </description>
  737.    </item>
  738.    <item>
  739.        <title>No Propeller found on any serial port, using Propeller Proto Board</title>
  740.        <link>https://forums.parallax.com/discussion/176092/no-propeller-found-on-any-serial-port-using-propeller-proto-board</link>
  741.        <pubDate>Tue, 21 Jan 2025 18:51:11 +0000</pubDate>
  742.        <category>Propeller 1</category>
  743.        <dc:creator>Rob v.d. berg</dc:creator>
  744.        <guid isPermaLink="false">176092@/discussions</guid>
  745.        <description><![CDATA[<p>Hi,  years i use for simple testing a Propeller Proto Board. <br />
  746. Suddenly, from one day to the next, i had a problem finding the propeller (p1).</p>
  747.  
  748. <p>The power on the board is ok, 5volt and 3,3volt. Nothing has changed! <br />
  749. The Prop plug works good on other systems! Is the Propeller dead?, are there components to check?</p>
  750. ]]>
  751.        </description>
  752.    </item>
  753.    <item>
  754.        <title>WX ESP8266D on Propeller Activity Board (32910)</title>
  755.        <link>https://forums.parallax.com/discussion/176089/wx-esp8266d-on-propeller-activity-board-32910</link>
  756.        <pubDate>Thu, 09 Jan 2025 20:40:55 +0000</pubDate>
  757.        <category>Propeller 1</category>
  758.        <dc:creator>deanthorne</dc:creator>
  759.        <guid isPermaLink="false">176089@/discussions</guid>
  760.        <description><![CDATA[<p>Hello All<br />
  761. I'm working on a little project as have resurrected an older Activity Board<br />
  762. I want to use the WiFi module for OTA programming and simple data display.</p>
  763.  
  764. <p>I know (or at least seem to recall) on these older boards there was a need to 'jumper' the XBee DO &amp; DI Pins to some pins on the Propeller.  Believe it was Pin 7 (DI) &amp; 8 (DO), but that isn't it.  Can someone point me to the old documents for the 32910 (if they still exist.</p>
  765.  
  766. <p>Thx</p>
  767. ]]>
  768.        </description>
  769.    </item>
  770.    <item>
  771.        <title>PULSIN_uS(PIN, State) / timeout</title>
  772.        <link>https://forums.parallax.com/discussion/176085/pulsin-us-pin-state-timeout</link>
  773.        <pubDate>Sat, 04 Jan 2025 15:40:10 +0000</pubDate>
  774.        <category>Propeller 1</category>
  775.        <dc:creator>Rob v.d. berg</dc:creator>
  776.        <guid isPermaLink="false">176085@/discussions</guid>
  777.        <description><![CDATA[<p>Hi, i often use the BS2_functions.  One that is very easy for RC projects is the PULSIN_uS and used PULSIN_Clk.  But when my transmitter is still off (no puls), the program who reads the puls, is not running any more.  The function waitpeq(|&lt; Pin, |&lt; Pin, 0)  in PULSIN_Clk  is waiting ....... for a RC puls.</p>
  778.  
  779. <p>Is it possible the build a time out there, so when there is no puls after timeout of say 2msec, then the puls width is 0msec. I'm not an expert in the special functions like waitpeq.</p>
  780.  
  781. <p>what means (in PULSIN_Clk):  Note: Absence of pulse can cause cog lockup if watchdog is not used - See distributed example</p>
  782.  
  783. <p>** here the functions *******************************************************<br />
  784. PUB PULSIN_uS (Pin, State) : Duration | ClkStart, clkStop, timeout<br />
  785. {{<br />
  786.  Reads duration of Pulse on pin defined for state, returns duration in 1uS resolution<br />
  787.  Note: Absence of pulse can cause cog lockup if watchdog is not used - See distributed example<br />
  788.    x := BS2.Pulsin_uS(5,1)<br />
  789.    BS2.Debug_Dec(x)<br />
  790. }}</p>
  791.  
  792. <p>Duration := PULSIN_Clk(Pin, State) / us + 1             ' Use PulsinClk and calc for 1uS increments</p>
  793.  
  794. <p>PUB PULSIN_Clk(Pin, State) : Duration <br />
  795. {{ special versi from Travis<br />
  796.  Reads duration of Pulse on pin defined for state, returns duration in 1/clkFreq increments - 12.5nS at 80MHz<br />
  797.  Note: Absence of pulse can cause cog lockup if watchdog is not used - See distributed example<br />
  798.    x := BS2.Pulsin_Clk(5,1)<br />
  799.    BS2.Debug_Dec(x)<br />
  800. }}</p>
  801.  
  802. <p>DIRA[pin]~<br />
  803.  ctra := 0<br />
  804.  if state == 1<br />
  805.    ctra := (%11010 &lt;&lt; 26 ) | (%001 &lt;&lt; 23) | (0 &lt;&lt; 9) | (PIN) ' set up counter, A level count<br />
  806.  else<br />
  807.    ctra := (%10101 &lt;&lt; 26 ) | (%001 &lt;&lt; 23) | (0 &lt;&lt; 9) | (PIN) ' set up counter, !A level count<br />
  808.  frqa := 1<br />
  809.  waitpne(|&lt; Pin, |&lt; Pin, 0)                         ' Wait for opposite state ready<br />
  810.  phsa:=0                                            ' Clear count<br />
  811.  waitpeq(|&lt; Pin, |&lt; Pin, 0)                         ' wait for pulse<br />
  812.  waitpne(|&lt; Pin, |&lt; Pin, 0)                         ' Wait for pulse to end<br />
  813.  Duration := phsa                                   ' Return duration as counts<br />
  814.  ctra :=0</p>
  815. ]]>
  816.        </description>
  817.    </item>
  818.    <item>
  819.        <title>Propeller emulator</title>
  820.        <link>https://forums.parallax.com/discussion/128698/propeller-emulator</link>
  821.        <pubDate>Wed, 12 Jan 2011 08:36:19 +0000</pubDate>
  822.        <category>Propeller 1</category>
  823.        <dc:creator>Alex.Stanfield</dc:creator>
  824.        <guid isPermaLink="false">128698@/discussions</guid>
  825.        <description><![CDATA[Hi There, in looking for a propeller emulator I found GEAR and pPropellerSim. I'd like a vote for which are the pros and cons of them (or any other simulator not a debugger since I need to do some work without having any HW around)<br /><br />
  826. Also I couldn't find any docs on GEAR, can someone post a pointer (or the docs)<br /><br />
  827. Best regards and thansk in advance<br />
  828. Alex]]>
  829.        </description>
  830.    </item>
  831.    <item>
  832.        <title>What you can do with the Flip Holiday Light Kit</title>
  833.        <link>https://forums.parallax.com/discussion/176068/what-you-can-do-with-the-flip-holiday-light-kit</link>
  834.        <pubDate>Thu, 19 Dec 2024 07:55:38 +0000</pubDate>
  835.        <category>Propeller 1</category>
  836.        <dc:creator>ke4pjw</dc:creator>
  837.        <guid isPermaLink="false">176068@/discussions</guid>
  838.        <description><![CDATA[<p>@"Ken Gracey" I just couldn't resist. This is a fun little bundle you put together and it needed some xLights action.</p>
  839.  
  840. <p><span data-youtube="youtube-b23IllQRl0U?autoplay=1"><a rel="nofollow" href="https://www.youtube.com/watch?v=b23IllQRl0U"><img src="https://img.youtube.com/vi/b23IllQRl0U/0.jpg" width="640" height="385" border="0" alt="image" /></a></span></p>
  841.  
  842. <p>I will try and drop some code with a tutorial this weekend.</p>
  843. ]]>
  844.        </description>
  845.    </item>
  846.   </channel>
  847. </rss>
  848.  

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=https%3A//forums.parallax.com/categories/propeller-1-multicore-microcontroller/feed.rss

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda