mstrdenz91 wrote:

Code: Select all

void Button1Click() {
      PORTB = PORTB || 0x0006;  
       //PORTB.B1 = 1;
      strcpy(Label3.Caption, "Solenoid on");
      DrawLabel(&Label3);
}

void Button2Click() {
 InitIO();
}

Hello,

What you have posted is not C code, it looks like MS Visual XXX code in part.

Kind regards,

Yako.

Bonca wrote:---
Sorry, I replied to a wrong place.

Bonca

No, you have come to the right place friend.

I use this compiler for all of my firmware, but not all of my projects use an MCU.

Difficult, resourceful, quirky and you wouldn't do it.

Interfacing an 74HC165 is actually pretty boring, but making a good video game that runs inside a one-dollar PIC using straight C code is an eye-opener. You should give it a go. Perhaps not Tetris, though, as this is just going to be so difficult to do with a few bytes of RAM on free scan lines that...

xpolhecx wrote:Oh i doubt i'm going to play with games because i have many unfinished projects

Arh, but how many of those projects have all been done before?

A game of Tetris using monochrome composite video would literally be a 'first' for mikroC.

No asm besides nop.

I did notice this, however I expected some form of assignment operator like Cblock or equ. i.e. INDF equ 0x0000 You are probably better off diving straight into raw Microchip assembly if you're questioning this sort of stuff. As a high-level C programmer, there is no need for it really. This is a p...

Then do a game of Tetris (my fav game of all time)

Not easy to do with a 5MIPS 2KB PIC in C, but possible none the less.

xpolhecx wrote:Sure, no problem

If you have some time to kill, then you can have a go at interfacing to that monochrome composite video code using another MCU.

Make a game of PONG or something.

You will save me a chore, because I need to write a demo application later on for it.

An 8-BIT DAC solution for controlling the output voltage: Are there better options that don't impose the 80mV resolution?

xpolhecx wrote: What did you mean by that?

Keep up the good work and always make sure that what you do and or say is genuine.

No more games.

Everythink is tested before posting, of course :) The solution is not perfect and can be optimized (i guess), but it works fine for my needs :) OK three rules from hereon in. 1. Posts and technical data must be absolute genuine 2. You must know what you're doing as in like for real 3. Don't ever sm...

Bit like the old saying: "give me 100 engineers and I'll give you 100 different solutions to (n) problem"

I'll have to get some of these chips and fire them up with some code.

You're testing these solutions before posting right?

It would be nice to see everything "genuine" from now on.

I have done a 4-digit counter, similar to what you are trying to do. Here is some relevant code for you to have a look through: // LED 4-Digit UP / DOWN Counter with Fail safes! unsigned short buttonDown = 0; unsigned short tens = 0; unsigned short hundreds = 0; unsigned short thousands = 0; unsigne...

I think that you are probably better off reading the ports directly rather than using the button lib (personal subjective opinion)

Also, with your IFs, you are better off doing this:
You really need to have a degree of coherency in your code.

I leave it in your capable hands.

I don't like flogging off solutions that I am unable to test, makes me look like a fool if not working.

There's nothing worse than looking like a fool.

I don't know these chips and I don't have them.