Advertisement
Guest User

Untitled

a guest
Mar 25th, 2011
154
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.71 KB | None | 0 0
  1. Triffid_Hunter: how goes the hacking?
  2. sliptonic: Some luck with the motherboard side of things. No luck on the extruder at all.
  3. sliptonic: It consistently reports the same value for the thermistor whether the extruder is connected or not.
  4. - 21:03 -
  5. sliptonic: I'm not convinced the two are even talking but I'm not sure how to test it.
  6. Triffid_Hunter: have you ever hacked on things in such a way that involved accessing raw memory?
  7. sliptonic: No. Always willing to learn though.
  8. Triffid_Hunter: would be interesting to write something into the rx struct and see if the reported value changes and stays changed
  9. sliptonic: Is it something you can talk me through?
  10. - 21:11 -
  11. Triffid_Hunter: sliptonic_shop: hm, do you have func.sh stuff working? can you mendel_reset; mendel_talk
  12. sliptonic: I've never heard of it. Where do I find it?
  13. Triffid_Hunter: sliptonic_shop: using linux or mac?
  14. sliptonic: linux
  15. Triffid_Hunter: lovely, well have a look at func.sh in your teacup repo
  16. * sliptonic walks up to the workshop
  17. Triffid_Hunter: put in your arduino serial device, then source ./func.sh in your shell.. that'll let you call all the functions therein like regular commands
  18. - 21:17 -
  19. Triffid_Hunter: the relevant ones here are mendel_readsym and friends which use M253/M254 to read arbitrary memory while it's running
  20. Triffid_Hunter: yep, M253
  21. sliptonic_shop: o.k. I think that's running
  22. Triffid_Hunter: mendel_readsym pulls addresses from mendel.sym, so you can for example mendel_readsym_uint8 mb_head to get the movebuffer head, or mendel_readsym_mb (special command) to dump the whole movebuffer
  23. Triffid_Hunter: or you can pass it an address you've come up with yourself
  24. - 21:25 -
  25. sliptonic_shop: mendel_readsym_uint8 mb_head returns 0
  26. sliptonic_shop: mendel_readsym_mb
  27. sliptonic_shop: dumps everything. cool.
  28. Triffid_Hunter: see what mendel_readsym rx gives you, should be 22 hex chars as it's 11 bytes long
  29. sliptonic_shop: 6900890D890D003C550000
  30. Triffid_Hunter: lose the first 10 (they're packet headers), next four should be a pair of temp readings if we're very lucky
  31. Triffid_Hunter: ah that's interesting, first should be 0x55
  32. Triffid_Hunter: mendel_readsym tx starts with 0x55?
  33. sliptonic_shop: 690000000000003C000055
  34. - 21:32 -
  35. Triffid_Hunter: hm, seems like your intercom isn't running
  36. Triffid_Hunter: post your config
  37. sliptonic_shop: http://pastebin.com/F9dS7ahQ
  38. sliptonic_shop: extruder config too?
  39. Triffid_Hunter: hm config looks ok
  40. - 21:39 -
  41. Triffid_Hunter: I'll have to have a play with it
  42. Triffid_Hunter: maybe put a serial_writechar('!'); in start_send in intercom.c or something so you can see if it's triggering
  43. sliptonic_shop: It won't let me. undefined reference to 'serial_writechar'
  44. Triffid_Hunter: may need to #ifdef HOST #include "serial.h" #endif at the top.. my toolchain complains about implicit declaration but links successfully, are you using the IDE?
  45. sliptonic_shop: yes.
  46. - 21:50 -
  47. sliptonic_shop: my skills are weak: what's wrong with this? http://pastebin.com/vkPspxae
  48. Triffid_Hunter: sliptonic_shop: might not like it before variable declaration, move it down a few lines, just before enable_transmit()
  49. - 22:00 -
  50. sliptonic_shop: o.k. the serial monitor is showing a marching line of exclamation marks. Like it's running start_send repeatedly.
  51. - 22:07 -
  52. Triffid_Hunter: sliptonic_shop: and so it should, about 100 per second?
  53. sliptonic_shop: About 2 or 3 per second.
  54. Triffid_Hunter: ah right, my bad, should be 4 per second
  55. sliptonic_shop: fair enough. I'll buy that.
  56. Triffid_Hunter: still no indication as to why tx wouldn't start with 0x55
  57. - 22:14 -
  58. Triffid_Hunter: hm, ends with 55 though
  59. Triffid_Hunter: wonder if gcc is packing it backwards
  60. Triffid_Hunter: they both have 55 actually, but in different spots
  61. sliptonic_shop: Any reason to believe this is related to my configuration at this point?
  62. Triffid_Hunter: no
  63. sliptonic_shop: was it something working at one time that has potentially changed?
  64. Triffid_Hunter: move your debug marker to the receive packet block, starting at line 167: if (packet_pointer >= sizeof(intercom_packet_t)) { here
  65. Triffid_Hunter: sliptonic_shop: I've never tested this stuff, markus amsler is the one who suggested the protocol change, then significantly fleshed out my skeleton code
  66. - 22:22 -
  67. sliptonic_shop: done. looks about the same 3-4 per second.
  68. Triffid_Hunter: hm so we should be receiving packets
  69. sliptonic_shop: I'm going to need to bail for the evening. I'll be around tomorrow though. Then gone for a week (kids on spring break).
  70. - 22:28 -
  71. sliptonic_shop: If you have any thoughts or want me to test anything, I'll stay logged in. Thanks again for the time.
  72. - 22:35 -
  73. Triffid_Hunter: yw, post on the forum, see if markus amsler has any ideas or comments
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement