My forum links are archived here for follow up reference.
Prop LU via Indexed Methods
http://forums.parallax.com/showthread.php?142348-A-quot-Gem-quot-found-in-the-Prop-Q-amp-A
And here, Prop Load Average
http://forums.parallax.com/showthread.php?142379-SPIN-Task-Switching-for-us-Prop-Noobies
--
Showing posts with label Prop-UI. Show all posts
Showing posts with label Prop-UI. Show all posts
Tuesday, September 11, 2012
Sunday, June 10, 2012
Prop UI Progress
It has been a grueling 18 days since my last post. The Propeller UI Board that I have been working on has provided some real challenges. All of the UI Board peripherals on wired to the same I2C Bus. Which means my standard method of debugging the code via a working a Display was not available. The Bus Pirate and a new VGA Display was necessary, which had to be configured which added to a already steep learning curve.
Coordinating and developing the Objects for the six UI peripheral was a challenge The task was a little easier thanks to Jeff - KO7M, who helped with the I2C Bus to Parallel Expander Code, and the necessary modification to his I2C LCD Driver.
Currently ALL six UI peripherals, which are on the same I2C Bus, are working in concert with each other without perceivable delays for; the two Rotary Encoders, four Push Buttons, eight LEDs, a Realtime Clock (RTC), and the LCD Display. Also there are the Sound (beeper) and the three I2C POTs that control the LCD Backlight Brightness, LCD Contrast, and Sound Volume - all working seamlessly together.
One of the Software Driver Goals is make moving the Programmed Display from LCD to VGA (and back) without difficultly, other than the obvious which are the Number of Lines and Number of Characters Per Line.
Note: my new I2C Huff-n-Puff board (see previous blog) will also be added to that same I2C Bus (external to the UI).
I had to learn a few new Propeller SPIN tricks to make it all work. Specifically how to coordinate and use "Locks" for Objects and COGs.
Only a few modifications were necessary to the UI PCB. I have already started the re-design with modifications for the next PCB. I will be adding more Pull-ups, and 0-Ohm Jumpers to make separation of circuits easier for future development and debugging.
I have several ideas and better organization of the current code, but that will wait for another day.
It has been a lot of fun. Now on to some projects that will use the Prop UI Board.
First, on the list to port are; my QRSS and WSPR Beacons, Jeff's Keyer, the Huff-n-Puff Freq Standard, and several other Prop Projects that are planned to use the new UI.
--
 |
| UI Board Installed on the Prop ProtoBoard |
Currently ALL six UI peripherals, which are on the same I2C Bus, are working in concert with each other without perceivable delays for; the two Rotary Encoders, four Push Buttons, eight LEDs, a Realtime Clock (RTC), and the LCD Display. Also there are the Sound (beeper) and the three I2C POTs that control the LCD Backlight Brightness, LCD Contrast, and Sound Volume - all working seamlessly together.
One of the Software Driver Goals is make moving the Programmed Display from LCD to VGA (and back) without difficultly, other than the obvious which are the Number of Lines and Number of Characters Per Line.
Note: my new I2C Huff-n-Puff board (see previous blog) will also be added to that same I2C Bus (external to the UI).
I had to learn a few new Propeller SPIN tricks to make it all work. Specifically how to coordinate and use "Locks" for Objects and COGs.
Only a few modifications were necessary to the UI PCB. I have already started the re-design with modifications for the next PCB. I will be adding more Pull-ups, and 0-Ohm Jumpers to make separation of circuits easier for future development and debugging.
I have several ideas and better organization of the current code, but that will wait for another day.
It has been a lot of fun. Now on to some projects that will use the Prop UI Board.
First, on the list to port are; my QRSS and WSPR Beacons, Jeff's Keyer, the Huff-n-Puff Freq Standard, and several other Prop Projects that are planned to use the new UI.
--
Friday, May 25, 2012
UI Project Update
Readers of this blog know that I have a Propeller UI Project in progress. The custom board that I created for that has been received and loaded with parts. Some simple parts of the board appear to function as can be seen, tested, and exercised with a clip on Bus Pirate. That is, the Real Time Clock (RTC) and the LED driver seem to work as expected.
The major elements of the board; which include the LCD Display and Knobs, have NOT been tested yet. Their control is complex enough that it will be necessary to tested them in conjunction with the Propeller processor. The eight interface wires for the connector have been installed on the Prop board.
Normally testing a new peripheral device is not difficult, but when the test and debugging involves the Display, which is used to Display the test results, it is problematic. It is a classic "Chicken and the Egg" problem.
To solve this dilemma, I am waiting for an ordered KVM connector for the Propeller (which should be here today). The KVM connector will allow the Prop to be connected to a dedicated VGA Monitor for display of debug information without the need of the LCD or Knobs.
Actually, I have been a little lax here, I could have used the USB TTY connection to do debug and testing, but in my Ubuntu Workstation environment using a single interface path for both; Prop Programming, and Displaying debug information, is a pain. Therefore I have been waiting for the KVM. And, I have also been diverted off to other projects and responsibilities.
My goal is to have UI working for Show-n-Tell at the next pQRP P&C meeting.
--
The major elements of the board; which include the LCD Display and Knobs, have NOT been tested yet. Their control is complex enough that it will be necessary to tested them in conjunction with the Propeller processor. The eight interface wires for the connector have been installed on the Prop board.
Normally testing a new peripheral device is not difficult, but when the test and debugging involves the Display, which is used to Display the test results, it is problematic. It is a classic "Chicken and the Egg" problem.
To solve this dilemma, I am waiting for an ordered KVM connector for the Propeller (which should be here today). The KVM connector will allow the Prop to be connected to a dedicated VGA Monitor for display of debug information without the need of the LCD or Knobs.
Actually, I have been a little lax here, I could have used the USB TTY connection to do debug and testing, but in my Ubuntu Workstation environment using a single interface path for both; Prop Programming, and Displaying debug information, is a pain. Therefore I have been waiting for the KVM. And, I have also been diverted off to other projects and responsibilities.
My goal is to have UI working for Show-n-Tell at the next pQRP P&C meeting.
--
Friday, May 11, 2012
Parts Received and some Shop Work
I received parts from Mouser to complete the Propeller User Interface (UI). I was missing two I2C I/O Expanders and 3.3V Regulators (see previous post).
So far, I have been using the BusPirate to test the four devices on the I2C circuit, the LEDs and the Real Time Clock (RTC) works as expected.
The LCD and the Knobs which are on one of the I/O Expanders will require some new wiring on a new Propeller USB Protoboard that I plan to use. Software is about the only way to do real tests here.
The one part that I can not get to work is the I2C POT, which will control the Backlight and sound volumn, the POTs are not necessary to do the initial checkout. And, maybe I just have not found the magic that makes it work.
More testing needed.
A Day of Shop Work
While looking for my photos of the UI build progress, I found some photos that I had taken a few days ago. I helped my Son cut-out some parts using my PlasmaCAM. It was a long day, we cut about 96 square feet of parts out of 3/16 inch sheet steal. It is a fun process to watch.
When working correctly, the PlamaCAM creates a lot of dark smoke, which tends to collect on everything (nasty stuff). I was wondering what the smoke actually is? The only ingredients in the process are "Electrons, Air and Steel". Although, at 10K degrees, almost anything could be being created.
I took some of the Smoke (black dust like stuff) that had settled on a surface, to my Lab where I could look at it under the Microscope at 30X. The smoke dust looks like very small, perfectly formed, black spheres (like ball barrings). They seem to be magnetic.
Later, I discovered they are very thin hollow spheres! Smashing a single sphere releases something that effect others in close proximity. Maybe they contain compressed gas, or maybe they release an electric charge, or collapsing magnetic field.
More investigation needed.
--
 |
| The Two New Parts |
The LCD and the Knobs which are on one of the I/O Expanders will require some new wiring on a new Propeller USB Protoboard that I plan to use. Software is about the only way to do real tests here.
The one part that I can not get to work is the I2C POT, which will control the Backlight and sound volumn, the POTs are not necessary to do the initial checkout. And, maybe I just have not found the magic that makes it work.
More testing needed.
A Day of Shop Work
 |
| Parts being Cut |
When working correctly, the PlamaCAM creates a lot of dark smoke, which tends to collect on everything (nasty stuff). I was wondering what the smoke actually is? The only ingredients in the process are "Electrons, Air and Steel". Although, at 10K degrees, almost anything could be being created.
 |
| Lots of Sparks and Smoke (more smoke, less sparks, makes for cleaner/better cuts) |
Later, I discovered they are very thin hollow spheres! Smashing a single sphere releases something that effect others in close proximity. Maybe they contain compressed gas, or maybe they release an electric charge, or collapsing magnetic field.
More investigation needed.
--
Friday, May 4, 2012
Murphy - My Consultant
Murphy and Assumptions as Consultants - will make projects more difficult.
Several weeks ago, I started designing a generic User Interface (UI) for my Propeller Microprocessor Projects (see previous post). The UI was planned to be an adaption of circuits that I am already using with current project (see previous post). The new adaptions included I2C Converters and stand-alone on-board 3.3V Regulator.
The UI board layout was sent for Manufacture on May 14 and was just received a few days ago. I was anxious to load a board with parts. My initial strategy was to load a board with as few parts as necessary to do some initial tests. But once I started loading, I decided to load all of the parts, starting with simple resistors and capacitors (what could go wrong? :-). Prior to installing the Major Expensive Components, I checked the LED circuits and did some simple resistant test - ALL looked good.
Then, In steps Murphy and Assumptions:
When I went to my parts storage bins for the 3.3V regulator, I could not find a SOT-89 3.3V regulator (similar to my often used L78L05 5V SOT-89 regulator). Maybe I have never had one, or maybe they do not exists with the foot print I used in the layout. But my board, as designed, defiantly needs one. When I laid out the board, I assumed they were in the bin. Now I will need to check availability and order something that will work.
When I went to my parts storage bins for the MCP23017 Dual I2C I/O Expander (16 pins of GPIO), I could not find them. I know they exist, and I thought I had order several, but I could not find them. My board as designed needs two. For this design and layout, I decided to use the Dual I2C I/O Expanders (similar to the previous used single expanders). They require less space for the available output pins, and they require one less device address on the I2C bus. So, now I need to order even more parts, to finish the build.
Most of the parts are installed, on the new UI board and is ready to test, but now must wait for the last few parts to be ordered - Thanks Murphy and Assumptions !
This iteration of the UI board was never planed to be the final form, it was just a functional test. I knew some modification maybe necessary. But that is the way it is, when building without breadboarding first.
UPDATE
I found the SOT-89 3.3Volt Regulators at Mouser, and they will be on order soon, along with a few other parts.
-
Several weeks ago, I started designing a generic User Interface (UI) for my Propeller Microprocessor Projects (see previous post). The UI was planned to be an adaption of circuits that I am already using with current project (see previous post). The new adaptions included I2C Converters and stand-alone on-board 3.3V Regulator.
The UI board layout was sent for Manufacture on May 14 and was just received a few days ago. I was anxious to load a board with parts. My initial strategy was to load a board with as few parts as necessary to do some initial tests. But once I started loading, I decided to load all of the parts, starting with simple resistors and capacitors (what could go wrong? :-). Prior to installing the Major Expensive Components, I checked the LED circuits and did some simple resistant test - ALL looked good.
Then, In steps Murphy and Assumptions:
When I went to my parts storage bins for the 3.3V regulator, I could not find a SOT-89 3.3V regulator (similar to my often used L78L05 5V SOT-89 regulator). Maybe I have never had one, or maybe they do not exists with the foot print I used in the layout. But my board, as designed, defiantly needs one. When I laid out the board, I assumed they were in the bin. Now I will need to check availability and order something that will work.
When I went to my parts storage bins for the MCP23017 Dual I2C I/O Expander (16 pins of GPIO), I could not find them. I know they exist, and I thought I had order several, but I could not find them. My board as designed needs two. For this design and layout, I decided to use the Dual I2C I/O Expanders (similar to the previous used single expanders). They require less space for the available output pins, and they require one less device address on the I2C bus. So, now I need to order even more parts, to finish the build.
 |
| Prop UI |
|
| UI With Traditional LCD Display ( Blue, Purple and Green Boards, who's idea was that? Murphy!! ) |
 |
| UI With Alternate Display |
UPDATE
I found the SOT-89 3.3Volt Regulators at Mouser, and they will be on order soon, along with a few other parts.
-
Wednesday, April 11, 2012
HomeBrew Prop-UI
While building my courage to troubleshoot the Smoke Released from my Propeller (see previous post) I have been designing a User Interface Board (UI) for the Prop. The idea is to avoid many of the point-to-point wire connections and provide as much of the user interface on one board.
The UI will be programmed to set: Transmit/Receive Frequency, CW Speed, Beacon Type/Timing, and a host of other function that have not been thought of yet. It is a general purpose UI for controlling the functions of the Prop. Note: Jeff and I have used the Prop for Beacon Transmit functions, but we have not successfully use it for a LO and BFO for a receiver yet (only due to lack of time and effort). There maybe concerns with phase noise, and Prop generated QRM, when used in a receive function.
The connection to the Prop Protoboard will be a single eight pin header.
The knobs, Push Buttons and LED's are not shown in the 3D images ( I still need to build (or find) their 3D models).
The UI will fit on the Propeller USB Protoboard along with the Standard KeyBoard, Video Connector, and Mouse (KVM). The I2C expanders that are used on the Prop-UI will minimize the required I/O pins from the Prop, allowing the KVM to be used when desired.
Note: there are many Display Boards available on the Internet, but nothing that provides a low pin count connection to the Prop, which include the peripherals that I am including for the UI.
The UI board will be about 2.5 x 3.1 inches, which is much bigger that most of my projects.
If all goes well, this project will be sent to the PCB manufacture by Friday, then a two week wait for the first three boards to return.
--
The UI will be programmed to set: Transmit/Receive Frequency, CW Speed, Beacon Type/Timing, and a host of other function that have not been thought of yet. It is a general purpose UI for controlling the functions of the Prop. Note: Jeff and I have used the Prop for Beacon Transmit functions, but we have not successfully use it for a LO and BFO for a receiver yet (only due to lack of time and effort). There maybe concerns with phase noise, and Prop generated QRM, when used in a receive function.
The connection to the Prop Protoboard will be a single eight pin header.
- SCL (I2C)
- SDA (I2C)
- 5 Volts
- Ground
- Clock Interrupt
- Reset
- Sound
- Switch Interrupt
- LCD Display (A Parallel LCD but the board will provide the I2C converter)
- LCD I2C (another connector for an alternate display from another manufacture)
- Real Time Clock (RTC)
- Battery Clip for RTC Backup
- Eight LED's
- Two Rotary Encoders with Push Buttons
- Two Push Buttons
- Piezo Speaker
- 3.3Volt Regulator
 |
| Top Side - LCD |
 |
| Back Side - Quad Pot, RTC, and Two I2C Expander |
The UI will fit on the Propeller USB Protoboard along with the Standard KeyBoard, Video Connector, and Mouse (KVM). The I2C expanders that are used on the Prop-UI will minimize the required I/O pins from the Prop, allowing the KVM to be used when desired.
Note: there are many Display Boards available on the Internet, but nothing that provides a low pin count connection to the Prop, which include the peripherals that I am including for the UI.
The UI board will be about 2.5 x 3.1 inches, which is much bigger that most of my projects.
If all goes well, this project will be sent to the PCB manufacture by Friday, then a two week wait for the first three boards to return.
--
Subscribe to:
Posts (Atom)