Reader not responding after bad settings

[Guest Bart]

Hello!

 

I have 0702 integrated reader.

I am currently working on a software which is using this device.

I needed to read this software from scratch because I use Python language.

Here is my problem:

I have made the module which is setting the paras and everything was working good.

However I have made one little change and I sent some wrong bytes to the device.

After that I think the device is working but I cannot connect with them. It is not responding at all.

 

Is there any solution to reset all setups?

I really need to make it alive again.

 

Maybe I can write the new firmware?

There need to be solution for this.

 

BTW. I think the firmware should have some protections to avoid this situations.

 

Please help!

 

 

[chain 57]

You can try to use the demo program: 

https://s3.amazonaws.com/linksprite/RFID/integrated+reader/Tutorial+of+using+LinkSprite+UHF+EPC+Gen2+RFID+Reader.pdf

 

And below is the communication protocol of the reader:

https://s3.amazonaws.com/linksprite/RFID/integrated+reader/Communication+Protocol+of+LinkSprite+Long+Range+RFID+reader+.pdf

[Guest Bart]

I have checked with Your software and all programs from SDK.

It doesnt communicate.

 

During the last communication  I have changed 4 positions: Work mode, trigger, sound and communication protocol.

Work mode, trigger and sound probably doesnt matter.

I am affraid that I have changed com protocol to wiegand, canbus, or the worst: TCPIP! (this device doesnt have hardware for TCPIP...)

 

I was using RS485. Now when I changed the protocol it doesnt work with RS485 and RS232.

 

How can I get back the right setup?

[Guest Bart]

Ok in my opinion I do not set the TCPIP.

More possible is CANBUS or SIRIS.

 

Would anyone tell me how Your readers are responding with this settings?

Is it possible to communicate with them using RS232, or not?

 

Device is working for sure because when I connet it by RS232, open the terminal and turn it on then it makes beep and send some information:

\0xb9\0x06\0xff\

 

but I still cannot communicate with it :/

[Guest Bart]

Hi,

 

I helped myself.

My reader is responding again.

 

For those who will get stuck as me I would like to give a hint.

 

The producer has scratched the name of a processor which is installed on mainboard. 

However he didn't hide the name of this device: SP3232EEN which is responsible for RS232 connection.

 

When You change the communication protocol signal from RXTX of the processor will be forwarded to one of four circuits responsible for RS485, CAN and so on (in my case

 

What we can do is to connect an external RS232 interface directly to RXTX in the processor.

If You bypass the source of the problem then You are at home

 

How to find the RXTX? It's easy! just check the datasheet of SP3232EEN:

http://pdf1.alldatasheet.com/datasheet-pdf/view/157043/SIPEX/SP3232EEN/TR.html

 

and find R1OUT and T1IN those pins are connected with microcontroller. On the right of this circuit are a few pads. Two of them are waiting to be used

 

 

 

[chain 57]

Hi,

 

I helped myself.

My reader is responding again.

 

For those who will get stuck as me I would like to give a hint.

 

The producer has scratched the name of a processor which is installed on mainboard. 

However he didn't hide the name of this device: SP3232EEN which is responsible for RS232 connection.

 

When You change the communication protocol signal from RXTX of the processor will be forwarded to one of four circuits responsible for RS485, CAN and so on (in my case

 

What we can do is to connect an external RS232 interface directly to RXTX in the processor.

If You bypass the source of the problem then You are at home

 

How to find the RXTX? It's easy! just check the datasheet of SP3232EEN:

http://pdf1.alldatasheet.com/datasheet-pdf/view/157043/SIPEX/SP3232EEN/TR.html

 

and find R1OUT and T1IN those pins are connected with microcontroller. On the right of this circuit are a few pads. Two of them are waiting to be used

Thanks for your share.