I am trying to add a Dymo LabelWriter Wireless to my CUPS server.
I have been using this ppd https://gist.github.com/vstath/0f5eab715cec427b86dcf9c47f397f04.
Also I am using socket://ip-address as an address for my printer inside CUPS, but nothing gets printed. CUPS says that the jobs are printed fine, but nothing happens.
Suggestions?
Unfortunately the PPD no longer works. I reached out to their support department (sdkreply#newellco.com) and received the following reply:
The PPD file looks OK, besides the cupsFilter line. The LabelWriter Wireless requires a new driver since we have modified the communication protocol.
The new drivers haven’t been published yet. An update Linux SDK is on the task list, but the development hasn’t been scheduled yet.
We will post an update on https://developers.dymo.com/
Related
I'm quite new to the world of the IOT (protocols). I want to update some devices remotely (they will be installed about 8000km away from my working place). I have found out that LWM2M would fit to my scope.
Because the internet connection there is not stable and the bandwidth is low, I have decided to also install a Raspberry Pi to collect the data of the sensors and to install a Leshan server to trigger the updates.
I have tested the devices and I can register them to the Leshan server on the Pi, read some data, and reboot the devices. The problem is, I don't know where to save my binary file for the update, so that the device can download them.
I tried following steps:
Save the file on [leshan-dir]/update.bin.
Write the "Package URI": coap://[raspi-IP]:5683/update.bin
After that, the backgroud color of the button "Write" changes to green.
Execute the update
The response of the server is 404 [Not Found].
I have looked for any API to find out where I can save the .bin file, but without success. And because nobody seems to have had a similar error, I start thinking I have missed some points.
Where do I have to save the files on the Raspbery Pi, so that I can perform an update?
I found a solution for the problem I exposed above.
I use from the californium-project the demo-app cf-simplefile-server (Ref. https://github.com/eclipse/californium/tree/2.0.x/demo-apps/cf-simplefile-server)
Note: You have to checkout to the git-branch 2.0.x to use it.
To run the leshan server and the file-server on the same machine I had to change the port of one of the server using the file Californium.properties.
I decide to change the ones of the file-server to 5685 and 5686
When both server runs I can insert in Package URI something like:
coap://[[ip_of_the_pi]]:5685/data/[[name_of_the_firmware_file]]
Probably there are better solution for it, but for a coap/lwm2m beginner like it works very well.
Note: If you have bigger file to transfer you can also change the property MAX_RESOURCE_BODY_SIZE
I hope this may help somebody.
Regards,
Elvys
We are running QuickBooks Enterprise 7 (I know it is old and not supported). I have MS Access applications that are using the SDK (via VBA) to send transactions to QB. Nothing has change, but all of a sudden we are getting an error that the certificate for the application is invalid. We never had certificates before. It also did not pop up the window that lets me say I want it to run regardless of the certificate.
Anyone have any ideas what causes this? I have tried deleteing the application from QB and created a new one just to see what would happen but it still gives me the error.
My code looks like this:
Set QB = CreateObject("QBFC7.QBSessionManager")
strDatabase = DLookup("Default_Company", "Configuration_table")
'get the qb file information
QB.OpenConnection "", "Upload Payroll"
QB.BeginSession strDatabase, omMultiUser
dblCredit = 0
Set JournalAddSet = QB.CreateMsgSetRequest("US", 5, 0)
I really need help with this! Our company is dead in the water until I can get this going!
I discovered that it was an update to Office 2016 that caused the certificate issues. The most recent update (Version 1707 dated July 31) corrects the problem for me. Not sure what was in either update (since I couldn't find a detailed description from Microsoft) that broke then fixed this issue.
I am looking into the same problem with my interface from MS Access to QBooks via the SDK.
I believe it is caused by heightened security for Windows 10. It happened to 2 of my customers yesterday. I am going to upgrade the SDK dll from QBFC2.....dll to QBFC13....dll type libraries in VBA window Tools, References...and browse for the location, but also uncheck the old one QBFC...dll in the references.
You can download QBFC13 from Intuit website.
There are a few other things that may have to be done. I had to do a replace all QBFC2 with QBFC13 when it calls libraries. ---> ...,QBFC2Lib.... replace with ,,,,QBFC13Lib....
I compiled the VBA code and got another error message:
It was all the request set messages had ...MSG... and I replaced it with ...IMSG...
Then the VBA compiled but I am waiting on my customer so I can test it on their PC with Windows 10 to see if it works.
Note 08/09/17 This did not fix the problem
However, My customer and I are both running Windows 8.1. She has MS Access 2016 and gets the Invalid certificate error when attempting to send an invoice to Qbooks using their SDK.
I brought her MS Access program back to me and sent the same invoice using the same version of QBooks SDK and did not get the error. I am running MS Access 2010.
Recently I’ve release my Windows 10 UWP application in store .
Last week I released a new update in store ,after a week I receive lots of mail from users about a bug in my app.(Pages that want to connect to database can't open and they crash)
Funny part is that when I deploy and run it by visual studio or Powershell (appx-package command) everything works fine, so I can't find a thing.(Even in RemoteMachine and Emulator)
So I was checking my dashboard in dev center and find some "failed log" there.
How can I use these logs to find my problem?
I'm really stuck and don't know what to do!!
Solution:
In Properties of the Project there is a file named Default.rd.xml that contains an element like <Assembly Name="*Application" ...
So by mistake the attribute it was changed to name="*Application" (Don't know what changed that and VisualStudio didn't notice that.)
When I try to run my Windows Store app, it won't, and shows me this:
..."does not support the contract specified"? What contract? I'm not implementing any contract; I assume it means the Settings contract or some such, but I'm not doing any of those yet.
I went to the Help page suggested, and it says, in part, "To diagnose these errors
There are no sure ways to fix these errors. Use these techniques to diagnose the problem."
The first suggestion is:
Open Event Viewer (on the Windows Start menu, search for Event Viewer.) In Event Viewer, navigate in the tree to the Application and Services Log\Microsoft\Windows\Apps folder.
Filter the view to event Ids: 5900-6000
Examine the log and see what occurred.
Windows 8.1 only brings up web pages when I search for "Event Viewer"
Actually, I did write a utility to catch event logs, and I ran that. I found these:
***Type: Error
Source: Microsoft-Windows-Immersive-Shell
Time Generated: 11/27/2014 15:10:39
Message: Activation of app App.adaf78a74.a8c80.a4ff5.a99ca.a97636d548196_8wekyb3d8bbwe!Designer.App failed with error: -2144927148 See the Microsoft-Windows-TWinUI/Operational log for additional information.
Type: Error
Source: Microsoft-Windows-Immersive-Shell
Time Generated: 11/27/2014 15:20:08
Message: Activation of app axXAndSpace.Visits_qtyjefqf75sa6!App failed with error: -2144927148 See the Microsoft-Windows-TWinUI/Operational log for additional information.***
But where is "Microsoft-Windows-TWinUI/Operational log"?
The second suggestion on the Help page was:
Use the native debugger
Configure the project to run under a native debugger.
In Visual Studio, set the Debugger Type to Native Only on the Debug (Debugging in C++ and JavaScript) page of the property pages of the start-up project.
Look at the exceptions being thrown by looking at the output window. You might want to configure the debugger to stop when these exceptions are thrown.
I did that, but it gave me no more information than previously - nothing at all displays in the Output pane.
What could be the cause of this?
UPDATE
Just to update the progress:
Based on Iris Classon's suggestions, I went to Control Panel to see if my app was installed so that I could uninstall it, but it's not in that list.
If I search for the app by typing its name, it tries to start up - its splash screen displays, but goes no further than that.
I went to Program Files\WindowsApps, and when selecting it got, "You don't currently have persimmons to access this folder, click continue to continually get access"
That leads me to "You have been denied permission to access this folder; to gain access to this folder, you will need to use the security tab"
Click the "security tab" link takes me to that tab, and a "For special permissions or advanced settings, click Advanced"
I do so.
That takes me to a Permissions tab, which says, "You must have Read permissions to view the properties of this object; Click continue to attempt the operation with administrative permissions"
I then selected (one at a time, as that is all it allows):
Trusted Installer : Full control
System: Read, Write, and Execute
System: Full Control
Administrators: Read & Execute
But so far, none of that seems to do anything good.
UPDATE 2
This problem has just "gone away" today; I don't think it was anything I did. I added a UserControl, tried running the app again, and now it runs - I don't see that error message. However, I do see a seemingly unrelated one. (at least I got further).
I just had this problem on a fresh install of Windows 8.1 on my laptop. I'm not sure which one of these steps solved it, but until somebody can give you a more exact answer here is something to try as I am sure you are keen on coding.
Only Store Apps run from VS gives that error, other Store apps work fine.
I first of all changed permissions on my WindowsApps folder under Program Files and made sure that I had full access to the folder and sub folders. Restarted the laptop, still no luck.
Then I set up an admin guest account (just something I tend to do for when I need to record tutorials- so not related to trying to solve the error). Out of curiosity I tried to create and run the same Windows Store App and got an error that another user had installed the app. Strange, how was it installed if it gave me the error that it couldn't activate the app on the main account?
I logged back in as the main user and uninstalled the application (which was showing up as installed), and I can now run any Store App from VS without problems.
Not sure this is an answer since I'm not sure what made it work, but give it a try and hopefully somebody else can clear this us up. I'll investigate further, but I'm on a train right now with poor WiFi connection :)
Best of luck!
I had the same scenario, here are the steps I did to resolve:
I tried to create packages, chose not to associate with the store.
It said that the certificate is expired, I created a new test certificate.
I created the test packages successfully.
Tried to run the project from VS and it finally ran.
I believe all of this had to do with the certificate. very frustrating and time wasting issue.
I also had the same problem and following steps fixed it. Hope it will help some one else.
Open the appxmanifest file
Go to "Packaging" tab
Select "Choose Certificate" and select "Pick from certificate store" and select your cetificate and click on ok
I have an internal web chat application implemented in python/django and using ejabberd 2.1.3 and Strophe.js.
When you open the website with a special access link, a cmd line call is executed to add you to a shared roster group:
ejabberdctl srg_user_add 00024-540-1mCYpYTTCRcjJK5OWI7cWs xmpp.mydomain.com
1mCYpYTTCRcjJK5OWI7cWs xmpp.mydomain.com
The executes successfully and if I execute this cmd manually the members are shown fine:
ejabberdctl srg_get_members 1mCYpYTTCRcjJK5OWI7cWs xmpp.mydomain.com
00024-540-1mcypyttcrcjjk5owi7cws#xmpp.mydomain.com
01114-540-1mcypyttcrcjjk5owi7cws#xmpp.mydomain.com
However, in the Strophe.js presence handler I only receive a presence stanza for myself, meaning if I open two different links in two different browsers for two different members, I do not receive a presence stanza for the other member.
If set the ejabberd log level to debug, this is reflected here.
<presence xmlns='jabber:client' from='0031-666-vjuuogji8mxvo5edtsvre#xmpp.mydomain.com/3189433061352390311794558' to='0031-666-vjuuogji8mxvo5edtsvre#xmpp.mydomain.com/3189433061352390311794558'/>
<presence xmlns='jabber:client' from='0030-666-vjuuogji8mxvo5edtsvre#xmpp.mydomain.com/3319710041135238652858307' to='0030-666-vjuuogji8mxvo5edtsvre#xmpp.mydomain.com/3319710041135238652858307'/>
It's missing the stanza to the other member:
<presence xmlns='jabber:client' from='0031-666-vjuuogji8mxvo5edtsvre#xmpp.mydomain.com/3189433061352390311794558' to='0030-666-vjuuogji8mxvo5edtsvre#xmpp.mydomain.com/3319710041135238652858307'/>
I have the same setup on a second server where it works fine, and I see the stanzas exactly as expected.
Before, it also worked on the problem server, but last week we had a total power failure in the data center and the server went down. Since then I cannot seem to get it to work again.
Could it be that some files might have been corrupted due to the power loss? Is there something I should clean up?
Unfortunately the previously responsible person is no longer in our company...
I found the problem - due to some stupid internal reasons, the
ejabberdctl srg_create ...
was missing, so the members were added to a non-existent group.
I just do not understand why the srg_user_add and srg_get_members commands worked without error. If they had given some hint about the group not existing I would have found the problem sooner