Data output issue using Raspberrypi v3 B+ and ConsoleWD issue 17.3

Hi
If you are referring to the “Timezone =” parameter in the config file I have already used Timezone =+1 and this did not increment the time by 1 hour.

Regards

Hi
Try on the raspberrypi open the terminal and Set time to London. Type

don’t use +1
just use
1

Hi,
I will try that next time, however, your idea about setting up the Pi fixed the problem.

Regarding using the

so you are not seeing any graph data?
is consolewd updating the logfiles OK?

I suspect that if you close wdpi and then re open it, the graph data is updated?

Hi Steve
I tried your suggestion but it did not work.

Run the main program, started dpi at 17:41 26/06/18 run it until 18:15 still with the main programming running closed wdpi and then restarted it, however still no chats displayed.
Have attached screen dump and the log file.

Regards


Test Data.zip (194 KB)

i have tested here and it works as I have described OK
that screen shot is very small image…hard to make out anything

Screen Dump V2


I have found one bug that will cause a silent crash and stop the graph from updating
I will get that version uploaded for you

Thank you, just let me know when you have uploaded it

actually, if you could .zip and email me your data files
last31daysdata.inf and latest.inf and latestindoor.inf
I will test/check here

I have zip’ed the whole folder, cant see the last one you have identified


datafiles.zip (22.2 KB)

i am getting closer to a resolution :slight_smile:

try a new update of consolewd for raspberrypi 3 from the download page
new version of wdpi and consolwd (update both)

graph should work for you hopefully
I have still not fixed it not updating at this stage (a restart does though)

Hi Steve
I have downloaded your updated file run consolewdfiles using sudo ./consolewd

once data was being logged I then opened wdpi no chat were displayed

still keeping consolewd logging data I closed wdpi then reopened dpi still no chats were displayed
Repeated this a few times on the last occasion I opened wdpi using the terminal mode, see below for data logged:-

[HINT] TWinControl.CreateWnd creating Handle during loading mainform:Tmainform csDesigning=False
[HINT] TWinControl.CreateWnd creating Handle during loading data_rec:TEdit csDesigning=False
[HINT] TWinControl.CreateWnd creating Handle during loading data_qual:TEdit csDesigning=False

(wdpi:1042): Gdk-CRITICAL **: IA__gdk_drawable_get_size: assertion ‘GDK_IS_DRAWABLE (drawable)’ failed

(wdpi:1042): Gdk-CRITICAL **: IA__gdk_drawable_get_size: assertion ‘GDK_IS_DRAWABLE (drawable)’ failed

(wdpi:1042): Gdk-CRITICAL **: IA__gdk_drawable_get_size: assertion ‘GDK_IS_DRAWABLE (drawable)’ failed

(wdpi:1042): Gdk-CRITICAL **: IA__gdk_drawable_get_size: assertion ‘GDK_IS_DRAWABLE (drawable)’ failed
ERROR in LCL: TGtk2WidgetSet.StretchCopyArea DestDC=759E05E0 Drawable=nil
Creating gdb catchable error:

$00134474 TLAZLOGGER__DEBUGLNSTACK, line 676 of lazloggerbase.pas
$000DF7AC DUMPSTACK, line 1415 of lclproc.pas
$000DD2B4 RAISEGDBEXCEPTION, line 860 of lclproc.pas
$001F2E24 RAISEDESTDRAWABLENIL, line 4060 of gtk2widgetset.inc
$001F29A4 TGTK2WIDGETSET__STRETCHCOPYAREA, line 4123 of gtk2widgetset.inc
$002114B4 TGTK2WIDGETSET__STRETCHMASKBLT, line 9489 of gtk2winapi.inc
$00197B6C STRETCHMASKBLT, line 467 of ./include/lclintf.inc
$00173314 TRASTERIMAGE__DRAW, line 246 of ./include/rasterimage.inc
$0017ED90 TCANVAS__STRETCHDRAW, line 48 of ./include/canvas.inc

are you using the new version?
1.4
of the WDPI program

Yes WD PI Vers 1.4 it the one in the updated folder I downloaded, I’m running it within the consolewd folder structure

I suspect those GDK errors are the issue

another way to see the data would be to setup meteotemplate
or
fresh WDL
or similar

Pleased I was able to provide some useful data