|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools |
Rating:
|
Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: New C18 3.0+ Compatible FRC Code
I'm sure I'm just being stupid or something like that, but whenever I try to open the workspace I get a "Unable to open the workspace because the format of the workspace file has changed" error followed by "A lock violation has occurred". I can open the individual *.c and *.h files just fine.
Anyway, I've only just started looking through this and it already looks awesome! I really like the timer setup and interrupt handling setup. Last year I did some interrupt and timer stuff and it could get rather confusing; this will be great for our new, inexperienced programmers to get into interrupts without quite as much trouble. It is almost like if you took the logical layout and ease of coding interrupts from WPIlib and combined them with the lower level control of IFI's code. Great work, Kevin! |
|
#2
|
||||
|
||||
|
Re: New C18 3.0+ Compatible FRC Code
I just setup a clean virtual machine with Windows XP Professional sp2. I ran Windows Update, installed MPLab 8.0, and installed C18 3.15 Student Edition.
Here are the errors I'm getting: MPLAB C18 v3.15 (demo) Copyright 1999-2005 Microchip Technology Inc. Days remaining until demo becomes feature limited: 60 C:\Documents and Settings\Eric Haskins\Desktop\ifi_frc_beta\ifi_frc_beta\ifi_code .c:31:Error [1105] symbol 'ADC_VREFPLUS_VDD' has not been defined C:\Documents and Settings\Eric Haskins\Desktop\ifi_frc_beta\ifi_frc_beta\ifi_code .c:31:Error [1105] symbol 'ADC_VREFMINUS_VSS' has not been defined Halting build on first failure as requested. BUILD FAILED: Wed Dec 26 19:25:06 2007 What did I forget? EDIT: I moved it to a shallower directory, but it still returns that error. EDIT: I uploaded a file with the output from the compiler. Last edited by EHaskins : 26-12-2007 at 20:47. |
|
#3
|
||||
|
||||
|
Re: New C18 3.0+ Compatible FRC Code
Quote:
Honestly, I don't think you did anything wrong. I believe a file or two were left out of the zip. If you'll notice, at the top of ifi_code.c is a "#include adc.h", that file is not included in the .zip. |
|
#4
|
||||
|
||||
|
Re: New C18 3.0+ Compatible FRC Code
I believe that headers within <>s are found in "c:\mcc18\h" by default. If you look adc.h, delays.h, and stdio.h, are all located there.
|
|
#5
|
||||
|
||||
|
Re: New C18 3.0+ Compatible FRC Code
I really love the format! much cleaner and easier to use... Please tell me this will become the new standard!
On my only annoyed note: i wish i could see the Main files and Process_data_from_master_uP function. i get antsy if i can't see when everything's being called. Also, i'd like to re-ask why i would use the Spin functions (maybe if i could see main.c, and i could see when they're bein called...) |
|
#6
|
||||
|
||||
|
Re: New C18 3.0+ Compatible FRC Code
Quote:
-Kevin |
|
#7
|
|||
|
|||
|
Re: New C18 3.0+ Compatible FRC Code
Should I be using MPLAB 8 or the 7.2 that came with the kit of parts?
|
|
#8
|
||||
|
||||
|
Re: New C18 3.0+ Compatible FRC Code
You should use MPLab 8 if you don't wan to have compatibility issues, but you can use 7.2.
|
|
#9
|
|||
|
|||
|
Re: New C18 3.0+ Compatible FRC Code
Where can I get that?
|
|
#10
|
||||
|
||||
|
Re: New C18 3.0+ Compatible FRC Code
Please define "that".
If you mean MPLAB 8.0 and C18 v3.1, please read the very first page. If you are referring to MPLAB 7.4 and C18 v2.7, look in the KOP for the CBOT CD. |
|
#11
|
|||
|
|||
|
Re: New C18 3.0+ Compatible FRC Code
I know this might be kinda random, but does anyone know if we are allowed to use any kind of gps system in our robot sense it's location on the field?
|
|
#12
|
|||
|
|||
|
Re: New C18 3.0+ Compatible FRC Code
This post is irrelevant to this topic, but in any case GPS is too inaccurate for this use. Also, it involves receiving external communications, which I understand is against the rules.
|
|
#13
|
|||
|
|||
|
Re: New C18 3.0+ Compatible FRC Code
I must be missing something simple. I am using your code that is a couple of versions back, and when i enable the gyro code, all i get is this:
Gyro Bias=-1 Gyro Rate=0 Gyro Angle=0 after it has initialized I then pulled your most recent code enabled the adc and the gyro in both spin and teleop the code compiles correctly, but soon as i load it, i get a code error. |
|
#14
|
||||
|
||||
|
Re: New C18 3.0+ Compatible FRC Code
Quote:
-Kevin |
|
#15
|
|||
|
|||
|
Re: New C18 3.0+ Compatible FRC Code
I got my code to work, there was an ifdef that i had written that blocked out part of the init, but the new code still fails to load.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Does the camera code suits to all versions of MPLAB and C18? | razer | Programming | 3 | 04-01-2007 14:50 |
| Trying to follow C18 interrupt context code... | dcbrown | Programming | 5 | 21-12-2006 09:01 |
| Error w/ FRC code | JamesBrown | Programming | 2 | 08-01-2005 16:17 |
| Programming code Fix FRC | Ferazel2001 | Programming | 6 | 08-02-2004 02:46 |
| FRC default code | hedgehogger | Programming | 2 | 21-01-2004 18:41 |