ftp corrupting AIRcable.bas on transfer

[mccgregor]

Hi, I use an AIRcable SMT as a device to control the door access to a room.

This has worked for many months (probably 2 years or more), and I have been able to control the users able to access the room by modifying the list of Bluetooth addresses in the AIRcable.bas.

in the past few months I have noticed that the code is being corrupted.

I use a Windows XP PC with a BT dongle to contact the AIRcable (in fact this hasn't changed since I first started) using Microsoft's My Bluetooth Places... to ftp. After looking on your website I tried using obexftp.exe with exactly the same results.

The file 'corruption' is limited to the 20 lines of numbers I use.

Here is what I transmit: (missing out lines 102 onwards)

@INIT 100

@IDLE 400

@SLAVE 430

@MASTER 0

@PIN_CODE 440

@PIO_IRQ 0

@INQUIRY 0

@MESSAGE 0

@CONTROL 0

@SENSOR 0

@ALARM 0

@UART 0

@FTP 0

1 111111111111

2 222222222222

3 28987BCC58DF

4 0019860029B1

5 555555555555

6 666666666666

7 777777777777

8 001F81000100

9 999999999999

10 101010101010

11 111111111111

12 002109f1a056

13 28987BCC58DF

14 0023763AA868

15 001CCCABB8FB

16 0022A5C494A5

17 28987BCC58DF

18 001F81000100

19 0019860029B1

20 28987BCC58DF

100 A=pioout2

101 A=pioout9

 

and this is what I get why I download it back from the Siteplayer:

 

@INIT 100

@IDLE 400

@SLAVE 430

@MASTER 0

@PIN_CODE 440

@PIO_IRQ 0

@INQUIRY 0

@MESSAGE 0

@CONTROL 0

@SENSOR 0

@ALARM 0

@UART 0

@FTP 0

1 3ñ111 3°±%1

2 000p22222:00

3 28yp·BC58@F

4 091y860029B1

5 5555545±551

6 626>46666646

7 7?u76773777

8 001v91000180 08

9 9991119999

10 101010101°10€!0

11 0±11±±11)111 11 [1]

12 002109f5a056€56

13 28987@Cµ8DF

14 082376;AA868

15 001CCCARB8FB

16 0022A5C494A5

17 28987BCC58dF

18 001F81000000

19 0019960029B1

20 20987BC58DF

100 A=pioout2

101 A=pioout9

 

It is as if the numbers are interpreted as control codes (BEL, ATX etc.)

Is it because I need to invoke a binary ftp someway?

Oddly, the 'corruption' isn't entirely consistent and predicable and seems to have worsened over the last few weeks as I have moved numbers to avoid them being ignored.

Any assistance would be greatly appreciated.

Thanks

Greg

[Juergen Kienhoefer]

Hi Greg,

Hm, the memory is an eeprom which is limited to a few hundred thousand writes.
Any chance you did that many? Writing to variables $1... count too.

If this is the case that the first sector of the eeprom is shot, you can start
later avoiding lines 1-16 or so.

I have seen only one or two examples ever that had this problem. We used
the solar controller to write data into the eeprom every few minutes. It did
not last more that 2 years.

Hope that helps
Juergen
Wireless Cables Inc.

> --
> You received this message because you are subscribed to the Google Groups
> "AIRcable(tm)" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/aircable/-/nIZXkqQOMvIJ.
> To post to this group, send email to airc...@googlegroups.com.
> To unsubscribe from this group, send email to
> aircable+u...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/aircable?hl=en.

[McCAWLEY Gregory C]

Thanks for your speedy reply Juergen, that seems like a strong possibility - I'll look into this (when I get back from holiday!).

:o)

It's a long time since I programmed this device can you remind me - how do I direct it to not use those suspect areas of memory?

Thanks and Best Regards

Greg

The information in this email is confidential and is intended solely for the addressee. Access to this email by anyone else is unauthorised.

If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, except for the purpose of delivery to the addressee, is prohibited and may be unlawful. Kindly notify the sender and delete the message and any attachment from your computer.