i am having problem in burning my hex file to my pic18f4550. I use a PicKit 3 with MPLab X IPE v5.25. MPLab can detect the PICKit 3 since it displays the serial number. But when i try to connect with the PIC device, it shows me an error "Connection Failed". I have tried it with other computers and it works. Any ideas how will i make it work in my laptop? Every idea is appreciated.
Related
I have a problem with my new bluetooth HC-05 module. In AT-mode it works perfectly with all commands that I need... exept INQ.
I have tried to send whole bunch of other commands beforehand:
AT+INIT
OK
AT+ORGL
OK
AT+ROLE=1
OK
AT+CLASS=0
OK
They all are working just fine. I tried to change IAC and INQM settings as well... but the answer from module is always the same:
AT+INQ
ERROR:(1F)
I read related topic here and tried to push the button at HC-05, as it recommended there, but -- no result either.
I have three modules from the same shop, and they all are working the same way
I have a HC-05 with 3.0-20170601 that I managed to bind to a slave last night. It turns out that the v3 has two AT-modes.
The first is when you hold the button while you connect power. The led will blink slowly and you can connect at 38400 baud. But this is like a configuration mode, where AT+INQ is not available.
In this mode I did these commands:
AT
AT+UART
AT+RMAAD
AT+ROLE=1
(Press and hold the button)
AT+RESET
(Release the button after device restarts and led is slowly blinking)
AT+CMODE=1
AT+INQM=0,5,5
AT+PSWD="9999"
AT should give OK as answer to know connection is working
AT+UART will show configured baudrate. Default is 9600.
AT+RMAAD clears all saved connections
AT+ROLE=1 sets it as master
AT+RESET restarts the device to change to master
AT+CMODE=1 accepts all kinds of devices
AT+INQM=0,5,5 inquires in standard mode, with 5 max connections or 5 secs
AT+PSWD="9999" sets the pin code 9999, change to the pin you need
After this it is time to update the arudino code so that it connects to the configured baud rate. It will be something like
BTSerial.begin(9600);
...or what ever value you might have set the baud rate to. Then reflash your arduino.
Now enter the very irritating second AT command mode.
Power up without holding the button. You will get the fast blink speed. When its powered up, press and hold the button. The led will continue blinking fast, but while the button is pressed you can now connect to the device on the configured baud rate. So open the serial monitor and type AT to verify.
Remember that the mode is only active while the button is pressed. So keep it pressed. I had a small clamp I put on there.
Then I entered these commands:
AT+STATE
AT+STATE will show current state, should be inquiring
Then power up the slave device and the adress should start popping up. It will be something like xyz:xy:xyzw,931F00,7FFF
The first part is the address you want (xyz:xy:xyzw)
Change : to , and get xyz,xy,xyzw
Check that you connecting to the correct device
AT+RNAME?xyz,xy,xyzw
Then bind
AT+PAIR=xyz,xy,xyzw,5
AT+BIND=xyz,xy,xyzw
AT+LINK=xyz,xy,xyzw
The AT+LINK command gave me FAIL as output. But it did not matter.
I restarted and did not press any button before or after. Just normal start.
After 5-10s serial data showed up in my serial monitor.
Modules are bound. And will automatically connect at power up. If not you might have the wrong pincode. Make sure to change 9999 above to 0000 or 1234 or what ever it may be. When I hade the wrong pin I still got OK from the AT+PAIR and AT+BIND commands... It didnt work for me until I entered the correct pin.
Sorry for long post, but I wanted to be thorough since info about HC-05 v3 is very scarce on the internet right now.
A reference to all commands can be found here:
http://www.electronicaestudio.com/docs/istd016A.pdf
(Link valid 2018-08-13)
We have same problem and you can see the answer in here.
The conclusion of problem is about the firmware on HC-05 you use. If you use firmware version 3.0, you will get error 1F in AT+INQ. Maybe HC-05 with firmware version 3.0 has different parameters to run AT+INQ. Now I'm confused about how to find HC-05 with firmware version 2.0. That HC-05 have push button or not.
In short, the answer is: The (B) module with firmware version 2.0-20100601 works ok with the following commands (set PIN34 high at power-up, or press button on module and keep pressed during commands).
So HC-05 with version 2.0 use push button or not, it's the same.
If you have some information about the different between HC-05 version 3.0 and version 2.0, please let me know.
I am running windows 8(64) and am using Arduino Uno for the first time. I downloaded the IDE and plugged in my arduino. I'm using a IMU 6050 Accelerometer Gyroscope Breakout Board and am using the first MPU6050 DMP6 example program to test it out. I open up the serial monitor and instead of displaying the text like it should, it only displays a line of weird symbols(cross,box, y with a dot over it, Germanic alphabet letters) and then nothing else. I am brand new to ardruino and can't figure out what to do. I checked the Uno driver and everything is fine. All the arduino files are downloaded, I have downloaded both the MPU library as well as the I2C library. The Uno is blinking, the data is coming through (I think) for some reason its just not displaying right. I have been searching all over the web for days now and I can't find anyone with the same problem.
It sounds like a baud rate mismatch issue. Try to change the baud rate from the drop-down and make sure that it matches the rate passed to Serial.begin in your sketch.
Sony xperia z1
Are Sony working on a fix for the broken camera problem when unlocking the bootloader of Xperia z1?
any estimate of arravial of such an fix?
Same problem here.
For now, you can just root on .534 then upgrade to .257
Use vRoot on .534 then with SuperSU Pro use OTA survival mode and upgrade to .257 with OTA.
If you unlock the bootloader, your DRM keys will be lost, so the camera will stop working correctly (no auto focus, etc.)
Unfortunatly, there is no way to flash a custom kernel without losing the camera functionality.
Tried also to contact sony, but the support for developers is a bit dead.
I've just purchased an Opticon F31 2D barcode scanner for use in a cocoa mac application as a USB Serial device.
We've used the NLV 2101 and scanned the C01 barcode from the universal manual which works, but the F31 always gives back a bad scan error and stays in HID mode (acts as a keyboard). Have I bought the correct scanner or is this one faulty?
It turns out that the command code to switch the scanner to VCP mode doesn't work on the F31. You need to use the barcodes on the following URL to switch between VCP and HID mode.
http://wiki.opticon.com/index.php/2D_Scanner_USB_Default
We have the Zebra TLP 2824-Z Plus label printer (ZLP). We recently purchased it, installed the driver and software successfully, and calibrated successfully (held button down at solid green, got single blink then double blink, and then released the button). We went to Zebra and retrieved the updated drivers (certified) and installed them (fyi have tried with and without these drivers - will do nothing without them).
The system it is installed on via USB is a Windows XP Pro 32-bit SP3.
Immediately after configuration, it will do a test print, and let us send the command to feed a label. If we try to print configuration or anything else, to include printing actual labels, it prints two labels/pages, stops, and then blinks red. If we lift the top off and put it down, it blinks green until we press the button. At that time, it will feed about 2 to 3 inches of labels and then print one label. The process repeats indefinitely until we uninstall the printer.
No, clearing the documents will not stop it. A hard reset will not stop it. The only way to get it to do anything else is to uninstall it and start all over again.
How do we fix this issue so we can get a configuration or just print our labels? Or, better yet, what are we doing wrong and how do we do it right? Our last printer worked fine with the exception that they stopped making the labels we used with that printer.
The drive sends down an initialization sequence for the printer based on the settings in the Printer Preferences. If, for example, your Printer preferences say that the printer is Thermal mode instead of direct thermal, the driver will send down the command to set the printer to Thermal mode (Ribbon). If your printer is printing Direct Thermal, and has no ribbon physically installed, the printer will think it is in an error mode with no ribbon. This could cause the issue you are seeing.
Ensure that your Printer Preferences are accurate to your printer's configuration, or disable the initialization sequence in the driver
Yes. Just make sure all the settings are correct.