Excited to announce Tickets CAD v4.0.0 (New Video Released)

[Eric Osterberg]

Hello all,

I'm pleased to share that we're one step closer to the release of the next generation of the Tickets CAD platform.

I've uploaded the first in a series of 24+ YouTube videos showcasing the new system's capabilities.

You can see the new video and software preview at: https://youtu.be/_CcKYVW4vUQ

Documentation will be temporarily available at: https://training.ticketscad.com/documentation/

You can expect the released documents to be available on GitHub when the software is released soon.

The software is currently available to those willing to share data, and test the upgrade procedure with my supervision.

There are over 250K new lines of code and numerous extensions to the database schema. 

This release is the equivalent to a team of developers writing new code over many months.

Currently, I am the only person supporting this release. 

I'm looking for volunteers who are committed to contributing their time and resources to testing and documenting the process.

Enjoy!

 -Eric Osterberg

Project Maintainer

[Chuck Killian]

Eric,

I'd be happy to test.

Chuck
WB6YOK

Cheers...

Chuck
WB6YOK
ARRL Life Member

[Darren Deakin (UKDeek)]

I have been using TicketsCAD on and off for quite a few years now, and I have to say Eric that this version 4 looks phenomenal, and I can't wait to get to use it.

Not only does this look really nice, but you also need a massive pat on the back for doing this on your own. Well done!

[Chris Byrd]

The video looks great.   Are you going to have Traccar integration in version 4?

[Eric Osterberg]

Hello Chuck,
Do you have a github account? I can invite you to the private repository.

--
You received this message because you are subscribed to the Google Groups "Open Source CAD" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-source-c...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/open-source-cad/B0E602F8-8598-4A95-8434-2385F93319E1%40xmission.com.

[Eric Osterberg]

Hello Chris,

Short version: not directly in the box today, but there's a workaround that works right now, and a native endpoint is on the near-term backlog. Details below.

## Where we are

TicketsCAD v4 has a multi-provider location framework — a unit or member can have positions coming from APRS, Meshtastic, OwnTracks, DMR-radio GPS, the browser's HTML5 geolocation, and a few others — and the dispatch map picks the freshest source per unit. The architecture has a slot for an OpenGTS / Traccar provider, with config UI and database wiring in place. What it's missing is the HTTP receiver itself — a device pointed at TicketsCAD's `/api/location.php` with Traccar's wire format would get accepted at the URL but nothing would parse the payload yet.

I'm being straight about this because adding a provider that half-works is worse than honestly saying it's not done.

## What works today

The OwnTracks endpoint is fully implemented and in production use. Traccar's HTTP forwarder can emit OwnTracks-shaped JSON, which means you can do this today:

1. Run a Traccar Server instance (or use Traccar Cloud).

2. Configure its HTTP forwarder to send positions to TicketsCAD's OwnTracks endpoint — same JSON shape OwnTracks devices use.

3. TicketsCAD treats those updates as if they came from OwnTracks directly: per-unit breadcrumbs, freshest-source-wins map, history retention, geofence alerts, the whole stack.

It's one extra hop, but every Traccar protocol your devices speak still works on the device → Traccar side. TicketsCAD just sees the OwnTracks output.

If you want, I can put together a one-page how-to for that specific config — happy to walk through it on a call.

## What's planned

A native Traccar / OpenGTS receiver is on the backlog and is a small build — I estimate a couple of hours of focused work. It would handle the standard OpenGTS GPRMC-over-HTTP format and Traccar's "osmand" JSON POST format, both of which Traccar Server can emit out of the box. The hard parts (binding device IDs to dispatcher-visible units, breadcrumb storage, map rendering) are already done by the APRS and OwnTracks paths — this is just adding the protocol parser to the same pipeline.

I haven't put a date on it because the priority depends on actual customer demand. If you're going to deploy with Traccar as your primary location source, please tell me — that bumps it up.

## What I'd ask of you

- Tell me what hardware / device firmware you're planning to point at it. The protocol mix Traccar supports is broad and I want to make sure the native receiver covers the format you actually use.

- Tell me whether the OwnTracks bridge above is good enough for now, or whether you need the native path before you can move forward.

Either way, thanks for the question — these "does it have X" asks are how the roadmap gets prioritized.

73,

Eric Osterberg

N0NKI

TicketsCAD

--

You received this message because you are subscribed to the Google Groups "Open Source CAD" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-source-c...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/open-source-cad/172f7cc6-9ef5-45ee-b33a-a8bceb120f77n%40googlegroups.com.

[Chris Byrd]

Eric,  I think the Owntracks solution will work.   I have tickets cad and traccar running on the same workstation.   If you have time to do the how-to that would be greatly appreciated.

Thanks

Chris

[Eric Osterberg]

Chris,

The OwnTrack integration mentioned above is for the NewUI v4.0.0+ versions. I have not yet released, but expect to have a few beta sites going next week, with a public beta release coming in mid-July.

In the meantime, here are a couple of questions for you. (I'm working Traccar Support into the beta release)

What I'd ask from you this week

So I'm building the right thing:

1. Which Traccar protocol(s) will your devices be using? Traccar Server speaks dozens; the ones I'm planning to support natively are OpenGTS (HTTP GPRMC) and the "osmand" JSON the official Traccar Client app sends. If you'll be using something else (a specific vendor's protocol — Concox, Teltonika, Queclink, etc.) the simplest path is still to run Traccar Server in front and let it translate.
2. Device count — rough order of magnitude. Affects rate-limit defaults

To view this discussion visit https://groups.google.com/d/msgid/open-source-cad/6fec3eac-7b7d-4623-99f8-2e7c5d522116n%40googlegroups.com.

[Chris Byrd]

Current using the Traccar Client app for Iphone and Android.  I would like to integrate the Seed Studio T1000 into traccar but have not found a good way to get the data into it.  I know I have to have a mqtt server but after that I am at a loss on exactly what I need.      We currently use up to 100 devices on a given mission.     

Chris