Rookie Questions
ajward
Posts: 1,130
Hey All...
I have a couple of questions...
I have a lot of mini-projects going on and yet another has come to mind.
Been assembling a second PEK on a large breadboard. I was wondering about connecting the two Propellers together. Read a lot about multiple props, but I'm not =real= clear on the process.
First... can I make the two Props perform identically by jumpering the 4 Prop plug pins to the second Propeller? Pointless exercise perhaps, but it's one of those "What would happen if I did this?" things.
Second, and I think it's possible, can you connect the two Props to function as a sorta, kinda P16X32A processor? No clue where to start with this, but I love to tinker.
My most used phrase when it comes to technology is... "What do you mean NO????"
Thanks for any advice.
Amanda
I have a couple of questions...
I have a lot of mini-projects going on and yet another has come to mind.
Been assembling a second PEK on a large breadboard. I was wondering about connecting the two Propellers together. Read a lot about multiple props, but I'm not =real= clear on the process.
First... can I make the two Props perform identically by jumpering the 4 Prop plug pins to the second Propeller? Pointless exercise perhaps, but it's one of those "What would happen if I did this?" things.
Second, and I think it's possible, can you connect the two Props to function as a sorta, kinda P16X32A processor? No clue where to start with this, but I love to tinker.
My most used phrase when it comes to technology is... "What do you mean NO????"
Thanks for any advice.
Amanda
Comments
You can interconnect two propellers with as a TX/RX serial connection using two pins simply tied together.
This will work for FullDuplexSerial. If you have the situation of two Protoboards non-USB. (The ones that require a propplug) then you could connect them together with a simple jumped cable between the plug ports. Providing that you don't have to program them while they are connected.
If you get serious about higher speed connections between Propellers, then you can used a circuit like this one: A few resistors with pull downs to grounds to keep the pins from floating around.
Dual Propeller experimentation is one that I've been very interested in myself.
OBC
You can't connect two Props to make a "sorta, kinda P16X32A", but you can connect them together so they talk to each other and you can write your programs to take advantage of that, but you gotta do most of the work. The only already-written stuff is some high speed inter-Prop communications (in the ObEx) that sends a message (some arbitrary bytes) from one Prop to the other.
Connecting multiple Props together works pretty well when there doesn't have to be a lot of detailed information sent back and forth. For example, one Prop handles a VGA display and keyboard, maybe an SD card as well, acting as an I/O processor for a 2nd Prop that does mostly computation and handles a bunch of servos.
OBC
Thanks Mike! Of course it can't be a simple as I thought... or would like. ;-) The "P16X" is a nice thought tho'!!
Much more research is needed!!!!
Amanda
The folks at Parallax have so many neat toys, I just have a lot of things going on and... Oh, what's that shiny thing? ;-)
Amanda
Jeff:
I read the the quoted part of Amanda's post to be asking if you can program both of them at the same time by tying the pins on the two props together and connecting them both the the same prop plug. As Mike says, that does not sound like a good idea.
I'm not concerned about the case where you have two Props intercommunicating using I/O pins 30 and 31. I'm concerned about trying to download the same program to two Props at the same time by jumpering the PropPlug pins together. The two Props will both attempt to respond to the PC's polling and they'll have slightly different timing, so they'll get out of sync and attempt to drive the I/O line in opposite directions theoretically damaging one or both Props. The attempt to download won't work for long because of the timing differences. The potential for damage can be avoided by putting series resistors between the two Prop's I/O pins, something like 220 Ohms would work fine, but not just jumpering them together.
More food for thought!
@
Hi Amanda
If your definition of "sorta, kinda P16X32A processor" can be made to include:
- two propchips
- accesses to both props through a common interface
- Prop1 cogs 0-7 on one area, and prop2 cogs 8-15 on another area, such that cogs0-7 don't expect direct access resources on Prop2 and vice versa,
Then you can maybe do some of what you want, if you can deal with FORTH. If you love to tinker, then download the propforth 4.5
http://propforth.googlecode.com/files/PropForth4.5-20110614.zip
The code you want is at
..\Propforth4.5-20110614RC0\doc\tests\test-4.3.2 MCS+NoROM.txt
Ah.. Yeah, I wouldn't try programming them at the same time either.. Just thought you might be onto something about the design of the Protoboard nonUSB that would cause issues interconnecting them together by the programming pins over the long term. I'm still learning this stuff too, so when I hear someone say "don't do that!" I like to get clarification as to "why" ---- Thanks!!
OBC
Most of the wiring is done. I'll put the power supply together tomorrow and check the re-assembly. My P2E Kit. ;-)
Amanda
I know you said you're not finished - but don't forget the jumper to ground for the Prop on the right
Someone on the forum has programmed multiple Props at the same time. I think it's in the Project forum now. Okay, I'll go find it. Here it is.
There are lots of posts about Prop to Prop communication. It comes down to what you want to do and how fast you need it done.
Duane
If yes how about a three-channel-switch. After booting the first propeller switching one EEPROM to the second prop and do a reset making the prop boot again. Now with connected EEPROM?
If you want to run different code the 3-channel-switch could be used to switch connection to prop-EEPROM 1 and prop-EEPROM2
As long as you do not use high frequency applications (more than 1MHz) you can simply use a flatcable to bring over prop-IO-pins to other bread-boards
keep the questions coming
best regards
Stefan
Thanks for the comment!! Actually, the small jumper is in place... just covered by the red wire to RESn.
@
Stephan... Running the same code on both Props was just a "Gee, I wonder..." kind of question, but yeah... I'd kind of like to load both processors with one connection. Just as a learnng exercise.
@
Duane,
I ran across that thread last night during a restless bout. Looks interesting. I need to finish up the wiring and install the power supply. My goal? Nothing to advance the betterment of mankind. Just something to prove that I can make it work. Speed? Pshtt. Don't need speed, just functionality!
Thanks,
@
http://forums.parallax.com/showthread.php?108928-CoggyTerm-2.0d-Terminal-w-VT100-emulation&highlight=PropCOMM
OBC
Byte Magazine, October 1981, the Local Networks issue, on Page 50, has an article entitled "Ultra-Low-Cost Network for Personal Computers". The author proposes a simple network which runs over a standard RS-232 connection. In it's simplest configuration, he attaches a single diode (he uses a 1N4933) between RXD and TXD with the cathode pointing to the RXD pin and the RXD pin connected to the data line of a 2-wire twisted pair cable. The other wire in the cable is grounded. The data line is pulled down to -12VDC through a 2K resistor on each end of the cable.
This network is designed for RS-232 voltage levels (+12 & -12), but it should be able to be reconfigured for TTL (change the pull-down voltage to 0 or change it to pull-ups to +5?). You could then dedicate one of the cogs to Network Control and it can then pass data between it's Prop and other Props on the network, handling things like addressing, broadcasts, collision handling, etc. I have been wanting to do some network experimentation with Props for a while, but am pretty busy at the moment.
The article also includes upgrades to handle better speed, increase the number of nodes and other things like that. If you would like the article, PM me.
I finished up the dual Prop board this morning and both are running independently. The photo shows the finished (mostly) board and the Props running LED4OnOff.spin. (Hi-tech stuff there! )
The biggest change I made from the PEK layout (Other than the Elenco Board) was moving and consolidating the power supplies. The new layout adds a 7812 regulator & cap. The power rail at the top provides unregulated voltage from the lab supply. The rails above and below the Props provide 3.3 vdc. The rails to the right can provide 5 & 12 vdc for other needs.
I need to tweak the wiring for the 3.3 volt to clean up the look of the board. (Not needed really, it's just me!)
Anyway... the thing works so it's time to start playing! Okay... playing =more=!
Amanda
Don't make it too neat or you won't want to tear it apart.....well, I guess it's OK for the power supply wiring!
Rick
What I don't see is DECOUPLING capacitors on power rails to >Propellers (100nF) 2 on one Propeller (Both sides).
Have it as practice That all IC's need that ones --- On every Power pair of its Power supply
Still getting back up to speed on my electronics knowledge. Decoupling caps...to keep transients from traveling along the power lines between IC's? My board has only one power rail supplying 3.3 vdc to the Prop chips. The second rail is provided power from the first through the wiring outlined in the PEK documentation (Something I want to change).
Though I've experienced no issues with the layout, I've added a .01 uF ceramic across the 3.3 vdc supply lines.
@
Sapieha explains it well here.
Duane