PDA

View Full Version : New Beta Code



P. Short
07-19-2007, 05:01 PM
Here is a new version of the firmware source code. It has the bug fix in place that was mentioned in the '50 Hz' topic, and has had the code re-arranged so that there is one single source file for the regular, PWM and DC versions. The file that you can download is set up for regular use, you will have to change some of the #define statements for the PWM or DC builds.

The three builds have been tested in a 60 Hz environment with an external clock oscillator at 57600 baud.

--

Phil

jshidemantle
06-08-2009, 11:09 AM
Phil I am new to this, just built my first SS 24. When I downloaded the regular code from the WiKi website it would not compile correctly. Didn't like the amp in the config line and missing several ) in various lines.
The beta code compiled fine. Is it ok to use this for now?

Thanks
Jack

P. Short
06-08-2009, 01:58 PM
That code is pretty old, if I were you I would try and get the version from the Wiki to work.

I don't remember anyone else having the problems that you are encountering. That sounds to me like either a problem with the download or Microchip has changed something in their assembler. What version of the MPLAB tools are you using?

rice66
06-08-2009, 02:37 PM
Phil, I am in the process of assembling the ren24 bds and gotten flashed pic with the kits, If I get them working ok, should I get a pic programmer (pickit1) and upgrade. I am really new to dimming and renards, as you can tell he he
regards
Rice66
btw thanks for all you do for this hobby!!

P. Short
06-08-2009, 03:52 PM
In a word, yes.

awhaley
06-08-2009, 06:42 PM
Phil's obviously the expert on all things Renard, but if you have programmed PICs, I'd personally get the thing assembled and try it out. If it does everything you need it to and you don't experience any bugs, you may not need to go through the trouble and expense of getting into programming chips right away. I would imagine that the chips that came in a coop kit were probably programmed with working firmware...

Learning how to (and getting the stuff to) program PICs isn't hard, and it's really worth it if you enjoy the hobby, but if you have a working part, I wouldn't rush to mess with it. :)

Just my .01 cent. ;)

Art

jshidemantle
06-09-2009, 09:21 AM
Phil, I am using MPLAB 8.3 and a PICStart Plus programmer. I downloaded the diagnostic firmware and it compiled ok. Any chance you could email me a copy that compiles ok for you?
My email is jackandkaye2@aol.com
Thanks
Jack

P. Short
06-09-2009, 10:05 AM
Use the latest version from the wiki...

jshidemantle
06-09-2009, 01:55 PM
Ok Phil, I downloaded the code again from the WiKi site and this time it compiled fine. Must have been a bad download. The problem I have now is only channels 1 - 8 work. 9 - 16 and 17 - 24 don't respond to the RS232 communication. Actually I assume these are characters being retransmitted by the first PIC?

Jack

jshidemantle
06-09-2009, 02:39 PM
Never mind Phil. Haste makes waste. I had a bent pin in the first PIC and of course it was the one pin that communicates with the other PICs.
Everything is fine, now I can proceed with Blinky/Flashy and mega trees.
Jack

P. Short
06-09-2009, 04:08 PM
Glad to hear that you have it going now.

pikoko
11-03-2009, 10:51 PM
Anychance there's a version of this code that works with the internal clock? I think I may have cooked my crystal

RavingLunatic
11-03-2009, 11:21 PM
If you suspect that you fried your oscillator, use the diagnostic firmware to confirm it.

Run the diagnostics first normally and if no channels come on, then try it using the internal oscillator.

To convert the firmware to internal oscillator change the following lines:

__CONFIG _FCMEN_OFF & _IESO_OFF & _BOD_OFF & _CPD_OFF & _CP_OFF & _MCLRE_OFF & _PWRTE_ON & _WDT_OFF & _EC_OSC
;; __CONFIG _FCMEN_OFF & _IESO_OFF & _BOD_OFF & _CPD_OFF & _CP_OFF & _MCLRE_OFF & _PWRTE_ON & _WDT_OFF & _INTOSCIO


to

;; __CONFIG _FCMEN_OFF & _IESO_OFF & _BOD_OFF & _CPD_OFF & _CP_OFF & _MCLRE_OFF & _PWRTE_ON & _WDT_OFF & _EC_OSC
__CONFIG _FCMEN_OFF & _IESO_OFF & _BOD_OFF & _CPD_OFF & _CP_OFF & _MCLRE_OFF & _PWRTE_ON & _WDT_OFF & _INTOSCIO


If you see some channels come on now then yes your oscillator is fried.

pikoko
11-04-2009, 01:10 AM
Oh I know it's fried. I did exactly what you said before I posted. Tried the 07 diag didn't get anything no channel 2 blinking. So I loaded the 06 diag firmware and got blinking on 2 and blinking on 6 I beleave which is zero crossing.


I'll be using internal in a bit

do I need to set these def's to
#define clockrate 8000000
#define baudrate 19200

pikoko
11-04-2009, 02:41 AM
okay well i gave that a try.

uncommented the int config, commented out the ext config and changed the clockrate to 800000 and tried the baudrate at 52000 and 19200 i got nothing.

got a ren64 with 1 chip and a sequence setup to run on 8 channels.

before it fired i was getting some light control but it wasnt dimming well so iv been trying to clean up the power

RavingLunatic
11-04-2009, 07:08 AM
If you did something significant enough to fry your oscillator, you probably also fried your RS485 chip(s) which would explain why you still don't get anything even with the internal oscillator.

pikoko
11-04-2009, 10:03 PM
thats what i was thinking and im gonna be trying another max485c chip tommaro.

the thing thats strange to me is i used 12v but i put it thru and 5v external voltage converter just to make sure it wasnt cause of the 5v supply i was using.