update data problem

I just downloaded the newest update(10.37Mac260). The comport is opened and connected fine but no data is received. Parameters seem to be the same as previously but the data received blinkie is blank. It is not loading most of the data either. Is it stored in a different location now?
Installation is Peet Bros. 2100 in complete record mode. The older version(10.37S build 24) works ok.
Suggestions?

Hi
I will see about getting it to work with this station type this weekend (when I will be able to get to where one of these stations are to test with)
(so for now use the older version)

Great and thank you

Hi
I have done some work on this
in the latest update
its not perfect…I need to do more work
but you could try it

downloaded and installed the latest update to no avail. The only info that displays in the data fields are the clock times but no values. The data received blinkie grays out as soon as the usb/serial interface is recognized and it ceases to blink.

try re selecting the needed comport and select the cu type

I tried releasing the comport then selected the cu type but still no change. I then closed and reopened the program which opened the cu version of the port, but, again, no data.

what shows under view, debug info
(and make sure to have ticked, setup, advanced/misc, log the raw data)

I totally screwed up everything and both old and new versions quit when I try to start them now. The following is the apple debug info if that helps

Apple debug info when the program suddenly quits

Process: weatherdisplay [513]
Path: /Applications/weatherdisplay.app/Contents/MacOS/weatherdisplay
Identifier: weatherdisplay
Version: 1.0 (1.0.0)
Code Type: X86 (Native)
Parent Process: ??? [1]
Responsible: weatherdisplay [513]
User ID: 501

Date/Time: 2015-11-19 07:50:19.972 -0500
OS Version: Mac OS X 10.10.5 (14F1021)
Report Version: 11
Anonymous UUID: 0621D004-3A96-5663-E238-037355D653FC

Time Awake Since Boot: 1100 seconds

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00000000bf7ffffc

VM Regions Near 0xbf7ffffc:
Stack 00000000b031f000-00000000b03a0000 [ 516K] rw-/rwx SM=COW
→ Stack 00000000bc000000-00000000bf800000 [ 56.0M] —/rwx SM=NUL
Stack 00000000bf800000-00000000c0000000 [ 8192K] rw-/rwx SM=COW

Application Specific Information:
BUG IN CLIENT OF LIBDISPATCH: Semaphore/group object deallocated while in use

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 weatherdisplay 0x0003ba2f catch_exception_raise_state_identity + 1255
1 weatherdisplay 0x0002a02b _dbk_fcall_wrapper + 5791
2 weatherdisplay 0x0002a0c3 _dbk_fcall_wrapper + 5943
3 weatherdisplay 0x0002a118 _dbk_fcall_wrapper + 6028
4 weatherdisplay 0x0002bbf3 _dbk_fcall_wrapper + 12903
5 weatherdisplay 0x000113bb 0x10000 + 5051
6 weatherdisplay 0x0003b9d8 catch_exception_raise_state_identity + 1168
7 weatherdisplay 0x00019237 0x10000 + 37431
8 weatherdisplay 0x0001c5ce @DbgExcNotify + 4906
9 weatherdisplay 0x0003b9d8 catch_exception_raise_state_identity + 1168
10 weatherdisplay 0x00019237 0x10000 + 37431

As an addendum,I clicked on the weather display executable while “open with” was on “terminal”. Thereafter the program crashed.

try as a test
back up
then delete
the wdisplayftp.ini settings file
then see if the program runs

No luck. Nothing changed.

bring back the backed up wdisplayftp.ini file
then do the same for the WDISPLAY.INI settings file
(i.e back up, then delete that)

Deleting the WDISPLAY.INI allows the program to run the older version(haven’t tried the new one yet). All instruments & graphs are ok though the program runs really rough. Selecting options might or might not work, closing option may or may not work, etc. I closed the program once to see if it would run smoother but had to repeat the delete of WDISPLAY.INI to get it to reboot. Am just letting it go for a while to see what happens. Then I’ll try with the new program version. When I restored the wdisplay.ini file I had to use a slightly older backup as I lost the newest one. Hopefully that is not a problem.

when I next visit my brother, who has an ultimeter
(I visit him to help him a shed roof repair ), I wll do more testing and improving :wink:

Great. After 24 hours the old program is running fine. I attempted to log the data, but as soon as I checked the appropriate box the computer showed constant disk access preventing me from doing anything. I finally had to force quit, delete the WDISPLAY.INI file again and start over.

Hi
which version is that with?
and when you say log data, what setting is that?

Version is 10.37S build 24.
Everything comes to a halt including the clock when I go into advanced/misc & tick log the raw data.
At that point the computer indicates constant disk access & nothing can be done except force quit the program at which point I have to delete the WEATHERDISPLAY.INI file and start over to make it reboot.

Hi
just to be clear, that particular problem you are describing occurs with vers 10.37S build 24?

yes. 10.37s build 24. This version runs fine. I only mention the program locking up because you requested I log data for trouble shooting.
When I attempt to run 10.37 build 262 the program sees the com port but will not collect data so I went back to the earlier version.