I've been thinking, (you already said this I think) I bet my problem is my 485 converter, and not the actual serial port. I need to make a cable to run true 232 from the PC to the REN16 (I don't have a cable like that today).
And I need to test the 485 converter on an OSCOPE... I am somewhat confident that is where the problem is....
My problem was mostly some MTA IDC connectors that I was using, they don't always make reliable, consistent contact with the solid 24AWG CAT5 wires (stranded, in this case). JEC knows what I'm talking about.
--
Phil
Hey guys,
I have 2 Ren64's and will soon have 6 Ren24's.
I have not flashed any PIC's yet, (Issues with WinPic and my Programmer / Vista) - But I'd be happy to test any configuration you need with the 64's or 24's...
kmc123 wrote:Hey guys,
I have 2 Ren64's and will soon have 6 Ren24's.
I have not flashed any PIC's yet, (Issues with WinPic and my Programmer / Vista) - But I'd be happy to test any configuration you need with the 64's or 24's...
please grab the latest FW Phil provided above, and try it at 115.2KBPS
Is there a way to identify the modified Renard Plug-in? The one I have is Renard.dll -> 24,576 bytes.
Thanks
ms
stempile wrote:Is there a way to identify the modified Renard Plug-in? The one I have is Renard.dll -> 24,576 bytes.Thanks
ms
I'm not sure, but you could grab the one from my website if you like
ritzfam.com/xmus
Download this:
http://beeblebrox.org/hashtab/
Using Xmus' website at http://ritzfam.com/xmus
I found the MD5 hash's to be:
* Ren-diag-20070815a_extosc18432.asm
MD5 = 38DBA772426EF8B61E023F06980D58D6
* Ren-diag-20070815a_extosc18432.HEX
MD5 = B9FA09AEACD508EC0C62CE2C0B971991
* Ren-diag-20060905_intOsc.asm
MD5 = B78AE4E18F98D3FA27B7038108922C7F
* Ren-diag-20060905_intOsc.HEX
MD5 = 6C86A2CD6544FD6120B38202F743A1BB
* Renard-20070812_57600_EXTOSC_NoPWM.asm
MD5 = 0C33ED510C0AB2BF63028AA0436760A8
* Renard-20070812_57600_EXTOSC_NoPWM.HEX
MD5 = 4799DA930436E5047C469676A2C0B059
* Renard-20070812_57600_EXTOSC_PWM.asm
MD5 = 36A53B9D16D67BF171A5E843C5B5C386
* Renard-20070812_57600_EXTOSC_PWM.HEX
MD5 = 48BD4D85A5FA3A8E1661786504812D59
* renard_test_dll.zip
MD5 = 12C6A594D19B53D04B8E20BE13305EC9
Good way to keep tabs on not only authenticity but versions. I'll leave it to Dave or Phil if they wish to continue finding MD5 hash's or not. 😉
P. Short wrote:An oscilloscope, measuring at the width of the narrowest pulse on the serial data line.--
Phil
Well, I'm getting 5.6us narrowest pulse @ 115.2KBPS (25ms resolution, 16 channels, native COM port, RS485 adapter off of ebay) which doesn't make any sense to me. It should be closer to 8.68us right? If I'm seeing this correctly, this would be 178.571KBPS?
I'll fall back to 57.6 and double check:
I'm seeing 14us min pulse... which would be 71.43KPBS
so 115.2 is 55% too fast and 57.6 is 24% too fast?
I must be doing something wrong. I know 57.6 works fine.
is that rising edge to falling edge or rising to rising edge?
im guessing theres a gap in between the pulses somewhere.
Peter
Given the limits of computer hardware, it looks like the DMX code for Renard will be a lot more stable at higher baud rates. I am looking forward to testing that.
To get the number of channels and speed we want with the computer hardware I already have, DMX will be the answer I think!
ms
