Last checkin for RifidiSDK lost all debug commands?

The Forum for Non-Technical questions

Moderators: Matt, kyle, Moderators

Post Reply
Pietro001
Posts: 4
Joined: Tue May 06, 2014 6:52 pm
Organization: Impinj

Last checkin for RifidiSDK lost all debug commands?

Post by Pietro001 » Mon May 19, 2014 4:40 pm

Hi, we noticed that the last checkin of the RifidiSDK does not seem to include the convenient Diagnostic Tag commands. These are very useful to me as they are the easiest way I know to debug the state of my reader remotely, by this I mean without physical access to the reader, without needing to write a custom app for this.

Anyway, If there is an alternate way to get similar functionality that does not require me to write ann app, please tell me and I will use that one.

BTW: The only checkin that may cause this seems to be this one:

------------------------------------------------------------------------
r3660 | mattrifidi | 2014-05-18 22:35:54 -0700 (Sun, 18 May 2014) | 1 line

Pietro001
Posts: 4
Joined: Tue May 06, 2014 6:52 pm
Organization: Impinj

Re: Last checkin for RifidiSDK lost all debug commands?

Post by Pietro001 » Mon May 19, 2014 7:04 pm

Question: Could this be due to some kind of slowness on startup of the Rifidi server due to network overload or similar? I ask because, I noticed on a build from earlier than yesterday, that upon a slow start the rifidi debug commands took a long time to appear, even when the OSGI console was functional. In this case the server for some reason took a long time to initialize. I am guessing that network traffic may be at issue but not sure.

Thanks,
Pierre

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest