Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - needhmi

Pages: [1]
1
Did a short search for this, is it possible to change the way the datalogger21 writes the bit status in the data log?  I'm using the ModbusRTUCom1 driver, version 3.99w, Visual Studio 15.9.11

I would like it to write the bit status (address of 0000x) as a 1 or a 0 instead of false or true in the data log .csv file.  In the past I have copied bits to a UI8 data type in the PLC solution (address of 4000x) and this works but I'd rather not need to do that if possible.  Thanks!

2
Fairly often I get an unhandled exception error message, along with a white circle and red "X" through my compact gauge.  If I close out the form and reopen, sometimes it takes multiple times, it finally works fine.  Using 3.99w, ModBusRTU.  Driver Log file is attached in case it's helpful, I see the "send" has more data than the "receive" and the data doesn't match, but don't know what that means.  Does the max read group size have anything to do with this perhaps, I have it set at 50 for the log noted as such?  I changed that and the pollrate override to 0 and 5 respectively.  I changed the baud rate on the driver to match on the computer side in my device manager settings.  I'm suspecting it could be the PLC performance, but any other ideas or ways to match the HMI to what the PLC can do?  Thanks!

The full part of the exception text reads:
System.ArgumentException: Parameter is not valid.
   at System.Drawing.Graphics.set_Transform(Matrix value)
   at MfgControl.AdvancedHMI.Controls.MeterCompact.DrawNeedle(Graphics g, Single angle, Int32 cx, Int32 cy)
   at MfgControl.AdvancedHMI.Controls.GaugeCompact.PaintActiveContent(Graphics g)
   at MfgControl.AdvancedHMI.Controls.MeterCompact.OnPaint(PaintEventArgs e)
   at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer)
   at System.Windows.Forms.Control.WmPaint(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

3
Support Questions / Sign Tool Error: No certificates were found
« on: May 05, 2018, 09:30:42 AM »
I've been using Visual Studio version 17 for several months with no issues, but last night got this error when trying to build:
An error occurred while signing: Failed to sign bin\Debug\app.publish\AdvancedHMI.exe. SignTool Error: No certificates were found that met all the given criteria.         

I thought it may be due to the changes I was making to my project, so went back to an old project and still have the same error. 

Any ideas?   

4
Support Questions / ModbusRTU driver not closing?
« on: June 01, 2017, 05:09:20 PM »
My solution has two forms, and both need the ModbusRTU driver.  I put the BasicDataLogger21 on page 2 and for some reason the pollrate seems much slower.  It seems that the slowness is caused from the mainform's driver remaining active.  When I go back to the main form, there is no normal delay for the driver to connect. 

I'm using a FormChangeButton to change forms.  Is there a different button I need to use or a setting I possibly have missed to close the mainform when I open page 2?

Thanks! 

5
Support Questions / The Given Key Not Found
« on: April 29, 2017, 08:13:47 PM »
My application runs fine in debug mode, with no errors - but after I have it published and installed on different computers the message "The Given Key Not Found in Dictionary" shows up on most of my "Value" or "Text" properties on my mainform.vb. 

I'm assuming I am missing some sort of dependency on the computers I have installed it on.  I found the "Prerequisites" tab in the Advanced HMI Properties section and a couple prerequisites that are not checked have flags:

.NET Framework 3.5 SP1 Client Profile

Windows Installer 3.1

Thanks for any ideas!  I'm really new to this stuff. 


6
Support Questions / time stamp format for data log
« on: April 27, 2017, 02:11:54 PM »
Thanks for the great open source HMI solution and this forum!

Is it possible to get milliseconds in the BasicDataLogger21 TimeStampFormat?  I have tried HH:mm:ss.ms.  I am using a 40ms log interval - and the stamps happen at the correct rate, but the milliseconds show up duplicated instead of counting up, like:

HH:MM:SS.?

12:01:01.11
12:01:01.11 .... until the second changes, then
12:01:02.12

I'm assuming I just don't have the right value for milliseconds in my format. 

Pages: [1]