Search found 19 matches

Thanks a bunch Very Happy

The thing is that the unit is used in potentially "noisy" environment. I hope to fix the problem by replacing the current PIC with the one with dedicated data eeprom (like PIC16F17xx).

RTC is not necessary. I prefer the pin compatible PIC to avoid the changes in the hardware design.

Hi.

I added BORV25 without success (My bad overseeing this, anyway).

All of the chips on the PCB are decoupled with 100 nF capacitors.
Power supply has a proper common mode choke filtering (te ...

How was the PIC programmed ?
ICD-U64

Only one PIC with this problem ?
Multiple devices installed in identical units (refrigerant compressors). Some working without problems, some having the probl ...

It seems like large chunks of the program memory are being deleted after some time (hours). I am not sure what causes this. Could it be RF or an error in virtual eeprom write functions.?

Any ideas ...

Hi guys,

Can point anything in the code below that can cause communication stop or the PIC to stop executing the code:

Ok. Thanks. I will check.

Hi,

What would be a physical limitation for the code below in terms of how often the slave unit can be polled by the master ? Previously polling was once per second.
In the new setup polling occur ...

It worked fine. Thanks a lot!

I have up to date compiler 5.087

//////////////////////////////////////////////////////////////////////////////////////////
//// modbus_phy_layer.h ...

I have quite new PC running Win10.

I tried to alter the data array definition in modbus_rx structure to unsigned int16 but it messes up the CRC.

Thanks. Works fine for holding registers with offset 200.

Now I have a new problem (surprise!):

The input registers have offset 300.

300 = 0b000100101100
is read by slave as
43 =0b‭001010 ...

From the supplied modbus_phy_layer.h:

struct
{
unsigned int8 address;
unsigned int8 len; //number of bytes in the message received
function func; ...

I am compiling for PIC16F1518.