BetterWB 4: blocked serial devices, why??

McTrinsic · 19 June 2016, 19:25

Hi,

I am running a Phoenix board with an A500-Clockportadapter. Attached to one of the CPs is a Hypercom 3p.

OS is 3.1 with BetterWB 4 (i. e. latest) on KS 3.1.

When I try to use NComm for a serial connection, I get a message that the serial port is not available for exclusive usage. No connection. Same goes for the serial ports of the Hypercom with hyperCOM3.device.

Any ideas why? Any other programs in BetterWB blocking the serial connection??

Cheers,
McT

gulliver · 19 June 2016, 19:28

Hi, there are no programs blocking the serial connection.

If you cannot set the device in your comms program, don't despair.
Then edit or zap serial.device ( located in DEVS: ), and replace the two occurences of the
string "artser" with "serial". If you already have used your comms
package since last reboot, you might have to reboot again before the
change will have any effect.

McTrinsic · 19 June 2016, 19:53

Hi,

interesting.

Could I as well replace it just for testing with a serial.device from the original WB 3.1?

Thanks,
McT

gulliver · 20 June 2016, 06:02

Yes indeed. Be my guest

McTrinsic · 20 June 2016, 07:39

Didnt work

.

I will try tomorrow with a different setup to check other root causes.

First make sure the board works then optimize

.

Cheers,
McT

McTrinsic · 08 January 2017, 22:33

Hi,
just in case someone digs this out eventually.

It was a hardware-issue.

Solved.

Cheers,
McT

gulliver · 09 January 2017, 04:38

It is good to know you finally solved.

Cheers

Zeph · 09 January 2017, 17:23

How did you solve it?

McTrinsic · 09 January 2017, 22:56

Well I asked someone to fix the hardware

.

I am using a VarIO in a Phoenix. The VarIO, very much like also a Hypercom and maybe other serial boards, need -12v from the Zorro-bus.

The A1000-PSU doesn't have that...

Cheers,
McT

19 June 2016, 19:25	#1
McTrinsic Registered User Join Date: Feb 2014 Location: Germany Posts: 527	BetterWB 4: blocked serial devices, why?? Hi, I am running a Phoenix board with an A500-Clockportadapter. Attached to one of the CPs is a Hypercom 3p. OS is 3.1 with BetterWB 4 (i. e. latest) on KS 3.1. When I try to use NComm for a serial connection, I get a message that the serial port is not available for exclusive usage. No connection. Same goes for the serial ports of the Hypercom with hyperCOM3.device. Any ideas why? Any other programs in BetterWB blocking the serial connection?? Cheers, McT

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
eye of the beholder (eob) wikispace blocked	CFou!	Coders. General	6	08 January 2016 18:13
Evil´s Doom - blocked path	Zapotek	support.Games	5	28 September 2015 00:14
BetterWB 3.6	gulliver	News	114	30 September 2014 12:11
BetterWB 3.4	gulliver	News	21	17 April 2014 19:55
BetterWB 3.3	gulliver	News	6	22 February 2014 12:38

19 June 2016, 19:28	#2
gulliver BoingBagged Join Date: Aug 2007 Location: The South of nowhere Age: 46 Posts: 2,358	Hi, there are no programs blocking the serial connection. If you cannot set the device in your comms program, don't despair. Then edit or zap serial.device ( located in DEVS: ), and replace the two occurences of the string "artser" with "serial". If you already have used your comms package since last reboot, you might have to reboot again before the change will have any effect.

19 June 2016, 19:53	#3
McTrinsic Registered User Join Date: Feb 2014 Location: Germany Posts: 527	Hi, interesting. Could I as well replace it just for testing with a serial.device from the original WB 3.1? Thanks, McT

20 June 2016, 06:02	#4
gulliver BoingBagged Join Date: Aug 2007 Location: The South of nowhere Age: 46 Posts: 2,358	Yes indeed. Be my guest

20 June 2016, 07:39	#5
McTrinsic Registered User Join Date: Feb 2014 Location: Germany Posts: 527	Didnt work . I will try tomorrow with a different setup to check other root causes. First make sure the board works then optimize . Cheers, McT

08 January 2017, 22:33	#6
McTrinsic Registered User Join Date: Feb 2014 Location: Germany Posts: 527	Hi, just in case someone digs this out eventually. It was a hardware-issue. Solved. Cheers, McT

09 January 2017, 04:38	#7
gulliver BoingBagged Join Date: Aug 2007 Location: The South of nowhere Age: 46 Posts: 2,358	It is good to know you finally solved. Cheers

09 January 2017, 17:23	#8
Zeph Registered User Join Date: Nov 2015 Location: Poole, Dorset Posts: 79	How did you solve it?

09 January 2017, 22:56	#9
McTrinsic Registered User Join Date: Feb 2014 Location: Germany Posts: 527	Well I asked someone to fix the hardware . I am using a VarIO in a Phoenix. The VarIO, very much like also a Hypercom and maybe other serial boards, need -12v from the Zorro-bus. The A1000-PSU doesn't have that... Cheers, McT

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