-
Notifications
You must be signed in to change notification settings - Fork 9
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
Add ZeDMD WiFi support #49
Changes from 2 commits
fcddb90
81c1bcb
4315c34
3877c5d
a3ec2e2
2c9925e
dac886f
f8d728e
1fe0ea3
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,7 @@ | ||
|
||
[DMDServer] | ||
# The address (interface) to listen for TCP connections. | ||
Addr = localhost | ||
Addr = 0.0.0.0 | ||
# The port to listen for TCP connections. | ||
Port = 6789 | ||
# Set to 1 if Serum colorization should be used, 0 if not. | ||
|
@@ -16,7 +16,7 @@ PUPVideosPath = | |
PUPExactColorMatch = 1 | ||
|
||
[ZeDMD] | ||
# Set to 1 if ZeDMD is attached. | ||
# Set to 1 if ZeDMD or ZeDMD WiFI is attached. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. In DMDext we treat ZeDMD and ZeDMD WiFi as different devices. For example, ZeDMDWiFi doesn't support setting brightness or RGB order over the WiFi stream. And it would be nice to have the possibility to attach two devices, one via USB within the cab and a second via WiFi at the wall ;-) But maybe we can do the split in a second step. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I believe we only need to modify findDisplays to get simultaneous functionality working. My question is: how should we handle failures? If I have both a ZeDMD Serial and a ZeDMD Wifi configured in the dmdserver.ini, should the thread stop if it fails to find one of them, or should it continue with whichever one is available? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
See the latest commit; i have changed it to working with 2 at the same time and seperated the config stuff. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. For now, I've set up error handling so that the system will continue if it finds at least one of the two configured displays. Let me know what you think is the best approach for handling this. |
||
Enabled = 1 | ||
# Disable auto-detection and provide a fixed serial port. | ||
Device = | ||
|
@@ -33,6 +33,12 @@ RGBOrder = -1 | |
Brightness = -1 | ||
# Set to 1 to permantenly store the overwritten settings above in ZeDMD internally. | ||
SaveSettings = 0 | ||
# ZeDMD WiFi enabled? This will disable COM port communication | ||
WiFiEnabled = 0 | ||
# ZeDMD WiFi IP address, you must fill this in for WiFi to work | ||
WiFiAddr = | ||
# ZeDMD Wifi Port number, you can leave this empty and it will default to 3333 | ||
WiFiPort = | ||
bartdesign marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
[Pixelcade] | ||
# Set to 1 if Pixelcade is attached | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with @jsm174 that 127.0.0.1 is the better and safer default.
I understand that the usage should be as easy as possible.
But you don't sell a car without a handbrake just because people might to forget to release it before driving.
The default usage for dmdserver is to run on the same machine as the clients like VPX or batocera. In your new handheld device, dmdserver will also run on the same device or you would use libdmdutil directly (embedded in VPX).