MCP3008 Lib to MCP3208

2021-04-01T08:02:55.074000Z

Wouldn't it be enough to shift 6 digits instead of only 4 digits and leave the code as it is?

//old / original code
//      aby[0] := 1;
//      aby[1] := 16#80 + SHL(usiChannel AND 7, 4);
//      aby[2] := 0;   
//changed code for MCP3208
        aby[0] := 1;
        aby[1] := 16#80 + SHL(usiChannel AND 7, 6);
        aby[2] := 0;   
//end of new code

      IF NOT transfer(pabyTxBuffer:=ADR(aby) , pabyRxBuffer:=ADR(aby) , udiLen:=3 , uiDelayus:=0) THEN
         _iState := 1000;
      END_IF
      ui := aby[2];
      ui := ui + (BYTE_TO_UINT(aby[1]) AND 2#1111) * 256;
      auiValue[usiChannel] := ui;

The Tx part has to be changed, because the transmitted data is shifted in relation to the 10-bit chip. But why do "AND 2#1111" to the received Rx part? Can you please explain?

I know for right now, that also the bit length is 12 instead of 10, with the MCP32 series. But the library for the MCP3202 don't have any other code for received data. Can anybody explain?

I did the changes mentioned in your post to a MCP3204 and didn't get some data put of it, yet. Everything I have to do additionally is to reduce the amount of channels from 0...7 to 0...3. The code in this section/method for the MCP3204 should look like this?

IF _iState = 10 THEN

    FOR usiChannel := 0 TO 3 DO
        aby[0] := 1;
        aby[1] := 16#80 + SHL(usiChannel AND 7, 6);
        aby[2] := 0;            

        IF NOT transfer(pabyTxBuffer:=ADR(aby) , pabyRxBuffer:=ADR(aby) , udiLen:=3 , uiDelayus:=0) THEN
            _iState := 1000;
        END_IF

        ui := aby[2];
        ui := ui + (BYTE_TO_UINT(aby[1]) AND 2#1111) * 256;
        auiValue[usiChannel] := ui;
    END_FOR     
END_IF

And additionally change the device description. Isn't it?

MCP3008 Lib to MCP3208

2020-05-18T09:53:16.842000Z

hello everyone, hope you are well.

I come back to you concerning the MCP3208,
after making the changes to go from MCP3008 to MCP3208, seen earlier in the post.
first, the modifications work well with the MCP3208, I receive many values of the chips.

my problem: I would like to use two MCP3208 chips.
I noticed that in the lib for MCP3008 or now MCP3208,
it is not possible to choose the hardware address, as it is possible to do for MCP23S17 chips.
and so I can only use one MCP3208 chip.

thanks for any help.

MCP3008 Lib to MCP3208

2020-02-27T15:26:01.378000Z

Originally created by: phenixrb

"[quote="I-Campbell"]Hi, phenixrb.
Did you install the device description to CODESYS using Tools > Device Repository? I copied your device description image out to file, then added it to my device repository, then it came up when I went to add a device to my master.

It looks OK."

HI I-Campbell,
thank you, i hadn't done that!
it works better now ....

I bought two MCP2308 chips, and now I have to test this in real life.
with a second activated SPI: SPI-1 with 2 CS, cs1.0 and cs.1.1
I keep SPI-0 for MCP23S17, with 1 CS,
since chips have physical addresses, 1 CS is sufficient.

Regarding FORGE, I'm going to look at how to make the driver available to others, it's new to me.
and above all I do not claim to have created the driver.
I took the explanations of the other participants on this post,
and I just did a program test on the raspberry.
also, comments are welcome.

MCP3008 Lib to MCP3208

2020-02-27T15:26:00.684000Z

Hi, phenixrb.
Did you install the device description to CODESYS using Tools > Device Repository? I copied your device description image out to file, then added it to my device repository, then it came up when I went to add a device to my master.

It looks OK.

Will you upload to forge?
I have already registered your device ID here:
https://forge.codesys.com/drv/io-drivers/database/Home/

Next step for you would be to :
1. register, then make a new io driver project here:
https://forge.codesys.com/drv/add_project
By convention, Either MCP3208 or SPI MCP3208 as the name, and mcp3208 as the URL
2. update the diver ID register (my first link of this post) to this newly created homepage url
3. Perhaps duplicate and reword the wiki from the MCP3008 project. I notice you handle your IO differently though, so proofread and make sure it make sense for your implementation. (You can get the source by clicking History > select r19 as v1 and r20 as V2 then hitting compare)
4. Perhaps use cForge tool to create a package of your two files, .library and .xml
5. select a license and add it's file to your project
6. check it into your project's code repository
7. (Optional) invite others to critque

let me know how I can help. I look forward to seeing you get your first driver up on the forge.

MCP3008 Lib to MCP3208

2020-02-27T15:25:58.733000Z

Originally created by: phenixrb

Hello everyone ,

can you tell me if the procedure is good regarding:
the modification of the MCP3008 library to MCP3208 ?

I used the MCP3008 files as a base.

I modified "AfterReadInputs" as indicated in the post,
replaced "MCP3008" by "MCP3208" in all the other files in the library.
save as a "compiled library" named MCP3208 and installed in the "library repository".

then I modified the "xml" file from MCP3008 to MCP3208.
following the indications of FORGE.

are there any errors?

is it possible to have an open source driver in the device list?
because, for the moment it does not appear in the list.
if so, what is the procedure?

thank you

MCP3008 Lib to MCP3208

2020-02-27T15:25:58.038000Z

Originally created by: phenixrb

hello Edwin,

thank you for that clarification ,
is the information described in this post sufficient to adapt the MCP3008 device to MCP3208?

and best wishes for this new year.

MCP3008 Lib to MCP3208

2020-02-27T15:25:57.339000Z

Hi,
the difference on these two device descriptions,
_IO offers additional the mapping page, to map variables.
So use either the one or the other.
( without _io you get the values from MCP3008.auiValue[0] see the example project)

BR
Edwin

MCP3008 Lib to MCP3208

2020-02-27T15:25:55.415000Z

Originally created by: phenixrb

Good morning all ,

I want to try to modify, the device MCP3008 to MCP3208, using the information described in this post.
I find two DEVICES for MCP3008, in "CODESYS Control for Raspberry PI" "3.5.15.20":
MCP3008.devdesc
MCP3008_IO.devdesc

should both be changed?
thank you

MCP3008 Lib to MCP3208

2020-02-27T15:25:54.734000Z

Originally created by: phenixrb

Hello everyone ,
can you explain to me how to integrate the MCP3208 library in a project.
or how to modify the existing MCP3008 library from codesys to MCP3208?

I can use the examples explained in this post, but impossible for me to integrate it into a complete project.

I wish to be able to use the 8 inputs.

Thanks for your help.

MCP3008 Lib to MCP3208

2020-02-27T15:25:54.048000Z

Originally created by: Joseph Sen Krobin

yyannekk hat geschrieben:
Hi backflip
Thank you for sharing your code! Helped me alot. I'm now also able to get data from an MCP3208
Now my problem is I want to communicate with a totally different DAC, the MCP4922 (data sheet http://akizukidenshi.com/download/MCP4922.pdf). It's a write-only device.
Now I think I just need to apply the datasheets SPI definition into the code (i.e. extend the BeforeWriteOutputs method). However this is not an easy task, as I'm pretty new to SCL programming. The sample SPI_MCP23S17 seems to be interesting, however with my limited knowledge it's also not easy (impossible) to understand.
Can you give me some hints on how to proceed? Maybe direct me to some other examples, or literature?

Recent posts to MCP3008 Lib to MCP3208

MCP3008 Lib to MCP3208

MCP3008 Lib to MCP3208

MCP3008 Lib to MCP3208

MCP3008 Lib to MCP3208

MCP3008 Lib to MCP3208

MCP3008 Lib to MCP3208

MCP3008 Lib to MCP3208

MCP3008 Lib to MCP3208

MCP3008 Lib to MCP3208

MCP3008 Lib to MCP3208