PI CHIP

[sido]

That's pretty slick,

I now need to figure out all the different pins that are controlled, (The OC's are pretty striaghtforward)
so it will be useful on the uno32 metal detector sheild I'm working on.

Same here after reading the relevant UNO32 documents.

It'll be usuing QED as the premise for it's operation.

Which version QED are you implementing the UNO32......Is it the single MCU or the Dual version?

Either way, would like to see your end results, as you have a better understanding on this platform.

BTW...what do you mean when you say a "UNO32 metal detector shield"......I do not understand.

Cheers Sid

[sido]

...you probably already got did but for anyone else make sure you select the correct device ..

[ATTACH=CONFIG]25115[/ATTACH]
[ATTACH=CONFIG]25114[/ATTACH]

Thanks for that Moodz....

Cheers Sid

[sido]

That's pretty slick,

I now need to figure out all the different pins that are controlled, (The OC's are pretty striaghtforward)
so it will be useful on the uno32 metal detector sheild I'm working on.

It'll be usuing QED as the premise for it's operation.

[ATTACH]25110[/ATTACH]

Hi Hdphilip, thanks for the screenshot showing Comms connection.

Cheers Sid

[moodz]

...you probably already got did but for anyone else make sure you select the correct device ..

[hdphilip]

That's pretty slick,

I now need to figure out all the different pins that are controlled, (The OC's are pretty striaghtforward)
so it will be useful on the uno32 metal detector sheild I'm working on.

It'll be usuing QED as the premise for it's operation.

[moodz]

Microchip® PIC32MX320F128H microcontroller (80 Mhz 32-bit MIPS, 128K Flash, 16K SRAM)  compatible with many existing Arduino code samples and other resources  Arduino Uno form factor  compatible with many Arduino shields  42 available I/O pins  two user LEDs  PC connection uses a USB A > mini B cable (not included)  12 analog inputs  3.3V operating voltage  80Mhz operating frequency  75mA typical operating current  7V to 15V input voltage (recommended)  20V input voltage (maximum)  0V to 3.3V analog input voltage range  +/-18mA DC current per pin

[Mechanic]

HI Sid,

Err no and I can't seem to find it listed in the code....

Moodz is rolling his eyes right now!

Cheers Mick

[sido]

Thanks Moodz!
I opened it up in MPlab with no problems(you have to take the files out of the zip folder)

Need to have a good look through the code and see whats what, oh and learn C along the way.

Cheers Mick

Hi Mick, ditto

Would you happen to know the full description of the PIC32 being used?

Have i missed something??

Cheers Sid

[Mechanic]

Thanks Moodz!
I opened it up in MPlab with no problems(you have to take the files out of the zip folder)

Need to have a good look through the code and see whats what, oh and learn C along the way.

Cheers Mick

[sido]

Hi Moodz, never mind, got it to work now the other way.

Nice bit of code. Got to get me head around it, so i could understand it as i am learning.

Great work though.

Should be receiving the UNO32 sometime next week.

Cheers Sid

[sido]

Hey Sid ... ( and hdPhilip ) ... here is something for ya and the rest of the gang .... did you know that Pie and Sauce is a classic Aussie snack ? Well this a basic PI and SOURCE (code ) recipe LOL .... well here is some code to chew on for the UNO32 .... its had some stuff stripped out as it pertains to some patent stuff I am putting through but there is enough in there function wise to build a nice backend for a roll your own PI .... TX an RX Pulse generator, Low pass filter, audio generator, 24 bit adc driver, SPI driver, RS232 menu driver. Just add a switching mosfet and driver, sample and holds, differential integrator, amplification, voltage limiting, blue tooth module for wireless RS232 remote menu on tablet / phone / laptop and you are in business.

DISCLAIMER .. this not a PI detector source code ... it is a collection of functions and some rough harness code for EXPERIMENTERS ... who basically know what they are doing to get a jumpstart into using a 32 bit procecessor like the one on the UNO32 for implementing a PI detector ...so please dont send me PMs asking for hexcodes ( thanks ). I will answer questions on the code and help with whatever changes you are trying to make as long as you share ... no sharing = no help

This source code will actually compile and is set up to provide basic pulses on the designated output pins ... you will have to investigate how the other functions would be used ... project for the Microchip MPIDE ( set config bits to code ).

Enjoy ...
[ATTACH=CONFIG]25082[/ATTACH]

Hi Moodz, thanks for the source and pie. Have not had one for a while.

I tried to transfer the Source and header files in MPIDE V8.90 and all files returned
(Files not found)

Not sure why.

UPDATE: In the zip file you provided with direct MPLAB link is the one that came up with errors in Files not found once the MPLAB application opened up. I could see the files on the left hand side but with errors.
Maybe the version of the MPLAB i am using v8.90??

Anyway, the source folder in your zip file provided with the individual seperate files worked ok in V8.90

Cheers Sid

[moodz]

PI and SOURCE

Hey Sid ... ( and hdPhilip ) ... here is something for ya and the rest of the gang .... did you know that Pie and Sauce is a classic Aussie snack ? Well this a basic PI and SOURCE (code ) recipe LOL .... well here is some code to chew on for the UNO32 .... its had some stuff stripped out as it pertains to some patent stuff I am putting through but there is enough in there function wise to build a nice backend for a roll your own PI .... TX an RX Pulse generator, Low pass filter, audio generator, 24 bit adc driver, SPI driver, RS232 menu driver. Just add a switching mosfet and driver, sample and holds, differential integrator, amplification, voltage limiting, blue tooth module for wireless RS232 remote menu on tablet / phone / laptop and you are in business.

DISCLAIMER .. this not a PI detector source code ... it is a collection of functions and some rough harness code for EXPERIMENTERS ... who basically know what they are doing to get a jumpstart into using a 32 bit procecessor like the one on the UNO32 for implementing a PI detector ...so please dont send me PMs asking for hexcodes ( thanks ). I will answer questions on the code and help with whatever changes you are trying to make as long as you share ... no sharing = no help

This source code will actually compile and is set up to provide basic pulses on the designated output pins ... you will have to investigate how the other functions would be used ... project for the Microchip MPIDE ( set config bits to code ).

Enjoy ...
BEEP002.zip

[Pete the Builder]

Hi!

I'm just dropping in to say "hi" to everyone. Easier than a new post!
So... Hi! 0/
Check out my thread in Misc/Off-Topic for updates and apologies!
Cheers my friends!
-Pete the non-Builder

[sido]

Hey Mick ....you can have as many pulses as you want provided the 32 bit timer has not reached final count in that cycle. There is a limitation however because interrupts are used on each pulse the sequential pulses cannot be too short or the interrupts will clash. For the sd2000 timing the margins are relatively big so no clash occurs. The 12.5 ns timing comes from the 80 MHz clock driving the timing reference. For Ian's application ...and mine also the multi pulse scheme will not be used because the interrupt timing clashes with the ultra short sampling and tx timing. Using one pulse per period per output uses no CPU overhead at all. ie. one tx and 4 sample outputs.

Hi Moodz, exactly what i asked previously.... if it can be done with multiple TX pulse train and samples.....awesome, well done.

Will scrap the UNIPI for now as multiple sampling and complex TX pulse output's opens up alot of experimental possibilities than before and can see other people's experiments further developed in the field of PI design which hopefully can be shared here for all to see.
ATM, I am pre-occupied with other life's commitments, but will order the UNO32 this week

Any chance of programming code?
Highly appreciate your programming skills......let alone your electronic design principles which are above the norm.


Cheers Sid

[moodz]

HI Paul,

Nice job man!!!

So how many times in one cycle can say output 1(or any of them) be turned on and off?
12.5ns resolution, you are the best Don't lower the resolution, if anything have a setting that can be set to adjust resolution.

Cheers Mick

Cheers Mick

Hey Mick ....you can have as many pulses as you want provided the 32 bit timer has not reached final count in that cycle. There is a limitation however because interrupts are used on each pulse the sequential pulses cannot be too short or the interrupts will clash. For the sd2000 timing the margins are relatively big so no clash occurs. The 12.5 ns timing comes from the 80 MHz clock driving the timing reference. For Ian's application ...and mine also the multi pulse scheme will not be used because the interrupt timing clashes with the ultra short sampling and tx timing. Using one pulse per period per output uses no CPU overhead at all. ie. one tx and 4 sample outputs.