Reader connects but does not respond to tags

Viewing 13 posts - 1 through 13 (of 13 total)

Author

Posts

June 18, 2018 at 11:42 am #63191

Participant

Hello –

After some finagling, I had the pro release of 2.3 up and running in my application. I could reliably connect to my device (FloBlePlus), scan tags (NTAG216) and read / write to any byte(s) on the tag using sendApdu.

This morning I upgraded to release 3.0. Now, after some finagling, I connect to the device but it does not respond to any tags. Also there is no “BEEP” when the device connects as there was with version 2.3 (not sure that’s important just pointing it out).

A partial log is included below. Any thoughts on what may be happening or, more precisely, not happening?

Thanks.

PS – please be sure to update the email people receive when they purchase the pro edition. It is a frustrating waste of time to implement
an older version from the get-go; starting off on the current version would also avoid support work on your end.

2018-06-18 11:22:30.733155-0400 [12240:3402109] Did discover service
2018-06-18 11:22:30.742300-0400 [12240:3402109] Reader Detected
2018-06-18 11:22:31.487314-0400 [12240:3402109] Peripheral Successfully Attached
2018-06-18 11:22:31.575130-0400 [12240:3402109] EscapeResponse <e1000045 00706a87 32da72f6 ddd54a86 b28d43ed 3b>
2018-06-18 11:22:31.642234-0400 [12240:3402109] EscapeResponse <e1000046 0069570f ccad0b8d 6e2a376d b6f5315d 00>
2018-06-18 11:22:31.642460-0400 [12240:3402109] Peripheral Successfully Authenticated
2018-06-18 11:22:31.692194-0400 [12240:3402109] Firmware: FWV 1.17.00
2018-06-18 11:22:31.752151-0400 [12240:3402109] Hardware: HWV 1.03
2018-06-18 11:22:31.812282-0400 [12240:3402109] Serial Number: RR431-003632
2018-06-18 11:22:31.814740-0400 [12240:3402109] Verfied Pro license
2018-06-18 11:22:32.100749-0400 [12240:3402176] Escape APDU:E0 00 00 48 04
2018-06-18 11:22:32.142930-0400 [12240:3402109] EscapeResponse <e1000000 0104>
2018-06-18 11:22:32.332882-0400 [12240:3402182] Escape APDU Semaphore timeout
2018-06-18 11:22:32.334758-0400 [12240:3402145] Escape APDU Semaphore timeout
2018-06-18 11:22:32.335191-0400 [12240:3402188] Escape APDU Semaphore timeout
2018-06-18 11:22:32.400766-0400 [12240:3402145] Escape APDU:E0 00 00 20 01 03
2018-06-18 11:22:32.443454-0400 [12240:3402109] EscapeResponse <e1000000 0103>
2018-06-18 11:22:32.606082-0400 [12240:3402188] Escape APDU:E0 00 00 49 03
2018-06-18 11:22:32.606158-0400 [12240:3402145] Escape APDU:E0 00 00 62 03 00 00 00
2018-06-18 11:22:32.606950-0400 [12240:3402145] Escape APDU:E0 00 00 40 01

June 18, 2018 at 11:45 am #63192

Hal

Participant

Sorry, meant to include the config settings. Note that the “specificDeviceUid” setting is included but it doesn’t seem to work.

let defaultConfiguration: FmConfiguration = FmConfiguration()
defaultConfiguration.deviceType = DeviceType.kFloBlePlus
defaultConfiguration.transmitPower = TransmitPower.highPower
defaultConfiguration.scanSound = true
defaultConfiguration.scanPeriod = 1000
defaultConfiguration.powerOperation = PowerOperation.bluetoothConnectionControl
defaultConfiguration.allowMultiConnect = false
defaultConfiguration.specificDeviceUid	= "RR431-003632"
rfidSM = FmSessionManager.init(configuration: defaultConfiguration)
rfidSM.delegate = self

June 18, 2018 at 1:01 pm #63193

Scott

Keymaster

Hi Hal,

Thanks for letting us know. I’ll have these resolved for you by tomorrow.

Scott

June 18, 2018 at 4:48 pm #63196

Scott

Keymaster

Hi Hal,

I’m very sorry about all these issues you’re having!
You can download an updated version of the SDK from the same link you were sent (via email today or when you bought the SDK).

specificDeviceUid will work now. Changing specificDeviceUid mid session is not recommended.

Kind Regards,
Scott

June 18, 2018 at 10:09 pm #63197

Hal

Participant

Thanks Scott.

I downloaded the file from the link and dropped it on top of the existing FlomioSDKPro.framework using the Mac finder, then started Xcode to see what would happen. Let me know if there’s anything else I should do to update the file correctly.

Now, sometimes it works and sometimes it does not. I don’t see a pattern as in, turn the device off, leave it off while starting the app, let it connect, and it always works, etc. – instead it seems random, but, I didn’t spend too much time looking at it just now.

BTW, I changed the power control setting to PowerOperation.autoPollingControl which is what I had on the previous version – I had changed it to Bluetooth while testing this morning and didn’t change it back. Didn’t seem to have an effect but again I didn’t go through combinations to verify that.

Below are console logs – let me know if there’s anything else that would be helpful to figure out what’s going on.

Thanks!

Here’s a console log from when it worked:

2018-06-18 22:00:29.156818-0400 [12899:3620118] ::centralManagerDidUpdateState supports 5
2018-06-18 22:00:29.157012-0400 [12899:3620118] CBCentralManagerStatePoweredOn
2018-06-18 22:00:29.198334-0400 [12899:3620118] ::discovered peripheral ACR1255U-J1-003632 C59F20F6-0AEF-EA4C-9FC5-A588652BF3D3
2018-06-18 22:00:29.246967-0400 [12899:3620118] ::discovered peripheral (null) 2D091D69-137E-4082-9EBA-0EC5A9CB5553
2018-06-18 22:00:29.266439-0400 [12899:3620118] ::discovered peripheral (null) B943F1A3-9910-00B8-8453-05E7FBCB0B19
2018-06-18 22:00:29.273179-0400 [12899:3620118] ::discovered peripheral (null) 33ACB4DB-26A4-A48C-D881-64D3A5C0E24E
2018-06-18 22:00:29.283015-0400 [12899:3620118] ::discovered peripheral (null) 6B0C29C9-72DD-F412-AA80-8A81E2BC6EDB
2018-06-18 22:00:29.294959-0400 [12899:3620118] ::discovered peripheral Odyssey 42D64620-8B30-F946-F4CA-ABB378A6535F
2018-06-18 22:00:29.301816-0400 [12899:3620118] ::discovered peripheral Odyssey 42D64620-8B30-F946-F4CA-ABB378A6535F
2018-06-18 22:00:29.328316-0400 [12899:3620118] ::discovered peripheral (null) 034F2260-1C70-AC38-A18D-8163FB08E6BF
2018-06-18 22:00:29.391911-0400 [12899:3620118] ::discovered peripheral (null) E689BF3E-81A0-5287-8101-B9F6FC794684
2018-06-18 22:00:29.458605-0400 [12899:3620118] ::discovered peripheral [TV] UN50JU6500 1F204446-7B4A-4CB6-8BC0-46ED443AF234
2018-06-18 22:00:29.478986-0400 [12899:3620118] ::discovered peripheral Odyssey 42D64620-8B30-F946-F4CA-ABB378A6535F
2018-06-18 22:00:29.481448-0400 [12899:3620118] ::discovered peripheral Odyssey 42D64620-8B30-F946-F4CA-ABB378A6535F
2018-06-18 22:00:29.657699-0400 [12899:3620118] FloBLE Plus Peripheral Connected
2018-06-18 22:00:29.852200-0400 [12899:3620118] ::discovered peripheral Odyssey 42D64620-8B30-F946-F4CA-ABB378A6535F
2018-06-18 22:00:30.029005-0400 [12899:3620118] ::discovered peripheral Bose Color II SoundLink CC0A7F2A-557F-4C87-9A0C-C315EFA94302
2018-06-18 22:00:30.076606-0400 [12899:3620118] Did discover service
2018-06-18 22:00:30.079038-0400 [12899:3620118] Reader Detected
2018-06-18 22:00:30.826017-0400 [12899:3620118] Peripheral Successfully Attached
2018-06-18 22:00:30.887362-0400 [12899:3620118] EscapeResponse <e1000045 00147372 931c504c b03d773b ad117e1a b9>
2018-06-18 22:00:30.947287-0400 [12899:3620118] EscapeResponse <e1000046 002bf5e0 5617ab21 78799bd5 b21d8100 f2>
2018-06-18 22:00:30.947423-0400 [12899:3620118] Peripheral Successfully Authenticated
2018-06-18 22:00:31.006209-0400 [12899:3620118] Firmware: FWV 1.17.00
2018-06-18 22:00:31.066277-0400 [12899:3620118] Hardware: HWV 1.03
2018-06-18 22:00:31.126156-0400 [12899:3620118] Serial Number: RR431-003632
2018-06-18 22:00:31.127196-0400 [12899:3620118] Verfied Pro license
SAL-9000	2018.06.18.22.00.31	RFID	Device	RR431-003632
2018-06-18 22:00:31.383980-0400 [12899:3620209] Escape APDU:E0 00 00 48 04
2018-06-18 22:00:31.426503-0400 [12899:3620118] EscapeResponse <e1000000 0104>
2018-06-18 22:00:31.630004-0400 [12899:3620210] Escape APDU Semaphore timeout
2018-06-18 22:00:31.630228-0400 [12899:3620215] Escape APDU Semaphore timeout
2018-06-18 22:00:31.633760-0400 [12899:3620204] Escape APDU Semaphore timeout
2018-06-18 22:00:31.700585-0400 [12899:3620215] Escape APDU:E0 00 00 20 01 03
2018-06-18 22:00:31.756563-0400 [12899:3620118] EscapeResponse <e1000000 0103>
2018-06-18 22:00:31.883988-0400 [12899:3620210] Escape APDU:E0 00 00 62 03 00 00 00
2018-06-18 22:00:31.883988-0400 [12899:3620215] Escape APDU:E0 00 00 49 03
2018-06-18 22:00:31.907078-0400 [12899:3620215] Escape APDU:E0 00 00 40 01
2018-06-18 22:00:32.116803-0400 [12899:3620118] Change Status:Absent
SAL-9000	2018.06.18.22.00.32	RFID	didChange
2018-06-18 22:00:36.978407-0400 [12899:3620118] Change Status:Present
SAL-9000	2018.06.18.22.00.36	RFID	didChange
2018-06-18 22:00:37.098161-0400 [12899:3620118] ATR Response: 3B 8F 80 01 80 4F 0C A0 00 00 03 06 03 00 03 00 00 00 00 68
2018-06-18 22:00:37.098345-0400 [12899:3620118] In transmitApdu acsbtreader
2018-06-18 22:00:37.109833-0400 [12899:3620211] Command APDU:FF CA 00 00 00
2018-06-18 22:00:37.277570-0400 [12899:3620118] Response Apdu: 04 73 5B 82 E8 50 84 90 00
2018-06-18 22:00:37.281906-0400 [12899:3620118] In didReturnResponseApdu acsbtreader
2018-06-18 22:00:37.282535-0400 [12899:3620179] In transmitApdu acsbtreader
2018-06-18 22:00:37.298091-0400 [12899:3620185] Command APDU:FFd600040448414c42
2018-06-18 22:00:37.367776-0400 [12899:3620118] Response Apdu: 90 00
2018-06-18 22:00:37.368121-0400 [12899:3620179] In transmitApdu acsbtreader
DT	Optional("90 00")
2018-06-18 22:00:37.368446-0400 [12899:3620118] In didReturnResponseApdu acsbtreader
2018-06-18 22:00:37.379643-0400 [12899:3620185] Command APDU:FFB0000404
2018-06-18 22:00:37.458526-0400 [12899:3620118] Response Apdu: 48 41 4C 42 90 00
DT	Optional("48 41 4C 42 90 00")
2018-06-18 22:00:37.458971-0400 [12899:3620118] In didReturnResponseApdu acsbtreader
SAL-9000	2018.06.18.22.00.37	CONTENT	Complete	00001.mp4
2018-06-18 22:00:38.512207-0400 [12899:3620118] Change Status:Absent
SAL-9000	2018.06.18.22.00.38	RFID	didChange

And here is the log from when it did NOT work:

2018-06-18 22:01:32.112212-0400 [12903:3621137] ::centralManagerDidUpdateState supports 5
2018-06-18 22:01:32.114077-0400 [12903:3621137] CBCentralManagerStatePoweredOn
2018-06-18 22:01:32.189867-0400 [12903:3621137] ::discovered peripheral (null) B943F1A3-9910-00B8-8453-05E7FBCB0B19
2018-06-18 22:01:32.199045-0400 [12903:3621137] ::discovered peripheral (null) 2D091D69-137E-4082-9EBA-0EC5A9CB5553
2018-06-18 22:01:32.265041-0400 [12903:3621137] ::discovered peripheral (null) 33ACB4DB-26A4-A48C-D881-64D3A5C0E24E
2018-06-18 22:01:32.270203-0400 [12903:3621137] ::discovered peripheral ACR1255U-J1-003632 C59F20F6-0AEF-EA4C-9FC5-A588652BF3D3
2018-06-18 22:01:32.278393-0400 [12903:3621137] ::discovered peripheral Bose Color II SoundLink CC0A7F2A-557F-4C87-9A0C-C315EFA94302
2018-06-18 22:01:32.348548-0400 [12903:3621137] ::discovered peripheral (null) D4C87D7C-695B-4302-AEC7-4E097F14FFF2
2018-06-18 22:01:32.378626-0400 [12903:3621137] ::discovered peripheral (null) 6B0C29C9-72DD-F412-AA80-8A81E2BC6EDB
2018-06-18 22:01:32.462016-0400 [12903:3621137] ::discovered peripheral Odyssey 42D64620-8B30-F946-F4CA-ABB378A6535F
2018-06-18 22:01:32.537592-0400 [12903:3621137] FloBLE Plus Peripheral Connected
2018-06-18 22:01:32.630488-0400 [12903:3621137] ::discovered peripheral [TV] UN50JU6500 1F204446-7B4A-4CB6-8BC0-46ED443AF234
2018-06-18 22:01:32.642655-0400 [12903:3621137] ::discovered peripheral Odyssey 42D64620-8B30-F946-F4CA-ABB378A6535F
2018-06-18 22:01:32.648525-0400 [12903:3621137] ::discovered peripheral Odyssey 42D64620-8B30-F946-F4CA-ABB378A6535F
2018-06-18 22:01:32.665862-0400 [12903:3621137] ::discovered peripheral (null) 034F2260-1C70-AC38-A18D-8163FB08E6BF
2018-06-18 22:01:32.986577-0400 [12903:3621137] Did discover service
2018-06-18 22:01:32.989737-0400 [12903:3621137] Reader Detected
2018-06-18 22:01:33.676810-0400 [12903:3621137] Peripheral Successfully Attached
2018-06-18 22:01:33.737430-0400 [12903:3621137] EscapeResponse <e1000045 0074ceb4 4f5d636e 60eb2f3b 514e345b a0>
2018-06-18 22:01:33.827273-0400 [12903:3621137] EscapeResponse <e1000046 0088539b 30ca5994 867f6298 3360ac17 d0>
2018-06-18 22:01:33.827388-0400 [12903:3621137] Peripheral Successfully Authenticated
2018-06-18 22:01:33.916895-0400 [12903:3621137] Firmware: FWV 1.17.00
2018-06-18 22:01:33.976423-0400 [12903:3621137] Hardware: HWV 1.03
2018-06-18 22:01:34.036698-0400 [12903:3621137] Serial Number: RR431-003632
2018-06-18 22:01:34.037652-0400 [12903:3621137] Verfied Pro license
SAL-9000	2018.06.18.22.01.34	RFID	Device	RR431-003632
2018-06-18 22:01:34.303785-0400 [12903:3621239] Escape APDU:E0 00 00 48 04
2018-06-18 22:01:34.366408-0400 [12903:3621137] EscapeResponse <e1000000 0104>
2018-06-18 22:01:34.542408-0400 [12903:3621199] Escape APDU Semaphore timeout
2018-06-18 22:01:34.542571-0400 [12903:3621219] Escape APDU Semaphore timeout
2018-06-18 22:01:34.544239-0400 [12903:3621220] Escape APDU Semaphore timeout
2018-06-18 22:01:34.620385-0400 [12903:3621220] Escape APDU:E0 00 00 20 01 03
2018-06-18 22:01:34.666388-0400 [12903:3621137] EscapeResponse <e1000000 0103>
2018-06-18 22:01:34.803898-0400 [12903:3621220] Escape APDU:E0 00 00 49 03
2018-06-18 22:01:34.803966-0400 [12903:3621219] Escape APDU:E0 00 00 62 03 00 00 00
2018-06-18 22:01:34.804429-0400 [12903:3621220] Escape APDU:E0 00 00 40 01

June 19, 2018 at 3:10 am #63200

Scott

Keymaster

Hi Hal,

Your update steps are correct, you will also need to add it to Embedded Binaries in the your project settings if Xcode doesn’t do it for you.

Try updating the SDK again now and it should connect more reliably.

Scott

June 19, 2018 at 9:05 am #63202

Hal

Participant

Hey Scott,

Thanks. I just re-downloaded the SDK using the same link that was sent in the email dated 6/18/18 8:11 AM – let me know if I should be using a different link.

Now, my application reliably connects to the reader IF the reader is turned off, the application is started, and the reader is turned back on.

If I have both the app and the reader running, everything looking good, then stop and restart the app, it does not reconnect to the reader.

Below is the log from when both the app and the reader were running fine, I stop / restart the app, and the app does not reconnect to the reader.

This seems similar to the issue reported by Sweet in post https://flomio.com/forums/topic/device-connection-issues/

Thanks for being so responsive on this!

2018-06-19 09:00:51.186096-0400 [14508:3766702] ::centralManagerDidUpdateState supports 5
2018-06-19 09:00:51.186737-0400 [14508:3766702] CBCentralManagerStatePoweredOn
2018-06-19 09:00:51.232600-0400 [14508:3766702] ::discovered peripheral Odyssey 42D64620-8B30-F946-F4CA-ABB378A6535F
2018-06-19 09:00:51.254961-0400 [14508:3766702] ::discovered peripheral ACR1255U-J1-003632 C59F20F6-0AEF-EA4C-9FC5-A588652BF3D3
2018-06-19 09:00:51.295896-0400 [14508:3766702] ::discovered peripheral (null) 2602B0DA-2D3D-415D-EACE-449307DFCC59
2018-06-19 09:00:51.322471-0400 [14508:3766702] ::discovered peripheral (null) A5417636-1666-81A2-E1F8-667EFC8B3640
2018-06-19 09:00:51.325362-0400 [14508:3766702] ::discovered peripheral (null) 8F6F68C7-DEDE-545A-A9C3-04869077168D
2018-06-19 09:00:51.336911-0400 [14508:3766702] ::discovered peripheral (null) 9D5D8863-C9D2-BBA2-4AEE-D0556D3CEDCC
2018-06-19 09:00:51.342251-0400 [14508:3766702] ::discovered peripheral (null) 5B102BB0-2A5E-838B-DF41-17E2F02389D3
2018-06-19 09:00:51.369923-0400 [14508:3766702] ::discovered peripheral (null) 7DAA3AEA-D023-FA37-1B01-CC4B01C57159
2018-06-19 09:00:51.388668-0400 [14508:3766702] ::discovered peripheral (null) 5FA08C74-9664-472B-5E22-0978AD6DBFBA
2018-06-19 09:00:51.411986-0400 [14508:3766702] ::discovered peripheral Odyssey 42D64620-8B30-F946-F4CA-ABB378A6535F
2018-06-19 09:00:51.523142-0400 [14508:3766702] ::discovered peripheral (null) 0A42DD77-A61D-CACE-6138-25EA8F94FE69
2018-06-19 09:00:51.526420-0400 [14508:3766702] FloBLE Plus Peripheral Connected
2018-06-19 09:00:51.583448-0400 [14508:3766702] ::discovered peripheral Odyssey 42D64620-8B30-F946-F4CA-ABB378A6535F
2018-06-19 09:00:51.595749-0400 [14508:3766702] ::discovered peripheral Odyssey 42D64620-8B30-F946-F4CA-ABB378A6535F
2018-06-19 09:00:51.606024-0400 [14508:3766702] ::discovered peripheral Odyssey 42D64620-8B30-F946-F4CA-ABB378A6535F
2018-06-19 09:00:51.648802-0400 [14508:3766702] ::discovered peripheral Odyssey 42D64620-8B30-F946-F4CA-ABB378A6535F
2018-06-19 09:00:51.832264-0400 [14508:3766702] ::discovered peripheral Odyssey 42D64620-8B30-F946-F4CA-ABB378A6535F
2018-06-19 09:00:51.915121-0400 [14508:3766702] Did discover service
2018-06-19 09:00:51.916516-0400 [14508:3766702] Reader Detected
2018-06-19 09:00:52.638514-0400 [14508:3766702] Peripheral Successfully Attached
2018-06-19 09:00:52.697104-0400 [14508:3766702] EscapeResponse <e1000045 008c553c 29b3e99e 30b26026 d50c88c7 dc>
2018-06-19 09:00:52.787861-0400 [14508:3766702] EscapeResponse <e1000046 000e15f7 76db601e e549719b b4c6dcc3 de>
2018-06-19 09:00:52.788099-0400 [14508:3766702] Peripheral Successfully Authenticated
2018-06-19 09:00:52.851072-0400 [14508:3766702] Firmware: FWV 1.17.00
2018-06-19 09:00:52.906002-0400 [14508:3766702] Hardware: HWV 1.03
2018-06-19 09:00:52.966549-0400 [14508:3766702] Serial Number: RR431-003632
2018-06-19 09:00:52.968772-0400 [14508:3766702] Verfied Pro license
2018-06-19 09:00:53.232300-0400 [14508:3766805] Escape APDU:E0 00 00 48 04
2018-06-19 09:00:53.299608-0400 [14508:3766702] EscapeResponse <e1000000 0104>
2018-06-19 09:00:53.482757-0400 [14508:3766751] Escape APDU Semaphore timeout
2018-06-19 09:00:53.483083-0400 [14508:3766807] Escape APDU Semaphore timeout
2018-06-19 09:00:53.493013-0400 [14508:3766804] Escape APDU Semaphore timeout
2018-06-19 09:00:53.573412-0400 [14508:3766804] Escape APDU:E0 00 00 20 01 03
2018-06-19 09:00:53.656793-0400 [14508:3766702] EscapeResponse <e1000000 0103>
2018-06-19 09:00:53.748598-0400 [14508:3766807] Escape APDU:E0 00 00 49 03
2018-06-19 09:00:53.748656-0400 [14508:3766804] Escape APDU:E0 00 00 62 03 00 00 00
2018-06-19 09:00:53.749844-0400 [14508:3766807] Escape APDU:E0 00 00 40 01

June 19, 2018 at 3:26 pm #63204

Scott

Keymaster

Hi Hal,

When you say “stop and restart the app”, what do you mean exactly?
Are you just pressing the Home button or are you double tapping the Home button and swiping the app up (in other words, putting the app in the background, or closing it).

If you are closing and restarting the app, there shouldn’t be an issue with reconnecting and that’s a issue, I can’t seem to recreate it here.

If you are going into the background, you should use startReaders and stopReaders to control the reader, you should not reinitialize the FlomioSDK upon reopening your app.

Let me know the above info and I can help fix it for you.

June 19, 2018 at 3:56 pm #63207

Hal

Participant

Hey Scott –

I am running the app from Xcode and when I say “closing” and “restarting”, I mean I am stopping the run from Xcode and then clicking “Run” to start it again. In this case it does not reconnect to the reader, but on the older version of the SDK this worked fine.

For my application it doesn’t make sense to ever put it in the background so I haven’t done that.

I’m going to insert a startReader right after the app starts and it initially “sees” the device..not sure this would do anything or is / should be required but I’ll let you know how it goes. Let me know if there’s anything I can provide that would be helpful.

Thanks!

June 19, 2018 at 4:05 pm #63208

Hal

Participant

OK, performing a startReader on didChangeStatus definitely seems to make it reconnect more reliably in cases where I have stopped my app from Xcode and restarted it, esp if I wait about 5-10 seconds between the start/stop..

June 20, 2018 at 4:16 am #63214

Scott

Keymaster

Hi Hal,

Glad you have something working. I will continue to investigate the issue you are seeing, I have not seen this issue before and am having trouble recreating it.
You should also update your SDK again and let me know if your issue persists.
I have emailed you a link to the Pro SDK.

Kind Regards,
Scott

June 20, 2018 at 8:52 am #63215

Hal

Participant

Morning Scott!

Thanks for the update late last night / early this morning (do you ever sleep?). This version of the framework appears to fix the connection issue, and the startReaders command is no longer required.

Thanks again!

June 20, 2018 at 3:27 pm #63219

Scott

Keymaster

Glad it’s all sorted!

Author

Posts

Viewing 13 posts - 1 through 13 (of 13 total)

The topic ‘Reader connects but does not respond to tags’ is closed to new replies.

Reader connects but does not respond to tags

Forum Statistics

Recent Replies

140 CHAR WISDOM!