Chuck,
Good point and another argument for top-level system engineering. There should be network documentation showing address and priority assignments for each payload. This should be a top-level function along with allocating the amount of power each payload can consume. None of these global issues should be left to the individual subsystem teams to determine.
Juan - WA6HTP
-----Original Message----- From: eagle-bounces@amsat.org [mailto:eagle-bounces@amsat.org] On Behalf Of Chuck Green Sent: Sunday, September 16, 2007 5:53 PM To: Jim Sanford Cc: Robert McGwier; eagle@amsat.org Subject: [eagle] Re: YAHOO!!!! IT WORKS!!!!
Hi Jim,
The mode and address must be soldered onto the widget (jumper pads provided on the widget for this purpose). It is assumed that the module builder would do this. It's that assumption that should be documented. I say this to bring up the follow-on issue.
The module builder chooses the mode.
The address should be specified by the system administrator since the addresses must be unique for each module and the priority is a function of the address. Module builders should give input to the system administrator as to what they feel their priority should be, but presumably only the system administrator is in a position to know the priority requirements of *all* modules and is therefor in a position to make these priority (address) decisions.
Chuck
Jim Sanford wrote:
Guys: There's a lesson here: DOCUMENTATION
Juan expected/assumed one thing, the CAN-Do! widget was something else. Other teams will go through exactly the same issue. SO, it appears we need to add some documentation to each WIDGET in terms of serial number, address, and probably a handful of other things I don't know about.
Let's learn from this experience.
Juan, thanks to you and your team for perservering.
Stephen, thanks for your prompt support on a short fuse.
This kind of response and mutual support is exemplary, and what it will take to get Eagle on orbit.
Thanks & very 73, Jim wb4gcs@amsat.org
Dave hartzell wrote:
Wow, this is a relief. I'm glad it was something simple....after all the hunting and pecking we did yesterday, I'm glad it was something so simple.
I guess when the term "bus" is used, an address as probably key to getting to your destination. ;-)
Dave
On 9/16/07, Juan Rivera juan-rivera@sbcglobal.net wrote:
All,
We need to take up a collection to buy Stephen a large hero badge. He
fixed
the problem and the receiver is now sitting on my bench happily
receiving a
signal. The new CAN-Do module that he sent me had a different address
than
the old one and the old files were addressing the initialization instructions to a non-existent device. All we have to do is change the address field in the initialization files and everything is fine.
Whew! The train of life in back on the tracks!
73 to all,
Juan
Via the Eagle mailing list courtesy of AMSAT-NA Eagle@amsat.org http://amsat.org/mailman/listinfo/eagle
Via the Eagle mailing list courtesy of AMSAT-NA Eagle@amsat.org http://amsat.org/mailman/listinfo/eagle
_______________________________________________ Via the Eagle mailing list courtesy of AMSAT-NA Eagle@amsat.org http://amsat.org/mailman/listinfo/eagle