Accelerometer | ADC | ADXL | Adxl20 | AVR | BasicStamp | BX-35 | BX28 | BX35 | COM3 | Compiler | Downloader | EEPROM | Electromagnet | GetADC | GP2D1 | GPS | I2C | IDE | Keypad | LCD | LCD+ | MIDI | Motors | Multitasking | Netmedia | Networking | PCB | PID | PlaySound | PWM | Relays | RTC | Servo | ShiftOut | SitePlayer | SPI | Stack | Timer | USB

I am considering buying a "RamSandy" :) As my project is still in "prototype" [some might say *perpetual* "prototype", heheehe] I need the convenience of the 40 pin expansion ribbon (ie. to a breadboard). From the pictures /info that I've seen so far it appears that if I use the RamSandy I'll no longer have the physical connection to the 40 pins on the Developement board available? Anybody know? Will I need to make/obtain an adapter? Is it possible to still get access to the dev board's 40 pins when using the Ramsandwich? Thanks a bunch dudez & dudettez, Dave Brace P.S. ONELIST + BasicX + You .and. I = Pretty Cool! Kudos to those responsible for the inception and maintenance of this COMMUNITY!

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

I posted a similar message back in Digest 33. I did not get a useful answer from NetMedia, despite several emails as well as a posting to this board. But from my investigation, once the RAMSandwich has been installed, virtually all of the i/o lines are consumed and no longer available. This makes the RAMSandwich pretty much useless with the development board. I wonder if anyone actually tried to do anything useful with it before turning it into a product? If you need a large amount of i/o you might consider a mux board type of solution which allows you to drive a large number of devices from a few microcontroller pins. However my BasicX can't seem to stack and process enough data to work properly with my sensor array. Or you might give some thought to a more usable chip/compiler/development board like the Rabbit. Sensible price, serious performance and none of the silly restrictions found on the NetMedia stuff. As you can tell, I'm not that impressed by NetMedia, their product or their customer "service". My $0.02. Don

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

-----Original Message----- From: <> To: <> Date: Friday, December 10, 1999 9:53 AM Subject: [BasicX] re: BX-01 Developement Kit & Ramsandwich - 40 pin ribbon still usable? >From: > >I posted a similar message back in Digest 33. > >I did not get a useful answer from NetMedia, despite several emails >as well as a posting to this board. But from my investigation, once >the RAMSandwich has been installed, virtually all of the i/o lines >are consumed and no longer available. You posted one message to this board that I know of, and I answered you the next day. I will repeat the answer: ---Beginning of answer 11/14/1999---- The RAM sandwich does consume the I/O lines. This is why we created extended I/O. Extended I/O is used with the address lines of the RAM and the RAM's data bus to provide a "bank" of 65536 I/O addresses. You use the I/O select line which is pin 3 (I think since I am at home), the read or write lines to the RAM and the address lines of the RAM (A0-A15) and the data bus of the RAM. When your address is selected and the I/O select is low, then it is your device. You use the read or write lines (low enabled) to decide what to do with your I/O. If it is a read, then you place your data on the data bus, if it is a write then you take the data and put it into your device. The other way to interface is to use the SPI bus. There are many devices that are SPI compatible - ADCs, DACs, I/O expanders, counters... This only requires one pin per device for a chip select and then the SPI bus pins." ----End of Answer--- See http://basicx.com/schematics/XIO_Schematic.gif >This makes the RAMSandwich pretty much useless with the development >board. I wonder if anyone actually tried to do anything useful with >it before turning it into a product? We expect you to put your board in the middle if you are talking about the physical nature of the connection. We have lots of people using RAM in production projects without any problems. >If you need a large amount of i/o you might consider a mux board >type of solution which allows you to drive a large number of devices >from a few microcontroller pins. However my BasicX can't seem to >stack and process enough data to work properly with my sensor array. How do you interface with your sensor array? >Or you might give some thought to a more usable chip/compiler/development >board like the Rabbit. Sensible price, serious performance and none >of the silly restrictions found on the NetMedia stuff. I am still waiting to hear any silly restrictions unless 128K of RAM and 524,280 bits of extended I/O isnt enough. If you are an expert C programmer and like to bit bang on your Rabbit then have fun. We never said BasicX is for everyone. When you have a multitasking operating system, IEEE floating point, networking, basic interpreter, and lots of internal system calls written in 8K of code space and 100 bytes of RAM let me know, we will hire you. >As you can tell, I'm not that impressed by NetMedia, their product >or their customer "service". > >My $0.02. > >Don Please send the BX1 development systems back for full credit assuming you did not modify them. My $100.02 Jack

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )