Hi Martin,
I have tried the way you suggested. Unfortunatly it doesnt work. It returns FF, FF
Delay is a typo, sorry. I have tried it with and without the delay and theres no change.
Im sure that i am just sending the data wrong to the device. I see a few others having the same problem when i ...
Search found 12 matches
- Wed Jul 14, 2021 10:41 am
- Forum: General
- Topic: BQ27441 - Incorrect data being returned
- Replies: 3
- Views: 4347
- Mon Jul 12, 2021 4:41 pm
- Forum: General
- Topic: BQ27441 - Incorrect data being returned
- Replies: 3
- Views: 4347
BQ27441 - Incorrect data being returned
Hi,
I am currently trying to get a BQ27441 to work properly.
The datasheet, is in my opinion pretty poor at explaining how its registers work. It refers to them as commands instead.
In any case, i have spent quite a few hours today, just trying to get it to output its own DEVICE_TYPE.
The first ...
I am currently trying to get a BQ27441 to work properly.
The datasheet, is in my opinion pretty poor at explaining how its registers work. It refers to them as commands instead.
In any case, i have spent quite a few hours today, just trying to get it to output its own DEVICE_TYPE.
The first ...
- Fri Jul 02, 2021 12:15 am
- Forum: Bug Reports
- Topic: Warning during compiling - Strings
- Replies: 2
- Views: 3548
Warning during compiling - Strings
Hi
I am getting the following warnings when compiling.
Can you guys tell me what the warnings are for, please.
v0.1.c:3890:2: warning: passing argument 3 of 'FCI_FLOAT_TO_STRING' discards 'volatile' qualifier from pointer target type [enabled by default]
C:\ProgramData\MatrixTSL\FlowcodeV9\CAL ...
I am getting the following warnings when compiling.
Can you guys tell me what the warnings are for, please.
v0.1.c:3890:2: warning: passing argument 3 of 'FCI_FLOAT_TO_STRING' discards 'volatile' qualifier from pointer target type [enabled by default]
C:\ProgramData\MatrixTSL\FlowcodeV9\CAL ...
- Thu Jul 01, 2021 9:37 am
- Forum: Bug Reports
- Topic: Software I2C odd behaviour
- Replies: 2
- Views: 3668
Re: Software I2C odd behaviour
Hi Ben
I have attached my flowcode file for you to take a look at. Its very much a work in progress so its a bit messy.
The sensor is the SI7020.
You will find the area where data is gathered in the SI7020_GET_DATA macro.
Unfortunatly there isnt a data ready flag, or at least not that i have seen ...
I have attached my flowcode file for you to take a look at. Its very much a work in progress so its a bit messy.
The sensor is the SI7020.
You will find the area where data is gathered in the SI7020_GET_DATA macro.
Unfortunatly there isnt a data ready flag, or at least not that i have seen ...
- Thu Jul 01, 2021 8:31 am
- Forum: Bug Reports
- Topic: Software I2C odd behaviour
- Replies: 2
- Views: 3668
Software I2C odd behaviour
Hi,
I am having an issue that i cant seem to narrow down. Thought it worth posting in case anyone else has a similar issue.
I am using PIC32MX575F256L
I have several sensors on I2C bus, using software I2C. So far i have an RTCC and Pressure sensor working perfectly.
A few days ago i started ...
I am having an issue that i cant seem to narrow down. Thought it worth posting in case anyone else has a similar issue.
I am using PIC32MX575F256L
I have several sensors on I2C bus, using software I2C. So far i have an RTCC and Pressure sensor working perfectly.
A few days ago i started ...
- Tue Jun 29, 2021 1:34 pm
- Forum: Bug Reports
- Topic: UART RXINT
- Replies: 3
- Views: 4281
Re: UART RXINT
Thanks Ben,
Tested and working as expected now.
Tested and working as expected now.
- Sun Jun 27, 2021 2:03 pm
- Forum: Bug Reports
- Topic: UART RXINT
- Replies: 3
- Views: 4281
UART RXINT
Hi,
I am trying to use the UART RX Interrupts.
When compiling i am getting errors.
v0.1.c:2557:10: error: '__IPC6bits_t' has no member named 'U1RXIP'
v0.1.c:2558:10: error: '__IPC6bits_t' has no member named 'U1RXIS'
v0.1.c:2635:2: error: Vector number must be an integer between 0 ...
I am trying to use the UART RX Interrupts.
When compiling i am getting errors.
v0.1.c:2557:10: error: '__IPC6bits_t' has no member named 'U1RXIP'
v0.1.c:2558:10: error: '__IPC6bits_t' has no member named 'U1RXIS'
v0.1.c:2635:2: error: Vector number must be an integer between 0 ...
- Fri Jun 25, 2021 10:45 am
- Forum: General
- Topic: PIC32MX575 @ 80MHz
- Replies: 5
- Views: 5184
Re: PIC32MX575 @ 80MHz
Good shout Kersing.
So, in order to get the serial to work, i am sending at 9600 from the PIC but receiving on the terminal at 4800. 2x slower
So heres what i have now set up.
8MHz crystal.
FLOWCODE CLOCK SPEED SET TO 80MHz
FPLLIDIV = DIVIDE BY 4
FPLLMUL = MULTIPLY 20
FPLLODIV = DIVIDE BY 1 ...
So, in order to get the serial to work, i am sending at 9600 from the PIC but receiving on the terminal at 4800. 2x slower
So heres what i have now set up.
8MHz crystal.
FLOWCODE CLOCK SPEED SET TO 80MHz
FPLLIDIV = DIVIDE BY 4
FPLLMUL = MULTIPLY 20
FPLLODIV = DIVIDE BY 1 ...
- Fri Jun 25, 2021 10:18 am
- Forum: General
- Topic: PIC32MX575 @ 80MHz
- Replies: 5
- Views: 5184
Re: PIC32MX575 @ 80MHz
More info.
I have tried to get the UART to work so i can output to terminal.
In both of the above setups, i receive jargon from the PIC. Suggesting again that timings are off.
I have tried to get the UART to work so i can output to terminal.
In both of the above setups, i receive jargon from the PIC. Suggesting again that timings are off.
- Fri Jun 25, 2021 9:57 am
- Forum: General
- Topic: PIC32MX575 @ 80MHz
- Replies: 5
- Views: 5184
PIC32MX575 @ 80MHz
Hi,
I am attempting to set up a PIC32MX575 @ 80MHz
I am using 8MHz crystal, so looking on other forums and the datasheet, i need to divide by 2and multiply by 20.
FPLLIDIV = DIVIDE BY 2
FPLLMUL = MULTIPLY 20
FPLLODIV = DIVIDE BY 1
FPBDIV = DIVIDE BY 2
Clock speed is set to 80MHz for timing ...
I am attempting to set up a PIC32MX575 @ 80MHz
I am using 8MHz crystal, so looking on other forums and the datasheet, i need to divide by 2and multiply by 20.
FPLLIDIV = DIVIDE BY 2
FPLLMUL = MULTIPLY 20
FPLLODIV = DIVIDE BY 1
FPBDIV = DIVIDE BY 2
Clock speed is set to 80MHz for timing ...