I'm trying to communicate with a bt module. It uses AT commands, but i'm unable to send all of them. I connected to the module (UART in transparent bridge), it responses correctly to the initial AT command, but i can't send anyother command:
if you i try to send, for example, AT+VERSION.. it always answers OK, because only gets the AT not the +VERSION. I tried to modify some settings related to the way the data is sent in teraterm but.. the same result.
is there an example of AT communication using BP? I need to send complete AT commands, with parameters...
Thanks.
Edited:
I could (i won't call it success xD) send some AT commands but in binary (normal UART communication), what means i had to code and decode the sent/received data in ascii and hexadecimal. Really annoying. Is there a better way to do this? i checked the examples in the site but i didn't find anything suitable.
I write here because i don't which thread could be more suitable.
I was playing with servos and found this behaviour, trying to find if there was a way to send multiple positions in the PWM generator for servos was active, without getting out from it, which i don't know if it's ok (remember i was playing with options and commands to see a way to repeat the pwm pulses):
2WIRE>(0) 0.Macro menu 1.ISO7816-3 ATR 2.ISO7816-3 parse only 2WIRE>0 WRITE: 0x00 2WIRE>S90 PWM disabled Servo active 2WIRE>90 WRITE: 0x5A 2WIRE>S 90 PWM disabled [b]Servo active[/b] <= (1) 2WIRE>S -90 PWM disabled [b]Position in degrees[/b] <= different behaviour than the previous point (1)
(90)>10 Servo active [b]WRITE: 0x5A[/b] <=== ?????????? it doesn't appear when using normally just in this case
Well, the servo worked fine in all situations, but the messages in the serial terminal were these ones. Because i have the BP since some days ago, i can't say if these messages are ok or not, anyway they aren't consistent.
This encourages me to ask if there is a way to send multiple positions to the servo once the servo is active, something like:
Here the servo is powered and stable with the PWM, but.. i can't send any other position. I have to get out from the PWM mode and re-enter. It would be nice if i could do something like:
... to generate 3 different positions without getting out from the Servo pwm generator. It'd be handy in the BP.
Also i noticed you can enter in the Servo mode from the 1-WIRE mode (it's not specified in the documentation).
am i wrong or there is some issue with the messages? is possible to generate different pulses without getting out from the PWM generator? if not, could it be added in future firmware releases?
i bought recently a BP3b -Firmware v5.10 (r559) Bootloader v4.4- and i tried to generate pwm signal but.. i always receive the message "Command not used in this mode" (i read the doc in wiki and followed the examples i saw, did some search in forum, and.. well i couldn't find anything interesting).
Some makeup points and some wrong behaviour in the client (0.9.3 SP1)
1- Replacing the client window's upper left logo (icon) for something nicer than the java default icon.
2-Saving preferences. They aren't stored from a session to other. I suggest storing them in xml format or just a .ini file.
3- I noticed a crash:
Connect the OLS device Open client. Capture any stream with Toolbar icon. Disconnect the device File -> New Project (loose changes). Capture data with toolbar icon. Then the client closes.
Sol: i think it's due to a unhandled exception (or an error condition) because it assumes the device is already connected when it's not. Well only guessing because i haven't seen the code.
4-No autodetection of the com:
Open client with OLS disconnected Try to capture data.
You'll notice you can't because it doesn't let you select the COM port. The autodetection only works if the OLS is connected before the client startup.
Sol: refresh the list of com ports each time the capture window is opened, but not forgeting the last one selected in the current session
These "errors" are systematic and repeatable under these conditions. If i detect some more issues i'll report them.
I never tested this feature (internal test), so i'm not sure if it's ok or not... but it does't match the results i saw in the tutorial videos. Also remark the noise in channels 3, 7 and 9. I have repeated the test with the same results. Other tests, changing the sample rate, etc. gave the same results with these channels: noise in 3, 7 and 9 (or what i interpret as noise). I'm using a IDE cable i had around here, just using one row of the pins. It's well attached and working, so i don't think it's the problem. Anyway i tested with standalone probes and they gave the same problem in the signals... so it's not the wires.
Resume:
Are the test signals correct? They don't match the signals i saw in the demostrative video (pairs of 2 different frecuency signals). Why noise in channels 3, 7 and 9?
UPDATED:
Misterioysly the channel 5 is ok now and doesn't show the signal in the image. I noticed the noise now appears in channels 5, 7, 9. 7 and 9 are constant in all tests i did. Also noticed the noise depends on the sample rate (avoiding a possible problem in the visualisation in the software client), the lower the sample is rate is, the less probable the noise appears, and the 20Mhz rate looks like a frontier. With 20Mhz it looks unestable (sometimes there's noise sometimes not). Below 20Mhz things get better, but i still notice some noise in isolated channels (always 5, 7 or 9). Surprisingly with 50Mhz i have the same result (some glitch in channel 7), but it's really bad in 100mhz. I repeated the tests with each sample rate...
Background: I received the sniffer today and tried updating the firmware. It was working nice. I tried updating the firmware, at least checking how it's done. While, i was looking some information with so bad luck that i clicked on the firmware folder, just over the file "OLS-erase.bat". Then the sniffer stopped working and was disconnected. I read the MSDOS widnows and it looks the pic was erased (i checked the .bat and fw_update.exe options to confirm it).
It doesn't work now, and Windows doesn't enumerate it when connected. Only PWR LED is on. If you push the UPDATE button then RESET once some seconds, the TRIG LED lights, but as soon as you release the RESET the TRIG LED goes off again. Neither ACT or ARM work.
I guess that the PIC flash has been deleted... i think it's recoverable reprograming the pic (i have a pic programmer), but i need to be sure of what happened before making things worse.
Any suggestion what happened and how i could recover it? I'm not sure the steps to follow because all i read is about the Bus Pirate (i haven't it).
Quote
OLS info: v1.04 16Mhz Xtal
At least i could enjoy the OLS 5 minutes... :/
PS: my PIC programmer isn't able to program 3.3V devices -only 5V devices-, and i think the 18J used in the OLS needs 3.3V -but not sure-. Could confirm it?
