RPM's DMX USB Pro - trying to get Enttec sample code to work

[ncc1701mda]

So... I built the interface, installed the drivers, the LED blinks... so far so good... Not familiar with Vixen so I decided to try the Enttec USB DMX Pro sample code (you can download it from their website). Compiled it under Visual Studio 8 and ran it. It sees the device, initializes it okay, reads the driver version which returns 0 0 0 (seems odd), reads the latency timer (returns 16) but fails when it makes the following call:

res=FTDI_ReceiveData(GET_WIDGET_PARAMS_REPLY,(unsi gned char *)&PRO_Params,sizeof(DMXUSBPROParamsType));

This call gets a zero response from the device.

Here's the program output:


Enttec Pro - C - Windows - FTDI Test

Looking for a PRO's connected to PC ...
Looking for Devices - 1 Found
Press Enter to Intialize 1st Device :
------ D2XX ------- Opening [Device 0] ------ Try 0
D2XX Driver Version:: 00.00.00
Latency Timer:: 16 Sending GET_WIDGET_PARAMS packet...
PRO Connected Succesfully
Waiting for GET_WIDGET_PARAMS_REPLY packet...
Press Enter to Exit :

Anyone else try this? Any ideas?

Mike

[RPM]

Mike,

The dongle will not work with these commands because it only uses a small subset of the Enttec DMX Pro commands.
The current firmware is DMX transmit only, so it won't respond to querys for widget parameters or for DMX recieve, only commands to initalize and transmit DMX packets.

Robert

[ncc1701mda]

Thanks Robert - that's what I suspected. Been a long time since I have written or read any assembly code (and that was on an 8085 if that gives you a rough idea of how long ;) ) - guess I need to start looking into the Enttec API in conjunction with your code before I start trying to write a control app! Thanks again for a great project!

Mike

BTW - received the resistors yesterday - now just waiting on a few more parts from Mouser and I can finish the second interface. Playing with the first one will keep me entertained in the meantime!