12f675_fuse_about_to_blow!

[mackrackit]

Yes, the FLOW PIN is automatically taken care of if used, but we do not need it for what we are doing. It is an option only.

Also what's a reasonable 'Timeout' period in milliseconds for this?

That depends on the whole setup for what you intend to do. For these test with keyboard/PC entry 500+ might be a good place to start. If you are connected to something like a GPS that continuously sends data and depending on what else the program does 100 may be what works.

[LEDave]

Quick question. What happens to the value of TOTAL at it's memory location after it's sent serially?
Does the memory location automatically get reset to zero or does the value TOTAL stay there until over-written
by the next TOTAL value to be sent?

SEROUT2 PORTC.3, 16780, [DEC TOTAL, 10, 13]

Dave

[mackrackit]

It stays until over-written or power down.

[LEDave]

Hi mackrackit,

I expect you can hear the cogs grinding from where you are today

Here's what I'm thinking:

Timeout con 500
 
MAIN:
PAUSE 250

SERIN2 PORTC.5, 16780, [WAIT ("#"),DEC NUM1,Timeout,Data_Not_Sent,]

I've made Timeout a CONSTANT 500. Then the program goes to the LABEL Data_Not_Sent. This is were I'm struggling in that I need to be able to tell if the data has been sent. If TOTAL did reset to zero when data was sent I could have used that but it doesn't and it could have just sent to nought's so that would be no good for a handle anyway. Then I though I could 'read' the PIN PORTC.3 to see if that had changed state, again that's only 50-50 that it has from HO to Low and also it could have just sent two zero's which would show no change.

So I'm looking for something to show a change or changed state when data is sent (I think).

Am I hot or cold in that last assumption?

Dave

[mackrackit]

SERIN2 PORTC.5, 16780,Timeout,Data_Not_Sent,[WAIT ("#"),DEC NUM1]

The SERIN2 command looks for the change of state, when using RF the time out thing does not work very well because of noise. The state is always changing even if data is not being sent.

[LEDave]

The SERIN2 command looks for the change of state

So SERIN2 looks at SEROUT2 (PORTC.3) to see if data has been sent?

PORTC.3's pin state is the key to DATA_Not_Sent?

I'm either getting a lot warmer or a lot colder with that one.

[mackrackit]

North of the Arctic Circle on that one...

The time-out option looks for a state change on the serial input pin to see if data has been received on that pin.