Author Topic: Working on the new eParrot 2018 (Read 39812 times)

ShiFu · « **on:** August 22, 2018, 02:46:37 PM »

This a good place to keep the notes, questions and problems associated with the new RGB LCD eParrot with Edwin's new PCB.

Quote

... out of 10 start ups maybe 6 times I have to reset...

Sorry, K3, I can't think of a reason for that.

At the moment I'm playing with the Data Logging feature and I'm not doing so great.
But really its my first time to dig into this feature.

ShiFu · « **Reply #1 on:** August 22, 2018, 02:48:58 PM »

In just a few minutes it generated hundreds of lines of excel data (but the file is not very large at all).
This is normal?

And the screen goes blank when I select the Data Logging to begin.

Oops, I bet I forgot to cut one of the pins off the new RGB shield!

ketel3 · « **Reply #2 on:** August 22, 2018, 02:53:29 PM »

Edwin explaned in a post how he does it,with his data.

And yep continue here is better.

ShiFu · « **Reply #3 on:** August 22, 2018, 03:02:25 PM »

Yep, removed that pesky pin and the Data Logger is working exactly as it should.

I'll let it run awhile and take a look at what it generates.

Another minor problem solved today! I'm on a roll

Working on the new eParrot 2018

DataLoggin.png (168 kB. 350x262 - viewed 1538 times.)

ketel3 · « **Reply #4 on:** August 22, 2018, 03:08:03 PM »

It is nice to have that feature,maybe you can see how the boiler pressure senor and the vents sensors are working if there is no data loss,like I had in the past without resistors.

ShiFu · « **Reply #5 on:** August 22, 2018, 03:16:01 PM »

Yikes! Boiler Pressure Sensor.

Another can of worms.

Its been baby steps for the past several days. I may need to stare at that one for a long while

ketel3 · « **Reply #6 on:** August 22, 2018, 03:24:03 PM »

The boiler pressure sensor is a great feature , I clould give advise on the Dutch forum as there was a heavy discusion about how tight the scrubbys should fitted and the possible danger of tight scrubbys,spp also.
I did a test with very tight pressed scrubs and never the alarm value of the eparrot was reached.
So end to all speculations thanks to the eparrot

The only isue was converting dpa to understandable pressure like mbar

ShiFu · « **Reply #7 on:** August 22, 2018, 03:40:22 PM »

If I remember correctly, the alarms need to be set. And they are active/inactive when you change the display color.

From the Friendly Manual:

Quote

Short press on Select switches alarm on (backlight goes to green when buzzer is audial, blue when buzzer is silent) or acknowledge alarm when active and triggered.
Long press on Select toggles between silent and audial.

Something like that. I'm taking this one little step at a time and not moving forward until it all looks and feels solid to me.
I've forgotten a lot since last year and some of it I never really learned!
Then I'll start a fresh, new build and document it.
Pictures and everything. Just like the old days.

Lots of progress so far in just a few days.
And these new PCBs make the assembly SO much easier than the original RBG eParrot build. Most of the wiring work is already done by the PCB (printed circuit board).

I agree about the Boiler Pressure Sensor. It should be a required safety feature on any still.
It only takes one "OH SHIT!!" to spoil everything.

ShiFu · « **Reply #8 on:** August 22, 2018, 04:00:09 PM »

Also, after selecting the logging to start, you can navigate back to the start screen to see the eParrot's current %ABV production and the Data Logging continues in the background.

That's a very nice feature but I suspect you do need to stop logging before shutting down the eParrot or you may risk data loss or corruption. (I have not tested this, so corruption may or may not happen).

ketel3 · « **Reply #9 on:** August 22, 2018, 04:06:08 PM »

Well,Edwin told me the alarm screens are not as in the past ,the sound can not be disabled anymore.
And the display color well I dint try the green screen maube that is the problem.
Good test saturday I will do a run.

I think the logged data will stay on the sd card untill it is full and overwrite the old data or refresh to zero,
closing down the eparrot in my opinion does not erase all data.

ShiFu · « **Reply #10 on:** August 22, 2018, 04:28:03 PM »

Quote

the sound can not be disabled anymore

Oh no! Really? I was used to pushing the temporary mute button so I didn't have to be bothered with the alarms

on my previous eParrot.

I don't think the SD card will get overwritten automatically, more likely the "SD card Full" error will cause you to power-cycle your eParrot.
But I'm not certain about any of this.
I'm learning those little bits now.

"No SD Card" and "SD card Full" are errors when data logging.

But I think it will take a long time to fill a 2GB data card with excel cs files.
I just ran a test data log for about 2 hours and the size was a tiny 225 kb. That's almost nothing to a multi GB card unless you intend to log for a VERY long time.

And a "small" 2 GB data card is getting harder to find. Most are 16 or 32 GB or even more.
My latest USB "Thumb Drive" is an incredible 2 TB capacity. Oh my, 2 TB of data (files, music, movies, anything... on a cheap device the size of your finger).

For 3D printing my best option is a card 2 GB or less and those are getting really hard to get locally.

For Data Logging an eParrot? I don't know what is the optimal size data card. I suspect 2 GB but I don't know for sure.

Edwin's sketch is tested to 16, 32 or higher GB? (Not that the higher GB is even necessary. I'm just curious.)

ShiFu · « **Reply #11 on:** August 22, 2018, 05:22:37 PM »

Up next, EEPROM.

The EEPROM (Electrically Erasable Programmable Read-Only Memory) chip is necessary when building the eParrot because the Nano needs that extra memory.
It is cheap, about a buck or so. It stores program data. It does stuff that I don't fully understand. It is magical and the eParrot with the Nano/Uno needs it.
Why? We will explore this question.

Does the Nano and EEPROM need to be installed together on the PCB before burning the eParrot sketch to the Nano?
Well, does it??

Inquiring minds want to know.

Working on the new eParrot 2018

eeprom.png (328.4 kB. 350x466 - viewed 1429 times.)

ketel3 · « **Reply #12 on:** August 22, 2018, 05:26:47 PM »

Yep no alarms without sound

But you can overrule the alarm by one button press.

And yes I did not look into Edwin's invention too ,so do not understand what its all doing.
BUT even more credits for Edwin for making this all work .

EDIT: a new build with photo's and info will be of help to others as things are changed very much,with the old info you cant build this newer version.
However both should be available.

ShiFu · « **Reply #13 on:** August 22, 2018, 06:22:39 PM »

More testing needs to be done but I did burn the Uno/Nano sketch before installing it to the PCB, without the EEPROM, and everything seems to be working OK.
So does the PCB need the EEPROM and Uno together or not before flashing the sketch, I'd say "Probably No".
But I'm not sure yet.

There could be something waiting to bite me. Always there is something I don't know about that is wanting to bite me. Usually something very small that takes a big bite.

Does the Uno/Nano and the EEPROM need to be programmed while connected together? I'm thinking no, but I'm an idiot.
How about you?

ketel3 · « **Reply #14 on:** August 22, 2018, 08:54:24 PM »

Well,if it works it works,but does everything works during a running test ?

And your are not the only one who got bitten.
I walked with Nando yesterday and a wasp landed on my ear ,before I could react he already had me ,awefull pain.

Bitten by a software bug is more harmless

I hope you can test some alarms soon,maybe my version has a bug

One more thing my rgb display is the one used with the old version, the one that had a breakdown/blew up due the connectors ...... so maybe that is the reason I have to reset sometimes to start the eparrot.?
It could be the display got hit too

ShiFu · « **Reply #15 on:** August 23, 2018, 07:12:24 AM »

I can probably test some alarms soon but not the Boiler Pressure.
I'll need to order those parts again. The one I had got lost.

The wasp attack is terrible. It definitely becomes your center of attention. Nature gave some bugs real power.

With that much damage to your RGB display shield it really should be replaced.
Who knows, maybe your alarms will start working again too.

ShiFu · « **Reply #16 on:** August 23, 2018, 07:56:25 AM »

The EEPROM.
Why do we need it? What does it do?

I haven't a clue.
I set the date and time on the eParrot, then set 2 offsets - one for vapor and the other for vapor.
You'd think the EEPROM would be storing the offsets but it does not.
The offsets are apparently being stored in the RTC's onboard memory.

To test this...
I put 2 offsets as described above and power cycled the eParrot, and verified that the offsets were in fact set.
I then removed the EEPROM and replaced it with a brand new one.
Upon power up, the offsets were still there. This proves a couple of things...
The offsets are not being stored in the EEPROM and the eParrot sketch was unaffected by replacing the EEPROM with a fresh one.

To go one step further, I removed the RTC battery, waited a few seconds and replaced it, powered up and yes, the date/time and offsets were all back to zero.

I removed the EEPROM from the PCB and powered up. I could find nothing wrong with the eParrot's operation with the EEPROM removed.
Putting the sensors in boiling water proved the eParrot was displaying %ABV so it doesn't look like its needed for that, either.

So what is the EEPROM for? What is its purpose? What does it do for us?

ketel3 · « **Reply #17 on:** August 23, 2018, 12:51:02 PM »

Well maybe or maybe not you need te eeprom during programming the arduino ? as tempory memory.
Quit nice experiment.
Sir Edwin can explane but where is he

And yes I will order a new rgb and see what happens,always ok to have a spare one.

ShiFu · « **Reply #18 on:** August 23, 2018, 02:09:23 PM »

After a bit of research, I've found an old post from Edwin, dated September 02, 2017:

Quote

I am working on the future version now

The basic version (MK1) is almost done and accepts the DS18B20 as temperature sensors only, Need some more testing. Maybe I can squeeze the logic for two more sensors in for the condenser alarms. Please let me know what you want

The extended version (MK2) adds SMT172 capability for the vapor sensor and needs additional power supply filtering and a 24cl256 eeprom. (less then $2 from Robotdyn) (This night I got this working Optional is a pressure sensor.

So I assume the EEPROM is only necessary if the SMT172 sensor is used?

ketel3 · « **Reply #19 on:** August 23, 2018, 02:30:18 PM »

Hello Sherlock , very good investigation

At the start I presumed the ds sensors were ok why do I need a smt172 ,but during the visit@ Edwin's place I noticed the big differance, steps 0,06 or 0,01 dgrs seems not that Importand but converting to abv does , as the steps abv with 0,06 dgrs sensors are simply to big.

The run tomorrow will be a pleasure

with the eparrot.