All Forums  GQ Electronics Forums  2.GQ Geiger Muller Counter  Data Viewer V2.69, needs revising

Note: You must be registered in order to post a reply.
To register, click here. Registration is FREE!

Screensize: 640 x 480 800 x 600 1024 x 768 1280 x 1024 UserName: Password: Format Mode: Basic  Help  Prompt  Format: Font Andale Mono Arial Arial Black Book Antiqua Century Gothic Comic Sans MS Courier New Georgia Impact Lucida Console Script MT Bold Stencil Tahoma Times New Roman Trebuchet MS Verdana   Size 1 2 3 4 5 6   Color Black Red Yellow Pink Green Orange Purple Blue Beige Brown Teal Navy Maroon LimeGreen Message: * HTML is OFF * Forum Code is ON Smilies [quote][i]Originally posted by GTS[/i] [br]The latest version, V2.69 of the "Data Viewer" only works after a certain amount of finagling. Connections are reported as successful on COM4. The correct GM device is identified. The heartbeat is reported as started. The Realtime Monitoring check box is checked (this seems to revert back to unchecked most of the time), but nothing is showing up on the graph! Checking the serial port setting in the app says Port: 3, Rate: 57600, Data bit: 8, Parity: None, Stop Bits: 1, Control: None. Noticing that the port is wrong, I change it to COM4 and the Rate to 115200 and punch OK. But for some reason the settings revert to the previous settings!? So I decided to fire up GeigerLog V1.5 v79. It connects no problem. The quicklog works. Everything WORKS. I close down Geigerlog and restart GQ GMC Data Viewer V2.69 and it connects and the realtime monitoring box is checked and the graph is being filled in. So I check the app Serial Port Settings and it's set to Port 3, at a rate of 57600 with the rest of the settings being OK. So I check my computers device manager which is port 4 at 115200. This setting seems to be TOTALLY useless and always wrong. Back to the app which for some reason has stopped graphing!? However when it was working minutes ago, the reported CPM of 55 was reported as .357 uSv/hr. This is calculated to be 154 CPM for 1 uSv/hr. This is not what it should be for the GMC600+ which is 354.1 CPM for 1 uSv/hr. My GMC is reporting the correct uSv/hr based on 354.1 rate. The app says it's connected to a GMC-600+Re 2.52. Now I know that the 154 CPM is for the Geiger tubes in the 300 and 500 series and this was apparently the default setting. AS for the Data Logger PRO V5.61, that one takes a little less finagling to eventually work. It has the same sort of non response to graphing until it is primed with Geigerlog. BTW, this happens with the GQE provided cable and two other cables I have, one new. Also happens with either a direct connect port or a hub. The Geigerlog app seems to be immune to this behavior and temporally passes on this immunity to both GQ apps. How strange is that! [/quote]    Insert an Image File Check here to include your profile signature.