JavaPOS with EPSON tm-t88iii, Cannot Print - epson

My situation is the following : I have to develop a POS application for a take away Pizzeria, I have an EPSON tm-t88iii receipt printer.
I did : Installed the ESPON JavaPOS ADK , generated a jpos.xml file with SETUPPOS (HealthCheck works fine).
My issue : When I try to connect to the printer with the open method, I have the following Exception and I don't know why :
"jpos.JposException: Could not connect to service with logicalName = tm88: Exception.message=Could not create service instance."
With this code :
POSPrinterControl19 ptr = (POSPrinterControl19) new POSPrinter();
try {
ptr.open("tm88");
} catch (JposException ex) {
System.err.println(ex.toString());
}
Here are my jpos.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE JposEntries PUBLIC "-//JavaPOS//DTD//EN"
"jpos/res/jcl.dtd">
<JposEntries>
<!--Saved by JavaPOS jpos.config/loader (JCL) version 2.2.0 on 23.06.14 21:59-->
<JposEntry logicalName="tm88">
<creation factoenter code hereryClass="jp.co.epson.uposcommon.util.EpsonJposServiceInstanceFactory" serviceClass="jp.co.epson.upos.core.v1_13_0001.pntr.T88IIIService"/>
<vendor name="SEIKO EPSON" url="http://www.epson.com"/>
<jpos category="POSPrinter" version="1.13"/>
<product description="EPSON TM-T88III Printer Device Service" name="EPSON Services for JavaPOS(TM) Standard" url="http://www.epson.com"/>
<!--Other non JavaPOS required property (mostly vendor properties and bus specific properties i.e. RS232 )-->
........
</JposEntry>
</JposEntries>
I do find this weird as the HealthCheck From the EPSON ADK works fine and my example not. Of course, I did include all the librairies from the EPSON ADK to the Project. Has anybody an idea ?
Thank you
My specs:
OS : WINDOWS 8.1 64 bits
IDE : netbeans 8
Connection to the receipt : Serial

You need to setup the printer with:
System.setProperty(JposPropertiesConst.JPOS_POPULATOR_FILE_PROP_NAME, "jpos.xml");
and load your jpos.xml use route\\jpos.xml
this file is generated by the utility program.

Related

Error message "OpenCV: not authorized to capture video (status 0)" in MacOS QT

I know there were already some similar questions and it seems the question is not arose by OpenCV but by MacOS authority rule.
I have read some solutions, like create a Info.plist into source directory. And that works! But for me now only in Debug mode in QTCreator, not in Release mode. That is, when I run the program in Debug mode, everything is just OK. But in Release mode within QTCreator, the error message shows up:
OpenCV: not authorized to capture video (status 0), requesting...
16:12:22: The program has unexpectedly finished.
Some more strange informations. The program, say Test.app which is generated by QTCreator in Release or Debug mode, can be executed by directly double clicking on it or on the executable file residing in Test.app/Contents, after authorized for sure.
Additional System Information:
macOS Catalina Version 10.15.4
Qt 5.14.2
OpenCV 4.3.0
Also the Info.plist
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist SYSTEM "file://localhost/System/Library/DTDs/PropertyList.dtd">
<plist version="0.9">
<dict>
<key>NSCameraUsageDescription</key>
<string>uses camera to see vision targets</string>
</dict>
</plist>
Some codes may be helpful. FYI, the program crashes before the Camera class created.
// camera.cpp
std::shared_ptr<Camera> Camera::Ptr = nullptr;
void Camera::CreateCamera()
{
if(!Ptr)
Ptr.reset(new Camera);
}
Camera::Camera()
: _device(1)
{
}
bool Camera::GrabMerged(cv::Mat &img)
{
if(_device.isOpened())
{
cv::Mat tmp;
_device.read(tmp);
if(tmp.empty())
{
qWarning("[Camera] Grab image failed.");
return false;
}
qInfo("[Camera] merged image info: cols=%d, rows=%d, channels=%d, step0=%luļ¼Œstep1=%lu, type=%d",
tmp.cols, tmp.rows, tmp.channels(), tmp.step[0], tmp.step[1], tmp.type());
cv::cvtColor(tmp, img, cv::COLOR_RGB2BGR);
return true;
}
qCritical("[Camera] Camera is not opened.");
return false;
}
...
// camera.h
class Camera: public QObject
{
...
private:
cv::VideoCapture _device;
...
}
In case helpful for others.
Qt Creator > Projects > Run > Environment > add OPENCV_AVFOUNDATION_SKIP_AUTH 0 , then you will get the MacOS prompt "QtCreator wants to access the camera". I'm running macOS 11.4
Thanks for taking time to push a minimal project that allow to reproduce the error.
After some test, it appears that this project works fine when started from command line or by double-clicking on the app bundle icon (both in Release and Debug mode). In the later case, system ask for permission to use the camera when clinking on the open button. Once permission is granted, we need to click again on the button, this is an expected behavior with OpenCV VideoCapture on macos.
But when I start it from Qt Creator, I had this weird message :
dyld: Symbol not found: __cg_jpeg_resync_to_restart
Referenced from: /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
Expected in: /usr/local/lib/libJPEG.dylib
in /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
18:29:38: The program has unexpectedly finished.
This is not the same as yours but that shows that there is some difference between normal execution and execution from QtCreator.
And in my case, Qt Creator is the culprit.
And after disabling the DYLD_LIBRARY_PATH variable under the Run environment (Projects Settings -> Run -> Environment), it works fine from QtCreator. Hourah !
My settings looks like :
This is with Qt Creator 4.12 / Qt 5.14.2 / OpenCV 4.3.0

Windows 10 IoT: exception code e0434352 causes?

I'm attempting to repackage a Desktop app (the code to which I do not have) for Windows 10 IoT using PACE Converter (basically a wrapped-up Desktop Bridge).
I've gotten to the point where I can install it on my device (actually a Minnowboard VM) using the Device Portal website, but I cannot run it.
The app instantly crashes, and provides the following log output:
Version=1
EventType=MoAppCrash
EventTime=131650324486808277
ReportType=2
Consent=1
UploadTime=131650324491343532
ReportIdentifier=0729d269-2339-11e8-844f-000c29c53adc
IntegratorReportIdentifier=0ac9bcb5-b460-4475-bdb5-86a8f0c18281
NsAppName=praid:ThermoVisionJoeC
Response.BucketId=d94813fac3d80d13b0156e9965e35ba5
Response.BucketTable=5
Response.LegacyBucketId=1158954084236221349
Response.type=4
Response.CabId=2077997148494651244
Sig[0].Name=Package Full Name
Sig[0].Value=ThermoVisionversion1.8_1.8.0.0_x86__69vzfematcnkr
Sig[1].Name=Application Name
Sig[1].Value=praid:ThermoVisionJoeC
Sig[2].Name=Application Version
Sig[2].Value=1.8.0.0
Sig[3].Name=Application Timestamp
Sig[3].Value=5a2a86fb
Sig[4].Name=Fault Module Name
Sig[4].Value=kernelbase.dll
Sig[5].Name=Fault Module Version
Sig[5].Value=10.0.10586.0
Sig[6].Name=Fault Module Timestamp
Sig[6].Value=5632d1bc
Sig[7].Name=Exception Code
Sig[7].Value=e0434352
Sig[8].Name=Exception Offset
Sig[8].Value=000d2ed2
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.10586.2.0.0.256.123
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=7d75
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=7d75e07ca427d63ce5d6b2980c892ce4
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=2a76
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=2a7669b2a9a5dd27db4411a185741431
UI[2]=c:\data\Programs\WindowsApps\ThermoVisionversion1.8_1.8.0.0_x86__69vzfematcnkr\TVision_V1.8.0.0\ThermoVision_JoeC.exe
LoadedModule[0]=c:\data\Programs\WindowsApps\ThermoVisionversion1.8_1.8.0.0_x86__69vzfematcnkr\TVision_V1.8.0.0\ThermoVision_JoeC.exe
LoadedModule[1]=C:\windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\windows\SYSTEM32\MSCOREE.DLL
LoadedModule[3]=C:\windows\system32\msvcrt.dll
LoadedModule[4]=C:\windows\system32\kernelbase.dll
LoadedModule[5]=C:\windows\system32\combase.dll
LoadedModule[6]=C:\windows\system32\RPCRT4.dll
LoadedModule[7]=C:\windows\system32\kernel32legacy.dll
LoadedModule[8]=C:\windows\system32\bcryptPrimitives.dll
LoadedModule[9]=C:\windows\SYSTEM32\kernel.appcore.dll
LoadedModule[10]=C:\windows\SYSTEM32\shcore.dll
LoadedModule[11]=C:\windows\SYSTEM32\wintypes.dll
LoadedModule[12]=C:\windows\system32\CoreClr\v1.0\CoreClr.dll
LoadedModule[13]=C:\windows\SYSTEM32\bcrypt.dll
LoadedModule[14]=C:\windows\SYSTEM32\CRYPTSP.dll
LoadedModule[15]=C:\windows\SYSTEM32\OLEAUT32.dll
LoadedModule[16]=C:\windows\SYSTEM32\advapi32legacy.dll
LoadedModule[17]=C:\windows\system32\sechost.dll
LoadedModule[18]=C:\windows\SYSTEM32\CRYPT32.dll
LoadedModule[19]=C:\windows\SYSTEM32\SspiCli.dll
LoadedModule[20]=C:\windows\SYSTEM32\MSASN1.dll
LoadedModule[21]=C:\windows\system32\CoreClr\v1.0\mscorlib.ni.dll
LoadedModule[22]=C:\windows\system32\rsaenh.dll
LoadedModule[23]=C:\windows\SYSTEM32\CRYPTBASE.dll
LoadedModule[24]=C:\windows\system32\CoreClr\v1.0\System.Runtime.WindowsRuntime.ni.dll
LoadedModule[25]=C:\windows\system32\WinMetadata\Windows.Foundation.winmd
LoadedModule[26]=C:\windows\system32\CoreClr\v1.0\System.Runtime.ni.dll
LoadedModule[27]=C:\windows\system32\CoreClr\v1.0\System.Runtime.InteropServices.WindowsRuntime.ni.dll
LoadedModule[28]=C:\windows\system32\WinMetadata\Windows.ApplicationModel.winmd
LoadedModule[29]=C:\windows\SYSTEM32\procthreadexthost.dll
LoadedModule[30]=c:\Windows\System32\MrmCoreR.dll
LoadedModule[31]=C:\windows\SYSTEM32\profapi.dll
LoadedModule[32]=c:\Windows\System32\Windows.UI.dll
LoadedModule[33]=C:\windows\SYSTEM32\dcomp.dll
LoadedModule[34]=C:\windows\SYSTEM32\minuser.dll
LoadedModule[35]=C:\windows\SYSTEM32\GDI32.dll
LoadedModule[36]=C:\windows\SYSTEM32\CoreUIComponents.dll
LoadedModule[37]=C:\windows\SYSTEM32\CoreMessaging.dll
LoadedModule[38]=C:\windows\SYSTEM32\Bcp47Langs.dll
LoadedModule[39]=c:\Windows\System32\twinapi.appcore.dll
LoadedModule[40]=C:\windows\SYSTEM32\faultrep.dll
LoadedModule[41]=C:\windows\SYSTEM32\dbghelp.dll
LoadedModule[42]=C:\windows\SYSTEM32\dbgcore.DLL
State[0].Key=Transport.DoneStage1
State[0].Value=1
File[0].CabName=WERInternalMetadata.xml
File[0].Path=WER815.tmp.WERInternalMetadata.xml
File[0].Flags=851970
File[0].Type=5
File[0].Original.Path=C:\Data\Users\DefaultAccount\AppData\Local\Temp\WER815.tmp.WERInternalMetadata.xml
File[1].CabName=triagedump.dmp
File[1].Path=triagedump.dmp
File[1].Flags=808255490
File[1].Type=6
File[2].CabName=WERGenerationLog.txt
File[2].Flags=851970
File[2].Type=5
File[2].Buffer=FFFE53006E0061007000730068006F0074002000640075006D007000650072002000640065006100630074006900760061007400650064002E000D000A002D002000200053006E0061007000730068006F007400200061007600610069006C00610062006C0065003A00200030002E000D000A002D002000200053006E0061007000730068006F00740073002000640069007300610062006C00650064003A002000300030002E000D000A002D002000200020002000200053006E0061007000730068006F00740020007300740061007400750073003A002000430030003000300030003000310037002E000D000A002D002000200020002000200020002000440075006D0070006500720020007300740061007400750073003A002000300030003000300030003000300031002E000D000A002D00200020002000500072006F0063006500730073002000570045005200200066006C006100670073003A002000300030003000300030003000300030002E000D000A002D00200057006100740073006F006E00200072006500710075006500730074002000640075006D0070003A002000300030003100300030003100410034002E000D000A000D000A0053006E0061007000730068006F0074002000640075006D007000650072002000640065006100630074006900760061007400650064002E000D000A002D002000200053006E0061007000730068006F007400200061007600610069006C00610062006C0065003A00200030002E000D000A002D002000200053006E0061007000730068006F00740073002000640069007300610062006C00650064003A002000300030002E000D000A002D002000200020002000200053006E0061007000730068006F00740020007300740061007400750073003A002000430030003000300030003000310037002E000D000A002D002000200020002000200020002000440075006D0070006500720020007300740061007400750073003A002000300030003000300030003000300031002E000D000A002D00200020002000500072006F0063006500730073002000570045005200200066006C006100670073003A002000300030003000300030003000300030002E000D000A002D00200057006100740073006F006E00200072006500710075006500730074002000640075006D0070003A002000300030003100300030003100410034002E000D000A000D000A00
File[3].CabName=memory.csv
File[3].Path=WERD53.tmp.csv
File[3].Flags=851971
File[3].Type=5
File[3].Original.Path=C:\Data\SystemData\Temp\WERD53.tmp.csv
File[4].CabName=Report.cab
File[4].Path=Report.cab
File[4].Flags=196608
File[4].Type=11
File[4].Original.Path=Report.cab
FriendlyEventName=Stopped working
ConsentKey=MoAppCrash
AppName=ThermoVisionversion1.8_69vzfematcnkr!ThermoVisionJoeC
AppPath=c:\data\Programs\WindowsApps\ThermoVisionversion1.8_1.8.0.0_x86__69vzfematcnkr\TVision_V1.8.0.0\ThermoVision_JoeC.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=4DCF491271EABACC61BC8E205D766FEB
I'm not a programmer, but I've gotten this far by educated poking at stuff and I'd like to know what to prod next (or refer to the author of the code).
Any tips?
Cheers,
R

Tizen application is not installing on target device

I built the Tizen sample application in wearable IDE 2.3.1 and 2.3.0. I was able to run it on the emulator. But the same application is not installing on my 2.3 wearable target device. While installing, it gives errors. I tried the procedures below for installing the application.
* sdb install app
* wrt-installer -i app (For installing web application)
These are the error messages I got:
E/WRT_INSTALLER( 513): pkgmgr_signal.cpp: setPkgname(164) >
[SECURE_LOG] name is empty
D/WRT_INSTALLER( 513): task_configuration.cpp: hasExtension(85) > [SECURE_LOG] Looking for extension .xml in
/opt/home/developer/WearableUI.wgt
D/WRT_INSTALLER( 513): widget_unzip.cpp: getDecryptedPackage(265) > [SECURE_LOG] Check DRM...
D/WRT_INSTALLER( 513): widget_unzip.cpp: isDRMPackage(171) > [SECURE_LOG] Enter : isDRMPackage()
E/WRT_INSTALLER( 513): widget_unzip.cpp: isDRMPackage(180) > [SECURE_LOG] Cannot open /usr/lib/libdrm-service-core-tizen.so!
I have one more concern: Is the libdrm-service-core-tizen.so library required for installing applications on Tizen? (For now we are using software rendering.)
Are there any command line tools for installing Tizen native/web apps?
This log is not enough to know the exact cause. WRT installer is to continue the installation regardless of the existence of the .so file. I think that will have more direct cause behind the log. Find and send more log.

flex 4.6 mobile project debug error using air 3.4

i've followed this in order to flashbuilder 4.6 to use air sdk 3.4. no problems, or hiccups with the update.
the only problem is when i try to debug a mobile project using this sdk, either for android or ios i get the following error:
Process terminated without establishing connection to debugger.
invalid application descriptor: Unknown namespace:
http://ns.adobe.com/air/application/3.4
Launch command details: "C:\Program Files (x86)\Adobe\Adobe Flash
Builder 4.6\sdks\4.6.1\bin\adl.exe" -runtime "C:\Program Files
(x86)\Adobe\Adobe Flash Builder 4.6\sdks\4.6.1\runtimes\air\win"
-profile mobileDevice -screensize 640x920:640x960 -XscreenDPI 326 -XversionPlatform IOS "C:\Users\joao\Adobe Flash Builder 4.6\teste34\bin-debug\teste34-app.xml" "C:\Users\joao\Adobe Flash Builder 4.6\teste34\bin-debug"
i've also got this problem.
following is what i've done:
1:create a new empty mobile application and debug it runs
2:open the new app's '{appname}-app.xml' file , find the 'xmlns' property in application root node for example
<application xmlns="http://ns.adobe.com/air/application/3.1">
3:replace the row of your old application
So i think the problem is your air sdk can not support the 3.4 version

Driver Installation Issue with Installshield

I am just trying to install using Installshield 2009 a demo driver written by me.
I wrote a demo inf file.
I also wrote a simple console application in VC++.
Then I wanted to install the application along with the drivers and so I created Basic MSI Project and added my application exe to it.
After this I added my inf file to it using Device Driver Wizard(located in Set Up Design >>> New Feature) where installshield also added the .sys and .cat files.
Now the problem is that when I run the generated msi file it only installs the application and the driver does not installed.
During installation it gives me a Windows Security window and when I clink on "Install this driver software anyway" it proceeds ahead for install completion.
But the are no drivers in system32/drivers and no entried in registry.
The demo driver contain just basic driver functions with printfs in them.
The inf contains:
[version]
Signature="$CHICAGO$"
Class=RKP_LTO_DEMO_DD
; GUID created by me usingGUIDGEN tool
ClassGuid={03E9C4D5-178E-4684-B407-A3E103D71CE9}
Provider=%DD_DEMO%
CatalogFile = dd_demo.cat
DriverVer=02/24/2012, 2.0.1.2
[DefaultInstall]
CopyFiles=XYZ_Device.Copy
AddReg=XYZ_DeviceHW
[XYZ_Device.Copy]
demo_dd.sys
[XYZ_DeviceHW]
HKLM,SYSTEM\CurrentControlSet\services\,demo_dd,0x00000000,"%12%\demo_dd.sys"
[SourceDisksNames]
1=%RTO_DISK_NAME%,Sample_DIF,0
[SourceDisksFiles]
demo_dd.sys=1,,
[DestinationDirs]
XYZ_Device.Copy=12
[Strings]
SPSVCINST_ASSOCSERVICE= 0x00000002
DD_DEMO = "RKP XYZ DD DEMO"
DisplayName = "RKP XYZ Driver Install Frameworks"
ClassName = "rkp xyz dd_demo"
DD_DEMO.DeviceDesc = "Rkp Xyz WI DIF Sample"
rto.SVCDESC = "RKP XYZ Device Driver"
RTO_DISK_NAME ="RKP XYZ Installation Disk"
The installshield install log gives the following message (0xE0000301):
DIFXAPP: INFO: ENTER: DriverPackageInstallW
DIFXAPP: WARNINGRIVER_PACKAGE_LEGACY_MODE flag set but not supported on Plug and Play driver on VISTA. Flag will be ignored.
DIFXAPP: INFO: Installing INF file 'C:\Program Files (x86)\DEMO\My Product Name\dd_demo\dd_demo.inf' (Plug and Play).
DIFXAPP: WARNING:No device Ids found in INF 'C:\Windows\System32\DriverStore\FileRepository\dd_demo.inf_amd64_neutral_c3727dded0bf2410\dd_demo.inf' for current platform.
DIFXAPP: INFO: RETURN: DriverPackageInstallW (0xE0000301)
The driver gets installed when I install it using run32dll.exe.
I verified this by checking the system32/drivers folder and the seeing the registry entry.
But with installshield it does not install it.
Will anybody pls let me know what might be the issue and how to resolve it?
How to fix this issue?

Resources