[Jesse Gilles]

Opkg isn’t configured by default to pull from any feeds because Multi-Tech doesn’t publish any feeds for public use.

You’ll need to set up a feed on your development machine if you want to use ‘opkg update’ and ‘opkg install’ to install packages that you build. See this article for more information: http://www.multitech.net/developer/products/cellular-development-platform/development/setting-up-a-package-feed/

How did you install gdb on the unit?

You also have the option of reflashing the unit with your custom image (that contains gdb, glibc-dbg, etc).

[Jesse Gilles]

If you used opkg to install glibc-dbg and libthread-db1, try forcefully reinstalling the libc6 package.

opkg update

opkg –force-reinstall install libc6

We ran into a similar issue and it was resolved by reflashing the entire rootfs or by reinstalling libc6.

[Jesse Gilles]

What libraries are you interested in specifically?

Most python modules can be added using the “distutils” bitbake class. Recipes for such modules can be very simple, look at the python-pybluez_0.15.bb recipe for an example (located in openembedded/recipes/python).

The distutils class is described here:

http://docs.openembedded.org/usermanual/usermanual.html#distutils_class

The easiest way to learn is by looking at the other python module recipes.

[Jesse Gilles]

If the full NTPD server is using too much data for you, you can also run “ntpdate” from a cron job. ntpdate will run a one-time sync and exit. Then you can run it as often as you like. This is probably the simplest solution.

You can get the cellular network time from the modem by using AT^SIND as you mentioned, but the “nitz” value is only updated when the modem registers with the network. It doesn’t get continually updated. You would have to read the “nitz” value from AT^SIND on start up and use that value to set the real time clock (AT+CCLK=). Note that the AT^SIND command is specific to the MTSMC-E1 modem.

[Jesse Gilles]

See http://www.multitech.net/developer/products/faxfinder/web-services-api/

The FaxFinder supports an HTTP/XML web API. You’ll need to create an XML document that contains the fax information and the fax itself and then post that to the web server on the FaxFinder using the correct URL.

[Jesse Gilles]

If you are running the 2.1.0 firmware (available on http://www.multitech.com), the limit for the FF130 is 6MB for sending via HTTP/XML. There is currently no way to have the server send multiple XML submissions as one fax.

Keep in mind that the 6MB limit applies to the total amount of data sent in the HTTP request and since the fax itself will be base64 encoded (which increases the size by about 4/3), the effective fax size limit is approximately 4.5MB.

[Jesse Gilles]

I would recommend trying NTP. There is a package included in the base-image called ‘ntpdate’ that allows syncing the clock with an NTP server. This can be called from a cron job to be done periodically.

If you need more continuous synchronization, the NTP daemon (ntpd) will constantly correct the clock. ntpd is provided by the “ntp” package.

[Jesse Gilles]

Hi Chris,

No, sorry, there is no WSDL document for the FaxFinder API — you’ll have to go from the XML examples and documentation as you mentioned.

Jesse

[Jesse Gilles]

The schedule.xml file included with the C# sample sends a PDF. You need to base64 encode the PDF file and embed it into the xml just like the sample file.

[Jesse Gilles]

One way to test the xml versus your code it is to use curl to post the same xml file to the server. Here is the command to send using curl on the command-line:

curl –basic –user admin –data @schedule.xml http://ff230/ffws/v1/ofax

Replace @schedule.xml with @yourfilename and make sure you use the right URL for your server.

[Jesse Gilles]

The supported file formats for sending faxes are PDF, TIFF, Postscript and plain text. This applies to all forms of sending faxes (Web API, Windows client software, T.37, and using the web interface on the server itself).

The first example on the API page under “Scheduling a Fax” shows the example XML posted to the web server to send a fax. Look for the <schedule_fax> element. The attachment must be base64-encoded and included in the XML. The example shown has a very small attachment to keep it simple to display.

If you scroll down farther on the page, you will find descriptions of the XML elements using embedded comments. This shows all of the options that are available, including attachment types:

application/pdf

application/postscript

image/tiff

text/plain

Also, I reformatted all of the XML examples on the API page so they are easier to read.

Jesse

[Author]

Posts