dirknerkle's Ren64/...
 
Notifications
Clear all

dirknerkle's Ren64/Ren-W problem

17 Posts
5 Users
0 Reactions
7,112 Views
Capt'n Jack
Posts: 274
Topic starter
(@capt-n-jack)
Reputable Member
Joined: 18 years ago
[#11576]

Dave, in reference to your post 127, Renard-WC Wireless Controller, is there a way to test for this problem before it's showtime or should the settings you mention be done, just in case? Is this problem unique to the 64 controllers or any time you reach the channels in question?


16 Replies
dirknerkle
Posts: 10310
(@dirknerkle)
Illustrious Member
Joined: 18 years ago

The problem is that the XBee's clock runs a little hot -- just enough faster than the clock in a PIC16F688 so that you run into this timing problem every 8 pics, whether they're on a Ren64 or spread across multiple controllers in a daisy chain fashion. If you daisy chain three SS24s together -- essentially a 72 channel controller -- the problem shows up at channels 57-64 there, too. The problem has been replicated multiple times using different gear, and the change in the com settings solves the problem.

If you do not have a block of 64-channels in succession and are using start address firmware instead, you don't have to worry about it at all. For example, if you have three Ren24s but they are not interconnected via cat5 wire and you're using start addresses for each of them instead, you're okay as-is. The problem only applies when the pics are hard-wired together into a chain of at least 8 pics.

So yes, I'd say the overall best thing to do is just set your com parameters at 57600, 8 bits, mark parity and 2 stop bits. You don't have to reprogram the pics at all if they're already at 57600 since the firmware will autoadjust to the extra stop bits.

The other solution is just to drop everything down to 38400,8,n,1 and the problem goes away, too, although the lower speed cuts you back by about 90 channels per com port.


Reply
Capt'n Jack
Posts: 274
Topic starter
(@capt-n-jack)
Reputable Member
Joined: 18 years ago

The XBeePro is not accepting version 10A5. It says (Lost communication with modem)Any help is appreciated.


Reply
dirknerkle
Posts: 10310
(@dirknerkle)
Illustrious Member
Joined: 18 years ago

You have to reset the xbee to defaults first. You can only change the firmware at 9600, 8,N,1. Then you have to downgrade it to a lower version before you can upgrade it to 10E6.


Reply
Posts: 3277
 Jrd
(@jrd)
Famed Member
Joined: 19 years ago

Do the XBees cause this problem with DMX also? Or are the XBees fast enough for DMX?


Reply
LabRat
Posts: 2981
(@labrat)
Famed Member
Joined: 17 years ago

I don't believe that 250kbits is a standard speed supported by the XBees. So DMX wouldn't be possible.


Reply
dirknerkle
Posts: 10310
(@dirknerkle)
Illustrious Member
Joined: 18 years ago
LabRat wrote:I don't believe that 250kbits is a standard speed supported by the XBees. So DMX wouldn't be possible.

Correct. The XBee has a streaming throughput of about 80kbps. It has settings that go up to 256kbps but to use that, it would require handshaking and flow control.

Nobody's tried it yet for DMX of course, and it might turn out to be an interesting experiment. However, the odds aren't in your favor on it... 🙁


Reply
Posts: 3277
 Jrd
(@jrd)
Famed Member
Joined: 19 years ago

Ok, I didn't think it could but I just thought I'd ask.


Reply
Capt'n Jack
Posts: 274
Topic starter
(@capt-n-jack)
Reputable Member
Joined: 18 years ago

Still not having any luck downgrading to 10A5 even though it is listed in the dropdown.


Reply
dirknerkle
Posts: 10310
(@dirknerkle)
Illustrious Member
Joined: 18 years ago

Do you have any other versions there, such as 10C8? You could try that instead.

EDIT: I'll be glad to reset it for you if that will help. Just let me know. There's kind of a "knack" to loading new firmware on the little guys...:-?


Reply
Page 1 / 2
Share: