• Welcome to Andy's Workshop Forums. Please login or sign up.
 
August 05, 2020, 06:54:15 pm

News:

SMF - Just Installed!


Recent posts

Pages 1 2 3 4 5 6 7 8 9 10
21
General discussion / Re: Process automation: accura...
Last post by Andy Brown - August 06, 2019, 09:47:20 am
Hi, I think you may run out of inputs on a single LTC2986. I would recommend downloading the evaluation software from the analog.com site and running the configuration designer to see if what you're planning is feasible.
22
General discussion / Re: Process automation: accura...
Last post by Bwanna - August 06, 2019, 08:58:43 am
Andy,

Don't mean to hijack this post, but I've starting planning a similar project and wanted to ask if you would have time to provide feedback?  More than happy to start a new post if you want.  Here's a quick summary of what I'm looking to do:

>Inputs: (6) K-type inputs and (2) 2-wire RTD
>SDI output goes to ESP32 running Ardunio IDE
>ESP32 outputs to TFT 320x240 display

Right now, I have a working version for just the 2 RTDs (and a few digital pressure sensors) with an Atmega328p and TFT display.  This project will add the k-types and a larger display. I've already successfully ported the code over for the display, etc. and am now working the inputs.

My first question is if you think the LTC2986 is an appropriate choice for obtaining input from the 8 (6+2) sensors and sending this to the ESP32 in via the SPI connections?

Thanks for your time in reading this.
Cheers,
23
Hardware projects / Re: An easy to build android/b...
Last post by Andy Brown - August 05, 2019, 01:56:12 pm
Hi, I see that there's a script available that converts Altium to KiCad. I'll run it on the schematic at the weekend and if it works then I'll provide the results.
24
stm32plus C++ library / stm32F103vet6 ssd1963 board ha...
Last post by Kamswomy - August 04, 2019, 05:52:01 pm
Hi,
Im glad to share with you a simple but working code ive wrote for use SSD1306 oled display 128x64 with ours pics.

Im using PIC16f1788 and tested on 18f4525.

good for any pic with i2c and 1k and little more of RAM.

line, circle, rect copied and adapted from glcd library


   Code:
25
Hardware projects / Re: An easy to build android/b...
Last post by _jp - August 02, 2019, 04:48:01 am
Hi Andy/Everyone

Thanks for posting so many articles, it really helps newbies like me getting started in electronics hardware projects.

I'm using KiCad and I can load up the the gerber files ok, but I would like to play with the schematic.
Is it permissible (or even possible) to get a copy of the reflow project so I can load the schematic into KiCad?

Also, I really like your process controller articles. Nice one.

JP

26
stm32plus C++ library / How to add/derive support for ...
Last post by avrguru - July 29, 2019, 12:21:41 am
Hi Andy/everyone!  Great projects and amazing library, this stm32plus!

I am trying to add support for the ILI9488 (has more h/w capability & color depth than existing ILI9481).  As a starting point, I tried simply duplicating the ili9481 lib and example directories to be the new ili9488 ones, with the goal of making something *called* ili9488 that was exactly the same as ili9481 but just a different name, to make sure it still compiled after the name change.  I simply changed every '9481' to '9488' in all affected files and file names where it existed, but it won't build successfully.  (I also modified the \display\tft.h file, \display\graphic\tft\TftInterfaces.h file, and \lib\include\error\ErrorProvider.h, since all those include the path to the ili9481 dir's.)  When attempting to build the derived ili9488 Example project, it fails to locate pretty much any header file in my "\src\stm32plus\lib\include\display\graphic\tft\ili9488\commands" folder (at least that seems to be the root cause, not clear) and thus complains about (a few dozen) things like:

lib/include/display/graphic/tft/ili9488/ILI9488.h:187:41: error: 'stm32plus::ili9488::ExitSleepModeCmd' has not been declared
       _accessMode.writeCommand(ili9488::ExitSleepModeCmd::Opcode)

Again, literally, what I did was copy the existing ili9481 folders (lib and example) and globally change every 9481 to a 9488.  I also modified the GUIDs that are present in some of the headers so they'd be different from the '9481 equivalents; no joy.  I'm at a loss as to why these files seem to be unavailable during the build.  Using the following cmd line to compile:  "scons mode=debug mcu=f1hd hse=8000000"   as well as other variants; all give the same result.  Almost seems like I'm missing a pre-compile step (clean? build some other thing first???)  Thanks for any suggestions!
27
Hardware projects / Re: A development board for th...
Last post by Andy Brown - July 20, 2019, 12:41:07 pm
Quote from: Phil on July 20, 2019, 11:45:06 am
Interesting comment on mini-B connector. I always heard that the micro-b was more reliable (see: https://electronics.stackexchange.com/questions/18552/why-was-mini-usb-deprecated-in-favor-of-micro-usb ).

though i only ever had 1 micro-b connector fail (none for micro-b). in the end i standardised on micro-b as this is more common though annoyingly, i still have some mini-b's around which i leave the cable plugged in to avoid annoyance.


Hi Phil, the micro-USB connectors that I encountered were fully SMD and had a tendency to rip off the board taking the pads with them if you pushed too hard. I just had a look on ebay and it looks like you can now get micro connectors with through-hole chassis pins. I would be more confident using those. Based on your linked article it seems I need take care inserting and removing mini-B cables if I want them to last a long time.  My favourite is the original full-size B connector but obviously, it's big.
28
Hardware projects / Re: A development board for th...
Last post by Phil - July 20, 2019, 11:45:06 am
Interesting comment on mini-B connector. I always heard that the micro-b was more reliable (see: https://electronics.stackexchange.com/questions/18552/why-was-mini-usb-deprecated-in-favor-of-micro-usb ).

though i only ever had 1 micro-b connector fail (none for micro-b). in the end i standardised on micro-b as this is more common though annoyingly, i still have some mini-b's around which i leave the cable plugged in to avoid annoyance.

29
Hardware projects / Re: A development board for th...
Last post by Andy Brown - July 14, 2019, 04:57:06 am
Thanks for the info about the crystal and also the ch340. I just tried the new_id method and it did work on my Ubuntu VM. I'll give it a try on the Pi later and will also try the permanent fix. Looks promising though.
30
Hardware projects / Re: A development board for th...
Last post by ddrown - July 13, 2019, 04:37:12 pm
Quote from: Andy Brown on July 13, 2019, 10:22:18 am
I've recently built a development board for the new STM32G081RBT6 MCU featuring the Cortex M0+ core.


Hello! And thank you for your videos, I'm a fan.

You mention in the video trying to get the ch340 to work on linux with the 9986 vendor ID.  I think there's two choices:

* add the IDs to /sys/bus/usb-serial/drivers/ch341-uart/new_id https://stackoverflow.com/questions/442833/forcing-driver-to-device-match  (this will have to happen every time you boot)

* recompile the ch341 driver with the new vendor ID:  https://elixir.bootlin.com/linux/latest/source/drivers/usb/serial/ch341.c#L82  (this would have to happen every time you upgraded your kernel)

Quote from: Andy Brown
I have no idea how crystals are constructed but I do find it fascinating and it looks a bit like a tuning fork. Does anyone out there know what's going on in there?


Crystals physically vibrate so the resemblance to a tuning fork is no accident.  There are different shapes used, and this cut is called the tuning fork shape.  "The chief application [of the tuning fork cut] is the 32.768 kHz RTC crystal" - https://en.wikipedia.org/wiki/Crystal_oscillator#Crystal_cuts
Pages 1 2 3 4 5 6 7 8 9 10