|
Dalek Dave wrote: Bishop has no grass in this hazardous area.
Dalek Dave wrote: BLACKSPOT
That was damn easy, wondering why nobody got that
|
|
|
|
|
Shameel wrote: That was damn easy, wondering why nobody got tha
Like the lottery numbers, once I see them I always think "I could have picked those".
|
|
|
|
|
Have you seen the new Raspberry Pi thing RS just emailed me about it, will have to have better look seems to be designed to run headless... The Raspberry PI Compute module
|
|
|
|
|
Hello!
No I don't think I have, I'll go have a look.......
|
|
|
|
|
Looks quite fancy. If you are going to this extreme you wonder if it would be better to move towards: http://www.parallella.org/[^]
Depends on the use case I suppose.
Raspberry Pi Compute Module
Raspberry Pi Compute is a SODIMM format module containing only the basic processor/RAM elements of a Raspberry Pi Model B, plus a Flash memory chip. All processor I/O are accessible via a 200-pin edge connector. The Compute module plugs into an I/O board providing a range of standard connectors for development purposes. A variety of 'boot' methods are available depending on the presence or otherwise of a host computer plugged into a microUSB socket, the state of a GPIO pin and a jumper link. The Raspberry Pi Compute module is aimed at industrial design engineers for integration into production embedded applications.
Raspberry Pi Compute Module
Broadcom BCM2835 700MHz ARM1176JZFS processor with FPU and VideoCore IV dual-core GPU
GPU provides Open GL ES 2.0, hardware-accelerated OpenVG, and 1080p30 H.264 high-profile decode
GPU is capable of 1Gpixel/s, 1.5Gtexel/s or 24GFLOPs with texture filtering and DMA infrastructure
512MB SDRAM
4GB eMMC MLC Flash memory (Replaces Flash memory card of standard Raspberry Pi)
Access to all I/O via 200-pin edge connector
Dimensions: 67 x 31mm 200-pin SODIMM format
Raspberry Pi Compute I/O Board
Provides standard I/O sockets for the Compute module
200-pin SODIMM connector for Compute module
4 x 30-pin headers (46 x GPIO, I2C bus, camera plus power and ground pins)
GPIO logic level selected by jumper link to 1.8V or 3.3V
HDMI socket
USB-A socket
microUSB socket for booting from attached host
microUSB socket for power supply
2 x CSI camera connectors (Requires adapter for Raspberry Pi video cameras, supplied with kit)
2 x DSI display connectors
Footprint for JTAG connector
Power LED
Boot Status LED
|
|
|
|
|
Well it seemed over kill to me, if you are going to use the Hardware to that extent there are other 'easier' cheaper means...
|
|
|
|
|
It does, but if you are heavy into rapid prototyping, it is platforms like this that allow you to quickly develop early protos to evaluate whether you would take them to next level.
|
|
|
|
|
Plus, having the "heavy lifting work" done of the high speed parts (processor / memory interface for example) makes the slower speed parts such as the IO a lot easier and cheaper to design. You can just plug in known working processor modules and your custom hardware is ready to go in a couple of weeks.
Layout of processors and suchlike gets expensive in man-hours as the speeds rise!
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
The way we do it, is take a known processor (tends to be PIC) and find the closest match (PWM, A to D Convertors, etc) and go from there...
|
|
|
|
|
That's fine, and it works well for low speed devices. But...once you start getting to reasonable processor speeds you have to be really careful about rack layouts - data line lengths need to be the same, you have to plan for and eliminate crosstalk, etc., etc.. 700Mhz processors talk to their RAM damn fast!
If you can drop in a known working module then the rest of the board is cheaper to design, and cheaper to manufacture - and still the the high speed processor we all want (and sometimes even need). I've done it before with a StrongArm / RAM / FPGA combo the size of a credit card.
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
Quote: really careful about rack layouts
If you mean track layouts I can say "Brother you are preaching to the choir!" at the moment I have a load of high speed digital boards to test & debug and the person that did the design & layout was one those "well it worked for me before types" causing some really interesting issues...
|
|
|
|
|
I forgot the T (probably because I don't drink the stuff!)
glennPattonWork wrote: "well it worked for me before types"
:brrrrrr:
And this time, one track is slightly shorter and the signal arrives - and worse disappears - a fraction earlier than the other 7.
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
Oooh you know my pain!
|
|
|
|
|
Fun to find, aren't they?
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952)
Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
|
|
|
|
|
No, Elephant me they are not!
|
|
|
|
|
How did they manage to squeeze all those acronyms into a tiny, 200-pin package? I once thought 4 kbit RAM on a S-100 card was impressive!
Will Rogers never met me.
|
|
|
|
|
.. can be made inserting @daveauld in your post !
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus
Entropy isn't what it used to.
|
|
|
|
|
I'm sure this is the wrong crowd to ask, but you never know.
Behind the mansion where I rest my being after working hours there are fields. This year there is corn and some sort of wheat I think. It doesn't really matter which type of crop there is grown as long as it has a long stem the same feature arises. The plants in the middle of the field grow larger than those on the side of the field. In fact all stems are large except for those within, let's say, 1 meter of the edges where it gradually grows until a maximum.
sample[^]
So the question is: why?
|
|
|
|
|
Because, they are 2 different plants planted there. It's either, on the side of the field are corn plants and in the middle are the wheat plants. Or vice versa.
Don't mind those people who say you're not HOT. At least you know you're COOL.
I'm not afraid of falling, I'm afraid of the sudden stop at the end of the fall! - Richard Andrew x64
|
|
|
|
|
It doesn't seem to affect various "low" crops - potatoes, sugar beets, that sort of thing. At least not as much.
Maybe it's the wind? It hits the edges but not really the middle.
|
|
|
|
|
seeding? the seeds sown on the edges are the single pass whilst those more in the middle get an overlap
also the crop at the edge are less protected from the elements than those further in
my guess anyway
You cant outrun the world, but there is no harm in getting a head start
Real stupidity beats artificial intelligence every time.
|
|
|
|
|
Crops on the edge tend to be better protected as hedges are better wind breaks than the crops themselves, assuming there are hedges, the hedges also provide a habitat for creatures that prey on the main crop pests.
One day I aspire to having a signature.
|
|
|
|
|
not according to that pic, there is a definite unplanted gap leaving the crop exposed
You cant outrun the world, but there is no harm in getting a head start
Real stupidity beats artificial intelligence every time.
|
|
|
|
|
Good call. Thinking back I've noticed that the smaller the fallow area between the crop and the hedge the lesser the effect so I will give you the point.
One day I aspire to having a signature.
|
|
|
|
|
Fertiliser is expensive so overspray onto the path is avoided?
|
|
|
|