NComm not accepting keyboard input

26 June 2017, 20:04

Okay, this is starting to do my head in a little.

I'm trying to type commands into NComm, but it doesn't seem to allow any input. Is there something I happen to be missing or overlooking?

For the curious, I happen to be using a modem emulator known as the Wifi232. I think it might be trying to find something, but I don't know what.

EDIT: So, it's looking for a carrier signal. Problem is, it's not implemented.

So, how do I bypass the need for a carrier signal, and just get it to accept commands?

idrougge · 26 June 2017, 23:45

Check the "Com" menu. There should be a "check carrier" option or similar. I'm not at any Amiga with NComm right now, so I'm only going by memory here…

27 June 2017, 03:52

There doesn't seem to be such an option on there. At least not on version 3.06.

emufan · 27 June 2017, 04:23

i'm really clueless but when you select: menu -> screen -> split screen
you get a window where you can enter text. with menu -> Com -> Duplex -> Half , it will get echoed in the top window.

found this in the NComm.doc file of version 3.0

did this using version 3.06 - so no need to downgrade.

27 June 2017, 04:50

Okay, I'm getting it echoing, but it's still waiting for a modem that's not there. Any way to bypass the carrier detect signal on 3.06?

modrobert · 27 June 2017, 06:55

Try setting the baudrate to 19200, in both NComm and wifi232. I don't know what the default is for wifi232, but modern devices usually ship with 115200 baud as default which might be too fast depending on the Amiga hardware you use.

If you suspect the modem is active somehow waiting for carrier then use "Hang Up" function from the "Phone" menu in NComm, it will send the escape code and 'ATH'. If you type 'ATZ' (reset) and hit enter key the response should be 'OK' from modem.

27 June 2017, 07:32

Okay, so it's speeding up a little, but when I attempt the ATH and ATZ commands, I don't get the OK response.

emufan · 27 June 2017, 12:14

Quote:

8.6.20 The 'Hard-DCD Checking' option switches the hardware CARRIER
detect option on or off. The hardware method is more reliable
than just looking for the NO CARRIER string (if it shows up in
a message, NComm will assume that the call has ended).

NOTE: Your modem must track TRUE CARRIER. This means that
the DCD signal must be "low" (off) in command state and should
not go "high" (on) until a connection has been established.

is this of any use?
menu -> Phone -> Modem Setup (checkbox in lower left area of setup window)

01 July 2017, 04:02

From one of the pulldowns you need to select 2400 baud. The modem comes default at that rate.

You then should be able to type ATI and get a status.

Also, it needs to be powered if you didn't do that.

26 June 2017, 20:04	#1
Jaymes Keller Posts: n/a	NComm not accepting keyboard input Okay, this is starting to do my head in a little. I'm trying to type commands into NComm, but it doesn't seem to allow any input. Is there something I happen to be missing or overlooking? For the curious, I happen to be using a modem emulator known as the Wifi232. I think it might be trying to find something, but I don't know what. EDIT: So, it's looking for a carrier signal. Problem is, it's not implemented. So, how do I bypass the need for a carrier signal, and just get it to accept commands? Last edited by Jaymes Keller; 26 June 2017 at 21:09.

27 June 2017, 06:55	#6
modrobert old bearded fool Join Date: Jan 2010 Location: Bangkok Age: 56 Posts: 775	Try setting the baudrate to 19200, in both NComm and wifi232. I don't know what the default is for wifi232, but modern devices usually ship with 115200 baud as default which might be too fast depending on the Amiga hardware you use. If you suspect the modem is active somehow waiting for carrier then use "Hang Up" function from the "Phone" menu in NComm, it will send the escape code and 'ATH'. If you type 'ATZ' (reset) and hit enter key the response should be 'OK' from modem. Last edited by modrobert; 27 June 2017 at 07:30.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
NComm keyboard problem	stet	support.Apps	2	22 June 2017 01:37
Adjusting Keyboard input?	Sinphaltimus	support.WinUAE	5	17 June 2017 11:10
Keyboard input lag with other programs	mark_k	support.WinUAE	2	15 October 2016 21:43
no keyboard input in JR-Comm	boosey	New to Emulation or Amiga scene	3	16 September 2006 18:14
It all works, but there's no keyboard input	frennen	New to Emulation or Amiga scene	3	01 November 2002 12:47

26 June 2017, 23:45	#2
idrougge Registered User Join Date: Sep 2007 Location: Stockholm Posts: 4,332	Check the "Com" menu. There should be a "check carrier" option or similar. I'm not at any Amiga with NComm right now, so I'm only going by memory here…

27 June 2017, 03:52	#3
Jaymes Keller Posts: n/a	There doesn't seem to be such an option on there. At least not on version 3.06.

27 June 2017, 04:23	#4
emufan Registered User Join Date: Feb 2012 Location: #DrainTheSwamp Posts: 4,545	i'm really clueless but when you select: menu -> screen -> split screen you get a window where you can enter text. with menu -> Com -> Duplex -> Half , it will get echoed in the top window. found this in the NComm.doc file of version 3.0 did this using version 3.06 - so no need to downgrade.

27 June 2017, 04:50	#5
Jaymes Keller Posts: n/a	Okay, I'm getting it echoing, but it's still waiting for a modem that's not there. Any way to bypass the carrier detect signal on 3.06?

27 June 2017, 07:32	#7
Jaymes Keller Posts: n/a	Okay, so it's speeding up a little, but when I attempt the ATH and ATZ commands, I don't get the OK response.

01 July 2017, 04:02	#9
wlemonds Posts: n/a	From one of the pulldowns you need to select 2400 baud. The modem comes default at that rate. You then should be able to type ATI and get a status. Also, it needs to be powered if you didn't do that.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)