Skip to content

Conversation

@stemnic
Copy link

@stemnic stemnic commented Sep 12, 2019

Created a new pull request, we would also like to add some references to the hardware files so people can also make their own adapters

@peternewman
Copy link
Member

Created a new pull request, we would also like to add some references to the hardware files so people can also make their own adapters

In terms of the hardware, can you give some more info? My gut feeling is you're probably in the right area making a new plugin, but see some other options here:
https://www.openlighting.org/ola/get-help/ola-faq/#What_is_the_difference_between_the_different_USB_plugins

So fixing the licence check would be an excellent and trivial place to start.

@peternewman peternewman added this to the 0.11.0 milestone Sep 22, 2019
Copy link
Member

@peternewman peternewman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@stemnic
Copy link
Author

stemnic commented Oct 9, 2021

Sorry this took a lot longer than I anticipated, kind of forgot it with everything that happened these last few years.

I have made the changes you suggested and hope everything is okey now. Regarding the hardware it is custom with a pcb layout and microcontroller code which you can find here https://github.com/omegav/ovdmx

@stemnic stemnic requested a review from peternewman October 9, 2021 14:47
Copy link
Member

@peternewman peternewman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some initial comments.

Is there anything special to identify your device via lsusb, or is it just on /dev/ttyACM0 or similar?

Comment on lines 100 to 101
dmx_packet.data_length_parts[0] = ((((uint16_t)DMX_UNIVERSE_SIZE)>>8) & 0xff);
dmx_packet.data_length_parts[1] = ((((uint16_t)DMX_UNIVERSE_SIZE)) & 0xff);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have a look at our SplitUInt16 function for this.

What happens if the incoming DMX frame has fewer than 512 slots?

Copy link
Author

@stemnic stemnic Nov 28, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm unsure, in the application I have used it in there has always been 512 frames afaik. The original author of the code @JanOveSaltvedt could probably comment on that
I have changed it at least to SplitUInt16 as requested.

@stemnic
Copy link
Author

stemnic commented Nov 28, 2021

Some initial comments.

Is there anything special to identify your device via lsusb, or is it just on /dev/ttyACM0 or similar?

From my understanding it just shows up as /dev/ttyACM0 since it's configured on the MCU side to show up as a usb cdc device. You can see the MCU usb config here https://github.com/omegav/ovdmx/blob/master/Code/OVDMX/src/config/conf_usb.h

@stemnic
Copy link
Author

stemnic commented Nov 28, 2021

All the changes you requested should now be committed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants