Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
4.1 Beta Discussions Thread
#11
I wasn't up to dealing with the big, big picture again yesterday, so I took on another task that I figured I could get done in a day. I didn't quite make it so I had to finish it up today. So, now there is a calendar widget.

[Image: CalendarWidget.jpg]

This initial implementation is a 'static calendar', so like other static widgets it's not connected to anything, it's just maintaining its own state. It accepts commands to move forward and back by month at a time, which the buttons on the top are sending.

It sends out an action event when you scroll the month or when you click on a day. In the example above the scrolling event is used to maintain the the text above the calendar that is showing the currently displayed month/year. During scrolling the day is meaningless. When you click, then the day RTV is also valid. So you can use the calendar to allow your users to pick some day that you can use for whatever purposes you want.

You can set an image that it will display behind today's date if you want. Otherwise today's date isn't treated differently.

You can set a 'selection type' on it. It defaults to 'All', which means any day clicked on will send out an action event. But you can set it to Forward or Reverse, in which case it will (respectively) ignore clicks on any day before today, or any day after today. Today is always legal.

The days of the week title bar across the top is not part of the calendar. I just drew that. It doesn't try to draw lines and the days of the week bar and such because it would never be flexible enough. In many cases folks will want to layer it over a background images and will need control over where these other elements are placed. So it just draws the day numbers and that's it.
Dean Roddey
Explorans limites defectum
#12
Dean

Is there any chance we could get a dial indicator. Something like a tacho gauge.

Mick
Mykel Koblenz
Illawarra Smart Home
#13
It could be done. Actually it could be done already with the logo image widget. All it would end up being is a set of images of a needle indicator, with one for each degree I assume, layered over whatever sort of background image you want. Even it was a new widget type, it would basically still be that. Trying to draw the needle would be a waste of effort. It would never look good enough.
Dean Roddey
Explorans limites defectum
#14
Yeah I had thought of that, but that's a lot of work to get a needle to move around, hence a widget would be better.

Let the user draw the needle, just supply the ability to put an image in as the background and one for the needle. let the field value do the rotation.

Maybe we need something where we can rotate and use logic on the value.

eg, rotate <image> (moniker.field*3.6). This would allow the field value (0-100) to be used and rotate the image through 360°.

You only use one image then and configuration is much faster.

I have used a system that employes this type of graphical configuration and it is one of the best I have used. Every aspect can be done via a formulae - Colours, size, text size everything. Its not just tied to the tag value, but every aspect of the tag and global tags as well (or in CQC speak, you could use variable driver, logic server driver anything to change colours etc).

I would love to see that introduced. (Bit of a digression from the original request)
Mykel Koblenz
Illawarra Smart Home
#15
A single image probably wouldn't work. Well, it would work technically but probably not what most folks would want, i.e. a more realistic look. That would require a shadow that changes position correctly based on the direction of the needle. That would pretty much require that each possible position be an image. And in some cases it wouldn't be something that looks the same in each possible rotated position either. So, for flexibility, using an image per possible rotation position would probably be the safest bet.

I guess it could allow for either scheme. But even something like a compass without a needle but a rotating background image, it would still want to have a shadow effect for realism and there's not really any way CQC could figure out how to correctly apply such a shadow after the fact to a single image. And here I don't mean under the rotating background, but that thrown onto the background, even if it's just a simple gradient shading.
Dean Roddey
Explorans limites defectum
#16
No work today. I got it into my head to do an epic music room re-arrangement. It's like The Godfather. These things have to happen every few years, but they are painful and dangerous. I'm going to seriously regret this tomorrow when I can barely stand up straight, and I'm still not quite done. But, it's a double benefit since it'll be a big improvement and it's a bodacious workout as well and I needed the exercise.
Dean Roddey
Explorans limites defectum
#17
Interesting... Can you put the Elk driver into verbose mode and make it happen and get me a log dump? Maybe it's just something as simple as the Elk taking longer to respond because of someone fighting it for attention. Or it could be something else. But that the log dump in verbose mode should help us pin it down.

Took me a while but i finally got a dump for you when it lost connection

09/19 15:11:29-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.3056, Status/App Status
Timed Out
}
09/19 15:11:29-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCKit, CQCKit_DriverBase.cpp.5080, Status/App Status
Driver 'Elk' has lost connection to it's device
}
09/19 15:11:39-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCKit, CQCKit_DriverBase.cpp.2927, Status/App Status
Driver 'Elk' is trying to connect to its device
}
09/19 15:11:39-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 06rr00
}
09/19 15:11:39-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command as
}
09/19 15:11:39-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command zs
}
09/19 15:11:39-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.2714, Status/App Status
Querying M1 version number
}
09/19 15:11:39-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 06vn00
}
09/19 15:11:40-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command xk
}
09/19 15:11:40-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command vn
}
09/19 15:11:40-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.2720, Status/App Status
Got version number reply
}
09/19 15:11:40-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.2743, Status/App Status
Elk version is: 5.1.24
}
09/19 15:11:40-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 06cp00
}
09/19 15:11:40-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command cr
}
09/19 15:11:40-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 06zs00
}
09/19 15:11:40-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command zs
}
09/19 15:11:40-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 06as00
}
09/19 15:11:40-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command as
}
09/19 15:11:40-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 06cs00
}
09/19 15:11:40-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command cs
}
09/19 15:11:40-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 06ss00
}
09/19 15:11:41-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command ss
}
09/19 15:11:41-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 07ps000
}
09/19 15:11:41-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command ps
}
09/19 15:11:41-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1014, Status/App Status
PLCBlock: 00000100001110000000000000000000000000000000000000000000000000000
}
09/19 15:11:41-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 08tr0100
}
09/19 15:11:41-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command tr
}
09/19 15:11:41-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 09st00100
}
09/19 15:11:41-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command st
}
09/19 15:11:41-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 09st00200
}
09/19 15:11:41-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command st
}
09/19 15:11:41-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 09st00300
}
09/19 15:11:42-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command st
}
09/19 15:11:42-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 09st00400
}
09/19 15:11:42-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command st
}
09/19 15:11:42-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 09st00500
}
09/19 15:11:42-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command st
}
09/19 15:11:42-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 09st00600
}
09/19 15:11:42-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command st
}
09/19 15:11:42-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 09st00700
}
09/19 15:11:42-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command st
}
09/19 15:11:42-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 09st00800
}
09/19 15:11:43-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command st
}
09/19 15:11:43-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 09st00900
}
09/19 15:11:43-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command st
}
09/19 15:11:43-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 09st10100
}
09/19 15:11:43-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command st
}
09/19 15:11:43-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCKit, CQCKit_DriverBase.cpp.2969, Status/App Status
Driver 'Elk' has connected to its device
}
09/19 15:11:43-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 06cp00
}
09/19 15:11:43-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command cr
}
09/19 15:11:43-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 06zs00
}
09/19 15:11:43-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command zs
}
#18
It looks like it had already lost the connection by the time you enabed the verbose logging? Does it happen often enough that you could catch one while it's in verbose mode?
Dean Roddey
Explorans limites defectum
#19
Dean Roddey Wrote:It looks like it had already lost the connection by the time you enabed the verbose logging? Does it happen often enough that you could catch one while it's in verbose mode?
Yeah i noticed that too but couldnt work out what was going on cause it was in high verbose mode for 15min prior to it losing connection.
Ill try it again, hopefully wont take me so long to catch it this time.
#20
got it all this time

09/19 16:51:50-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command zs
}
09/19 16:52:00-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command as
}
09/19 16:52:00-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 06cp00
}
09/19 16:52:00-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command zs
}
09/19 16:52:02-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.3056, Status/App Status
Timed Out
}
09/19 16:52:02-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCKit, CQCKit_DriverBase.cpp.5080, Status/App Status
Driver 'Elk' has lost connection to it's device
}
09/19 16:52:12-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCKit, CQCKit_DriverBase.cpp.2927, Status/App Status
Driver 'Elk' is trying to connect to its device
}
09/19 16:52:12-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 06rr00
}
09/19 16:52:12-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command as
}
09/19 16:52:12-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command zs
}
09/19 16:52:12-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.2714, Status/App Status
Querying M1 version number
}
09/19 16:52:12-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 06vn00
}
09/19 16:52:13-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command vn
}
09/19 16:52:13-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.2720, Status/App Status
Got version number reply
}
09/19 16:52:13-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.2743, Status/App Status
Elk version is: 5.1.24
}
09/19 16:52:13-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 06cp00
}
09/19 16:52:13-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command xk
}
09/19 16:52:13-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command cr
}
09/19 16:52:13-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 06zs00
}
09/19 16:52:13-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command zs
}
09/19 16:52:13-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 06as00
}
09/19 16:52:13-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command as
}
09/19 16:52:13-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 06cs00
}
09/19 16:52:13-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command cs
}
09/19 16:52:13-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 06ss00
}
09/19 16:52:14-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command ss
}
09/19 16:52:14-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 07ps000
}
09/19 16:52:14-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command ps
}
09/19 16:52:14-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1014, Status/App Status
PLCBlock: 00000100001110000000000000000000000000000000000000000000000000000
}
09/19 16:52:14-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 08tr0100
}
09/19 16:52:14-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command tr
}
09/19 16:52:14-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 09st00100
}
09/19 16:52:14-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command st
}
09/19 16:52:14-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 09st00200
}
09/19 16:52:14-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command st
}
09/19 16:52:14-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 09st00300
}
09/19 16:52:15-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command st
}
09/19 16:52:15-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 09st00400
}
09/19 16:52:15-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command st
}
09/19 16:52:15-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 09st00500
}
09/19 16:52:15-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command st
}
09/19 16:52:15-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 09st00600
}
09/19 16:52:15-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command st
}
09/19 16:52:15-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 09st00700
}
09/19 16:52:15-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command st
}
09/19 16:52:15-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 09st00800
}
09/19 16:52:16-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command st
}
09/19 16:52:16-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 09st00900
}
09/19 16:52:16-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command st
}
09/19 16:52:16-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 09st10100
}
09/19 16:52:16-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command st
}
09/19 16:52:16-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCKit, CQCKit_DriverBase.cpp.2969, Status/App Status
Driver 'Elk' has connected to its device
}
09/19 16:52:16-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 06cp00
}
09/19 16:52:16-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command cr
}
09/19 16:52:16-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.430, Status/App Status
->Elk: 06zs00
}
09/19 16:52:16-server, CQCServer, CQCDrv_Elk_Thread23
{
CQCGenDrvS, MEng.System.CQC.Drivers.ElkM1.DriverImpl.1866, Status/App Status
Got command zs
}


Possibly Related Threads...
Thread Author Replies Views Last Post
  Official 5.4 Beta Discussion Thread Dean Roddey 441 41,754 06-15-2019, 02:33 AM
Last Post: Bugman
  Official 5.4 Beta Release Thread Dean Roddey 55 7,322 06-07-2019, 07:02 PM
Last Post: Dean Roddey
  Official 5.3 Beta Discussion Thread Dean Roddey 815 151,299 07-05-2018, 12:44 PM
Last Post: Dean Roddey
  Official 5.3 Release Thread Dean Roddey 27 7,910 07-05-2018, 12:44 PM
Last Post: Dean Roddey
  Official 5.2 Beta Discussion Thread Dean Roddey 244 87,644 10-14-2017, 07:57 PM
Last Post: Dean Roddey
  Official 5.2 Beta Release Thread Dean Roddey 13 8,804 10-09-2017, 06:49 PM
Last Post: Dean Roddey
  Official 5.1 Beta Discussion Thread Dean Roddey 453 197,127 05-16-2017, 03:45 PM
Last Post: Dean Roddey
  Official 5.1 Beta Release Thread Dean Roddey 28 19,502 05-12-2017, 05:44 PM
Last Post: Dean Roddey
  Official 5.0 Beta Discussions Dean Roddey 2,019 489,144 11-09-2016, 04:34 PM
Last Post: Dean Roddey
  Official 5.0 Beta Release Thread Dean Roddey 15 13,314 11-01-2016, 10:32 AM
Last Post: Dean Roddey

Forum Jump:


Users browsing this thread: 1 Guest(s)