Again "Error on port 3000"

[J?rgen]

Hi,
I already posted this message a while ago and we assumed it was the demo mode of the USB-key.
But now the error "Error connecting on RF Server Ip ... on port 3000" is back and i am SURE that is it NOT the demo mode.

This error blocs completly the terminal Falcon 335. Only a reboot with Ctrl+Alt+Del will allow me to reconnect to the RF Server. Meanwhile the other terminals continues to fonction correctly.

I am using RFSDK version 6.0.0.

I also included already some RFStatus() in a few long time traitements, so that the connection stays open.

Can this not be a timeout on the Falcon ?

Do you have an idee, why the terminals cause now this problem.

Thank you

[tmhinchey]

It could be a timeout on the Falcon Radio settings.  I know with Cisco and with Symbol Spectrum 24 there are various power management settings on the radio that will shut down the Rf card after a certain amount of time.  It might be worth while to examine the pattern of occurrence regarding the error connecting.  For example is it occuring after the unit has gone to sleep?  After it has wandered to a different point in the warehouse? If the Falcon was timing out, or going to power save and shutting down the RF card it would make sense that the reboot resets any timer settings and re-initiates the RF receiving in the Falcon antennae.    You may look at the RF configuration file for your radio type and see if it has time out settings in it.

[Redline]

Were experiencing the same issue with the port 3000 error, except worse.  All of our Falcon 345's go down at the same time with a port 3000 error.  We are using Cisco Aironet 1200's, and version 5.3 of the Intellitrack WMS.  This has been a sporadic problem for us in the past where it would hit single scanner here and there, and fixable with a re-boot of the scanner, but recently it has gotten worse, now collapsing our whole scanning network.

[itadmin]

Port 3000 just happens to be the port that the RF client is using to communicate with the server application across a TCP/IP network connection.  When those errors are coming up in the RF client it is typically a radio/Server connection issue such as out of range of antennae, dropped RF connection etc.  When the error comes up try to ping the IP address of the portable from the RF server PC.  I would suspect that the ping will fail and that the trouble lies somewhere between the RF hardware or RF backbone and either routing or AP associations. I have seen duplicated IP addresses assigned to Portables yield a similiar result.