Software :: Minicom Versus Gtkterm / Putty - App For Serial Communications?
May 21, 2009
I am running kubuntu 9.04. I have minicom, Gtkterm and Putty installed. minicom seems to be really good, but I am missing scroll back functionality on there. Either that or I'm a novice with it and don't know how to do it. Putty is a GREAT app. But what I'm finding is that after the terminal runs for a bit, the screen shows characters from the previous lines and goofs up the output. If I move the window, the gibirish disappears. gtkterm is adding several empty lines to any of the screen output.
I am trying to get two way serial communications going between a Windows XP system and a Linux system (RHEL 5).I have /sbin/agetty -L 9600 ttyS0
in /etc/inittab. I am using a generic USB to serial adaptor on Windows (Unitek) and a null modem cable. I have putty configured for 9600 baud, 8 bits, no parity, one stop bit, no flow control.I get the login prompt from agetty in the putty window but input does not work; I see weird characters in the putty screen. I can echo output into the device from windows and see it, but
cat < /dev/ttyS0. just prints out weird characters from what I type.
I am wanting to set-up serial communications between my server (ubuntu 9.04) and a picaxe chip (a pic with a bootloader) I need to send data in the format of "1,1,1" or "1,1,0" at 9600 baud 8 data bits, no parity, 1 stop bit and no flow control. the data must be sent as numbers not ASCII I have tried Code: echo 1,1,0 > /dev/ttyS0 Any simple shell script or even python.
I have two linux boxes A and B. Each of them have serial ports (ttyS0 on both) and these ports are connected using null modem serial cable. "A" box is always on and it has getty process on its ttyS0 (I need this getty for serial communication). If I reboot box B, it doesn't boot default entry - just displays grub os select table. After some investigation I realized that getty process on A sends some data to grub on B while it's booting and grub behaves the same way as if some key is pressed during timeout period - it doesn't boot default and waits for interactive user response. I need to reboot B remotely so its no good for me.
I have an application written in C (by somebody else) monitoring a device connected to a serial port. I'm using an old laptop w. tinycore linux for an os. The app works well enough, and the communication speed is relatively slow, 9600bps, unidirectional, comes in packets of 18 bytes. The app is just picking apart the packets and displaying the contents on a formatted screen (ncurses), updating about once every 1/2 second. The trouble is, the app is polling the serial port and using *all* of the cpu bandwidth. The cpu fan runs full bore all the time.
Other activities are sluggish when the monitoring program is running. I'd like to modify the app to be a little more intelligent, use a receive buffer and interrupts to trigger processing each packet and, most importantly, not poll in a tight loop waiting for data. I'm not sure where to start, but I'm convinced this isn't that complicated of a change. Is there a good resource that would explain the basics of reading data from serial port software buffers, triggering on interrupts and suspending or sleeping when no interrupt is pending?
I have a usb serial adapter and was happily using minicom with it under openSUSE 11.2. I've upgraded to openSUSE 11.3 and I can only use minicom with this serial adapter as root. I had previously had problems writing to /var/lock under openSUSE 11.2 which I worked around by changing the minicom config to use /tmp as its lock file location.
Unfortunately my laptop doesn't have a built in serial port so I can't tell if its a general problem or something specific to the /dev/ttyUSB0 device. This is the output I get when I run minicom with my regular user account. I get the same output whether the lock file location is set to /tmp or /var/lock
Code:minicom usb0 Device /dev/ttyUSB0 lock failed: Permission denied. Before I started tinkering my user belonged to the following groups groups=16(dialout),33(video),100(users) I've since added 5(tty),14(uucp),21(console) but still no joy.
I am working on a embedded target board which runs on linux. The target board is connected to a linux machine through serial port. To bootup the target board, I run the minicom in the linux machine, boot the kernal of the target board through giving the boot command through the serial console (minicom). Now the question is when the target board boots up, it doesn't starts a shell. The rc scripts are getting executed. There are target specific applications getting started from the rc scripts. I appended & to the last launched application. Still I don't get shell prompt.
I am using a Prolific pl2303 USB<=>Serial adapter. dmesg reports everything seems ok when I plug it in (see below) but when I open the ttyUSB0 port in minicom, it is always offline and nothing works. Also, minicom reports:
If I plug the adapter into a different machine (Windows) everything works fine. The serial port is setup correctly (9600-8-N-1) What can I do to get this working?
usb 5-2: new full speed USB device using uhci_hcd and address 3 usb 5-2: configuration #1 chosen from 1 choice pl2303 5-2:1.0: pl2303 converter detected usb 5-2: pl2303 converter now attached to ttyUSB0 usb 5-2: New USB device found, idVendor=067b, idProduct=2303 [Code]....
Im a very basic Linux/ Centos user. I have Putty installed and a USB to serial adapter. All settings seem to be right as far as speed, etc, but I'm not sure how to list the device to open for the program. The default location it gives is "/dev/ttyS0" Trying to find where the USB is located using the "/sbin/lsusb" command gives me-
Bus 001 Device 001: ID 0000:0000 Bus 002 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus 004 Device 002: ID 0557:2008 ATEN International Co., Ltd UC-232A Serial Port [pl2303] Bus 004 Device 001: ID 0000:0000
So I think this means that it is on bus 4 correct? So how do I list this for putty to open the device.
There has been a lot of effort invested in getting external USB connected anything to work well during the connect then disconnect processing. It seems that there are troubles with OEM serial digitizers like those built-in for a tablet-PC. The built-in OEM devices do not have the same sort of connection events to trigger device creation and configuration.
Does anyone know how to make all of the find-hardware then create configuration processing visible? While I find several postings that describe "... edit xorg.conf ..." but then those edits don't want to work with the recent evolution in Xorg and X11-server configuration that deprecates (abandons?) xorg.conf. Does anyone understand what is going on with Xorg and X11-config to help me get my tablet working? Has anyone used an external USB tablet, then adapted those configuration details to get an OEM tablet working? I know that every tablet is different, but if the external device connect-creates-config process works best, it seems there might be value here.
I am trying to setup a putty session to putty from one Ubuntu machine to another. I know how to setup to connect to the machine from Windows and I am using the same settings for the one I am trying on the Ubuntu machine but it fails to connect. It fails immediately so I believe that putty is not able to find ssh. Is there some configuring that I need to do.
I would like to save the input of gtkterm ( what is displayed from its window) to a file, and this iautmatically. Because from GTKterm you can rsave raw file by clicking "save every to raw file manually". As it's say on the readme file, you can use "gtkterm -f filename.txt", but i tried and any file is created on the current directory.
On my CentOS 5.2 install I've installed a dual-port serial card based on the NetMOS 9835 chipset. I've followed the serial instructions, but everything they tell me to do is already done - see setserial outputs below. I've compared these values to the lspci output (below, NetMos card is at the bottom of the output) for the card and it appears right. Problem being, I can't use the serial ports. Oh and I did use search, and looked at every 9835-related article before posting this :)
I am hoping to be able to get an old serial-touchscreen to work with a usb/serial adapter. I had this touchscreen working some years ago on different hardware. I would like to hook it to the machine I am setting up as a multimedia host with mythtv among other things.
Following the instructions I left behind when I got this to work way back when does not work. See [URL] ....
This info is a work around to get the xserver to see the touchscreen. [URL] ....
I do know that the touchscreen works as I am able to get garbage on the screen as in the first part of my howto. But I have not had any success getting xorg to see it. I wish I had posted a copy of the xorg.conf at the time, but......
There is an issue with the current xserver in testing that I am hoping the next update (in unstable) will fix when it gets pushed to testing. That is that Code: Select all# X -configure fails with a segfault. So I am not able to generate the xorg.conf needed to get it to work. I was going to post a bugreport, that is when I found out there is an update in unstable, so I am waiting for it to get pushed at the moment.
Anyway I am hoping that I can link /dev/ttyUSB0 to /dev/tty0 and get it to work. I would like some kind of guess as to my chances of success before I go to all the work of getting the monitor hooked to the host.
I have a bit of a dilemma. I'm attempting to use a microcontroller to send MIDI messages over a virtual serial port. I want to (eventually) read them with Mixxx. I'm using an FTDI chip, so I get a /dev/ttyUSB0. I've tried spikenzielabs' Serial-Midi program, but it doesn't see any serial ports. NOTEMIDI looks really old and won't compile on my 10.04 LTS machine.
We have a new machine with RedHat enterprise 5 on it. I need to connect a serial cable to the serial port and talk to another system (old alpha system) instead of using a VT connected to the alpha.Does RedHat come with anything like Keaterm/hyperterm/etc etc?
I'm running Ubuntu 10.10 desktop in a VirtualBox VM on a Windows 2008 host machine. The end goal is join the the Ubuntu VM to a Windows 2008 domain. I've downloaded likewilikewise-open_184.108.40.206111-2ubuntu1.2_i386.deb se-open_220.127.116.11111-2ubuntu1.2_i386.deb to get the joining of the VM to the domain. But from this point forward, I'm completely lost.
1) How do I implement this likewise package? 2) How do I get files from my Windows 2008 host to the Ubuntu guest VM?
The likewise file is burned to a DVD. When I try to read the DVD, I get the "My Disk" icon but only one file gets displayed. In other words, the DVD the likewise file is burned to has a ton of files. Ubuntu doesn't see any of them expect one .exe file. The /etc/fstab had no entry for cdrom, so I put a line in that says
/dev/hdc /media/cdrom0 udf,iso9660 user,noauto 0 0 rebooted and that didn't do squat. There is no entry /etc/cdrom but there is directory /etc/My Disc. And I suppose that's what gets mounted because I can see one file on that disc. So then I thought, to hell with the DVD drive and I'll just get the Linux guest to see a "shared drive" on the host. I shared out a folder on the host via the Virtualbox "shared folders". But how I get the Ubuntu guest to see this shared folder is as big a mystery to me as is the creation of life.
A relative will soon be traveling to China to adopt a child. China is cracking down on communication tools like Skype. Some people are using Virtual Private Networks (VPN) to ensure they can communicate with families back home. I know nothing about VPNs so I have some questions.
1. Is VPN some kind of software that you can install on 2 computers to have a secure communications?
2. Is there something in Ubuntu's Software Center that I should try?
3. If China is cracking down on external communication, is VPN the best tool to ensure communication back home?
I'm trying to get WiFi up and running on an older desktop PC. lspci gives me the following information about the WiFi card: 00:0d.0 Ethernet controller: Atheros Communications Inc. AR2413 802.11bg NIC (rev 01) Is there an RPM package for the driver that I need? If no, what should I do to install the driver manually? The PC in question doesn't have any other form of direct internet access. It does have an Ethernet port, but the WiFi router is too far away to hook it up to the access point directly.
I've just set up an LTSP server, with all its clients on a separate subnet to my main network - the main network is 192.168.1.x, and the LTSP clients are all 192.168.2.x. My LTSP server has 2 NICs, one on each network, and is merrily forwarding normal IP traffic from the clients to the rest of the network. I have a client/server application that has a server on one machine, and clients locate and attach to it using multicast protocols. The server is on the main network, and any other machines on the network can locate and talk to the server quite happily. The LTSP clients, however, cannot - I assume because the multicast communications aren't being forwarded by the LTSP server. How I can get this working?
Well, upto now i have been using minicom on linux platform.Can any one tell me whether minicom is meant only for linux or is it platform independent?Actually i'm connecting 2 PC's using RS-232 and then passing and viewing the messages using minicom. Both the PC's use Fedora11. Now suppose i want to do the same thing between 2 pc's where one uses linux and other uses windows. So, if minicom is meant only for linux then how to do this?Can some one also suggest some useful links or tutorials regarding this serial communication between to different OS?
I have a netbook which has no serial port. However I use my netbook to connect to Cisco network devices via serial to USB converter. I installed Minicom on my netbook and I don't know how I can tell Minicom to use my USB port rather than default to /dev/ttyS0.
Can anyone tell me how I can change or point Minicom to use my USB port so my serial to USB will work?
I just fully installed slack 13.37 on my laptop. I was trying to use minicom. But after I typed the command line 'minicom -s' or 'minicom', I did not get the minicom window, the curson stop at the console and never return back until I kill the minicom process.
I have a Sun V120 server, and I connected to it via minicom from a linux machine. The problem is that when I connect, immeadiatly starts to receive the letter m as a command and it returns "Unrecognized command", so it is impossible to configure anything ot to give any command whatsoever. Also, sometimes receives all kind of letters, dots and characters, resulting the same and blocking my keyboard. When I connect from a Windows machine via HyperTerminal all is fine.
Initially i wrongly entered the serial port device as ttys0 and save it. It wont reply due to wrong device selection. Actual device is ttyS0 and i select this and try to save it as dfl,but an message appear as 'cannot write to /etc/minicom/minirc.dfl'
So i have to configure each and every time i open the minicom. how to configure this correctly?