Renard DMX
 
Notifications
Clear all

Renard DMX

28 Posts
9 Users
0 Reactions
14.6 K Views
budude
Posts: 10400
(@budude)
Illustrious Member
Joined: 18 years ago

It depends on if you are using an AC power supply vs a DC power supply to the LV since the AC supply will provide ZC for the AC SSRs - that's why I asked that question first. If using an AC supply then all you should need to change is the sink map. If you had a DC supply then an AC SSR would not work so I wanted to clarify that bit.


Reply
RichF
Posts: 1356
(@richf)
Noble Member
Joined: 19 years ago

So to summarize since I am using ac to power my ren24lv and using external ac ssr's all I need to to is change the sink map.

I changed the sink map to 0x00 and it works now.

Thanks for the help


Reply
RichF
Posts: 1356
(@richf)
Noble Member
Joined: 19 years ago

Time to revive this thread again. ON the DMX firmware for a renard that I want to have PWM enabled on all ports is the statement #define PWM_map 255xFF correct? When I set to any number over a single digit the line shows as read in MPlab.

Looking to enable PWM as i have LEDs now and get some flickering while dimming.


Reply
RavingLunatic
Posts: 1502
(@ravinglunatic)
Noble Member
Joined: 19 years ago
RichF wrote:Time to revive this thread again. ON the DMX firmware for a renard that I want to have PWM enabled on all ports is the statement #define PWM_map 255xFF correct? When I set to any number over a single digit the line shows as read in MPlab.

Looking to enable PWM as i have LEDs now and get some flickering while dimming.

NO

#define PWM_map 0xFF is already set to Hexidecimal value 255, never change the 0 before the x. That is the source code way of knowing that is a hex value.

The Renard-DMX firmware is defaulted to PWM (0xFF), 0x00 (value = 0) would be all non-PWM

Try changing this line:

#define CTR_LOCKOUT 40

to

#define CTR_LOCKOUT 15

If that doesn't help then you probably need to look at other possible (non-firmware) solutions. Like snubbers, re-routing cables, reducing EMI.

RL


Reply
budude
Posts: 10400
(@budude)
Illustrious Member
Joined: 18 years ago

The mapping may or may not be obvious but the 0xFF is a channel bit map for the 8 channels - so in binary it would be 1111 1111 and represents each channel 1-8 for that PIC. If for some reason you wanted some channels to be PWM and others non-PWM, you can do that. So 0x0F would be channels 1-4 are non-PWM, and 5-8 are PWM. (although I should look at the code to ensure it's not ordered 8-1 vs 1-8...).


Reply
RichF
Posts: 1356
(@richf)
Noble Member
Joined: 19 years ago

thanks for the help. I thought I was in the wrong place. Will try to reprogram tonight. I have re routed data. Re routed powered and Replaced controllers.

My flickering shows up when I dim my new LED net lights in the 60 to 40 percent range and everything on that controller goes nuts.


Reply
RavingLunatic
Posts: 1502
(@ravinglunatic)
Noble Member
Joined: 19 years ago

Yeah Brian, it looks like you are backwards.

According to Phil's comments in the code, decimal value 67 equals PWM for channels 0,1,7 (using 0-7 as the channel numbers), so the Hex would be 0x43. So the channel order is: 7-6-5-4-3-2-1-0.

You can always change the entry to binary if that is easier (for those who want to mix outputs): b'10000011' for the above example.

BTW: Rich - have you tried it with the regular firmware or just the DMX so far? I doubt the firmware is to blame but it would be a troubleshooting step to try to eliminate possibilities.

RL


Reply
RichF
Posts: 1356
(@richf)
Noble Member
Joined: 19 years ago

Have not tried any other firmware this year. I only notice it during one song when I have the LED netlights dimed at about 40 percent. It is then that the other lights around the LED lights begin to shimmer

I have tried torid coils and even swappping hardware clear down to the external SSR's Still no joy.


Reply
Page 3 / 3
Share: