Richard already covered it but it seems to have been overlooked.
The duty cycle register is 10bit wide but, as Ioannis says, the usable number of bits differs depending on the PWM period. The...
Type: Posts; User: HenrikOlsson; Keyword(s):
Richard already covered it but it seems to have been overlooked.
The duty cycle register is 10bit wide but, as Ioannis says, the usable number of bits differs depending on the PWM period. The...
As long as both variables are of the same size adding a two's compliment value to another is the same as subtracting the absolute value of one from the absolute value of the other.
In these...
PBP command SEROUT2 can handle flow control.
With that said I've never needed to use it with OpenLOG but it depends on how much data and at what speed you you're trying to log.
Have you measure what clock speed you're getting?
Standard "high speed" I2C clock is 400kHz, maximum clock speed of a Microchip 24C256 when run at >2.5V is 1MHz.
SPI-interface flash chips usually...
No.
SSPBUF is the Synchronous Serial Port Receive Buffer/Transmit Register. It's the name of register to/from which you write/read whatever gets shifted out.
I'll just point to MELABS: https://melabs.com/samples/PBP-mixed/spimast.htm That example is what I used as a basis when I first used the MSSP module for SPI (for interfacing the W5100 (search the...
Oh, you don't want to limit yourself to the hundreds of available 18F series devices so your contemplating using old parallell I/F EEPROMs instead, needing so many I/O-lines that you'll probably have...
Oh, you don't want to limit yourself to the hundreds of available 18F series devices so your contemplating using old parallell I/F EEPROMs instead, needing so many I/O-lines that you'll probably have...
Store the font data in program memory instead.
It depends on what you're doing with the number(s).
If your displaying them using LCDOUT/SEROUT/HSEROUT/ARRAYWRITE you can use the SDEC modifier to display the value 65535 as -1.
If you're doing...
Yes. SEROUT, SEROUT2 or HSEROUT/HSEROUT2 is what you want.
No extra hardware needed.
The easiest way is to put a config.txt, containing your desired options, on the SD card. See the Configuration File section of the tutorial.
Again, for simple datalogging type applications there's really no need for any sample code. Just send it ASCII data over a UART line and it will write it to a .txt file on a microSD card. It CAN do...
For data logging type applications I've had great success with the OpenLOG. Just send it ASCII data over a UART line and it will write it to a .txt file on an microSD card.
No, I don't see anything wrong with that code. Have you tried increasing the delay between packages?
Since you don't say which Bluetooth module you're using I can't tell what size the buffer is but if you keep feeding that buffer faster than the module is able to send the data out over the air it...
No, that can't be it.
SEROUT and SEROUT2 are bitbanged routines so they don't use the (E)USART and therefor not the TXREG. HSEROUT does use the (E)USART but its smart enough to pace itself as to not...
There's a list of supported devices available here: https://pbp3.com/devicelist.html and it lists the 12LF1252. Microcode Studio populates the list of microcontrollers from the available...
Yes, the datasheet specifies INT pin input high or low time: Minium 25ns so should be no problem with 1us. Question then becomes how much latency you can accept, how fast do you need to "react" on...
You didn't miss anything. My point is basically that it's not as simple as just telling the compiler to count the number of GOSUB and RETURN statements and generate an error they don't match.
You can have one entry-point (Label) and multiple exit points (Returns) or multiple entry-points (Labels) and a signle return. Both are valid and very useful. For example, my SK6812 RGBW LED code...
No, you're forgetting the stop-bit! You have 1 startbit, 8 databits and 1 stopbit.
In your diagram, from left to right: First you have the start-bit (1), then you have 8 data-bits (11000010), then...
Because at 2400 baud ~420us of that 0.92ms is the normal stopbit. Add to that the additional character pacing of 500us.
At 2400 baud you'd also get the same result by specifying two stop-bits.
Bit timing seems to be in the ballpark for 2400 but apparently the PICAxe has quite a bit of delay between each byte (usually not what you want to see). If the display(s) do work with the PICAxe and...
Enlighten me please, displaying word vars obviously worked for me. Was there then a change that broke it which has now been fixed or what actually happened here.
Anyway, glad you got it going and...