gnupic: Thread: Minicom and testing hardware

I'm needing some help in the communications area.
Is there a site that explains how to set minicom to talk to a pic? I 
have found tons of stuff for modems and the like but nothing for a pic.
Also could I put a jumper from the tx to the rx and know if the hardware 
is correct up to the pic?
I really need some help.
Thanks,
wayne

On Fri, Jan 30, 2004 at 01:44:54PM -0600, WaynePatterson wrote:
> I'm needing some help in the communications area.
> Is there a site that explains how to set minicom to talk to a pic?

Simple: 

1) Do a ^AO to go to the config page. 
2) Select serial port setup. 
3) Set bit rate and parity (8N1 most likely)
4) Turn off hardware flow control
5) Turn off software flow control
6) Save the config (you need to be root to do this)

That's it. After that you should have direct access to the pic.

> I 
> have found tons of stuff for modems and the like but nothing for a pic.

See above.

> Also could I put a jumper from the tx to the rx and know if the hardware 
> is correct up to the pic?

Yup.

> I really need some help.

That should do it.

BAJ

Byron A Jeff wrote:
> On Fri, Jan 30, 2004 at 01:44:54PM -000, WaynePatterson wrote:
>>I'm needing some help in the communications area.
>>Is there a site that explains how to set minicom to talk to a pic?
> 1) Do a ^AO to go to the config page. 
> 2) Select serial port setup. 
> 3) Set bit rate and parity (8N1 most likely)
> 4) Turn off hardware flow control
> 5) Turn off software flow control
> 6) Save the config (you need to be root to do this)

You'll also probably want to delete the modem initialisation rubbish 
from the Init String and Reset String parts of the "Modem and Dialling" 
menu so they don't get sent to the PIC every time you start or exit the 
program, and unless you run it as root and ignore the nag message you'll 
most likely need to add yourself to whatever group owns the serial ports 
on your system (uucp?).

-- 
------------ Alex Holden - http://www.linuxhacker.org ------------
If it doesn't work, you're not hitting it with a big enough hammer

So if I don't receive back what I type in the minicom window there is 
something wrong in the hardware?
Or do I have to set up a script?
Thanks for your help Byron!!!
wayne

Byron A Jeff wrote:

>On Fri, Jan 30, 2004 at 01:44:54PM -0600, WaynePatterson wrote:
>  
>
>>I'm needing some help in the communications area.
>>Is there a site that explains how to set minicom to talk to a pic?
>>    
>>
>
>Simple: 
>
>1) Do a ^AO to go to the config page. 
>2) Select serial port setup. 
>3) Set bit rate and parity (8N1 most likely)
>4) Turn off hardware flow control
>5) Turn off software flow control
>6) Save the config (you need to be root to do this)
>
>That's it. After that you should have direct access to the pic.
>
>  
>
>>I 
>>have found tons of stuff for modems and the like but nothing for a pic.
>>    
>>
>
>See above.
>
>  
>
>>Also could I put a jumper from the tx to the rx and know if the hardware 
>>is correct up to the pic?
>>    
>>
>
>Yup.
>
>  
>
>>I really need some help.
>>    
>>
>
>That should do it.
>
>BAJ
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: ####@####.####
>For additional commands, e-mail: ####@####.####
>
>
>  
>

WaynePatterson wrote:
> So if I don't receive back what I type in the minicom window there is 
> something wrong in the hardware?

You'll only get that if you put a program on the PIC which echoes back 
what it receives.

-- 
------------ Alex Holden - http://www.linuxhacker.org ------------
If it doesn't work, you're not hitting it with a big enough hammer

On Fri, Jan 30, 2004 at 02:26:29PM -0600, WaynePatterson wrote:
> So if I don't receive back what I type in the minicom window there is 
> something wrong in the hardware?

Maybe. I always test systematically:

1) Wire with TX/RX hooked together. Test for echo.
2) Then hook the TX/RX to the RS-232 converter. Tie the far end RX/TX of the
converter together. Test for echo.
3) Finally hook to the target. Test again.

> Or do I have to set up a script?

Not that I know of.

> Thanks for your help Byron!!!

Good Luck.

BAJ

Thanks Byron, and Alex!
I got it working!
What do you guys think about a "newbie corner" or something like that?
Just for stuff like this.
wayne

WaynePatterson wrote:

> I'm needing some help in the communications area.
> Is there a site that explains how to set minicom to talk to a pic? I 
> have found tons of stuff for modems and the like but nothing for a pic.
> Also could I put a jumper from the tx to the rx and know if the 
> hardware is correct up to the pic?
> I really need some help.
> Thanks,
> wayne
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>
>

On Fri, Jan 30, 2004 at 02:52:28PM -0600, WaynePatterson wrote:
> What do you guys think about a "newbie corner" or something like that?
> Just for stuff like this.

The trouble is the experts would then need to remember it was there so 
they could point the newbie with the question to it.  The experts aren't 
good at that.  And the newbies we hear from are the ones who don't know
that the answer is on a FAQ somewhere.  ;-)

So while the motivation is great, it won't achieve much, unless it 
becomes a repository for all sorts of other newbie stuff, and if everyone 
starts referring to it.

Then there's the cost of maintaining the information.  

So here's a solution ... have a look at the electronics chat Wiki.  
http://www.electronicschat.org/echatwiki/  This would let everybody 
maintain it.  You could even join our IRC channel and chat.

As for talking to a PIC attached to a serial port, it depends on what I
need.  For example;

- set the baud rate, I use "stty 2400 < /dev/ttyS0"
- see what the PIC sends, I use "cat /dev/ttyS0"
- say something to the PIC, I use "echo 'something' > /dev/ttyS0"
- talk to it, I use ckermit.

quozl:~$ kermit
C-Kermit 7.0.196, 1 Jan 2000, for Linux
 Copyright (C) 1985, 2000,
  Trustees of Columbia University in the City of New York.
Type ? or HELP for help.
(/root/) C-Kermit>set line /dev/ttyS0
(/root/) C-Kermit>set carrier-watch off
(/root/) C-Kermit>connect
Connecting to /dev/ttyS0, speed 9600.
The escape character is Ctrl-\ (ASCII 28, FS)
Type the escape character followed by C to get back,
or followed by ? to see other options.
----------------------------------------------------

hello

-- 
James Cameron    ####@####.####     http://quozl.netrek.org/

James,
Thanks for the link and the advice!
wayne

James Cameron wrote:

>On Fri, Jan 30, 2004 at 02:52:28PM -0600, WaynePatterson wrote:
>  
>
>>What do you guys think about a "newbie corner" or something like that?
>>Just for stuff like this.
>>    
>>
>
>The trouble is the experts would then need to remember it was there so 
>they could point the newbie with the question to it.  The experts aren't 
>good at that.  And the newbies we hear from are the ones who don't know
>that the answer is on a FAQ somewhere.  ;-)
>
>So while the motivation is great, it won't achieve much, unless it 
>becomes a repository for all sorts of other newbie stuff, and if everyone 
>starts referring to it.
>
>Then there's the cost of maintaining the information.  
>
>So here's a solution ... have a look at the electronics chat Wiki.  
>http://www.electronicschat.org/echatwiki/  This would let everybody 
>maintain it.  You could even join our IRC channel and chat.
>
>As for talking to a PIC attached to a serial port, it depends on what I
>need.  For example;
>
>- set the baud rate, I use "stty 2400 < /dev/ttyS0"
>- see what the PIC sends, I use "cat /dev/ttyS0"
>- say something to the PIC, I use "echo 'something' > /dev/ttyS0"
>- talk to it, I use ckermit.
>
>quozl:~$ kermit
>C-Kermit 7.0.196, 1 Jan 2000, for Linux
> Copyright (C) 1985, 2000,
>  Trustees of Columbia University in the City of New York.
>Type ? or HELP for help.
>(/root/) C-Kermit>set line /dev/ttyS0
>(/root/) C-Kermit>set carrier-watch off
>(/root/) C-Kermit>connect
>Connecting to /dev/ttyS0, speed 9600.
>The escape character is Ctrl-\ (ASCII 28, FS)
>Type the escape character followed by C to get back,
>or followed by ? to see other options.
>----------------------------------------------------
>
>hello
>
>  
>