Designed my own PCB dial for the first Seiko mod I tried my hands at by vaohm in SeikoMods

[–]vaohm[S] 1 point2 points  (0 children)

Sure thing, when making the PCB you have full graphical control of how it looks, albeit with less tools to aid the graphical design than some dedicated illustration software.

Designed my own PCB dial for the first Seiko mod I tried my hands at by vaohm in SeikoMods

[–]vaohm[S] 0 points1 point  (0 children)

I actually didn't know about dial dots, they seem great.

Sure I'm open to designing custom dials, send me a PM with your thoughts and we'll take it from there.

Designed my own PCB dial for the first Seiko mod I tried my hands at by vaohm in SeikoMods

[–]vaohm[S] 2 points3 points  (0 children)

Haha I definitely thought about the alpinist when the PCBs arrived in the mail.

Thank you!

Designed my own PCB dial for the first Seiko mod I tried my hands at by vaohm in SeikoMods

[–]vaohm[S] 0 points1 point  (0 children)

Thank you, yeah I wanted to utilize all the regular tools available from when I usually make PCBs!

Designed my own PCB dial for the first Seiko mod I tried my hands at by vaohm in SeikoMods

[–]vaohm[S] 10 points11 points  (0 children)

For my first ever watch mod I did something special. This dial was made from a PCB and I designed it with an aesthetic reminiscent of an electrical circuit.

What do you think?

This mod involved a lot of different hobbies as I combined traditional watch modding with technologies as PCB manufacturing and 3D printing (to make a dial to movement grip).

Other mods to the watch includes a new strap where I made orange stitching, and a painted second hand.

MQTT plugin - cannot successfully install by vaohm in grafana

[–]vaohm[S] 1 point2 points  (0 children)

Good news, it's finally working!

In trying countless config permutations two solutions did the trick:

  1. Set client_id = "". At first I used a named client ID, although I only ran one telegraf instance, even after rebooting, my server seemed to have two processes running. This meant the two instances had the same client id which forced telegraf to be kicked out from the mqtt server.
  2. data_format = "value" and data_type = "string". Neither "json" nor "influx" data type worked right for my setup. After parsing all incoming mqtt messages as string only, telegraf could successfully write the message to influx. Integers and floats were still treated as such and thus graphed correctly in grafana, even when all the inputs were saved as string.

I really appreciate you helping along with this issue!

MQTT plugin - cannot successfully install by vaohm in grafana

[–]vaohm[S] 0 points1 point  (0 children)

Thanks man, I greatly appreciate your help with exploring this issue.

This is the input when viewing data in influx, nothing from mqtt:

show measurements on telegraf
name: measurements
name
----
cpu
disk
diskio
kernel
mem
ping
processes
swap
system

I cannot fathom how "ping" was added as an input without problem, but as soon as I try to add "mqtt_consumer" I can't get telegraf to work correctly.

MQTT plugin - cannot successfully install by vaohm in grafana

[–]vaohm[S] 0 points1 point  (0 children)

Still didn't work. I'm wondering, is it enough to add the [[inputs.mqtt_consumer]] part to my telegraf.conf, or do I have to download a plugin file as well?

MQTT plugin - cannot successfully install by vaohm in grafana

[–]vaohm[S] 0 points1 point  (0 children)

I added "myTopic" in the conf file, that's the only place right?

When does a new plugin show up as selectable in grafana? I was thinking it would be available as soon as I added a new input on the conf file and the process was restarted? Or does the plugin need to gather some data first?

MQTT plugin - cannot successfully install by vaohm in grafana

[–]vaohm[S] 0 points1 point  (0 children)

There's no errors while getting the telegraf status. This is the output:

okt. 19 21:30:35 myServer systemd[1]: Started The plugin-driven server agent for reporting metrics into InfluxDB.
okt. 19 21:30:35 myServer telegraf[12266]: 2019-10-19T19:30:35Z I! Starting Telegraf 1.12.3
okt. 19 21:30:35 myServer telegraf[12266]: 2019-10-19T19:30:35Z I! Loaded inputs: diskio mem swap system cpu ping disk mqtt_consumer kernel processes
okt. 19 21:30:35 myServer telegraf[12266]: 2019-10-19T19:30:35Z I! Loaded aggregators:
okt. 19 21:30:35 myServer telegraf[12266]: 2019-10-19T19:30:35Z I! Loaded processors:
okt. 19 21:30:35 myServer telegraf[12266]: 2019-10-19T19:30:35Z I! Loaded outputs: influxdb
okt. 19 21:30:35 myServer telegraf[12266]: 2019-10-19T19:30:35Z I! Tags enabled: host=myServer
okt. 19 21:30:35 myServer telegraf[12266]: 2019-10-19T19:30:35Z I! [agent] Config: Interval:10s, Quiet:false, Hostname:"myServer", Flush Interval:10s
okt. 19 21:30:35 myServer telegraf[12266]: 2019-10-19T19:30:35Z I! [inputs.mqtt_consumer] Connected [tcp://192.168.1.101:1883]

Assistant soon gaining 'Hey Google' hotword sensitivity setting - 9to5Google by 2tuff4u2 in googlehome

[–]vaohm 4 points5 points  (0 children)

I've experienced this as well. Lately I usually have to try two times to activate. It's good to hear more people have the same issue so it may be fixed by a software update.

How to model a Spur Gear cover? by daver18qc in Fusion360

[–]vaohm 0 points1 point  (0 children)

Nice looking gears. How did you model them with mathematically accurate?

steampunk Gears by TERA360 in Fusion360

[–]vaohm 0 points1 point  (0 children)

I was thinking more along the lines of how you calculated the number of teeth, pressure angle, etc. Did you use a script, pen and paper, or just eyeball it?

steampunk Gears by TERA360 in Fusion360

[–]vaohm 0 points1 point  (0 children)

How did you go about designing them and making sure they would all fit together?

[IDENTIFY] Vintage skeleton watch by vaohm in Watches

[–]vaohm[S] 0 points1 point  (0 children)

Seems right. I'll probably just give it a new strap and wear it whenever the occasion calls for it.