-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Any harware refrance. #17
Comments
Hi @ScobbyDoo and I'm happy that you want to try it. Of course, you can also do a prototyping solution and simply hook up some RS-485-Driver breakout-boards to the RPi Pico board via jumper wires. The connections can be seen in the KiCad-schematics but don't hesitate to ask here if something is unclear. Each IO board usually contains one I2C-EEPROM to give the base board some information about the IO board (available ports, port direction, .....) but at the moment, the firmware just assumes 16 OUTs |
Oh, and the KiCad-files are automatically rendered to PDFs using GitHub actions. The latest results are here: https://github.com/OpenLightingProject/rp2040-dongle/suites/4741501920/artifacts/130997826 |
But hiw do i send command to drive dmx? Is it standalone system ,or usb , Ethernet option available. |
Since I don't know your skill level, regarding DMX-512 hard- and software, it's a bit hard to guess where to start. Then, you can fire up your favourite web browser and enter the board's IP in the address bar. The web interface of the board should open, showing you the general system status. At the top, there is a item called "Console". If you click there, you will be able to modify the values via the web browser. The other alternative is to use some kind of DMX-data-generating software such as OLA or QLC+. You can send E1.31 (sACN) or ArtNet frames from that software running on your PC to the Pico board via the virtual Ethernet connection. The Pico board should react to those values and output the data as DMX-512 on one of the GPIOs (depending on universe value in the sACN or ArtNet frames). You should also see the values change on the web interface. All this can be done without additional hardware. The hardware is only needed if you want to actually connect DMX-512 fixtures, use the wireless modes or want to see the board's status on the status LEDs. ... and I know that I should update the Readme file with all of this information ;) |
So to answer the questions: |
Yes, I'm familiar with artnet & e1.31 I will attach Ethernet(lan8720a) to controller & send data over udp to mcu ,as per calculation (16 x 512 byte ) universes how do i assign those data to specific data lines Like store first 512 byte to 1st data line Now the point is how do i fill that buffer & drive it? Sorry for silly logics(if their is any) |
Where to you plan to attach the LAN8720a? As I wrote above, the firmware won't recognize or use it. The Ethernet-Emulation uses the USB connection to the host PC. You don't need an Ethernet-cable if you want to send data from your PC to the dongle. The assignment of the data to the "data lines" is done automatically. In ArtNet and sACN you can specify a "universe id/number". That number is used to decide on which pin the data will be sent/driven. Yes, memcpy is also used in the background but the firmware/code for all that is already done. To go step by step: Do you have a pico-board connected via USB to your PC with the rp2040-dongle firmware running? |
Oh, and to avoid any mis-understandings: This project is not a library that you should include in you projects. It's a project for a "complete device" on its own. If you simply want to "use it", there's no code that you need to write. Just build/order the hardware and you're good to go. |
@ScobbyDoo : I've prepared a new version of the README: https://github.com/kripton/rp2040-dongle/tree/readme |
For connrcting Ethernet, see #29. Closing this due to inactivity, feel free to reopen |
Hi,
Im looking for any schematic to make one & try
If you have schematic i wll design pcb & share it.
The text was updated successfully, but these errors were encountered: