Joined: Nov 01, 2003
Posts: 127
Location: Hampshire
Posted: Sun Jan 15, 2006 4:31 pm Post subject: Betatesters wanted
Hi all,
I did star a new project, that could be interesting for those driving with tacho and under EC rules (at this stage).
It intends to be similar to the Drivers Hour Guard, but a little more complex in a near future, executed in a PDA (possibly in SmartPhones in the future).
Basically it will keep record of the drivers activity and showing to the driver:
Actual date and time
Total Time On (For wages purpouses)
Effective Working Time
Driving Time
Other Jobs Time
Actual Break Time
Accumulated Break Time
How long (as maximum) for the next break
How long (as minimum) should be the next break.
In a seconde stage the program will keep records of dayly activity as long as the customer wants to keep. This second stage will start as soon I will know the obtained records are accurated and reliable.
For a third stage I intend to analyze the records to keep drivers legal about the dayly, weekly rest periods.
If there are customers working under other regulations I could think about a fourth stage where regulations could be changed through a setup.
The program can be handled with a finger touch with just four buttons:
New Day/Driving
Other Jobs
Break
End of Day
I´m testing it whilst TTN 5 is running without any problem.
I would like to have between 10 and 20 betatesters. If you are interested just drop me an email to info@geopostcode.com
ive been using the first version this week and looks very promissing indeed he is looking at adding a poa button as well at the moment its in the very early stages at the moment thought but is a stable program
posted with the permission of lucy
Currently I started the second stage on the beta version and included your suggestion about PoA that currently is already working.
In this second stage I will try to make the program to survive even to a hard reset, so you will be able to retrieve your data and the last button you tapped, I mean the last partial day recorded if there was some serious fault in your machine.
As I know you are working in landscape mode and this is becoming more and more usual these days, the program is too now responsive to these changes.
Here are some screenshots, I think they are selfexplanatory but if somebody likes to have more information feel free to PM or email me.
Once downloaded just run it in your computer with your PDA syncy and it will install it for you.
When asked for name, company and serial number you can leave it blank.
When asked to install it in Default Folder you can say NO, strongly suggested, and then you can select to install it in your Memory Card. In this way the data will survive even a hard reset.
This is the second stage. So data cannot yet be retrieved.
The OK button at the top of the screen is a simulator for soft reset that will affect only to this program, closing it instantly without to save data. Once running again you can check your clocks are still correct and they survived the “incident”.
If somebody needs further help don´t hesitate to contact me, and same, of course, for your suggestions and comments.
spacemonkey what type of smartphone do you have is it windows or a nokia smartphone if its something like an xda 2 2s etc then yes it will work I don’t think at the moment that the new xda such as the xdamini s t mobile mda vario will work as the it has a newer version o windows mobile currently it will work with wm2003 wm2003se and in threory run on a pocketpc 2002 if it has an arm processorr tough I’m hoping to try the ppc2002 this 3weekend at some point
It will run on the vast majority of Windows CE devices produced. However, there are quite a number of variations of these devices. Here, by version of Windows CE, are the devices that are supported. You can get the version of Windows CE from the Settings…System screen on the device if you are not sure.
Windows CE 5.0
All Windows Mobile 5.0 Pocket PC devices
All Windows Mobile 5.0 Pocket PC Phone Edition devices
Smartphone devices (other than Pocket PC Phone Edition) are not supported. The ROMs of these devices do not have the MFC (Microsoft Foundation Class) compenents that NS Basic/CE needs to run.
Windows CE .NET (also known as Windows CE 4.x → i.e: Latest Medion machines)
All Windows Mobile Pocket PC Second Edition devices
All Windows Mobile Pocket PC devices
All Windows Mobile 2003 for Pocket PC devices.
Advantech TPC-60
Diagnostic Instruments Di-400
DoCoMo Sigmarion III
Intermec CK31
NEC MobilePro 900c
PSC Falcon 4220
Psion Teklogix NetBook Pro
Psion Teklogix WorkAbout Pro
SmarTerminal iPC320
Symbol MC1000
Symbol MC3000
Symbol MC9000
Windows CE .NET 4.2 devices using StrongArm processors in ARMV4 or ARMV4I mode.
So as you can see it will run from very old machines to the newest with the WM 5.
At this stage the beta version has not included the library for CE .Net 4.■■ (i.e: latest Medion machines) but can be supplied separately if anyone is interested.
SmartPhones are (but not a comprehensive list):
Cingular 2125
i-mate SP3/SP3i
Mio 8390
Motorola MPx200/220
Sagem myS-7
Samsung i300
SDA (II) (Music) Smartphone
SPV C500/C600
Qtek 8080
TSM520
Vop Professional Phone
pocket pc 2002 will not run on jornada 568 error message “can not run tgaurd one or more of it components is missing” this wa installed as instructed nsb runtime was also install but would not run
alix776:
pocket pc 2002 will not run on jornada 568 error message “can not run tgaurd one or more of it components is missing” this wa installed as instructed nsb runtime was also install but would not run
The installation package I did is a minimum installation for devices with ARM processors, trying to make it easier to betatesters to download it.
It should install properly in any machine PPC 2002 and 2003.
VBScript is in the ROM of those devices, but I remember that last year I did install a VB application in my PDA and a new VBScript was installed (?) and from that moment no other VBasic (and NSBasic) application will run until I removed that file.
Your Jornada has a ARM processor and to my knowledge should install and run this program correctly unless I had some mistake building up the installer.
Spacemonkeypg:
i have a spv 200 its running on windows 2003 i think
Yours is a Smartphone, and it´s my intention to do this application for them too, but to be honest it will be the latest development.
Reasons? I intend to do a complete program, a very complete one, for PDAs (Pocket PC and CE machines) followed for a version for desktop PCs as I will need just a few small changes.
To do the same for SmartPhones will imply a lot of re-encoding in .NET as them have not MFC (Microsoft Foundation Class) in their ROM and I need to take other ways to achieve the same results. Not to speak about the difference in the size of the screen, that means too a total re-write of them.
Sorry for this could water, but don´t blame on me, is Microsoft who created the problems.
looks like a very simple program to use, I have put it on my XDA 11i and will give it a try alongside my hours guard…when do you expect to have it set for recording over a longer period, IE so I won’t have to copy data and add them together for poa and working weeks etc
jimti:
looks like a very simple program to use, I have put it on my XDA 11i and will give it a try alongside my hours guard…when do you expect to have it set for recording over a longer period, IE so I won’t have to copy data and add them together for poa and working weeks etc
The link for downloading has been updated today, to avoid the little problem with machines PPPC 2002.
The new link has the latest beta with a few more enhancements:
A new screen (Setup) has been added. It allows you to change the period of screen refreshment, so it gives more cycles of the processor for other programs like TomTom. I tried in mine with 1 sec and TomTom was working fine but for smaller processors it can be changed up to 99 secs.
The program is saving your data right now. Screens to retrieve this data and to give you alarms hopefully will be done along this week.
Program is already resistent to soft reset, and hard reset if installed in memory card. So no data is lost.
You can switch off your machine after start the program or to close the program, when you switch on again the program remembers what was the last button tapped and will do the timings acording to it. So no need to keep the PDA on, just when you are going to change the mode (driving, break, other work, p.o.a). It will give extra life to your battery.
With 1 Mb of space it can save 365 days working with an average of 50 changes of mode during every one. Every change of mode consumes about 56 bytes. So you can do your own numbers.
As suggested by Alix now the clock corresponding to the actual mode stays in red, rest black. Easier to see it at first glance.
In the pipe line:
Alarms when close to the end of working or driving periods.
Screen at the end of the day letting you know when you can start next day based in the analysis of the day, how many breaks you had with more than 1 h (split rest period 8+4), etc…
Same for weeks/fortnights and correspondents rest periods and compensation for reduced breaks.
Same for 17/26 weeks average period, taken between any gap you liked, and supposing you have enough data stored.
By my own suggestion (I´m very lazy taking notes in agendas) a screen where you can save your starting and finish paid hours (minus breaks if is the case) to be retrieved by the period of your choice (weekly/fortnight/monthly/any period hours you expect to be paid for).
Export of data in CSV format to be treated with spreadsheets programs.
You can put here your own suggestions (7a,7b…)
For those running TomTom an advisory screen in case you´re running and mode still in break/other work/p.o.a.
Full English breakfast cooked to the order… sorry, no, that´s for another program…
As you can see the list is big, and sure you will give me more ideas… but right now data is being stored so use it, then you will be able to see the analysis in few days.
Regards,
Jose Adell
Edited: A small bug has been detected. It only happens if your regional settings are other than English UK and is about how other countries print the time in the screen (12 or 24 hours, am/pm, etc.) I will have a look on it tomorrow and if sorted the link will be updated).
If you find any bug please don´t post it here, try to reproduce it to get the sequence properly and send me an email or a PM with it and I will deal with the problem quicker. Thanks.
After a carefull looking into my code about the error due to the Regional settings it came up to be a “bug” inside the proper vBasic, so nothing can be done.
For some reason, when regional settings are to print the hour in the format 0-12 A.M./P.M. and clock is programmed to be 00:00:00 the system translates it to 12:00:00 A.M.
If real time is p.m. this can cause too an overflow error.
I could do a little trick I testedd, just to re-set all the clocks wih 1 sec, then all is O.K. but I don´t like it very much.
So to avoid the problem before to run the program just go to Regional Settings in your machine and set the clock to HH:mm:ss and all is sorted (English UK have it as default, but English US has the opposite h:mm:ss tt).
Once installed and running and before to do anything with it tap the “Setup” option at the bottom of the screen, then in the new screen tap the button named “Rebuild indexes”. Now the program is ready for the new features.
The main addition is the screen to retrieve the data. Two date pickers are there. So you can select just one day or several days. No limits for it but the period you started to work with the program and the actual date.
A new screen where to introduce the hours you get paid for as been added too. Just introduce the date and time for clock on and clock off. Then tap “Get Hours” and the result will be saved. Laterly it will be retrieved too.
All new screens are not yet working for landscape mode, will be shortly.
I expect to have all ready for a final customer release about 19/02/2006.
Of course, any idea or sugestion is more than welcome.
