sigrok - User contributions [en]

PoLabs PoScope Mega50

2020-01-06T11:28:50Z

Benimautner: /* Hardware */

The [https://www.poscope.com/product/poscope-mega50/ PoLabs PoScope Mega50] is a mixed signal oscilloscope with 2 analog channels (8 bits each) and 2 digital ports (16 digital lines in summary).

...

See [[PoLabs PoScope Mega50/Info]] for some more details (such as '''lsusb -v''' output) on the device.

== Hardware ==

* ''Cypress'' CY7C68013A-56: USB Microcontroller
* ''Analog Devices'' AD9288: 8-Bit Dual A/D Converter
* ''NXP'' LPC1111F: Cortex-M0 based microcontroller (For the output probably)
* ''NXP'' PCA9555: 16 I/O CMOS device
* 4x ''Nexpia'' 74HC4052: Dual 4-channel analog multiplexer/demultiplexer (two per analog channel)
* ''Microchip'' 24lc128i: I2C EEPROM
* 2x ''Nexpia'' 74HC245: Octal bus transceiver
* ''TI'' LM358: opamp

== Photos ==

[[File:PoScopeMx50 PCB.JPG|200px]]
[[File:PoscopeMx50 inside.JPG|200px]]
[[File:Poscope_inside_2.JPG|200px]]

== Protocol ==

The main communication when setting it up/changing configuration always goes like this:

The host sends a "URB_BULK out" command where there are 64 bytes of data.

The device sends a packet with 4 times 0x00 as data

The host returns the same data but with an 0x00 instead of an 0x01 at byte 16

The device returns a "URB_BULK in" command with a lot of data in the 64 bytes of data.

'''The setup:'''

// In the following examples, I'm only talking about the 64 bytes of data, because (I think) everything else gets handled by the driver itself

//I'm making assumptions about what the commands do

'''Booting:'''

the host sends 0xa2 followed by 63 0x00

the host sends 0xa8 followed by 63 0x00

the host sends 0xa4 + 0x30 + 0x00 + 0x20 + 60 * 0x00

now, the host counts bytes 1 and 2 up in 0x20 steps, always 0xa4 at byte 0 like that:

this is probably to clean out old values

<table>
<tr>
<th>byte 0</th>
<th>1</th>
<th>2</th>
<th>3</th>
<th>4-64</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x20''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x40''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x60''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x80''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xa0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xc0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xe0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x31 + </th>
<th>'''0x00''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x31 + </th>
<th>'''0x20''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>

</table>
until byte 1 is 0x3f and byte 2 is 0xe0

then the host sends: 0xa4 + 0x40 + 0x00 + 0x00 + 60 * 0x00

Starting (setting modes and other stuff probably):

<table>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x01 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa6 + </th>
<th>0x28 + </th>
<th>0x07 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x06 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x01 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa6 + </th>
<th>0x28 + </th>
<th>0x07 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0x06 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
<th>maybe initializes mode change. always comes before b2</th>
</tr>
<tr>
<th>0xb2 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x01 + </th>
<th>0xe0 + </th>
<th>0x14 + </th>
<th>58 * 0x00</th>
<th>b2 could set the mode. it repeats with other data when switching modes</th>
</tr>
<tr>
<th>0x05 + </th>
<th>0xc7 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
</table>

after that you can ask for data with:

0ad5ffff000000000900000100ff00860300000000

== Resources ==

* [https://www.poscope.com/product/poscope-mega50/ vendor device page]

PoLabs PoScope Mega50

2020-01-05T20:59:34Z

Benimautner: /* Photos */

The [https://www.poscope.com/product/poscope-mega50/ PoLabs PoScope Mega50] is a mixed signal oscilloscope with 2 analog channels (8 bits each) and 2 digital ports (16 digital lines in summary).

...

See [[PoLabs PoScope Mega50/Info]] for some more details (such as '''lsusb -v''' output) on the device.

== Hardware ==

* ''Cypress'' CY7C68013A-56: USB Microcontroller
* ''Analog Devices'' AD9288: 8-Bit Dual A/D Converter
* ''NXP'' LPC1111F: Cortex-M0 based microcontroller (For the output probably)
* ''NXP'' PCA9555: 16 I/O CMOS device
* 4x ''Nexpia'': 74HC4052: Dual 4-channel analog multiplexer/demultiplexer (two per analog channel)

== Photos ==

[[File:PoScopeMx50 PCB.JPG|200px]]
[[File:PoscopeMx50 inside.JPG|200px]]
[[File:Poscope_inside_2.JPG|200px]]

== Protocol ==

The main communication when setting it up/changing configuration always goes like this:

The host sends a "URB_BULK out" command where there are 64 bytes of data.

The device sends a packet with 4 times 0x00 as data

The host returns the same data but with an 0x00 instead of an 0x01 at byte 16

The device returns a "URB_BULK in" command with a lot of data in the 64 bytes of data.

'''The setup:'''

// In the following examples, I'm only talking about the 64 bytes of data, because (I think) everything else gets handled by the driver itself

//I'm making assumptions about what the commands do

'''Booting:'''

the host sends 0xa2 followed by 63 0x00

the host sends 0xa8 followed by 63 0x00

the host sends 0xa4 + 0x30 + 0x00 + 0x20 + 60 * 0x00

now, the host counts bytes 1 and 2 up in 0x20 steps, always 0xa4 at byte 0 like that:

this is probably to clean out old values

<table>
<tr>
<th>byte 0</th>
<th>1</th>
<th>2</th>
<th>3</th>
<th>4-64</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x20''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x40''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x60''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x80''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xa0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xc0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xe0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x31 + </th>
<th>'''0x00''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x31 + </th>
<th>'''0x20''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>

</table>
until byte 1 is 0x3f and byte 2 is 0xe0

then the host sends: 0xa4 + 0x40 + 0x00 + 0x00 + 60 * 0x00

Starting (setting modes and other stuff probably):

<table>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x01 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa6 + </th>
<th>0x28 + </th>
<th>0x07 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x06 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x01 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa6 + </th>
<th>0x28 + </th>
<th>0x07 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0x06 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
<th>maybe initializes mode change. always comes before b2</th>
</tr>
<tr>
<th>0xb2 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x01 + </th>
<th>0xe0 + </th>
<th>0x14 + </th>
<th>58 * 0x00</th>
<th>b2 could set the mode. it repeats with other data when switching modes</th>
</tr>
<tr>
<th>0x05 + </th>
<th>0xc7 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
</table>

after that you can ask for data with:

0ad5ffff000000000900000100ff00860300000000

== Resources ==

* [https://www.poscope.com/product/poscope-mega50/ vendor device page]

PoLabs PoScope Mega50

2020-01-05T20:58:29Z

Benimautner: /* Photos */

The [https://www.poscope.com/product/poscope-mega50/ PoLabs PoScope Mega50] is a mixed signal oscilloscope with 2 analog channels (8 bits each) and 2 digital ports (16 digital lines in summary).

...

See [[PoLabs PoScope Mega50/Info]] for some more details (such as '''lsusb -v''' output) on the device.

== Hardware ==

* ''Cypress'' CY7C68013A-56: USB Microcontroller
* ''Analog Devices'' AD9288: 8-Bit Dual A/D Converter
* ''NXP'' LPC1111F: Cortex-M0 based microcontroller (For the output probably)
* ''NXP'' PCA9555: 16 I/O CMOS device
* 4x ''Nexpia'': 74HC4052: Dual 4-channel analog multiplexer/demultiplexer (two per analog channel)

== Photos ==

[[File:PoScopeMx50 PCB.JPG|200px]]
[[File:Poscope_inside.JPG|200px]]
[[File:Poscope_inside_2.JPG|200px]]

== Protocol ==

The main communication when setting it up/changing configuration always goes like this:

The host sends a "URB_BULK out" command where there are 64 bytes of data.

The device sends a packet with 4 times 0x00 as data

The host returns the same data but with an 0x00 instead of an 0x01 at byte 16

The device returns a "URB_BULK in" command with a lot of data in the 64 bytes of data.

'''The setup:'''

// In the following examples, I'm only talking about the 64 bytes of data, because (I think) everything else gets handled by the driver itself

//I'm making assumptions about what the commands do

'''Booting:'''

the host sends 0xa2 followed by 63 0x00

the host sends 0xa8 followed by 63 0x00

the host sends 0xa4 + 0x30 + 0x00 + 0x20 + 60 * 0x00

now, the host counts bytes 1 and 2 up in 0x20 steps, always 0xa4 at byte 0 like that:

this is probably to clean out old values

<table>
<tr>
<th>byte 0</th>
<th>1</th>
<th>2</th>
<th>3</th>
<th>4-64</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x20''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x40''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x60''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x80''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xa0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xc0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xe0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x31 + </th>
<th>'''0x00''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x31 + </th>
<th>'''0x20''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>

</table>
until byte 1 is 0x3f and byte 2 is 0xe0

then the host sends: 0xa4 + 0x40 + 0x00 + 0x00 + 60 * 0x00

Starting (setting modes and other stuff probably):

<table>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x01 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa6 + </th>
<th>0x28 + </th>
<th>0x07 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x06 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x01 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa6 + </th>
<th>0x28 + </th>
<th>0x07 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0x06 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
<th>maybe initializes mode change. always comes before b2</th>
</tr>
<tr>
<th>0xb2 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x01 + </th>
<th>0xe0 + </th>
<th>0x14 + </th>
<th>58 * 0x00</th>
<th>b2 could set the mode. it repeats with other data when switching modes</th>
</tr>
<tr>
<th>0x05 + </th>
<th>0xc7 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
</table>

after that you can ask for data with:

0ad5ffff000000000900000100ff00860300000000

== Resources ==

* [https://www.poscope.com/product/poscope-mega50/ vendor device page]

PoLabs PoScope Mega50

2020-01-05T20:58:11Z

Benimautner: /* Photos */

The [https://www.poscope.com/product/poscope-mega50/ PoLabs PoScope Mega50] is a mixed signal oscilloscope with 2 analog channels (8 bits each) and 2 digital ports (16 digital lines in summary).

...

See [[PoLabs PoScope Mega50/Info]] for some more details (such as '''lsusb -v''' output) on the device.

== Hardware ==

* ''Cypress'' CY7C68013A-56: USB Microcontroller
* ''Analog Devices'' AD9288: 8-Bit Dual A/D Converter
* ''NXP'' LPC1111F: Cortex-M0 based microcontroller (For the output probably)
* ''NXP'' PCA9555: 16 I/O CMOS device
* 4x ''Nexpia'': 74HC4052: Dual 4-channel analog multiplexer/demultiplexer (two per analog channel)

== Photos ==

[[File:PoScopeMx50 PCB.JPG|200px]]
[[File:Poscope_inside_2.JPG|200px]]

== Protocol ==

The main communication when setting it up/changing configuration always goes like this:

The host sends a "URB_BULK out" command where there are 64 bytes of data.

The device sends a packet with 4 times 0x00 as data

The host returns the same data but with an 0x00 instead of an 0x01 at byte 16

The device returns a "URB_BULK in" command with a lot of data in the 64 bytes of data.

'''The setup:'''

// In the following examples, I'm only talking about the 64 bytes of data, because (I think) everything else gets handled by the driver itself

//I'm making assumptions about what the commands do

'''Booting:'''

the host sends 0xa2 followed by 63 0x00

the host sends 0xa8 followed by 63 0x00

the host sends 0xa4 + 0x30 + 0x00 + 0x20 + 60 * 0x00

now, the host counts bytes 1 and 2 up in 0x20 steps, always 0xa4 at byte 0 like that:

this is probably to clean out old values

<table>
<tr>
<th>byte 0</th>
<th>1</th>
<th>2</th>
<th>3</th>
<th>4-64</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x20''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x40''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x60''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x80''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xa0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xc0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xe0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x31 + </th>
<th>'''0x00''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x31 + </th>
<th>'''0x20''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>

</table>
until byte 1 is 0x3f and byte 2 is 0xe0

then the host sends: 0xa4 + 0x40 + 0x00 + 0x00 + 60 * 0x00

Starting (setting modes and other stuff probably):

<table>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x01 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa6 + </th>
<th>0x28 + </th>
<th>0x07 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x06 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x01 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa6 + </th>
<th>0x28 + </th>
<th>0x07 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0x06 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
<th>maybe initializes mode change. always comes before b2</th>
</tr>
<tr>
<th>0xb2 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x01 + </th>
<th>0xe0 + </th>
<th>0x14 + </th>
<th>58 * 0x00</th>
<th>b2 could set the mode. it repeats with other data when switching modes</th>
</tr>
<tr>
<th>0x05 + </th>
<th>0xc7 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
</table>

after that you can ask for data with:

0ad5ffff000000000900000100ff00860300000000

== Resources ==

* [https://www.poscope.com/product/poscope-mega50/ vendor device page]

PoLabs PoScope Mega50

2020-01-05T20:57:45Z

Benimautner: /* Photos */

The [https://www.poscope.com/product/poscope-mega50/ PoLabs PoScope Mega50] is a mixed signal oscilloscope with 2 analog channels (8 bits each) and 2 digital ports (16 digital lines in summary).

...

See [[PoLabs PoScope Mega50/Info]] for some more details (such as '''lsusb -v''' output) on the device.

== Hardware ==

* ''Cypress'' CY7C68013A-56: USB Microcontroller
* ''Analog Devices'' AD9288: 8-Bit Dual A/D Converter
* ''NXP'' LPC1111F: Cortex-M0 based microcontroller (For the output probably)
* ''NXP'' PCA9555: 16 I/O CMOS device
* 4x ''Nexpia'': 74HC4052: Dual 4-channel analog multiplexer/demultiplexer (two per analog channel)

== Photos ==

[[Media:PoScopeMx50 PCB.JPG]]

PoscopeMx50_inside.JPG

Poscope_inside_2.JPG

[[File:Poscope_inside_2.JPG|200px]]

== Protocol ==

The main communication when setting it up/changing configuration always goes like this:

The host sends a "URB_BULK out" command where there are 64 bytes of data.

The device sends a packet with 4 times 0x00 as data

The host returns the same data but with an 0x00 instead of an 0x01 at byte 16

The device returns a "URB_BULK in" command with a lot of data in the 64 bytes of data.

'''The setup:'''

// In the following examples, I'm only talking about the 64 bytes of data, because (I think) everything else gets handled by the driver itself

//I'm making assumptions about what the commands do

'''Booting:'''

the host sends 0xa2 followed by 63 0x00

the host sends 0xa8 followed by 63 0x00

the host sends 0xa4 + 0x30 + 0x00 + 0x20 + 60 * 0x00

now, the host counts bytes 1 and 2 up in 0x20 steps, always 0xa4 at byte 0 like that:

this is probably to clean out old values

<table>
<tr>
<th>byte 0</th>
<th>1</th>
<th>2</th>
<th>3</th>
<th>4-64</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x20''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x40''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x60''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x80''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xa0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xc0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xe0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x31 + </th>
<th>'''0x00''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x31 + </th>
<th>'''0x20''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>

</table>
until byte 1 is 0x3f and byte 2 is 0xe0

then the host sends: 0xa4 + 0x40 + 0x00 + 0x00 + 60 * 0x00

Starting (setting modes and other stuff probably):

<table>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x01 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa6 + </th>
<th>0x28 + </th>
<th>0x07 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x06 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x01 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa6 + </th>
<th>0x28 + </th>
<th>0x07 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0x06 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
<th>maybe initializes mode change. always comes before b2</th>
</tr>
<tr>
<th>0xb2 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x01 + </th>
<th>0xe0 + </th>
<th>0x14 + </th>
<th>58 * 0x00</th>
<th>b2 could set the mode. it repeats with other data when switching modes</th>
</tr>
<tr>
<th>0x05 + </th>
<th>0xc7 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
</table>

after that you can ask for data with:

0ad5ffff000000000900000100ff00860300000000

== Resources ==

* [https://www.poscope.com/product/poscope-mega50/ vendor device page]

PoLabs PoScope Mega50

2020-01-05T20:57:26Z

Benimautner: /* Photos */

The [https://www.poscope.com/product/poscope-mega50/ PoLabs PoScope Mega50] is a mixed signal oscilloscope with 2 analog channels (8 bits each) and 2 digital ports (16 digital lines in summary).

...

See [[PoLabs PoScope Mega50/Info]] for some more details (such as '''lsusb -v''' output) on the device.

== Hardware ==

* ''Cypress'' CY7C68013A-56: USB Microcontroller
* ''Analog Devices'' AD9288: 8-Bit Dual A/D Converter
* ''NXP'' LPC1111F: Cortex-M0 based microcontroller (For the output probably)
* ''NXP'' PCA9555: 16 I/O CMOS device
* 4x ''Nexpia'': 74HC4052: Dual 4-channel analog multiplexer/demultiplexer (two per analog channel)

== Photos ==

[[Media:PoScopeMx50 PCB.JPG]]

PoscopeMx50_inside.JPG

Poscope_inside_2.JPG

[[File:Poscope_inside_2.JPG|thumb]]

== Protocol ==

The main communication when setting it up/changing configuration always goes like this:

The host sends a "URB_BULK out" command where there are 64 bytes of data.

The device sends a packet with 4 times 0x00 as data

The host returns the same data but with an 0x00 instead of an 0x01 at byte 16

The device returns a "URB_BULK in" command with a lot of data in the 64 bytes of data.

'''The setup:'''

// In the following examples, I'm only talking about the 64 bytes of data, because (I think) everything else gets handled by the driver itself

//I'm making assumptions about what the commands do

'''Booting:'''

the host sends 0xa2 followed by 63 0x00

the host sends 0xa8 followed by 63 0x00

the host sends 0xa4 + 0x30 + 0x00 + 0x20 + 60 * 0x00

now, the host counts bytes 1 and 2 up in 0x20 steps, always 0xa4 at byte 0 like that:

this is probably to clean out old values

<table>
<tr>
<th>byte 0</th>
<th>1</th>
<th>2</th>
<th>3</th>
<th>4-64</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x20''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x40''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x60''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x80''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xa0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xc0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xe0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x31 + </th>
<th>'''0x00''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x31 + </th>
<th>'''0x20''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>

</table>
until byte 1 is 0x3f and byte 2 is 0xe0

then the host sends: 0xa4 + 0x40 + 0x00 + 0x00 + 60 * 0x00

Starting (setting modes and other stuff probably):

<table>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x01 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa6 + </th>
<th>0x28 + </th>
<th>0x07 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x06 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x01 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa6 + </th>
<th>0x28 + </th>
<th>0x07 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0x06 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
<th>maybe initializes mode change. always comes before b2</th>
</tr>
<tr>
<th>0xb2 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x01 + </th>
<th>0xe0 + </th>
<th>0x14 + </th>
<th>58 * 0x00</th>
<th>b2 could set the mode. it repeats with other data when switching modes</th>
</tr>
<tr>
<th>0x05 + </th>
<th>0xc7 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
</table>

after that you can ask for data with:

0ad5ffff000000000900000100ff00860300000000

== Resources ==

* [https://www.poscope.com/product/poscope-mega50/ vendor device page]

File:Poscope inside 2.JPG

2020-01-05T20:56:55Z

Benimautner:

File:PoscopeMx50 inside.JPG

2020-01-05T20:49:48Z

Benimautner:

PoLabs PoScope Mega50

2020-01-05T19:28:54Z

Benimautner: /* Photos */

...

See [[PoLabs PoScope Mega50/Info]] for some more details (such as '''lsusb -v''' output) on the device.

== Hardware ==

* ''Cypress'' CY7C68013A-56: USB Microcontroller
* ''Analog Devices'' AD9288: 8-Bit Dual A/D Converter
* ''NXP'' LPC1111F: Cortex-M0 based microcontroller (For the output probably)
* ''NXP'' PCA9555: 16 I/O CMOS device
* 4x ''Nexpia'': 74HC4052: Dual 4-channel analog multiplexer/demultiplexer (two per analog channel)

== Photos ==

[[Media:PoScopeMx50 PCB.JPG]]

== Protocol ==

The main communication when setting it up/changing configuration always goes like this:

The host sends a "URB_BULK out" command where there are 64 bytes of data.

The device sends a packet with 4 times 0x00 as data

The host returns the same data but with an 0x00 instead of an 0x01 at byte 16

The device returns a "URB_BULK in" command with a lot of data in the 64 bytes of data.

'''The setup:'''

// In the following examples, I'm only talking about the 64 bytes of data, because (I think) everything else gets handled by the driver itself

//I'm making assumptions about what the commands do

'''Booting:'''

the host sends 0xa2 followed by 63 0x00

the host sends 0xa8 followed by 63 0x00

the host sends 0xa4 + 0x30 + 0x00 + 0x20 + 60 * 0x00

now, the host counts bytes 1 and 2 up in 0x20 steps, always 0xa4 at byte 0 like that:

this is probably to clean out old values

<table>
<tr>
<th>byte 0</th>
<th>1</th>
<th>2</th>
<th>3</th>
<th>4-64</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x20''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x40''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x60''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x80''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xa0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xc0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xe0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x31 + </th>
<th>'''0x00''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x31 + </th>
<th>'''0x20''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>

</table>
until byte 1 is 0x3f and byte 2 is 0xe0

then the host sends: 0xa4 + 0x40 + 0x00 + 0x00 + 60 * 0x00

Starting (setting modes and other stuff probably):

<table>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x01 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa6 + </th>
<th>0x28 + </th>
<th>0x07 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x06 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x01 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa6 + </th>
<th>0x28 + </th>
<th>0x07 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0x06 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
<th>maybe initializes mode change. always comes before b2</th>
</tr>
<tr>
<th>0xb2 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x01 + </th>
<th>0xe0 + </th>
<th>0x14 + </th>
<th>58 * 0x00</th>
<th>b2 could set the mode. it repeats with other data when switching modes</th>
</tr>
<tr>
<th>0x05 + </th>
<th>0xc7 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
</table>

after that you can ask for data with:

0ad5ffff000000000900000100ff00860300000000

File:PoScopeMx50 PCB.JPG

2020-01-05T19:27:01Z

Benimautner:

PoLabs PoScope Mega50

2020-01-05T15:59:42Z

Benimautner:

See [[PoScopeMega50/Info]] for '''lsusb''' information.

== '''Hardware''' ==

* ''Cypress'' CY7C68013A-56: USB Microcontroller
* ''Analog Devices'' AD9288: 8-Bit Dual A/D Converter
* ''NXP'' LPC1111F: Cortex-M0 based microcontroller (For the output probably)
* ''NXP'' PCA9555: 16 I/O CMOS device
* 4x ''Nexpia'': 74HC4052: Dual 4-channel analog multiplexer/demultiplexer (two per analog channel)

== '''Photos''' ==

Coming soon

== '''Protocol''' ==

The main communication when setting it up/changing configuration always goes like this:

The host sends a "URB_BULK out" command where there are 64 bytes of data.

The device sends a packet with 4 times 0x00 as data

The host returns the same data but with an 0x00 instead of an 0x01 at byte 16

The device returns a "URB_BULK in" command with a lot of data in the 64 bytes of data.

'''The setup:'''

// In the following examples, I'm only talking about the 64 bytes of data, because (I think) everything else gets handled by the driver itself

//I'm making assumptions about what the commands do

'''Booting:'''

the host sends 0xa2 followed by 63 0x00

the host sends 0xa8 followed by 63 0x00

the host sends 0xa4 + 0x30 + 0x00 + 0x20 + 60 * 0x00

now, the host counts bytes 1 and 2 up in 0x20 steps, always 0xa4 at byte 0 like that:

this is probably to clean out old values

<table>
<tr>
<th>byte 0</th>
<th>1</th>
<th>2</th>
<th>3</th>
<th>4-64</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x20''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x40''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x60''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x80''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xa0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xc0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xe0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x31 + </th>
<th>'''0x00''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x31 + </th>
<th>'''0x20''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>

</table>
until byte 1 is 0x3f and byte 2 is 0xe0

then the host sends: 0xa4 + 0x40 + 0x00 + 0x00 + 60 * 0x00

Starting (setting modes and other stuff probably):

<table>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x01 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa6 + </th>
<th>0x28 + </th>
<th>0x07 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x06 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x01 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa6 + </th>
<th>0x28 + </th>
<th>0x07 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0x06 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
<th>maybe initializes mode change. always comes before b2</th>
</tr>
<tr>
<th>0xb2 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x01 + </th>
<th>0xe0 + </th>
<th>0x14 + </th>
<th>58 * 0x00</th>
<th>b2 could set the mode. it repeats with other data when switching modes</th>
</tr>
<tr>
<th>0x05 + </th>
<th>0xc7 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
</table>

after that you can ask for data with:

0ad5ffff000000000900000100ff00860300000000

PoLabs PoScope Mega50

2020-01-05T15:58:28Z

Benimautner:

See [[PoScopeMega50/Info]] for '''lsusb''' information.

== '''Hardware''' ==

* ''Cypress'' CY7C68013A-56: USB Microcontroller
* ''Analog Devices'' AD9288: 8-Bit Dual A/D Converter
* ''NXP'' LPC1111F: Cortex-M0 based microcontroller (For the output probably)
* ''NXP'' PCA9555: 16 I/O CMOS device
* 4x ''Nexpia'': 74HC4052: Dual 4-channel analog multiplexer/demultiplexer (two per analog channel)

== '''Photos''' ==

Coming soon

== '''Protocol''' ==

The main communication when setting it up/changing configuration always goes like this:

The host sends a "URB_BULK out" command where there are 64 bytes of data.

The device sends a packet with 4 times 0x00 as data

The host returns the same data but with an 0x00 instead of an 0x01 at byte 16

The device returns a "URB_BULK in" command with a lot of data in the 64 bytes of data.

'''The setup:'''

// In the following examples, I'm only talking about the 64 bytes of data, because (I think) everything else gets handled by the driver itself

//I'm making assumptions about what the commands do

'''Booting:'''

the host sends 0xa2 followed by 63 0x00

the host sends 0xa8 followed by 63 0x00

the host sends 0xa4 + 0x30 + 0x00 + 0x20 + 60 * 0x00

now, the host counts bytes 1 and 2 up in 0x20 steps, always 0xa4 at byte 0 like that:

this is probably to clean out old values

<table>
<tr>
<th>byte 0</th>
<th>1</th>
<th>2</th>
<th>3</th>
<th>4-64</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x20''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x40''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x60''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x80''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xa0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xc0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xe0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x31 + </th>
<th>'''0x00''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x31 + </th>
<th>'''0x20''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>

</table>

until byte 1 is 0x3f and byte 2 is 0xe0

then the host sends: 0xa4 + 0x40 + 0x00 + 0x00 + 60 * 0x00

Starting (setting modes and other stuff probably):

<table>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x01 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa6 + </th>
<th>0x28 + </th>
<th>0x07 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x06 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x01 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0xa6 + </th>
<th>0x28 + </th>
<th>0x07 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0x06 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
<th>maybe initializes mode change. always comes before b2</th>
</tr>
<tr>
<th>0xb2 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x01 + </th>
<th>0xe0 + </th>
<th>0x14 + </th>
<th>58 * 0x00</th>
<th>b2 could set the mode. it repeats with other data when switching modes</th>
</tr>
<tr>
<th>0x05 + </th>
<th>0xc7 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>58 * 0x00</th>
</tr>
</table>

after that you can ask for data with:

0ad5ffff000000000900000100ff00860300000000

PoLabs PoScope Mega50

2020-01-05T15:49:59Z

Benimautner:

See [[PoScopeMega50/Info]] for '''lsusb''' information.

== '''Hardware''' ==

* ''Cypress'' CY7C68013A-56: USB Microcontroller
* ''Analog Devices'' AD9288: 8-Bit Dual A/D Converter
* ''NXP'' LPC1111F: Cortex-M0 based microcontroller (For the output probably)
* ''NXP'' PCA9555: 16 I/O CMOS device
* 4x ''Nexpia'': 74HC4052: Dual 4-channel analog multiplexer/demultiplexer (two per analog channel)

== '''Photos''' ==

Coming soon

== '''Protocol''' ==

The main communication when setting it up/changing configuration always goes like this:

The host sends a "URB_BULK out" command where there are 64 bytes of data.

The device sends a packet with 4 times 0x00 as data

The host returns the same data but with an 0x00 instead of an 0x01 at byte 16

The device returns a "URB_BULK in" command with a lot of data in the 64 bytes of data.

'''The setup:'''

// In the following examples, I'm only talking about the 64 bytes of data, because (I think) everything else gets handled by the driver itself

//I'm making assumptions about what the commands do

'''Booting:'''

the host sends 0xa2 followed by 63 0x00

the host sends 0xa8 followed by 63 0x00

the host sends 0xa4 + 0x30 + 0x00 + 0x20 + 60 * 0x00

now, the host counts bytes 1 and 2 up in 0x20 steps, always 0xa4 at byte 0 like that:

this is probably to clean out old values

<table>
<tr>
<th>byte 0</th>
<th>1</th>
<th>2</th>
<th>3</th>
<th>4-64</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x20''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x40''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x60''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x80''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xa0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xc0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xe0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x31 + </th>
<th>'''0x00''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x31 + </th>
<th>'''0x20''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>

</table>

until byte 1 is 0x3f and byte 2 is 0xe0

then the host sends: 0xa4 + 0x40 + 0x00 + 0x00 + 60 * 0x00

Starting (setting modes and other stuff probably):

<table>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x01 + </th>
<th>0x00 + </th>
<th>59 * 0x00</th>
</tr>
<tr>
<th>0xa6 + </th>
<th>0x28 + </th>
<th>0x07 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>59 * 0x00</th>
</tr>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x06 + </th>
<th>0x00 + </th>
<th>59 * 0x00</th>
</tr>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x01 + </th>
<th>0x00 + </th>
<th>59 * 0x00</th>
</tr>
<tr>
<th>0xa6 + </th>
<th>0x28 + </th>
<th>0x07 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>59 * 0x00</th>
</tr>
<tr>
<th>0x06 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>59 * 0x00</th>
</tr>
<tr>
<th>0xb2 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x01 + </th>
<th>0xe0 + </th>
<th>0x14 + </th>
<th>58 * 0x00</th>
</tr>
<tr>
<th>0x05 + </th>
<th>0xc7 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>59 * 0x00</th>
</tr>
</table>

PoLabs PoScope Mega50

2020-01-05T15:49:07Z

Benimautner:

See [[PoScopeMega50/Info]] for '''lsusb''' information.

== '''Hardware''' ==

* ''Cypress'' CY7C68013A-56: USB Microcontroller
* ''Analog Devices'' AD9288: 8-Bit Dual A/D Converter
* ''NXP'' LPC1111F: Cortex-M0 based microcontroller (For the output probably)
* ''NXP'' PCA9555: 16 I/O CMOS device
* 4x ''Nexpia'': 74HC4052: Dual 4-channel analog multiplexer/demultiplexer (two per analog channel)

== '''Photos''' ==

Coming soon

== '''Protocol''' ==

The main communication when setting it up/changing configuration always goes like this:

The host sends a "URB_BULK out" command where there are 64 bytes of data.

The device sends a packet with 4 times 0x00 as data

The host returns the same data but with an 0x00 instead of an 0x01 at byte 16

The device returns a "URB_BULK in" command with a lot of data in the 64 bytes of data.

'''The setup:'''

// In the following examples, I'm only talking about the 64 bytes of data, because (I think) everything else gets handled by the driver itself

//I'm making assumptions about what the commands do

'''Booting:'''

the host sends 0xa2 followed by 63 0x00

the host sends 0xa8 followed by 63 0x00

the host sends 0xa4 + 0x30 + 0x00 + 0x20 + 60 * 0x00

now, the host counts bytes 1 and 2 up in 0x20 steps, always 0xa4 at byte 0 like that:

this is probably to clean out old values

<table>
<tr>
<th>byte 0</th>
<th>1</th>
<th>2</th>
<th>3</th>
<th>4-64</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x20''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x40''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x60''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x80''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xa0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xc0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xe0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x31 + </th>
<th>'''0x00''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x31 + </th>
<th>'''0x20''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>

</table>

until byte 1 is 0x3f and byte 2 is 0xe0

then the host sends: 0xa4 + 0x40 + 0x00 + 0x00 + 60 * 0x00

Starting (setting modes and other stuff probably):

<table>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x01 + </th>
<th>0x00 + </th>
<th>59 * 0x00</th>
</tr>
<tr>
<th>0xa6 + </th>
<th>0x28 + </th>
<th>0x07 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>59 * 0x00</th>
</tr>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x06 + </th>
<th>0x00 + </th>
<th>59 * 0x00</th>
</tr>
<tr>
<th>0xa5 + </th>
<th>0x28 + </th>
<th>0x01 + </th>
<th>0x01 + </th>
<th>0x00 + </th>
<th>59 * 0x00</th>
</tr>
<tr>
<th>0xa6 + </th>
<th>0x28 + </th>
<th>0x07 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>59 * 0x00</th>
</tr>
<tr>
<th>0x06 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>59 * 0x00</th>
</tr>
<tr>
<th>0xb2 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x01 + </th>
<th>0xe0 + </th>
<th>0x14 + </th>
<th>59 * 0x00</th>
</tr>
<tr>
<th>0x05 + </th>
<th>0xc7 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>0x00 + </th>
<th>59 * 0x00</th>
</tr>
</table>

PoLabs PoScope Mega50

2020-01-05T15:40:11Z

Benimautner: /* Protocol */

See [[PoScopeMega50/Info]] for '''lsusb''' information.

== '''Hardware''' ==

* ''Cypress'' CY7C68013A-56: USB Microcontroller
* ''Analog Devices'' AD9288: 8-Bit Dual A/D Converter
* ''NXP'' LPC1111F: Cortex-M0 based microcontroller (For the output probably)
* ''NXP'' PCA9555: 16 I/O CMOS device
* 4x ''Nexpia'': 74HC4052: Dual 4-channel analog multiplexer/demultiplexer (two per analog channel)

== '''Photos''' ==

Coming soon

== '''Protocol''' ==

The main communication when setting it up/changing configuration always goes like this:

The host sends a "URB_BULK out" command where there are 64 bytes of data.

The device sends a packet with 4 times 0x00 as data

The host returns the same data but with an 0x00 instead of an 0x01 at byte 16

The device returns a "URB_BULK in" command with a lot of data in the 64 bytes of data.

'''The setup:'''

// In the following examples, I'm only talking about the 64 bytes of data, because (I think) everything else gets handled by the driver itself

//I'm making assumptions about what the commands do

'''Booting:'''

the host sends 0xa2 followed by 63 0x00

the host sends 0xa8 followed by 63 0x00

the host sends 0xa4 + 0x30 + 0x00 + 0x20 + 60 * 0x00

now, the host counts bytes 1 and 2 up in 0x20 steps, always 0xa4 at byte 0 like that:

byte:



<table>
<tr>
<th>byte 0</th>
<th>1</th>
<th>2</th>
<th>3</th>
<th>4-64</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x20''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x40''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x60''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0x80''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xa0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xc0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x30 + </th>
<th>'''0xe0''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x31 + </th>
<th>'''0x00''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>
<tr>
<th>0xa4 + </th>
<th>0x31 + </th>
<th>'''0x20''' + </th>
<th>0x20 + </th>
<th>60 * 0x00</th>
</tr>

</table>

until byte 1 is 0x3f and byte 2 is 0xe0

then the host sends: 0xa4 + 0x40 + 0x00 + 0x00 + 60 * 0x00

PoLabs PoScope Mega50

2020-01-05T08:36:54Z

Benimautner:

== '''Hardware''' ==

- ''Cypress'' CY7C68013A-56: USB Microcontroller

- ''Analog Devices'' AD9288: 8-Bit Dual A/D Converter

- ''NXP'' LPC1111F: Cortex-M0 based microcontroller (For the output probably)

- ''NXP'' PCA9555: 16 I/O CMOS device

- 4x ''Nexpia'': 74HC4052: Dual 4-channel analog multiplexer/demultiplexer (two per analog channel)

== '''Photos''' ==

Coming soon

== '''Protocol''' ==

== '''lsusb''' ==

'''lsusb''': Bus 001 Device 005: ID 0404:0081 NCR Corp

'''lsusb -vvv -d 0404:0081''':

Bus 001 Device 014: ID 0404:0081 NCR Corp.
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0404 NCR Corp.
idProduct 0x0081
bcdDevice 0.00
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x002e
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 4
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86 EP 6 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0

PoLabs PoScope Mega50

2020-01-05T08:36:29Z

Benimautner:

PoLabs PoScope Mega50

2020-01-05T08:35:51Z

Benimautner:

== '''Hardware''' ==

----

- ''Cypress'' CY7C68013A-56: USB Microcontroller

- ''Analog Devices'' AD9288: 8-Bit Dual A/D Converter

- ''NXP'' LPC1111F: Cortex-M0 based microcontroller (For the output probably)

- ''NXP'' PCA9555: 16 I/O CMOS device

- 4x ''Nexpia'': 74HC4052: Dual 4-channel analog multiplexer/demultiplexer (two per analog channel)

== '''Photos''' ==

----

Coming soon

== '''Protocol''' ==

----

== '''lsusb''' ==

----
'''lsusb''': Bus 001 Device 005: ID 0404:0081 NCR Corp
'''lsusb -vvv -d 0404:0081''':
Bus 001 Device 014: ID 0404:0081 NCR Corp.
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0404 NCR Corp.
idProduct 0x0081
bcdDevice 0.00
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x002e
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 4
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86 EP 6 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0

PoLabs PoScope Mega50

2020-01-04T23:32:04Z

Benimautner:

'''Hardware'''
----

- ''Cypress'' CY7C68013A-56: USB Microcontroller

- ''Analog Devices'' AD9288: 8-Bit Dual A/D Converter

- ''NXP'' LPC1111F: Cortex-M0 based microcontroller (For the output probably)

- ''NXP'' PCA9555: 16 I/O CMOS device

- 4x ''Nexpia'': 74HC4052: Dual 4-channel analog multiplexer/demultiplexer (two per analog channel)

'''Photos'''
----

Coming soon

'''Protocol'''
----

PoLabs PoScope Mega50

2020-01-04T23:31:22Z

Benimautner:

'''Hardware'''
----

- Cypress CY7C68013A-56: USB Microcontroller

- Analog Devices AD9288: 8-Bit Dual A/D Converter

- NXP LPC1111F: Cortex-M0 based microcontroller (For the output probably)

- NXP PCA9555: 16 I/O CMOS device

- 4x Nexpia: 74HC4052: Dual 4-channel analog multiplexer/demultiplexer (two per analog channel)

'''Photos'''
----

Coming soon

'''Protocol'''
----

PoLabs PoScope Mega50

2020-01-04T23:30:55Z

Benimautner:

'''Hardware'''
----

Cypress CY7C68013A-56: USB Microcontroller
Analog Devices AD9288: 8-Bit Dual A/D Converter
NXP LPC1111F: Cortex-M0 based microcontroller (For the output probably)
NXP PCA9555: 16 I/O CMOS device
4x Nexpia: 74HC4052: Dual 4-channel analog multiplexer/demultiplexer (two per analog channel)

'''Photos'''
----

Coming soon

'''Protocol'''
----

PoLabs PoScope Mega50

2020-01-04T23:30:26Z

Benimautner: Created page with "'''Hardware''' ---- - Cypress CY7C68013A-56: USB Microcontroller - Analog Devices AD9288: 8-Bit Dual A/D Converter - NXP LPC1111F: Cortex-M0 based microcontroller (For the..."

'''Hardware'''
----

- Cypress CY7C68013A-56: USB Microcontroller
- Analog Devices AD9288: 8-Bit Dual A/D Converter
- NXP LPC1111F: Cortex-M0 based microcontroller (For the output probably)
- NXP PCA9555: 16 I/O CMOS device
- 4x Nexpia: 74HC4052: Dual 4-channel analog multiplexer/demultiplexer (two per analog channel)

'''Photos'''
----

Coming soon

'''Protocol'''
----