Banks related to memory problem?

[Acetronics2]

the strange thing is ...

PBP states there is ( should be ? ) no problem with banks spanking with 18F devices ...

PBP manual $ 2.6.2 :

Arrays may span banks on PIC18 devices.
On PIC18 devices, BYTE, WORD and LONG-sized arrays are only limited in length by the amount of available memory. The compiler will assure that arrays, as well as scalar variables, will fit in memory before successfully compiling.

so, one also could have a look to $ 7.2 " Code Pages and RAM Banks" if some assembler coding is included somewhere ...

Alain

[rsfutch]

I am now able to share the code for debugging, so attached are the five .pbp files that go into this whole software. OACIS-Main is the main program and includes the other 4 codes. R134a_R404a_K contains the conversion table that was having problems disappearing before, but now that it is in bank 4, it is having no trouble.

The new problem is the RPMAvg variable being lost (or one of the three variables that goes into calculating RPMAvg).

Another thing I noticed is that I have an array of 166 longs for my temperature conversion table. This makes for 664 bytes and is way bigger than the theoretical maximum bank size of 256. Could this be causing the problem of kicking other variables out of memory?

[Archangel]

I am more likely to be one of your customers than someone who can give you any meaningful help,BUT
I sort of think the subroutines should endif before the return is called, so you do not overflow the stack. I might be wrong, but that is my thoughts.

[Demon]

Yup, always end your IFs before returning.

Robert

[rsfutch]

Thanks for your help.

I am assuming you are talking about the cases below where this problem occurs?

I found this problem to occur once in the OACIS-Main code:

if fButtonHold = 1 then 'If a button is being held, return to prevent too quick button responses.

if MenuPage = 8 and fHoldEnable = 1 then 'Or if we are on page 8 force the Valve on holds
if RightButton = 0 then 'but only if the code was put in to enable forcing.
pEvapEEV = 1
pBuzzer = 1
elseif LeftButton = 0 then
pEvapEEV = 0
pBuzzer = 1
endif
'Update the display to reflect forced valve
hserout2[$FE, $47, 20, 2, dec1(pEvapEEV)]
endif

return
endif



And in three locations in the PCB6_3 Setup.txt:

if(AOValue > 1023) then AOValue = 1023 ; limit value
if(AOValue < 0) then AOValue = 0
if(AOCh > 7) then return ; limit value
if(AOCh < 0) then return

EEWRITE:
if(EEAddress > 131071) then EEAddress = 131071 ; limit value

....

return


EEREAD:
if(EEAddress > 131071) then EEAddress = 131071 ; limit value

....

return

• 
  I'll see what I can do to fix these and then get back to you guys with whether or not that fixed the problem.
  
  Thanks again.
  
  
  
  
  
  
  
  
  

[Demon]

Does this work?

Routine:
If bla bla then goto exitroutine
Bla
Bla
Bla
Endif

Exitroutine:
Return

If you use this in multiple routines, then just suffix with a number so the labels are unique.
Robert