Ren24LSD - Troubleshooting

[michaelc]

I've build my Ren24LSD and I'm trying to test it. I've done the basic tests and the correct voltages are appearing where they are supposed to on the PICS and other chips. Just nothing happening on the output jack. Here are my symptoms.

I've created a test sequence in Vixen using 48 channels. The output is going to an ENTTEC Open DMX USB. The software 'appears' to recognize the dongle because it does not give me a missing error. I confirm this by unplugging it and restarting the program, where it DOES throw an error.

SO I run the Test of all channels and according to Vixen, it looks like it's working but absolutely nothing is happening. My PICs are programmed with all chips set to a DMX default start of 1 and for this test it is the ONLY board I'm connecting. I also have the TERM jumper on.

Is there a way to test for a valid signal coming from the USB dongle. I have an inkling that the issue might be the dongle but since this is a brand new build on the board, I've got to have an open mind. A nice signal status LED would be a nice addition to future versions. Any help would be greatly appreciated.

[dirknerkle]

Do you mean a Ren24LV or a Ren48LSD? I'm confused...

[michaelc]

Ren48LSD

[budude]

Did you enable the DMX Add-in (not just the Enttec Open Plug-in) - if not do so and try your tests again.

[michaelc]

Brian, yes, I forgot to mention that in the description. The DMX addin is checked. I really think it is dongle related. I tried a test late last night connecting one of my LOR boards directly using the dongle and it had a hard time seeing/keeping the signal as well.

I'm going to try a different computer to see if it's a computer/port issue. My current laptop is running Windows Vista64. It all seemed to work last week but now I'm having issues. Troubleshooting 101, remove all accessories and start at the source confirming operation!

[michaelc]

One thing I noticed tonight when trying to troubleshoot the Open DMX. According to the online documentation in the SUPPORT section or ENTTEC, the dongle should show up in the USB section of the device manager as an FTDI device. Mine is popping into the Ports (COM &LPT) section.

Are there any tricks to get this thing to run on a Vista64 machine?

[budude]

Vista - - ugh... I think it's correct to come up as COM port - I haven't used my Enttec Open for quite a while but that sounds right to me anyway. I'll try and find it to double-check. I think my daughter's machine is a Vista/64 (my last Vista box in the house). Is there any way to test on an XP or Win7 machine - or at another PC in general?

[michaelc]

We must think alike. I'm currently trying to configure on another PC.

[mschell]

Just to be sure - you did load the DMX firmware on the Ren48LSD, right? The normal Renard firmware will not work with the DMX output dongle.

[michaelc]

Yes, I am going to re-image the PICS to be sure, but I'm positive that's what I used since I went in and did the DMX specific edits.

Here is the top part of the code that is in the source directory of MPLAB-IDE that was used to burn the PICS

;; filename: renard-fast-20080307.asm
;; Copyright (c) 2006-2008 Phil Short
;;
;; This program is provided free for you to use in any way that you wish,
;; subject to the laws and regulations where you are using it. Due diligence
;; is strongly suggested before using this code.
;;
;; The Author makes no warranty of any kind, express or implied, with regard
;; to this program or the documentation contained in this document. The
;; Author shall not be liable in any event for incidental or consequential
;; damages in connection with, or arising out of, the furnishing, performance
;; or use of these programs.
;;
;; --------------------------------------------------------------------------
;; NOTE:
;; This code is configured for regular use (the firmware generates 30 uS (at
;; 60 Hz) pulses to drive the SSRs, synchronized to the zero-crossing input
;; pin). Here are the DEFINE statements to change for PWM use (generates a
;; variable width pulse sync'd to the zero-crossing signal) or DC use
;; generates a variable-width pulse, not sync'd to anything).

;; PWM_map determines which bits should be 'PWM' (normally 0, for all non-PWM).
;; It is binary-encoded, with bit 0 corresponding to channel 0 through bit 7
;; channel 7. As an example, the value 67 = 64 + 2 + 1 would have three
;; channels (0,1 and 7) as PWM and the rest as non-PWM.

#define PWM_map 0xFF

;; DC_build should be either 0 (for AC operation) or 1 (for DC operation). It
;; should remain 0 if PWM_map is anything other than 255

#define DC_build 1

#define CLOCKRATE 18432000
#define BAUDRATE 250000

;; CTR_LOCKOUT should be 0 for the DC build, can be a somewhat larger number
;; for non-PWM or non-DC builds.

#define CTR_LOCKOUT 0

;; Bitmap of outputs which sink current (normally 0xFF, for all 8 outputs).
;; This is binary-encoded the same way as the PWM_map 'variable'. A '1' bit
;; means that the output sinks current (is active low), a '0' bit means that
;; output sources current (active high).

#define SINK_map 0x00

#define DEBUG_DMX 0

;; The DMX start address should be between 1 and 505 inclusive.

#define DMX_START_ADDRESS 1