Search found 17 matches

I think the link below should explain how to use hyperterminal to talk to your PIC.

http://www.ccsinfo.com/forum/viewtopic.php?t=9253&start=1

Here we see the problem with 'search':
If you k ...

Hi Bill,

If you want to be able to communicate with multiple ports you can use the 'stream' option within the #use rs232

You will only be able to use the built in hardware UART with the 2 pins ...

I notice that you are manually altering PIN_C6 before and after you send data, this is incorrect. You should leave the UART to control this pin.

You may see a similar bit of code in programs that ...

OK, ruling out the option that that was an invalid cross bank data transfer, it looks like I have now spotted the problem.

While the syntax of that command was fine, it looks like I have used all t ...

SET_TRIS_B(0x00);

TRIS needs to be set high on a pin for it to be read as an input.

I am also not sure if the way you have the switch wired would work,it may eb worth checking the voltage on ...

I agree, more info would be needed to accurately identify the problem, but I can offer you a theory for you to try out.
0x0A is the new line character, which certain protocols use to identify the end ...

I don't know if you have any external pullup resistors on your device to make the pins go high.
You may need the line
port_b_pullups(TRUE);
before your while loop.

I would also suggest ...

Hi,
I hope the question I have is very simple for someone, I've already spent days tracking down this peculiar bug and am at my wits end with this so please can someone help me please.

I found une ...

OK, I'm not sure now if the latest change I made (while systematically reducing the code size) has rectified the fault or simply masked the symptoms but it certainly looks to be behaving itself at the ...

one potential problem I could see would be if the unit starts running after the MIDI stream has begun, or if a byte is lost, in this case the unit may not read characters 0,1,2 of the MIDI stream, ins ...

I could take a look at shrinking the code but this precise problem has only come to light in the latest stages of code development, I am concerned that shrinking the code would simply make it go away ...

I can throw in a fairly uneducated guess:

As I recall Unix systems are more particular about files ending with a blank line than Windows systems.

Perhaps the line number offset is a result of wh ...

I have made that modification exactly as described above and the fault remains affecting the same location,
ie motor_fast_step_size_lookup_old[] (at 0x002A)is getting overwritten
but motor_fast ...

I have tried to recreate this in a smaller project but have been unable, I have therefore picked out what I think may be the relevant parts of this project to see if anyone can see what is going wrong ...

Is there a better way of doing this:
I wish to have a string containing the compile date in dd/mm/yy format.

I have written a very Heath Robinson routine that takes __DATE__ in its format 17-Jul-0 ...