I am running the Rifid Edge Server in Windows 7,32bit JVM,and using a Alien ALR-9900 Reader,the reader config as folling:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<configurationStore>
<services>
<attributes>
<entry>
<key>PersistTime</key>
<value>-1</value>
</entry>
<entry>
<key>Password</key>
<value>password</value>
</entry>
<entry>
<key>IpAddress</key>
<value>192.168.1.100</value>
</entry>
<entry>
<key>ExternalOutput</key>
<value>0</value>
</entry>
<entry>
<key>ReaderNumber</key>
<value>1</value>
</entry>
<entry>
<key>MaxNumConnectionAttempts</key>
<value>10</value>
</entry>
<entry>
<key>DisplayName</key>
<value>Alien</value>
</entry>
<entry>
<key>IOStreamPort</key>
<value>54322</value>
</entry>
<entry>
<key>ReconnectionInterval</key>
<value>5000</value>
</entry>
<entry>
<key>Port</key>
<value>23</value>
</entry>
<entry>
<key>NotifyPort</key>
<value>54321</value>
</entry>
<entry>
<key>InvertExternalOutput</key>
<value>OFF</value>
</entry>
<entry>
<key>Username</key>
<value>alien</value>
</entry>
<entry>
<key>InvertExternalInput</key>
<value>OFF</value>
</entry>
<entry>
<key>RFAttenuation</key>
<value>0</value>
</entry>
</attributes>
<factoryID>Alien</factoryID>
<serviceID>Alien_1</serviceID>
<sessionDTOs>
<commands>
<commandID>Alien_Poll_1</commandID>
<interval>5000</interval>
<processID>0</processID>
<timeUnit>MILLISECONDS</timeUnit>
</commands>
<ID>1</ID>
<status>PROCESSING</status>
</sessionDTOs>
</services>
<services>
<attributes>
<entry>
<key>TagType</key>
<value>1</value>
</entry>
</attributes>
<factoryID>Alien-Poll</factoryID>
<serviceID>Alien_Poll_1</serviceID>
</services>
</configurationStore>
But the rifidi Edge Server reports errors :
Queing command: CommandExecutor: Alien_Poll_1IPSession: 192.168.1.100:23 (CLOSED
), [Autonomous Session IPServerSession: 54321 (PROCESSING)],[GPIO Session IPServ
erSession: 54322 (CREATED)]
11:27:15,327 ERROR org.rifidi.edge.sensors.sessions.ReadThread:92 - java.net.Soc
ketException: socket closed
11:27:15,331 INFO org.rifidi.edge.sensors.sessions.AbstractServerSocketSensorSe
ssion:165 - Stopping Alien_1
11:27:15,332 INFO org.rifidi.edge.sensors.sessions.AbstractIPSensorSession:200
- Attempting to connect to : 192.168.1.100:23
11:27:15,371 WARN org.rifidi.edge.adapter.alien.commandobject.AlienGetCommandOb
ject:72 - Something is wrong with the command: *********************************
**************
*
* Alien Technology : RFID Reader
*
***********************************************
Username>
11:27:15,373 WARN org.rifidi.edge.adapter.alien.commands.internal.AlienProperty
Command:77 - Alien Exception while executing command externalinput**************
*********************************
*
* Alien Technology : RFID Reader
*
***********************************************
Username>
11:27:15,392 FATAL org.rifidi.edge.adapter.alien.Alien9800ReaderSession:196 - Se
nsorSession is not an alien sensorSession:
11:27:15,394 WARN org.rifidi.edge.sensors.sessions.AbstractIPSensorSession:349
- Connection Failed 192.168.1.100:23
11:27:15,395 ERROR org.rifidi.edge.sensors.sessions.ReadThread:92 - java.net.Soc
ketException: socket closed
11:27:15,399 INFO org.rifidi.edge.sensors.sessions.AbstractServerSocketSensorSe
ssion:132 - Alien_1 listening on port 54321. Maximum number of concurrent reade
rs supported: 15
11:27:20,303 WARN org.rifidi.edge.sensors.sessions.AbstractSensorSession:298 -
----------------------------------------------------------------------------------------------------
Can you help me?
Alien ALR-9900 Reader Connecting Problem
Re: Alien ALR-9900 Reader Connecting Problem
Hi Childek,
I don't have a 9900 on me, but I ran your configuration file against an emulator-generated Alien reader and it checked out fine. The only values I changed were the IP and the port. Is anything hooked up to GPIO? I can't tell exactly, but it looks like it may be a GPIO problem of some sort based on the errors that are being reported. Also try connecting to the reader manually and trying the command "get externalinput". See if there is anything wrong with it, like a timeout or maybe it takes too long to return a result.
If you like you could try setting up an Alien autonomous reader instead of a regular Alien reader. That would almost certainly solve your problem, as it appears to be a result of trying to connect to interactive mode. Autonomous would get around that; it simply pushes the data straight back to the client.
-Matt
I don't have a 9900 on me, but I ran your configuration file against an emulator-generated Alien reader and it checked out fine. The only values I changed were the IP and the port. Is anything hooked up to GPIO? I can't tell exactly, but it looks like it may be a GPIO problem of some sort based on the errors that are being reported. Also try connecting to the reader manually and trying the command "get externalinput". See if there is anything wrong with it, like a timeout or maybe it takes too long to return a result.
If you like you could try setting up an Alien autonomous reader instead of a regular Alien reader. That would almost certainly solve your problem, as it appears to be a result of trying to connect to interactive mode. Autonomous would get around that; it simply pushes the data straight back to the client.
-Matt
Re: Alien ALR-9900 Reader Connecting Problem
To provide some closure on this issue:
I experienced the exact same problem with an Alien 9900 as described here trying to use interactive mode. (Alien-Poll)
I solved it by upping the timeout value for commands.
Set the system property for org.rifidi.edge.sessions.timeout=10000
the default is 5000 and doesn't seem to give a 9900 enough time to respond.
I experienced the exact same problem with an Alien 9900 as described here trying to use interactive mode. (Alien-Poll)
I solved it by upping the timeout value for commands.
Set the system property for org.rifidi.edge.sessions.timeout=10000
the default is 5000 and doesn't seem to give a 9900 enough time to respond.
Re: Alien ALR-9900 Reader Connecting Problem
Thanks Paul,
I'll up the default to the value you suggest for the next release. No sense in it being so low if there is a potential problem.
-Matt
I'll up the default to the value you suggest for the next release. No sense in it being so low if there is a potential problem.
-Matt
Re: Alien ALR-9900 Reader Connecting Problem
This has been fixed as of 3.0.1 release
Who is online
Users browsing this forum: No registered users and 3 guests