Is the signal being read correctly - you are just reading a pin for RemoteUp, EndStopUp etc - check that you are getting 0 or 1...

|| and && do work correctly for OR and AND ...

Martin

Hi Jorgen, I'd recommend some parenthesis around the parts of the OR So if (A = 1) || (B = 1).... Alternatively - as A and B are 0 or 1 (RemoteUp and EndStop!) - declare them as boolean (true = 1 and false = 0) and then just if A || B ... (Use || for OR and && for AND - though bitwise OR sho...

Hi Julian,

Something like this - it runs AOK in simulation - in hardware you might need to check the pins used (C0 for ADC for example)

Adding a SetFontScaler(2,2) makes the display easier to read! (from the gLCD component)

Martin

Odd - I've just tested with a PIC18F46K80 as the target and: OSCCONbits.INTRF = 0b101; BRGCON1bits.BRP = 0b10001; Compiles okay - maybe been missed from the include for the MCU you are using? The alternative is something like (assuming BRP is bits 0..4) BRGCON1 = (BRGCON1 & 0b11100000) | DESIRED...

The 'bits' refers to a bitfield

So for example OSCCONbits.ICRF = 0b101 would set three bits (ICRF<0..2> - on a sample PIC18F) would be my understanding - whereas OSCCONbits.ICRF0 would refer to a single bit.

Martin

There are still some very disturbing 'errors' in the output. Sometimes the results are very good - and others - not so much. For example - I asked which pin to use for an interrupt - and it gave the wrong one, and then argued that I must be using an out of date datasheet (and old silicon). When I as...

Yes - I think I follow: So maybe something along the lines of: In Up: Read RemoteUp Read EndStopUp If (RemoteUp == 1) && (EndStop == 0) // RemoteUp pressed and door isn't already up Loop Read RemoteUp Until RemoteUp == 0 // Wait for button to be released StartMotor to raise door Loop Read En...

Hi Jorgen,

In 'Up' - it checks if RemoteUp = 1 then immediately does a loop PortB->RemoteUp while RemoteUp = 0 should this be until RemoteUp = 0?

Martin

You are constantly updating the display in a loop - this means it will refresh very rapidly probably with slightly different values. Try adding a delay. Also - if the value's representation changes in length (say '10' then '9') - it will not clear trailing digits. One way round this is to convert th...

In the i2c properties there is a 'stop delay' setting - check this is set to no.

Martin