[[modules:start]]
Table of Contents
VSCP Hardware Modules
Open Hardware/Firmware
Everything here is open hardware and open software. That mean that all design materials and software are openly available. If you make and sell a VSCP module we would be glad to list it here.
CAN based modules
| module, can, dimmer | ||
| module, can, gpio | ||
| module, can, meter | ||
| module, can, accu | ||
| module, can, counter | ||
| module, can, gpio | ||
| module, can, ir | ||
| module, can, accel | ||
| module, can, humidity | ||
| module, can, temperature | ||
| module, can, climate | ||
| module, can, climate | ||
| module, can, display | ||
| module, can, relay | ||
| module, can, rfid | ||
| module, can, meter | ||
| module, can, gpio | ||
| module, can, counter | ||
| module, can, adc |
Ethernet based modules
| module, interface, ethernet, can, serial | ||
| module, ethernet, can, interface, gpio | ||
| module, interface, ethernet, rs232 |
Wireless modules
Interfaces and Gateways
| module, can, interface | ||
| module, interface, ethernet, can, serial | ||
| module, ethernet, can, interface, gpio | ||
| module, interface, can, wireless | ||
| module, interface, powerline | ||
| module, interface, ethernet, rs232 | ||
| module, usb, can, interface, usb2can |
Modules "work in progress"
Commercial VSCP products
Reference projects
- can485gateway - Reference project for a VSCP ↔ RS-485 Gateway based on the Modtronix SBC 28PC IR4 card and implementing the VSCP RS-485 protocol.
http://www.vscp.org/wiki/doku.php?id=vscp_specification_-_vscp_level_i_over_rs-485 - sweetbox - The sweetBox design in the PIC32 challenge to promote the VSCP protocol.
Please vote for this design to make it possible for me to continue to promote VSCP. - kent - Washing Machine Security
Demonstration projects
Modules - where to find or store hardware projects
If you want to take a look at the modules described here or if you want to submit your own hardware projects to this site, please follow these rules:
All files will be put into the SVN repository under the firmware tree found here.
The suggested directory/file naming scheme is:
| path | description |
| /firmware/$platform$/$projectname$_$compiler$ | put your README (or better readme.txt or even better _readme.txt) here $platform$ is avr, pic, arm, etc. $projectname$ is the actual name of your choice, keep it short and descriptive $compiler$ is a short for the used compiler like _gcc and so on |
| ~/hardware | subfolder that contains schematics, layouts, etc. |
| ~/docs | subfolder for all other documentation |
| ~/src | subfolder for the firmware of that module |
