AT Commands missing..?

Hey all,

I picked up a cheap AT-09 BLE module from ebay, from ebay. I also grabbed an Arduino 33 BLE, with the broad idea of sending data from the IMU there over to another arduino, which is then going to control some servo motors.

I've got the rest of it working, i.e. the IMU -> orientation conversion, and the servo control, however I can't seem to get the two BLE modules to talk to each other. The 33 BLE is set up as a peripheral device, and is posting its data just fine (I can read this from my phone). The AT-09, on the other hand, seems off.

I've popped it into master role, which should have it acting as a central device, right? After that, here's the result of the AT+HELP command:

22:29:45.697 -> Sketch:   /Users/wildjames/Documents/Arduino/BT_setup/BT_setup.ino
22:29:45.769 -> Uploaded: Jun 17 2020
22:29:45.769 ->  
22:29:45.769 -> BTserial started at 9600
22:29:45.804 ->  
22:29:55.588 -> >AT+HELP
22:29:55.622 -> ********************************************************************
22:29:55.725 -> * Command             Description                    *
22:29:55.826 -> * ---------------------------------------------------------------- *
22:29:55.929 -> * AT                  Check if the command terminal work normally  *
22:29:56.031 -> * AT+RESET            Software reboot                *
22:29:56.132 -> * AT+VERSION          Get firmware, bluetooth, HCI and LMP version *
22:29:56.233 -> * AT+HELP             List all the commands                  *
22:29:56.333 -> * AT+NAME             Get/Set local device name                    *
22:29:56.435 -> * AT+PIN              Get/Set pin code for pairing                 *
22:29:56.536 -> * AT+BAUD             Get/Set baud rate                          *
22:29:56.637 -> * AT+LADDR            Get local bluetooth address        *
22:29:56.740 -> * AT+ADDR             Get local bluetooth address        *
22:29:56.840 -> * AT+DEFAULT          Restore factory default             *
22:29:56.942 -> * AT+RENEW            Restore factory default            *
22:29:57.047 -> * AT+STATE            Get current state                  *
22:29:57.118 -> * AT+PWRM             Get/Set power on mode(low power)           *
22:29:57.219 -> * AT+POWE             Get/Set RF transmit power          *
22:29:57.321 -> * AT+SLEEP            Sleep mode                         *
22:29:57.422 -> * AT+ROLE             Get/Set current role.                      *
22:29:57.523 -> * AT+PARI             Get/Set UART parity bit.                     *
22:29:57.623 -> * AT+STOP             Get/Set UART stop bit.                       *
22:29:57.725 -> * AT+INQ              Search slave model                           *
22:29:57.830 -> * AT+SHOW             Show the searched slave model.               *
22:29:57.931 -> * AT+CONN             Connect the index slave model.               *
22:29:58.032 -> * AT+IMME             System wait for command when power on.     *
22:29:58.136 -> * AT+START            System start working.              *
22:29:58.236 -> * AT+UUID             Get/Set system SERVER_UUID .                 *
22:29:58.338 -> * AT+CHAR             Get/Set system CHAR_UUID .                   *
22:29:58.438 -> * -----------------------------------------------------------------*
22:29:58.539 -> * Note: (M) = The command support master mode only.                *
22:29:58.640 -> * Copyright@2013 www.cyobd.com.   All rights reserved.        *
22:29:58.740 -> ********************************************************************
22:30:02.599 -> >AT+VERSION
22:30:02.633 -> +VERSION=Firmware V4.2.0,Bluetooth V4.0 LE
22:30:49.838 -> >AT+CMODE
22:31:02.395 -> >AT+CMODE?
22:31:07.460 -> >AT+INQM
22:31:07.460 -> OK
22:31:07.460 -> +INQS
22:31:11.494 -> +INQE
22:31:11.494 -> Devices Found 0

Note the lack of an AT+CMODE command! The AT+INQM should report the INQ mode, not start searching... Also, it should at least pick up some device, since I'm sat next to my phone, my wife's phone, and the 33 BLE that is definitely transmitting!

The same things happen if I:

  • Hook the module up to the arduino and don't touch it
  • Hook it up and hold the button during power on
  • Tie pin 34 of the actual chip to +3.3V, and power on
  • Tie pin 34 to high, hold the button, and power on (can you tell I'm getting desperate?)

If I go to www.cyobod.com, it seems to have changed hands and now sells Chinese tyres, or something :( Not very helpful.

Has anyone come across this kind of problem before?